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

    sendto error: 65

    General pfSense Questions
    5
    45
    8.4k
    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.
    • N
      newUser2pfSense
      last edited by newUser2pfSense

      Thanks for that info. I think I found the post:
      https://forum.netgate.com/topic/96923/pfsense-not-recovering-from-wan-failure

      I found a few other posts from other sites as well. I'll change the Protocol timing Timeout and Retry times and see what happens.

      Interestingly, I wonder why it does it only at night or early morning hours?

      1 Reply Last reply Reply Quote 0
      • N
        newUser2pfSense
        last edited by

        So I changed the Protocol timing settings to -
        Timeout: 3600
        Retry: 3

        This didn't work. Any further ideas? Maybe some more favorable settings for the Protocol timing?

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          My last remaining suggestion is to do a packet capture (Diagnostics - Packet Capture) when you're having the problem to see what's really going on. That's how the other DHCP timeout error was discovered. Post the cap here and someone can look at it to help you figure out the real issue.

          1 Reply Last reply Reply Quote 0
          • N
            newUser2pfSense
            last edited by

            While pfSense was reporting the gateway as being offline, I ran a packet capture on the WAN. There were no packets captured. I may have to run a packet capture overnight since it seems to occur more during the early morning hours, after midnight.

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              There should have been something. You left it at the default of WAN, Any protocol, any address?

              1 Reply Last reply Reply Quote 0
              • N
                newUser2pfSense
                last edited by

                There was no captures at all. I made sure the settings were WAN, any protocol and any address.

                1 Reply Last reply Reply Quote 0
                • N
                  newUser2pfSense
                  last edited by newUser2pfSense

                  I don't know if there is going to be a solid solution to this or not. However, seeing that the Protocol timing doesn't seem to be working, it would be nice if there was an installable System Package that would monitor the gateway and do something like release/renew automagically when it goes offline. Just a thought.

                  Troubleshooting continues.

                  1 Reply Last reply Reply Quote 0
                  • N
                    newUser2pfSense
                    last edited by

                    I did a Packet Capture on my WAN but for whatever reason pfSense will not allow me to download it; it's only 130 MB. After trying to download it, pfSense locks up and I have to restart it. If I knew the files path, I could SFTP into pfSense and download it.

                    In the Status > System Logs > DHCP, I've found a lot of the following entries. My WAN is on igb7.

                    dhclient 94735 DHCPDISCOVER on igb7 to 255.255.255.255 port 67 interval 21
                    dhclient 94735 DHCPDISCOVER on igb7 to 255.255.255.255 port 67 interval 18
                    dhclient 94735 DHCPDISCOVER on igb7 to 255.255.255.255 port 67 interval 11
                    dhclient 94735 DHCPDISCOVER on igb7 to 255.255.255.255 port 67 interval 7

                    dhclient 92079 send_packet: Host is down

                    I'm not sure of the relevance of those entries but it seemed to have something to do with what's going on. Maybe not?

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      The last packet capture is in /root/packetcapture.cap

                      1 Reply Last reply Reply Quote 0
                      • N
                        newUser2pfSense
                        last edited by

                        stephenw10...thanks for the path. I was able to download it to my Ubuntu desktop.

                        I've imported the cap file into Wireshark. Now, it's not that I haven't used Wireshark in the past, I mean way past, but in this case for the issue I'm trying to resolve, I'm not sure what I should be looking for.

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          If the pcap shows it is continually broadcasting dhcp requests then it looks like it's something at the other end.

                          If it stops sending after a while you could be hitting the referenced dhclient bug that required the timeout increase. It will still timeout and fail to restart though if so.

                          Steve

                          1 Reply Last reply Reply Quote 0
                          • N
                            newUser2pfSense
                            last edited by newUser2pfSense

                            I wrote a Python program a while ago that goes out and checks for internet connectivity every so many seconds. The program writes to a log file when the internet is unreachable. In this particular instance, the internet became unreachable between 07:06am and 07:07am. I've changed the display times in Wireshark to be able to see the dates and times as we would normally see them.

                            I'm not sure that I'm seeing any entries that says or describes dhcp. I'm looking in the time frame that internet connectivity was lost, just before and after.

                            After a search for dhcp traffic (udp.port == 68), the only entries I'm seeing is:
                            20633 2019-11-29 23:25:15.602566 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f
                            52915 2019-11-30 00:25:15.623471 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f
                            69178 2019-11-30 01:25:15.288596 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f
                            84088 2019-11-30 02:25:15.350459 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f
                            100715 2019-11-30 03:25:15.408722 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f
                            116291 2019-11-30 04:25:15.462404 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f
                            167247 2019-11-30 05:25:15.512665 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f
                            183374 2019-11-30 06:25:15.560319 138.88.12.1 138.88.12.188 DHCP 334 DHCP ACK - Transaction ID 0xa348e56f

                            The times seem to correspond hourly to the Protocol timing Timeout I changed to 3600, 1 hour.

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              Well those TCP ACK packets look to be replies from some external site so I'd suggest the WAN was not down at that moment.
                              I expect to see it start to send DHCP requests if the WAN went down, unless the link actually failed...

                              1 Reply Last reply Reply Quote 0
                              • N
                                newUser2pfSense
                                last edited by newUser2pfSense

                                Sorry, I just changed my reply, up two posts. Those were the only DHCP entries I could find. Sorry for the confusion.

                                1 Reply Last reply Reply Quote 0
                                • N
                                  newUser2pfSense
                                  last edited by newUser2pfSense

                                  I just found this post which may be a temporary answer. I haven't read all of it yet.
                                  https://redmine.pfsense.org/issues/9267

                                  After reading, it looks a little too complicated for me to try ☺ . Looks like I'll have to wait for the next pfSense release for this to be fixed.

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Yup, that's the bug we are referring to. The dhcp client fails to handle that error correctly and instead of simply retrying until it gets a reply it just stops. If the cause of that is the upstream device booting slowly for example then simply increasing the timeout there can get past it. But if there is some bigger delay it can be a problem.

                                    Steve

                                    1 Reply Last reply Reply Quote 0
                                    • N
                                      newUser2pfSense
                                      last edited by

                                      stephenw10...Thanks for that information. It's great to know the issue is being addressed. I just hope as Jim Pingle mentioned in the redmine link, it's not much longer now. I just can't wait for it to be resolved. Thanks for the assistance.

                                      1 Reply Last reply Reply Quote 0
                                      • N
                                        newUser2pfSense
                                        last edited by newUser2pfSense

                                        It just hit me to ask. Since this issue affects the user base of pfSense, have the pfSense developers thought of releasing a fix at least just for this issue before the next version of pfSense is released? This would at least alleviate a lot of restart frustration. Just wondering.

                                        1 Reply Last reply Reply Quote 0
                                        • N
                                          newUser2pfSense
                                          last edited by newUser2pfSense

                                          In System > Update, would anyone happen to know if the fix for the dhclient is in the "Latest 2.4.x development version (2.4.5)", Latest Base System 2.4.5.a.20101222.1312? I would be willing to install just to fix the issue.

                                          When I login to the terminal, would anyone know what the release/renew command is so I don't have to keep restarting?

                                          Thanks.

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            It doesn't look like it made 11 stable so not in 2.4.5 either:
                                            https://github.com/pfsense/FreeBSD-src/commits/RELENG_2_4_5/sbin/dhclient/dhclient.c

                                            Steve

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