richo
hi
just playing around with a small linux network but i'm having trouble exporting nfs from the server.. ( a message about RPC not registered)
in red hat 8 i could use the security dialog box to specify 'other ports' (111.369.2049) to allow nfs to be exported.
unfortunately the firewall dialog box in RH9 doesn't have an 'other ports' input box and i'm not able to work out how to specify those necessary ports
thanks i a
richo
just playing around with a small linux network but i'm having trouble exporting nfs from the server.. ( a message about RPC not registered)
in red hat 8 i could use the security dialog box to specify 'other ports' (111.369.2049) to allow nfs to be exported.
unfortunately the firewall dialog box in RH9 doesn't have an 'other ports' input box and i'm not able to work out how to specify those necessary ports
thanks i a
richo
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Dapper Dan
What do you get when you set to "No firewall?" That should open up every port on the box to let it through.
Edit: Are you using a router? If so, have you checked it to make sure those ports are open?
Edit: Are you using a router? If so, have you checked it to make sure those ports are open?
blackpage
greetings,
I don't know what RedHat exactly does to initiate the firewall, and moreover _what_ firewall it is using. But in case it's iptables then you could "search" along the bootup sequence and find out what firewall script is used to fire up iptables. Start to look for files in the "rcX.d"-directories (whatever your regular runlevel is, normallly "3"->"rc3.d" and check for files like "S99iptables" or whatever; that's under MDK here). Doing so you will find out which file is passed to iptables, containing the firewall rules..
Once you've found it, it should be easy to add 2 apropriate rules (outgoing, incoming) for uncommon ports. If the script's somewhat reasonable it should have the port-familes specified in groups anyway (like $UNPRIVELEGDED=1023:65535, $SSH_PORT=22 or something like that).
In case there is no rule set for NFS (in case NFS is handeled by another "top-level"-gouverning rule) you can still launch some tool like "Firewall Builder" or the aforementioned "Firestarter" (not tested this one though) and examine the structure of their ruleset.
hope this helps
I don't know what RedHat exactly does to initiate the firewall, and moreover _what_ firewall it is using. But in case it's iptables then you could "search" along the bootup sequence and find out what firewall script is used to fire up iptables. Start to look for files in the "rcX.d"-directories (whatever your regular runlevel is, normallly "3"->"rc3.d" and check for files like "S99iptables" or whatever; that's under MDK here). Doing so you will find out which file is passed to iptables, containing the firewall rules..
Once you've found it, it should be easy to add 2 apropriate rules (outgoing, incoming) for uncommon ports. If the script's somewhat reasonable it should have the port-familes specified in groups anyway (like $UNPRIVELEGDED=1023:65535, $SSH_PORT=22 or something like that).
In case there is no rule set for NFS (in case NFS is handeled by another "top-level"-gouverning rule) you can still launch some tool like "Firewall Builder" or the aforementioned "Firestarter" (not tested this one though) and examine the structure of their ruleset.
hope this helps
