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

    Filter needs manual reload to open incoming ports

    Scheduled Pinned Locked Moved 2.1.1 Snapshot Feedback and Problems - RETIRED
    26 Posts 7 Posters 5.0k 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.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by

      Can you clear your DNS cache (if you have one) and try again? It should be on ::56 now. cmb noticed some issues routing to ::55 but ::56 seems to be OK at the moment.

      Remember: Upvote with the šŸ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Well yes, but the files are not there… :D

        
        #Ā  wget -v http://files.pfsense.org/lists/fullbogons-ipv6.txt
        --2014-01-24 18:03:04--Ā  http://files.pfsense.org/lists/fullbogons-ipv6.txt
        Resolving files.pfsense.org (files.pfsense.org)... 2610:1c0:1:25::56, 66.111.2.167
        Connecting to files.pfsense.org (files.pfsense.org)|2610:1c0:1:25::56|:80... connected.
        HTTP request sent, awaiting response... 404 Not Found
        2014-01-24 18:03:05 ERROR 404: Not Found.
        
        

        P.S. Thanks for looking into the problem!Ā  8)

        1 Reply Last reply Reply Quote 0
        • G
          gogol
          last edited by

          @doktornotor:

          Well yes, but the files are not there… :D

          Yes, they are…, oh no they are not..., ah there they are again..., oh my, gone again. :-[

          Edit: I was finally able to download packages by disabling my ipv6 tunnel. Weird. Probably Pfsense was connecting ipv6 which didn't work?

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            @gogol:

            Yes, they are…, oh no they are not..., ah there they are again..., oh my, gone again. :-[
            [/quote]

            Yes, they are, right now.Ā  ;D

            IPv6:

            
            # wget -v http://files.pfsense.org/lists/fullbogons-ipv6.txt
            --2014-01-24 19:29:30--Ā  http://files.pfsense.org/lists/fullbogons-ipv6.txt
            Resolving files.pfsense.org (files.pfsense.org)... 2610:1c0:1:25::57, 66.111.2.167
            Connecting to files.pfsense.org (files.pfsense.org)|2610:1c0:1:25::57|:80... connected.
            HTTP request sent, awaiting response... 200 OK
            Length: 738156 (721K) [text/plain]
            Saving to: `fullbogons-ipv6.txt'
            
            100%[===================================================================================================================================================================================================>] 738,156Ā  Ā  Ā  222K/sĀ   in 3.3s
            
            2014-01-24 19:29:33 (222 KB/s) - `fullbogons-ipv6.txt' saved [738156/738156]
            
            # wget -v --no-check-certificate https://files.pfsense.org/lists/fullbogons-ipv6.txt
            --2014-01-24 19:29:49--Ā  https://files.pfsense.org/lists/fullbogons-ipv6.txt
            Resolving files.pfsense.org (files.pfsense.org)... 2610:1c0:1:25::57, 66.111.2.167
            Connecting to files.pfsense.org (files.pfsense.org)|2610:1c0:1:25::57|:443... failed: Connection refused.
            Connecting to files.pfsense.org (files.pfsense.org)|66.111.2.167|:443... connected.
            WARNING: cannot verify files.pfsense.org's certificate, issued by `/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - G2':
            Ā  Unable to locally verify the issuer's authority.
            HTTP request sent, awaiting response... 200 OK
            Length: 738156 (721K) [text/plain]
            Saving to: `fullbogons-ipv6.txt.1'
            
            100%[===================================================================================================================================================================================================>] 738,156Ā  Ā  Ā  744K/sĀ   in 1.0s
            
            2014-01-24 19:29:50 (744 KB/s) - `fullbogons-ipv6.txt.1' saved [738156/738156]
            
            

            IPv4:

            
            # wget -4 -v http://files.pfsense.org/lists/fullbogons-ipv6.txt
            --2014-01-24 19:31:06--Ā  http://files.pfsense.org/lists/fullbogons-ipv6.txt
            Resolving files.pfsense.org (files.pfsense.org)... 66.111.2.167
            Connecting to files.pfsense.org (files.pfsense.org)|66.111.2.167|:80... connected.
            HTTP request sent, awaiting response... 200 OK
            Length: 738156 (721K) [text/plain]
            Saving to: `fullbogons-ipv6.txt.3'
            
            100%[===================================================================================================================================================================================================>] 738,156Ā  Ā  Ā  523K/sĀ   in 1.4s
            
            # wget -4 -v --no-check-certificate https://files.pfsense.org/lists/fullbogons-ipv6.txt
            --2014-01-24 19:30:41--Ā  https://files.pfsense.org/lists/fullbogons-ipv6.txt
            Resolving files.pfsense.org (files.pfsense.org)... 66.111.2.167
            Connecting to files.pfsense.org (files.pfsense.org)|66.111.2.167|:443... connected.
            WARNING: cannot verify files.pfsense.org's certificate, issued by `/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - G2':
            Ā  Unable to locally verify the issuer's authority.
            HTTP request sent, awaiting response... 200 OK
            Length: 738156 (721K) [text/plain]
            Saving to: `fullbogons-ipv6.txt.2'
            
            100%[===================================================================================================================================================================================================>] 738,156Ā  Ā  Ā  721K/sĀ   in 1.0s
            
            2014-01-24 19:30:43 (721 KB/s) - `fullbogons-ipv6.txt.2' saved [738156/738156]
            
            

            All good now, thanks jimp and else everyone involved!Ā  8) 8) 8)

            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by

              @jimp:

              Try it with Thu Jan 23 17:15:05 EST 2014 or later.

              It was the same issue after the upgrade.

              The filter needed a manual reload and the apinger service needed to be restarted.

              1 Reply Last reply Reply Quote 0
              • ?
                Guest
                last edited by

                Same for.Ā  8.3-RELEASE-p14 FreeBSD 8.3-RELEASE-p14 #1: Sat Jan 25 11:19:23 EST 2014 root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64

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

                  Huh I don`t have this problems since THU snapshot…
                  Today I upgraded to SAT snapshot and all is OK...

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

                    OK disregard above post…
                    I just checked my logs again and here we go:

                    Jan 26 19:48:16 	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN_PPPOE' -c 'service reload ipsecdns' -c 'service reload openvpn WAN_PPPOE' -c 'filter reload' ) exited with status: 255
                    Jan 26 19:48:16 	apinger: Error while starting command form alarm(WAN_PPPOEdelay) on target(IP-WAN_PPPOE)
                    Jan 26 19:48:07 	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN_PPPOE' -c 'service reload ipsecdns' -c 'service reload openvpn WAN_PPPOE' -c 'filter reload' ) exited with status: 255
                    Jan 26 19:48:07 	apinger: Error while starting command form alarm(WAN_PPPOEdelay) on target(IP-WAN_PPPOE)
                    Jan 26 19:48:06 	apinger: alarm canceled: WAN_PPPOE(IP) *** WAN_PPPOEdelay ***
                    Jan 26 19:47:57 	apinger: ALARM: WAN_PPPOE(IP) *** WAN_PPPOEdelay ***
                    
                    1 Reply Last reply Reply Quote 0
                    • M
                      maverick_slo
                      last edited by

                      Tested on:

                      2.1.1-PRERELEASE (i386)
                      built on Mon Jan 27 02:29:41 EST 2014
                      FreeBSD 8.3-RELEASE-p14
                      

                      Still same errors…

                      1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        Next new snap should be OK.
                        https://forum.pfsense.org/index.php/topic,71555.msg393514.html#msg393514

                        Remember: Upvote with the šŸ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

                        1 Reply Last reply Reply Quote 0
                        • A
                          adam65535
                          last edited by

                          Wrong thread….

                          1 Reply Last reply Reply Quote 0
                          • ?
                            Guest
                            last edited by

                            @jimp:

                            Next new snap should be OK.
                            https://forum.pfsense.org/index.php/topic,71555.msg393514.html#msg393514

                            Yep, works!Ā  :D

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