Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    NFS through pfsense fails but used to work with M0n0wall

    Firewalling
    3
    5
    3503
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rogard last edited by

      Hi,

      I have a problem with a freebsd box (client) trying to reach a nfs server through pfsense.

      I recenlty updated from monowall 1.1 which worked fawlessly with the firewall rules, however after upgrading the nfs share mounts but when doing an "ls" in all of the mounts but one it hangs.

      I have 3 shares mounted /mnt/all /mnt/music and /mnt/movies.
      All shares mount but only /mnt/movies works, the rest hang on a directory listing.

      After a while I get the messages "…server not responding" and the only way to get out is to reboot the client :(

      I have checked the firewall logs and just cannot see anything being blocked.

      I can only think there is something else blocking it?

      This is my frist post here so thanks for stopping to help :)

      1 Reply Last reply Reply Quote 0
      • dotdash
        dotdash last edited by

        Did you see this checkbox on System, Advanced?:
        Disable Firewall Scrub
        Disables the PF scrubbing option which can sometimes interfere with NFS and PPTP traffic.

        Seems like a good place to start.

        1 Reply Last reply Reply Quote 0
        • R
          rogard last edited by

          Thanks for the info.

          I will try that and get back to you.

          1 Reply Last reply Reply Quote 0
          • P
            paulwollner last edited by

            I had the same problem with NFS connections. Weather srub was on or off it exhibited the same behavior. I had to mount my the share using tcp to work around the problem. Rather annoying, but it works.

            1 Reply Last reply Reply Quote 0
            • R
              rogard last edited by

              Found the solution!!!

              After trying the latest version of monowall (i was previously on version 1.1) and it having the same problem I guessed it must be a kernel/driver thing and changed all my network cards from realtek to Intel pro 100/s and it is now working!

              1 Reply Last reply Reply Quote 0
              • First post
                Last post