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

    Gateways showing down after upgrade from 2.2 to 2.3 release

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    26 Posts 11 Posters 16.7k 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.
    • W
      waynemariette
      last edited by

      Home page screen shot

      pfsense1.jpg
      pfsense1.jpg_thumb

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

        What logs do you have from dpinger in your gateways log?

        1 Reply Last reply Reply Quote 0
        • W
          waynemariette
          last edited by

          This is what i saw

          Apr 12 16:22:06 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.160.202 bind_addr x.x.160.202 identifier "GW_WAN "

          Apr 12 16:22:06 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.1.254 bind_addr 192.168.1.89 identifier "ADSLGW "

          Apr 12 16:22:06 dpinger GW_WAN x.x.160.202: sendto error: 65
          Apr 12 16:22:06 dpinger ADSLGW 192.168.1.254: sendto error: 65
          Apr 12 16:22:07 dpinger GW_WAN x.x.160.202: sendto error: 65
          Apr 12 16:22:07 dpinger ADSLGW 192.168.1.254: sendto error: 65
          Apr 12 16:22:07 dpinger ADSLGW 192.168.1.254: sendto error: 65
          Apr 12 16:22:07 dpinger GW_WAN x.x.160.202: sendto error: 65
          Apr 12 16:22:08 dpinger GW_WAN x.x.160.202: sendto error: 65

          Apr 12 16:22:09 dpinger ADSLGW 192.168.1.254: Alarm latency 0us stddev 0us loss 100%
          Apr 12 16:22:09 dpinger GW_WAN x.x.160.202: Alarm latency 0us stddev 0us loss 100%

          Apr 12 17:51:18 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x160.202 bind_addr x.x.160.202 identifier "GW_WAN "

          Apr 12 17:51:18 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.1.254 bind_addr 192.168.1.89 identifier "ADSLGW "

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

            Hm, nothing apparent from that. Mind getting me into the system? Can allow 208.123.73.0/24 WAN-side, and PM me here with access info. Or /msg cmb on Freenode if you're on IRC and we can arrange.

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

              I'm having the same issue! Looks like I'll have to do a fresh install and hope it fixes the dpinger gateway issue!  :(

              I'm also having cpu spikes, that I never had with 2.2.6?

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

                If dpinger isn't running, it's almost certainly because you had advanced monitoring options defined that are now invalid. Go to System>Routing, edit your gateway, and click Save. That'll trigger the input validation showing what's wrong. Reinstall is not going to fix that, it's something in your config.

                If you have a config that didn't work post-upgrade, I'd like to know exactly what was in there for gateway monitoring. I'd like to add config upgrade code to the next release so it fixes invalid configs.

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

                  @cmb:

                  If dpinger isn't running, it's almost certainly because you had advanced monitoring options defined that are now invalid. Go to System>Routing, edit your gateway, and click Save. That'll trigger the input validation showing what's wrong. Reinstall is not going to fix that, it's something in your config.

                  If you have a config that didn't work post-upgrade, I'd like to know exactly what was in there for gateway monitoring. I'd like to add config upgrade code to the next release so it fixes invalid configs.

                  I did a fresh install and had the same problem… however did what you mentioned I had to input the internal IP into the MONITOR IP section and wah-la it works! Thanks for the info, I appreciate what you're doing kind sir, you are a gentleman & a scholar!

                  Cheers!

                  1 Reply Last reply Reply Quote 0
                  • W
                    waynemariette
                    last edited by

                    @cmb:

                    If dpinger isn't running, it's almost certainly because you had advanced monitoring options defined that are now invalid. Go to System>Routing, edit your gateway, and click Save. That'll trigger the input validation showing what's wrong. Reinstall is not going to fix that, it's something in your config.

                    If you have a config that didn't work post-upgrade, I'd like to know exactly what was in there for gateway monitoring. I'd like to add config upgrade code to the next release so it fixes invalid configs.

                    This does not work for me so i hope there is a fix in the code with the next release

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

                      @waynemariette:

                      @cmb:

                      If dpinger isn't running, it's almost certainly because you had advanced monitoring options defined that are now invalid. Go to System>Routing, edit your gateway, and click Save. That'll trigger the input validation showing what's wrong. Reinstall is not going to fix that, it's something in your config.

                      If you have a config that didn't work post-upgrade, I'd like to know exactly what was in there for gateway monitoring. I'd like to add config upgrade code to the next release so it fixes invalid configs.

                      This does not work for me so i hope there is a fix in the code with the next release

                      Worked for me - even gave exact instructions on how to fix in a pretty pink box… For what it is worth my 'loss_interval' was a stupid high number, while the 'time_period' was much less at the default 60000ms. Was not this way pre-update if memory serves me (unfortunately it normally doesn't) ;-s

                      Cheers for the solution cmb!

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

                        @waynemariette:

                        This does not work for me so i hope there is a fix in the code with the next release

                        Can't fix something that has no apparent breakage. See my last post in reply to you.

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

                          good afternoon,

                          I am Brazilian, also I did the update 2.2.6 to 2.3 and also I have a accesses the Internet without connection on my firewall.

                          Iso occurred after the upgrade, already tested this link that shows offline, and is working normally. I changed up the network card machine I use the firewall, and still can not solve this problem.

                          could help?

                          1 Reply Last reply Reply Quote 0
                          • W
                            waynemariette
                            last edited by

                            @cmb:

                            @waynemariette:

                            This does not work for me so i hope there is a fix in the code with the next release

                            Can't fix something that has no apparent breakage. See my last post in reply to you.

                            yeah i sent a pm with the info

                            1 Reply Last reply Reply Quote 0
                            • P
                              phil.davis
                              last edited by

                              I added an issue in redmine https://redmine.pfsense.org/issues/6142
                              I can have a look at it today.

                              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                                @waynemariette:

                                yeah i sent a pm with the info

                                Thanks, I missed that. Yours is fixed. You had two issues, neither of them in pfSense. One, your monitor IP was set to your WAN IP, you need that set to something other than the system's own IP. I set it to 8.8.8.8. Maybe that was different before and you changed it around trying things. Two, your modem (or something upstream of that WAN NIC) drops ICMP packets with no data payload. That's a bug in the NAT on whatever that 192.168.1.254 device is, but we have a data payload config option to work around such problems. I set that to 1 instead of the default 0, and then it started getting replies. You're in good shape now.

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

                                  Has solved the problem of my internet access backup that was as unavailable to available. Marked the gateway monitoring option to off and ran on time. Probably this is a problem caused in the update.

                                  tela01.jpg
                                  tela01.jpg_thumb
                                  Tela02.jpg
                                  Tela02.jpg_thumb

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

                                    @cmb:

                                    Two, your modem (or something upstream of that WAN NIC) drops ICMP packets with no data payload. That's a bug in the NAT on whatever that 192.168.1.254 device is, but we have a data payload config option to work around such problems. I set that to 1 instead of the default 0, and then it started getting replies. You're in good shape now.

                                    Cheers! - Fixed the issue for me on 6 different pfsense users - all using VM in Modem Mode. It appears Virgin Media UK customers need to set a payload to 1 to fix the issue (or use another IP) or else the gateway just drops the packet! - all my other customers on non-VM connections had no issue.

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

                                      Can someone please outline the solution to this issue? I've tried changing the monitor IP on my WAN gateway in the routing menu on the system tab to an OPENDNS IP and it still isn't fixed.

                                      dpinger

                                      send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 208* bind_addr 97* identifier "WAN_DHCP "

                                      I took out the IP addresses above.

                                      Thanks.

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

                                        @PF64:

                                        Can someone please outline the solution to this issue?

                                        here:
                                        https://forum.pfsense.org/index.php?topic=110043.0

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          sapelli
                                          last edited by

                                          Hi,

                                          I think I have the same bug here.
                                          I have 2 gateways. One of those is ok. But the another, simply show "Disconnected"

                                          If I ping throught the gateway "with problems" by de Status/Ping command, there are no problems.

                                          Apr 18 18:02:48 dpinger UNFQ_DHCP 8.8.8.8: Alarm latency 0us stddev 0us loss 100%
                                          Apr 18 18:02:40 dpinger send_interval 5000ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 8000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 192.168.2.100 identifier "UNFQ_DHCP "
                                          Apr 18 18:02:40 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 5000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 192.168.1.2 identifier "BRT_DHCP "

                                          what is wrog?

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            sapelli
                                            last edited by

                                            same problem here.

                                            One gateway is ok, the other one shows "disconnected":

                                            
                                            Apr 18 18:02:48 	dpinger 		UNFQ_DHCP 8.8.8.8: Alarm latency 0us stddev 0us loss 100%
                                            Apr 18 18:02:40 	dpinger 		send_interval 5000ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 8000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 192.168.2.100 identifier "UNFQ_DHCP "
                                            Apr 18 18:02:40 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 5000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 192.168.1.2 identifier "BRT_DHCP " 
                                            
                                            

                                            if I ping, everything is ok:

                                            
                                            PING 8.8.8.8 (8.8.8.8) from 192.168.2.100: 56 data bytes
                                            64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=11.371 ms
                                            64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=11.322 ms
                                            64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=11.649 ms
                                            --- 8.8.8.8 ping statistics ---
                                            3 packets transmitted, 3 packets received, 0.0% packet loss
                                            round-trip min/avg/max/stddev = 11.322/11.447/11.649/0.144 ms
                                            
                                            

                                            what is wrong??

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