04-11-2011
Quote:
Originally Posted by
famasutika
Is there a way to fix the NFS server/client port range so that we could have NFS setup behind a firewall?
What are the best practice for NFS setup behind a firewall?
As i have said in the post i linked for you: there is probably no such way. The best practice is to use some other protocol/means for file sharing.
What is the point of using a firewall between two hosts when you share diskspace between them?
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Just starting to work with unix, wondering if there is any good on-line documentation explaining TCP/UDP ports, how to use them, etc...
Thanks.... (1 Reply)
Discussion started by: eugene_mayo
1 Replies
2. IP Networking
Just wondering if anyone knows of any good on-line documentation on TCP/UDP Ports. Basically i want to know how to check if they are in use, learn how to close them, etc...
Thanks... (5 Replies)
Discussion started by: eugene_mayo
5 Replies
3. UNIX for Advanced & Expert Users
3600 tcp/udp, trap-daemon, text relay-answer
Does anyone know what this service is responsible for, or how significant it is?
Thanks.....James (1 Reply)
Discussion started by: cassj
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in?
Regards,
Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies
5. AIX
Looking at /etc/services on AIX 6.1, I noticed some bizarre port numbers which exceed the 16-bit maximum port number for TCP (i.e. they are higher than 65535.)
sco_printer 70000/tcp sco_spooler # For System V print IPC
sco_s5_port 70001/tcp lpNet_s5_port ... (5 Replies)
Discussion started by: garethr
5 Replies
6. UNIX for Advanced & Expert Users
I use forwarders for a subzone, but TCP 53 is blocked, So does forwarders really need TCP?
If forwaders use UDP, I can't get following scenario to work:
main zone is master, but subzone is forwad. Is it possible?
(On name sever itself, resolution of xx.stub.abc.com worked fine.)
#sub zone... (2 Replies)
Discussion started by: honglus
2 Replies
7. Infrastructure Monitoring
hi guys
My linux server have SNMP configure port by default is 161 (UDP)
now my monitor team - who are using Nagios - say the server are not being monitor
so check netstat -lnu and I see all is OK and snmp service is running fine
what else should I check about this port 161? to see if it is... (0 Replies)
Discussion started by: karlochacon
0 Replies
8. Shell Programming and Scripting
We have open port UDP port 31011, how to verify if port were working or traffic were receive. (2 Replies)
Discussion started by: avtalan
2 Replies
9. IP Networking
i want to kill a tcp connection by killing its pid
with netstat -an i got the tcp ip connection on port 5914
but when i type ps -a or ps-e there is not such process running on port 5914
is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies
10. UNIX for Beginners Questions & Answers
hi,
i would like to create a bash script that check which port in my Linux server are closed (not in use) from a specific range, port range (3000-3010).
the print output need to be only 1 port, and it will be nice if the output will be saved as a variable or in same file.
my code is:
... (2 Replies)
Discussion started by: yossi
2 Replies
LEARN ABOUT DEBIAN
shorewall6-routestopped
SHOREWALL6-ROUTESTO(5) [FIXME: manual] SHOREWALL6-ROUTESTO(5)
NAME
routestopped - The Shorewall6 file that governs what traffic flows through the firewall while it is in 'stopped' state.
SYNOPSIS
/etc/shorewall6/routestopped
DESCRIPTION
This file is used to define the hosts that are accessible when the firewall is stopped or is being stopped. When shorewall6-shell is being
used, the file also determines those hosts that are accessible when the firewall is in the process of being [re]started.
The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in
the alternate specification syntax).
INTERFACE - interface
Interface through which host(s) communicate with the firewall
HOST(S) - [-|address[,address]...]
Optional comma-separated list of IP/subnet addresses. If your kernel and ip6tables include iprange match support, IP address ranges are
also allowed.
If left empty or supplied as "-", 0.0.0.0/0 is assumed.
OPTIONS - [-|option[,option]...]
An optional comma-separated list of options. The order of the options is not important but the list can contain no embedded whitespace.
The currently-supported options are:
routeback
Set up a rule to ACCEPT traffic from these hosts back to themselves. Beginning with Shorewall 4.4.9, this option is automatically
set if routeback is specified in shorewall6-interfaces[1] (5) or if the rules compiler detects that the interface is a bridge.
source
Allow traffic from these hosts to ANY destination. Without this option or the dest option, only traffic from this host to other
listed hosts (and the firewall) is allowed. If source is specified then routeback is redundant.
dest
Allow traffic to these hosts from ANY source. Without this option or the source option, only traffic from this host to other listed
hosts (and the firewall) is allowed. If dest is specified then routeback is redundant.
critical
Allow traffic between the firewall and these hosts throughout '[re]start', 'stop' and 'clear'. Specifying critical on one or more
entries will cause your firewall to be "totally open" for a brief window during each of those operations. Examples of where you
might want to use this are:
o 'Ping' nodes with heartbeat.
o LDAP server(s) if you use LDAP Authentication
o NFS Server if you have an NFS-mounted root filesystem.
Note
The source and dest options work best when used in conjunction with ADMINISABSENTMINDED=Yes in shorewall6.conf[2](5).
EXAMPLE
Example 1:
#INTERFACE HOST(S) OPTIONS
eth2 2002:ce7c:92b4::/64
eth0 2002:ce7c:92b4:1::/64
br0 - routeback
eth3 - source
FILES
/etc/shorewall6/routestopped
SEE ALSO
http://shorewall.net/starting_and_stopping_shorewall.htm
http://shorewall.net/configuration_file_basics.htm#Pairs
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5),
shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcrules(5),
shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)
NOTES
1. shorewall6-interfaces
http://www.shorewall.net/manpages6/shorewall6-interfaces.html
2. shorewall6.conf
http://www.shorewall.net/manpages6/shorewall6.conf.html
[FIXME: source] 06/28/2012 SHOREWALL6-ROUTESTO(5)