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

    NAT bugs

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    5 Posts 3 Posters 2.2k Views
    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.
    • Y
      yon
      last edited by

      2.1-BETA0 (i386)
      built on Sat Nov 3 15:03:48 EDT 2012

      when I update to new version. The NAT to wan not normal work.

      I have setup four WAN, now only main WAN1 NAT normal work, other WAN2-WAN4 not normal.

      eg: I use WAN1  web server (port80) of LAN 80 port is open .  but use WAN2-WAN4  web server  80 port is closed.  it is the same web server.

      If you are interested in free peering for clearnet and dn42,contact me !

      1 Reply Last reply Reply Quote 0
      • Y
        yon
        last edited by

        I have to reback to 2.1-BETA0 (i386) built on Tue Oct 30 10:31:41 EDT 2012  version, it is seem NAT normal just now.

        If you are interested in free peering for clearnet and dn42,contact me !

        1 Reply Last reply Reply Quote 0
        • M
          msi
          last edited by

          Depending on your time available, it would be interesting to find out the exact date where
          NAT got broken for you by trying differently-aged snapshots . This miht make it possible to pin down things to a certain commit in cuase (maybe)

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            This change is the only one in that timeframe that would seem to have any relation.
            https://github.com/bsdperimeter/pfsense/commit/073cb45dd4baa33bea21a76bc20349a055bc4131

            Can you try upgrading again, edit /tmp/rules.debug and remove the "set state-policy if-bound" line, then run:

            pfctl -f /tmp/rules.debug

            and then immediately, before touching anything in the web interface, test to see if that fixes it.

            1 Reply Last reply Reply Quote 0
            • Y
              yon
              last edited by

              I will try, but pfSense-Full-Update-2.1-BETA0-i386-20121106-0041.tgz ipv6 tunnel not work. I will waiting for good version.

              If you are interested in free peering for clearnet and dn42,contact me !

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.