[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: fedora 11 alpha nfs not listening on udp port 2049?



Robert P. J. Day wrote:
On Wed, 4 Mar 2009, John Summerfield wrote:

... snip ...

I'm running WBEL4 crossed with CentOS4. NFS works. Nothing's listening to port
2049.

I'm also running CentOS4. Same deal.

Likewise on a Debian system at the other end of my VPN.

  ok, here's the situation -- just more adventures in the lab today.
this all started when i couldn't mount an exported directory on an f11
alpha system to an embedded linux system.  so i changed things up
today.

  i now have two f11 alpha systems:

	192.168.1.1 (NFS server)	192.168.1.2 (NFS client)

statically set and connected through a simple switch -- there's no one
else on that 2-node network.  (and, yes, ping works in both
directions.)

  i've exported a simple directory under my home directory,
"showmount -e" on the server verifies it's exported, as it does from
the client as well, so everyone seems to agree that the directory is
NFS-mountable.

  on the client side, i type:

  # mount 192.168.1.1:/home/rpjday/rootfs /mnt

at which point the command hangs for a couple minutes, then returns
with:

  mount.nfs: mount system call failed

hmmmmmm.  on the server side, i decided to drop tcpdump on eth0, and i
got numerous repeats of the following:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
09:19:29.746158 IP 192.168.1.2.55077 > 192.168.1.1.sunrpc: S 2110643412:2110643412(0) win 5840 <mss 1460,sackOK,timestamp 689837822 0,nop,wscale 5>
09:19:29.749703 IP 192.168.1.1.sunrpc > 192.168.1.2.55077: S 2140216678:2140216678(0) ack 2110643413 win 5792 <mss 1460,sackOK,timestamp 4661466 689837822,nop,wscale 6>
09:19:29.746547 IP 192.168.1.2.55077 > 192.168.1.1.sunrpc: . ack 1 win 183 <nop,nop,timestamp 689837822 4661466>
09:19:29.746745 IP 192.168.1.2.55077 > 192.168.1.1.sunrpc: P 1:133(132) ack 1 win 183 <nop,nop,timestamp 689837822 4661466>
09:19:29.746821 IP 192.168.1.1.sunrpc > 192.168.1.2.55077: . ack 133 win 108 <nop,nop,timestamp 4661467 689837822>
09:19:29.751467 IP 192.168.1.1.sunrpc > 192.168.1.2.55077: P 1:33(32) ack 133 win 108 <nop,nop,timestamp 4661472 689837822>
09:19:29.751951 IP 192.168.1.2.55077 > 192.168.1.1.sunrpc: . ack 33 win 183 <nop,nop,timestamp 689837828 4661472>
09:19:29.752144 IP 192.168.1.2.55077 > 192.168.1.1.sunrpc: F 133:133(0) ack 33 win 183 <nop,nop,timestamp 689837828 4661472>
09:19:29.752305 IP 192.168.1.1.sunrpc > 192.168.1.2.55077: F 33:33(0) ack 134 win 108 <nop,nop,timestamp 4661473 689837828>
09:19:29.752541 IP 192.168.1.2.kink > 192.168.1.1.60204: S 2110169891:2110169891(0) win 5840 <mss 1460,sackOK,timestamp 689837828 0,nop,wscale 5>
09:19:29.752681 IP 192.168.1.1.60204 > 192.168.1.2.kink: S 2151425405:2151425405(0) ack 2110169892 win 5792 <mss 1460,sackOK,timestamp 4661473 689837828,nop,wscale 6>
09:19:29.752719 IP 192.168.1.2.55077 > 192.168.1.1.sunrpc: . ack 34 win 183 <nop,nop,timestamp 689837828 4661473>
09:19:29.753245 IP 192.168.1.2.kink > 192.168.1.1.60204: . ack 1 win 183 <nop,nop,timestamp 689837829 4661473>
09:19:29.753372 IP 192.168.1.2.kink > 192.168.1.1.60204: P 1:45(44) ack 1 win 183 <nop,nop,timestamp 689837829 4661473>
09:19:29.753440 IP 192.168.1.1.60204 > 192.168.1.2.kink: . ack 45 win 91 <nop,nop,timestamp 4661474 689837829>
09:19:29.754003 IP 192.168.1.1.60204 > 192.168.1.2.kink: P 1:29(28) ack 45 win 91 <nop,nop,timestamp 4661475 689837829>
09:19:29.754407 IP 192.168.1.2.kink > 192.168.1.1.60204: . ack 29 win 183 <nop,nop,timestamp 689837830 4661475>
09:19:29.763226 IP 192.168.1.2.kink > 192.168.1.1.60204: P 45:185(140) ack 29 win 183 <nop,nop,timestamp 689837839 4661475>
09:19:29.803022 IP 192.168.1.1.60204 > 192.168.1.2.kink: . ack 185 win 108 <nop,nop,timestamp 4661524 689837839>
09:19:29.995560 IP 192.168.1.1.60204 > 192.168.1.2.kink: P 29:97(68) ack 185 win 108 <nop,nop,timestamp 4661716 689837839>
09:19:29.996324 IP 192.168.1.2.kink > 192.168.1.1.60204: F 185:185(0) ack 97 win 183 <nop,nop,timestamp 689838072 4661716>
09:19:29.996561 IP 192.168.1.1.60204 > 192.168.1.2.kink: F 97:97(0) ack 186 win 108 <nop,nop,timestamp 4661717 689838072>
09:19:29.997013 IP 192.168.1.2.kink > 192.168.1.1.60204: . ack 98 win 183 <nop,nop,timestamp 689838073 4661717>
09:19:29.997786 IP 192.168.1.2.58109 > 192.168.1.1.sunrpc: S 2108454518:2108454518(0) win 5840 <mss 1460,sackOK,timestamp 689838073 0,nop,wscale 5>
09:19:29.997903 IP 192.168.1.1.sunrpc > 192.168.1.2.58109: S 2143912611:2143912611(0) ack 2108454519 win 5792 <mss 1460,sackOK,timestamp 4661718 689838073,nop,wscale 6>
... etc etc ...

  those similar blocks repeat several times until the mount command
gives up as above.  multiple attempts produce exactly the same result.

  thoughts?

What's kink?
Could you
1. Try mounting the export on the server. This should work.
2. Run the tcpdump again, using -nn
3. What's talking on port "kink?"
4. Explicitly try proto=tcp and proto=udp

Remember I said I don't have anything listening on port 2049?
00:21:23.648338 IP 192.168.9.4.2049
That's my server. I'm supposing it's a kernel module that's talking, and that lsof can't see it.



rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================



--

Cheers
John

-- spambait
1aaaaaaa coco merseine nu  Z1aaaaaaa coco merseine nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]