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

    WAN disconnect every few weeks - WAN_DHCP sendto error

    Scheduled Pinned Locked Moved
    General pfSense Questions
    2
    2
    184
    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.
    • F
      FredSmith99
      last edited by

      I was wondering if someone can help with an issue I have quite frequently with pfsense.

      I'm running 2.4.4-RELEASE-p1 (amd64) on an Intel NUC
      It's a VM inside Proxmox but its the only thing running on there
      A USB 3.0 Ethernet Adapter (one of the recommended ones) is used for WAN connectivity to a Virgin Superhub in modem mode.
      Onboard ethernet is used for LAN connectivity. I've got various VLANs configured and a wireless access point.

      The issue is as follows:

      Every 1-3 weeks I lose internet access on all VLANs, both over wireless and wired, even though the Virgin Superhub still has the purple "connected" light on it.
      If I check the WAN interfaces in pfsense it's shown as Up and it has the correct WAN IP details on, however there's actually no connectivity through that interface.

      It's definitely an issue with the WAN rather than the LAN, as I can see the OpenVPN connections in pfsense (which are linked to a specific VLAN) attempting but failing to connect to the outside world)

      The only reliable way I've found that brings the WAN back online is rebooting pfsense first, waiting a minute then rebooting the Virgin Superhub, and then using Reliniqush Lease -> Release -> Renew on the WAN interface shortly after.

      If I just reboot the Superhub + pfsense without renewing the release it doesn't seem to restore WAN connectivity.
      If I renew the release without rebooting both boxes, it also doesn't seem to restore connectivity.

      This is obviously a big issue as if the internet goes down, it takes quite a bit of messing to get it back online. It's also not a wife-friendly process so I really need to figure out what's going on and was hoping that someone else has had the same issue and can assist?

      Some diagnostic info (I'm writing this whilst it's disconnected):

      Under Status --> Gateways:
      WAN_DHCP (default) x.x.x.x y.y.y.y 7.693ms 1.649ms 0.0% Online Interface WAN_DHCP Gateway

      Under Status --> System Logs --> System --> Gateways:

      Mar 27 12:21:50 	dpinger 		VPN_PIA_INTERFACE_BACKUP_VPNV4 y.y.y.y: Alarm latency 0us stddev 0us loss 100%
Mar 27 12:21:50 	dpinger 		VPN_PIA_INTERFACE_VPNV4 z.z.z.z: Alarm latency 0us stddev 0us loss 100%
Mar 27 12:21:48 	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 y.y.y.y bind_addr w.w.w.w identifier "VPN_PIA_INTERFACE_BACKUP_VPNV4 "
Mar 27 12:21:48 	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 z.z.z.z bind_addr v.v.v.v identifier "VPN_PIA_INTERFACE_VPNV4 "
Mar 27 12:21:48 	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.x.x bind_addr x.x.x.x25 identifier "WAN_DHCP "
Mar 27 12:21:46 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 12:21:46 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 12:21:45 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 12:21:45 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:48 	dpinger 		VPN_PIA_INTERFACE_BACKUP_VPNV4 y.y.y.y: Alarm latency 0us stddev 0us loss 100%
Mar 27 11:15:48 	dpinger 		VPN_PIA_INTERFACE_VPNV4 z.z.z.z: Alarm latency 0us stddev 0us loss 100%
Mar 27 11:15:46 	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 y.y.y.y bind_addr w.w.w.w identifier "VPN_PIA_INTERFACE_BACKUP_VPNV4 "
Mar 27 11:15:46 	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 z.z.z.z bind_addr v.v.v.v identifier "VPN_PIA_INTERFACE_VPNV4 "
Mar 27 11:15:46 	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.x.x bind_addr x.x.x.x25 identifier "WAN_DHCP "
Mar 27 11:15:44 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:43 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:43 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:42 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:42 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:41 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:41 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:40 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:40 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:39 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:39 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:38 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:38 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:37 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:37 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:36 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:35 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:35 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:34 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:34 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:33 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:33 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:32 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:32 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 11:15:31 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 65
Mar 27 10:18:30 	dpinger 		WAN_DHCP x.x.x.x: Clear latency 7465us stddev 2968us loss 5%
Mar 27 10:17:30 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:29 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:29 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:28 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:28 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:27 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:27 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:26 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:26 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:17:25 	dpinger 		WAN_DHCP x.x.x.x: sendto error: 64
Mar 27 10:12:59 	dpinger 		WAN_DHCP x.x.x.x: Alarm latency 7728us stddev 1410us loss 22%

      Obviously the issue with the VPN interfaces are expected, but the "WAN_DHCP x.x.x.x: sendto error" are what I'm trying to figure out.

      Any thoughts/suggestions much appreciated.

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

        You should upgrade to 2.4.4p2 when you can.

        Try swapping the WAN and LAN NICs so that WAN is using the on-board real NIC. See if the failure moves to LAN.

        Ultimately there are no recommended USB NICs. If you're lucky you might find one that runs reliably.

        If you do find the LAN now fails after swapping them consider using VLANs and a managed switch instead.

        Steve

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