weird NFS problem ?

From: Aziz Kezzou (french.linuxian_at_gmail.com)
Date: 05/26/05

  • Next message: Muhammad Reza: "Re: two ISP connections, three nics, and a NAT"
    Date: Wed, 25 May 2005 21:32:27 -0400
    To: freebsd-net <freebsd-net@freebsd.org>, freebsd-hackers <freebsd-hackers@freebsd.org>
    
    

    Hi all,
    I am experiencing a weird problem while mounting nfs files.

    Configuration :
    - NFS client : FreeBSD 5.3 running on QEMU, IP = 192.168.0.2
    - NFS server : FC3, the host, IP = 192.168.0.1

    Firewalling:
    absolutely everything is authorized from 192.168.0.2 on 192.168.0.1

    Problem :
    some UDP ports on 192.168.0.2 are unreachable without any reason I know of ?!!

    Command:
    arwen# mount -t nfs 192.168.0.1:/home/akezzou/pfe/cvs /mnt/host
    [udp] 192.168.0.1:/home/akezzou/pfe/cvs: RPCPROG_MNT: RPC: Timed out
    [udp] 192.168.0.1:/home/akezzou/pfe/cvs: RPCPROG_MNT: RPC: Timed out

    Tcpdump output :
    [root@eowyn bin]# /usr/sbin/tcpdump -i tun0
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on tun0, link-type EN10MB (Ethernet), capture size 96 bytes
    21:04:51.560121 IP 192.168.0.2.675 > 192.168.0.1.sunrpc: UDP, length 56
    21:04:51.561806 arp who-has 192.168.0.2 tell 192.168.0.1
    21:04:51.564088 arp reply 192.168.0.2 is-at 52:54:00:12:34:56
    21:04:51.564118 IP 192.168.0.1.sunrpc > 192.168.0.2.675: UDP, length 28
    21:04:51.570214 IP 192.168.0.2.1117046890 > 192.168.0.1.nfs: 40 null
    21:04:51.570368 IP 192.168.0.1.nfs > 192.168.0.2.1117046890: reply ok 24 null
    21:04:51.575164 IP 192.168.0.2.954 > 192.168.0.1.sunrpc: UDP, length 56
    21:04:51.576338 IP 192.168.0.1.sunrpc > 192.168.0.2.954: UDP, length 28
    21:04:51.581561 IP 192.168.0.2.621 > 192.168.0.1.650: UDP, length 108
    21:05:04.528129 IP 192.168.0.1.650 > 192.168.0.2.621: UDP, length 68
    21:05:04.530154 IP 192.168.0.2 > 192.168.0.1: icmp 36: 192.168.0.2 udp
    port 62 1 unreachable
    21:06:01.613750 IP 192.168.0.2.1006 > 192.168.0.1.sunrpc: UDP, length 56
    21:06:01.616083 IP 192.168.0.1.sunrpc > 192.168.0.2.1006: UDP, length 28
    21:06:01.622336 IP 192.168.0.2.1117192688 > 192.168.0.1.nfs: 40 null
    21:06:01.626734 IP 192.168.0.1.nfs > 192.168.0.2.1117192688: reply ok 24 null
    21:06:01.637315 IP 192.168.0.2.843 > 192.168.0.1.sunrpc: UDP, length 56
    21:06:01.641915 IP 192.168.0.1.sunrpc > 192.168.0.2.843: UDP, length 28
    21:06:01.646715 IP 192.168.0.2.792 > 192.168.0.1.650: UDP, length 108
    21:06:06.614378 arp who-has 192.168.0.2 tell 192.168.0.1
    21:06:06.615755 arp reply 192.168.0.2 is-at 52:54:00:12:34:56
    21:06:16.682754 IP 192.168.0.1.650 > 192.168.0.2.792: UDP, length 68
    21:06:16.684556 IP 192.168.0.2 > 192.168.0.1: icmp 36: 192.168.0.2 udp
    port 79 2 unreachable
    21:07:11.659900 IP 192.168.0.2.764 > 192.168.0.1.sunrpc: UDP, length 56
    21:07:11.662292 IP 192.168.0.1.sunrpc > 192.168.0.2.764: UDP, length 28
    21:07:11.668228 IP 192.168.0.2.1117147813 > 192.168.0.1.nfs: 40 null
    21:07:11.671916 IP 192.168.0.1.nfs > 192.168.0.2.1117147813: reply ok 24 null
    21:07:11.676171 IP 192.168.0.2.693 > 192.168.0.1.sunrpc: UDP, length 56
    21:07:11.683197 IP 192.168.0.1.sunrpc > 192.168.0.2.693: UDP, length 28
    21:07:11.688238 IP 192.168.0.2.958 > 192.168.0.1.650: UDP, length 108
    21:07:16.660731 arp who-has 192.168.0.2 tell 192.168.0.1
    21:07:16.661668 arp reply 192.168.0.2 is-at 52:54:00:12:34:56

     
    Any hint is greatly appreciated.
    thanks,
    -aziz
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"


  • Next message: Muhammad Reza: "Re: two ISP connections, three nics, and a NAT"

    Relevant Pages

    • weird NFS problem ?
      ... some UDP ports on 192.168.0.2 are unreachable without any reason I know of ?!! ... Tcpdump output: ... 21:04:51.561806 arp who-has 192.168.0.2 tell 192.168.0.1 ... port 62 1 unreachable ...
      (freebsd-hackers)
    • OT: Supermicro IPMI 2.0 boards
      ... We ordered a whole batch of servers which have the IPMI 2.0 board (I am ... 00:30:48:12:34:56 being swapped from port to port and switch to switch. ... 13:37:37.023915 arp who-has 192.168.1.113 tell 192.168.1.113 ...
      (freebsd-questions)
    • Re: Excessive network traffic -
      ... John Summerfield wrote: ... Looking at port 53 produced nothing in half an hour with only tcpdump running so I assume wireshark or iptraf was causing the dns messages. ... 14:48:00.580934 arp who-has 75.105.105.75 tell 75.105.105.1 ...
      (Fedora)
    • Re: Blocking UDP ports
      ... I saw a lot of 'closed' UDP ports. ... > One cannot tell if a UDP port is blocked or closed. ... > to a UDP connection to a port that is not open is an ICMP error ... > That's why a traceroute using udp packets may not indicate when it ...
      (linux.redhat)
    • Re: Firewall-1 NG and NMAP
      ... when nmap tests to see if a UDP port is open, it sends a UDP packet to the ... packet like with a TCP scan. ... nmap assumes that there must be something listening. ... > reports a lot of open udp ports. ...
      (comp.security.firewalls)