Problem with NFS routing (Version 2.0)



  • Hi,

    a pfsense Version 2.0 is the default gw of some of our our Hosts. One of the hosts has an NFS mount, which is routed through the pfsense. The mount itself works good, but when i open an (for example) logfile on the mountpoint and start searching in the logfile, my ping timings go crazy.

    Example (without searching in the logfile):

    ping 10.10.110.42
    PING 10.10.110.42 (10.10.110.42) 56(84) bytes of data.
    64 bytes from 10.10.110.42: icmp_seq=1 ttl=62 time=0.352 ms
    64 bytes from 10.10.110.42: icmp_seq=2 ttl=62 time=0.209 ms
    64 bytes from 10.10.110.42: icmp_seq=3 ttl=62 time=0.264 ms
    64 bytes from 10.10.110.42: icmp_seq=4 ttl=62 time=0.270 ms
    64 bytes from 10.10.110.42: icmp_seq=5 ttl=62 time=0.296 ms
    64 bytes from 10.10.110.42: icmp_seq=6 ttl=62 time=0.229 ms
    […]

    if i now start a search:

    ping 10.10.110.42
    PING 10.10.110.42 (10.10.110.42) 56(84) bytes of data.
    64 bytes from 10.10.110.42: icmp_seq=1 ttl=62 time=1.44 ms
    64 bytes from 10.10.110.42: icmp_seq=2 ttl=62 time=0.319 ms
    64 bytes from 10.10.110.42: icmp_seq=3 ttl=62 time=0.219 ms
    64 bytes from 10.10.110.42: icmp_seq=4 ttl=62 time=0.254 ms
    64 bytes from 10.10.110.42: icmp_seq=5 ttl=62 time=0.279 ms
    64 bytes from 10.10.110.42: icmp_seq=6 ttl=62 time=0.304 ms
    64 bytes from 10.10.110.42: icmp_seq=7 ttl=62 time=9.83 ms
    64 bytes from 10.10.110.42: icmp_seq=8 ttl=62 time=24.1 ms
    64 bytes from 10.10.110.42: icmp_seq=10 ttl=62 time=22.3 ms
    64 bytes from 10.10.110.42: icmp_seq=11 ttl=62 time=0.252 ms
    64 bytes from 10.10.110.42: icmp_seq=12 ttl=62 time=11.4 ms
    64 bytes from 10.10.110.42: icmp_seq=13 ttl=62 time=36.1 ms
    64 bytes from 10.10.110.42: icmp_seq=14 ttl=62 time=33.4 ms
    64 bytes from 10.10.110.42: icmp_seq=15 ttl=62 time=25.3 ms
    64 bytes from 10.10.110.42: icmp_seq=16 ttl=62 time=27.0 ms
    64 bytes from 10.10.110.42: icmp_seq=17 ttl=62 time=35.6 ms
    64 bytes from 10.10.110.42: icmp_seq=18 ttl=62 time=30.9 ms
    64 bytes from 10.10.110.42: icmp_seq=19 ttl=62 time=32.9 ms
    64 bytes from 10.10.110.42: icmp_seq=20 ttl=62 time=37.5 ms
    64 bytes from 10.10.110.42: icmp_seq=21 ttl=62 time=14.5 ms
    64 bytes from 10.10.110.42: icmp_seq=22 ttl=62 time=0.249 ms
    64 bytes from 10.10.110.42: icmp_seq=23 ttl=62 time=0.284 ms
    64 bytes from 10.10.110.42: icmp_seq=24 ttl=62 time=0.236 ms
    64 bytes from 10.10.110.42: icmp_seq=25 ttl=62 time=0.266 ms
    64 bytes from 10.10.110.42: icmp_seq=26 ttl=62 time=0.293 ms
    64 bytes from 10.10.110.42: icmp_seq=27 ttl=62 time=33.2 ms
    64 bytes from 10.10.110.42: icmp_seq=28 ttl=62 time=31.4 ms
    64 bytes from 10.10.110.42: icmp_seq=29 ttl=62 time=29.2 ms
    […]

    this connection is routed through the pfsense.

    It is no Problem to send a big File (about 3GB) via sftp to the server (also through the pfsense). The ping timings then stay normal.

    Also other Servers with this pfsense as default gw get the crazy ping timings, when i search the log on the NFS mount.

    I do not see any errors on the Interfaces of the pfsense.

    Maybe one of you guys can help me.

    Best regards and thanks in advanced
    Sebastian


Locked