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

    2nd WAN doesn't respond after today's update

    2.0-RC Snapshot Feedback and Problems - RETIRED
    4
    12
    4.1k
    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.
    • M
      mastermindpro
      last edited by

      Installed the Oct. 20th snap on one of my pfSense boxes that has two WAN's.  After the update, the OPT1 interface stopped responding to pings from the outside world.  Also, all traffic NAT'd in on that interface is not responding.  The interface is handling traffic, however, but only that which comes from the LAN.

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        Wrong snapshot please upgrade to a newer one if you can find.

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

          Guess I have to wait until tomorrow, then.

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

            Installed the Wednesday night snapshot, and the problem is not resolved.  Additionally, I have more problems:

            There were error(s) loading the rules: pfctl: Duplicate signature for BeOS 5.1 : File exists
            pfctl: Duplicate signature for BeOS 5.0-5.1 : File exists
            pfctl: Duplicate signature for BeOS 5.0 : File exists
            pfctl: Duplicate signature for BeOS 5.0 : File exists
            pfctl: Duplicate signature for OS/400 VR4 : File exists
            pfctl: Duplicate signature for OS/400 VR4 : File exists
            pfctl: Duplicate signature for OS/400 VR5 : File exists
            pfctl: Duplicate signature for OS/400 VR5 : File exists
            pfctl: Duplicate signature for OS/400 V4R5 CF67032: File exists
            pfctl: Duplicate signature for OS/400 V4R5 CF67032: File exists
            pfctl: Duplicate signature for ULTRIX 4.5 : File exists
            pfctl: Duplicate signature for ULTRIX 4.5 : File exists
            pfctl: Duplicate signature for QNX  : File exists
            pfctl: Duplicate signature for QNX  : File exists
            pfctl: Duplicate signature for Novell NetWare 5.0: File exists
            pfctl: Duplicate signature for Novell NetWare 5.0: File exists
            pfctl: Duplicate signature for Novell IntranetWare 4.11: File exists
            pfctl: Duplicate signature for Novell IntranetWare 4.11: File exists
            pfctl: Duplicate signature for Novell BorderManager : File exists
            pfctl: Duplicate signature for Novell BorderManager : File exists
            pfctl: Duplicate signature for Novell Netware 6: File exists
            pfctl: Duplicate signature for Novell Netware 6: File exists
            pfctl: Duplicate signature for SCO UnixWare 7.1: File exists
            pfctl: Duplicate signature for SCO UnixWare 7.1: File exists
            pfctl: Duplicate signature for SCO UnixWare 7.1: File exists
            pfctl: Duplicate signature for SCO UnixWare 7.1: File exists
            pfctl: Duplicate signature for SCO OpenServer 5.0: File exists
            pfctl: Duplicate signature for SCO OpenServer 5.0: File exists
            pfctl: Duplicate signature for DOS WATTCP 1.05: File exists
            pfctl: Duplicate signature for DOS WATTCP 1.05: File exists
            pfctl: Duplicate signature for DOS WATTCP 1.05Arachne: File exists The line in question reads [ Duplicate signature for BeOS 5.1 ]:

            There were error(s) loading the rules: pfctl: Duplicate signature for NeXTSTEP 3.3 : File exists
            pfctl: Duplicate signature for BeOS 5.0 : File exists
            pfctl: Duplicate signature for BeOS 5.1 : File exists
            pfctl: Duplicate signature for BeOS 5.0-5.1 : File exists
            pfctl: Duplicate signature for BeOS 5.0 : File exists
            pfctl: DIOCADDRULE: Device busy The line in question reads [ Duplicate signature for NeXTSTEP 3.3 ]:

            There were error(s) loading the rules: /tmp/rules.debug:148: cannot define table bogons: Device busy
            pfctl: Syntax error in config file: pf rules not loaded The line in question reads [148]: table <bogons>persist file "/etc/bogons"

            There were error(s) loading the rules: pfctl: Duplicate signature for HP-UX 11.11 : File exists
            pfctl: Duplicate signature for HP-UX B.11.00 A: File exists
            pfctl: Duplicate signature for HP-UX B.11.00 A: File exists
            pfctl: Duplicate signature for RISC OS 3.70 4.10: File exists
            pfctl: Duplicate signature for RISC OS 3.70 4.10: File exists
            pfctl: Duplicate signature for BSD/OS 3.1 : File exists
            pfctl: Duplicate signature for BSD/OS 3.1 : File exists
            pfctl: Duplicate signature for BSD/OS 4.0 : File exists
            pfctl: Duplicate signature for BSD/OS 4.1 : File exists
            pfctl: Duplicate signature for BSD/OS 4.2 : File exists
            pfctl: Duplicate signature for BSD/OS 4.3 : File exists
            pfctl: Duplicate signature for BSD/OS 4.0-4.3 : File exists
            pfctl: Duplicate signature for BSD/OS 4.0 : File exists
            pfctl: Duplicate signature for BSD/OS 4.1 : File exists
            pfctl: Duplicate signature for BSD/OS 4.2 : File exists
            pfctl: Duplicate signature for BSD/OS 4.3 : File exists
            pfctl: Duplicate signature for BSD/OS 4.0-4.3 : File exists
            pfctl: Duplicate signature for NewtonOS 2.1 : File exists
            pfctl: Duplicate signature for NewtonOS 2.1 : File exists
            pfctl: Duplicate signature for NeXTSTEP 3.3 : File exists
            pfctl: Duplicate signature for NeXTSTEP 3.3 : File exists
            pfctl: Duplicate signature for NeXTSTEP 3.3 : File exists
            /tmp/rules.debug:148: cannot define table bogons: Device busy
            pfctl: Syntax error in config file: pf rules not loaded The line in question reads [ Duplicate signature for HP-UX 11.11 ]:

            There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy The line in question reads [ DIOCADDRULE]:</bogons>

            1 Reply Last reply Reply Quote 0
            • E
              eri--
              last edited by

              Can you post your config?

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

                Sure, here's the firewall rules.  Let me know if you need something else.

                filter-config-20101021093912.txt

                1 Reply Last reply Reply Quote 0
                • E
                  eri--
                  last edited by

                  I do need the other sections as well. Remove all the other sensitive data.

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

                    Got it.  Here you go.

                    config-20101021095416.txt

                    1 Reply Last reply Reply Quote 0
                    • X
                      xudus
                      last edited by

                      Got the same problem here too. 2nd WAN got a static IP, plus AON and PBR is on. Egress traffic works as expected, however ingress is just plain dead.

                      TIA Dave

                      2.0-BETA4 (i386)
                      built on Wed Oct 20 20:31:52 EDT 2010
                      FreeBSD 8.1-RELEASE-p1

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

                        Was this fixed in a newer snapshot?  I see multiple people with multiple problems with the snaps over the last few days.

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

                          To answer my own question, this is not fixed with the snapshot built today.  Any idea what's going on here?

                          1 Reply Last reply Reply Quote 0
                          • D
                            databeestje
                            last edited by

                            I can confirm it

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