Date: Fri, 31 Jan 2003 11:39:02 -0800 From: Tim Kientzle <kientzle@acm.org> To: current@freebsd.org Subject: NFS over TCP doesn't umount Message-ID: <3E3AD0D6.8010205@acm.org>
next in thread | raw e-mail | index | archive | help
Tinkering with NFS over TCP through a firewall,
I ran across the following:
# mount_nfs -3TN server:/path /mnt
Generates the following traffic:
UDP exchanges with server port 111 (rpcbind)
TCP exchanges with server ports 1023 and 2049
That is, if your firewall allows UDP 111 through,
then NFS over TCP can mount and function through it.
But, umount is a different story:
# umount /mnt
Bad MNT RPC: RPC: Timed out
The following tcpdump trace shows that the umount
is using UDP transport, even though the filesystem was
mounted using TCP transport:
11:21:42.811506 client.1124 > server.2049: F 129:129(0) ack 125 win 1
7396 (DF)
11:21:42.811912 client.962 > server.111: udp 56
11:21:42.812446 server.2049 > client.1124: . ack 130 win 33176 (DF)
11:21:42.812596 server.2049 > client.1124: F 125:125(0) ack 130 win 3
3176 (DF)
11:21:42.812614 client.1124 > server.2049: . ack 126 win 17395 (DF)
11:21:42.813195 server.111 > client.962: udp 28
11:21:42.813336 client.961 > server.1023: udp 128
11:21:45.817521 client.961 > server.1023: udp 128
11:21:48.827565 client.961 > server.1023: udp 128
11:21:51.837612 client.961 > server.1023: udp 128
11:21:54.847657 client.961 > server.1023: udp 128
11:21:57.857700 client.961 > server.1023: udp 128
11:22:00.867747 client.961 > server.1023: udp 128
This is reproducible with both a 4.3-RELEASE client
and a recent -CURRENT client. The server is running
4.3-RELEASE, if it's relevant.
Tim Kientzle
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E3AD0D6.8010205>