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

    PfSense Gateway Timing Out (Error 64-65)

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 3.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.
    • SoarinS
      Soarin
      last edited by

      Hello,

      A friend of mine is having problems with his pfSense, every 10-30 minutes the gateway goes down and all connections time out, I've disabled hardware checksum and TCP Offloading (and enabled it), the pfSense is a fresh install with no packages installed, simple port forwards for game servers, websites, SQL, and mail server.

      However, the pfSense is under HyperV, with a direct line going into the firewall, it is on a static IP.
      My friend has tried legacy drivers and default NICs for HyperV, no difference in the problem.

      HyperV Version: 6.3.9600.16384
      Physical NICL: QLogic BCM5709C Gigabit Ethernet (Default R610 NIC)
      pfSense Version: 2.4.1-RELEASE
      pfSense VM: gen1
      Other VMs: gen2
      Windows Server 2012 Datacenter edtion R2/ Hyper-V (2012)

      Any help is greatly appreciated

      Oct 29 16:15:15  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:15  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:16  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:16  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:17  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:17  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:18  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:18  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:19  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:19  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:20  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:20  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:21  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:21  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:22  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:23  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:23  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:24  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:24  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:25  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:25  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:26  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:26  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:27  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:27  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:28  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:28  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:29  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:29  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:30  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:30  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:31  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:32  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:32  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:33  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:33  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:34  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:34  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:35  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:35  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:36  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:36  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:37  dpinger   WAN 185.194.168.1: sendto error: 64  
Oct 29 16:15:37  dpinger   GW_LAN 192.168.1.1: sendto error: 65  
Oct 29 16:15:37  dpinger   WAN 185.194.168.1: sendto error: 65  
Oct 29 16:15:52  dpinger   GW_LAN 192.168.1.1: Alarm latency 138us stddev 84us loss 21%  
Oct 29 16:16:37  dpinger   WAN 185.194.168.1: Clear latency 1846us stddev 5356us loss 5%  
Oct 29 16:16:54  dpinger   GW_LAN 192.168.1.1: Clear latency 155us stddev 170us loss 5%  
Oct 29 19:32:47  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.1 bind_addr 192.168.1.1 identifier "GW_LAN "  
Oct 29 19:32:47  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 185.194.168.1 bind_addr 185.194.168.16 identifier "WAN " 

      I hardly understand pfSense but it was love at first sight.

      1 Reply Last reply Reply Quote 0
      • D
        Dafoxx
        last edited by

        One of our Cisco switche's ports were both giveing Tx errors out (bad packets), Annoyingly simply reconnecting seemed to fix this…

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