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 REDHAT
rpc.statd
rpc.statd(8) System Manager's Manual rpc.statd(8)
NAME
rpc.statd - NSM status monitor
SYNOPSIS
/sbin/rpc.statd [-F] [-d] [-?] [-n name ] [-o port ] [-p port ] [-V]
DESCRIPTION
The rpc.statd server implements the NSM (Network Status Monitor) RPC protocol. This service is somewhat misnomed, since it doesn't actu-
ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is used by the NFS file
locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots.
Operation
For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/statd/sm. When starting, it iterates
through these files and notifies the peer rpc.statd on those machines.
OPTIONS
-F By default, rpc.statd forks and puts itself in the background when started. The -F argument tells it to remain in the foreground.
This option is mainly for debugging purposes.
-d By default, rpc.statd sends logging messages via syslog(3) to system log. The -d argument forces it to log verbose output to stderr
instead. This option is mainly for debugging purposes, and may only be used in conjunction with the -F parameter.
-n, --name name
specify a name for rpc.statd to use as the local hostname. By default, rpc.statd will call gethostname(2) to get the local hostname.
Specifying a local hostname may be useful for machines with more than one interfaces.
-o, --outgoing-port port
specify a port for rpc.statd to send outgoing status requests from. By default, rpc.statd will ask portmap(8) to assign it a port
number. As of this writing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be
useful when implementing a firewall.
-p, --port port
specify a port for rpc.statd to listen on. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writ-
ing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing
a firewall.
-? Causes rpc.statd to print out command-line help and exit.
-V Causes rpc.statd to print out version information and exit.
TCP_WRAPPERS SUPPORT
This rpc.statd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.statd if they should be allowed
to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow:
statd: .bar.com
You have to use the daemon name statd for the daemon name (even if the binary has a different name).
For further information please have a look at the tcpd(8) and hosts_access(5) manual pages.
FILES
/var/lib/nfs/statd/sm/state
/var/lib/nfs/statd/sm/*
/var/lib/nfs/statd/sm.bak/*
SEE ALSO
rpc.nfsd(8), portmap(8)
AUTHORS
Jeff Uphoff <juphoff@transmeta.com>
Olaf Kirch <okir@monad.swb.de>
H.J. Lu <hjl@gnu.org>
Lon Hohberger <hohberger@missioncriticallinux.com>
08 Mar 2001 rpc.statd(8)