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

    Gateway bugs cause no internet dpinger sendto error 65

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 1 Posters 2.6k 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.
    • T
      totalimpact
      last edited by

      Getting the following in system gateway log, and have really limited internet, usually none. Was on 2.3.2 when it failed, just upgraded to 2.3.4.p1, same. Have tried ifconfig down/up on the interface. I can 100% access the pfsense page remotely over the WAN, but workstations cannot get out. I disabled gateway monitoring on that interface, no change, rebooted, same. All gateways show status online, and can ping them at 0ms.

      This is a Netgate SG-2440.

      
      Jul 27 20:04:08	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 fe80::224:14ff:fe63:a5d9%igb0 bind_addr fe80::208:a2ff:fe0a:aefe%igb0 identifier "WAN1COX_DHCP6 "
      Jul 27 20:08:33	dpinger		WAN1CoxGW 187.187.187.177: sendto error: 65
      Jul 27 20:08:33	dpinger		WAN1CoxGW 187.187.187.177: sendto error: 65
      Jul 27 20:08:34	dpinger		WAN1CoxGW 187.187.187.177: sendto error: 65
      Jul 27 20:08:34	dpinger		WAN1CoxGW 187.187.187.177: sendto error: 65
      Jul 27 20:08:35	dpinger		WAN1CoxGW 187.187.187.177: sendto error: 65
      
      
      1 Reply Last reply Reply Quote 0
      • T
        totalimpact
        last edited by

        Well…. turned out some user put a Tp-link managed switch in somewhere that was using 192.168.0.1, which by chance is the same as pfsense LAN. I dont know why, but this did not show up in the system log until hours later, and then it was in there every 20 seconds:

        Jul 27 11:15:40	kernel		arp: 84:16:f9:b9:9e:e9 is using my IP address 192.168.0.1 on igb1!
        Jul 27 11:15:35	kernel		arp: 84:16:f9:b9:9e:e9 is using my IP address 192.168.0.1 on igb1!
        Jul 27 11:15:03	kernel		arp: 84:16:f9:b9:9e:e9 is using my IP address 192.168.0.1 on igb1!
        Jul 27 11:14:46	kernel		arp: 84:16:f9:b9:9e:e9 is using my IP address 192.168.0.1 on igb1!
        
        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.