Gateway keep going offline after one minute



  • I am so frustrated with this issue and cannot seem to get help anywhere. My default gateway keeps going offline after one minute ( that’s after the WAN id disable and the enabled). I have tried reinstalling PFSense a total of around ten time, thinking that I did something wrong during the installation with no luck. Am I  the only person with this issue, the strange thing is that no one can answer or help.

    Also for some reason internet connection is enabled for the same short period if I use the diagnostic ping, but then it goes back down.

    I find it hard to believe that I am the only person with this problem.

    Last 50 General Log Entries. (Maximum 50)
    Mar 12 19:48:40 check_reload_status Restarting OpenVPN tunnels/interfaces
    Mar 12 19:48:40 check_reload_status Reloading filter
    Mar 12 21:00:06 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 21:09:48 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 21:24:30 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 21:32:09 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 21:41:47 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 22:09:48 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 22:32:30 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 22:39:48 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 22:57:30 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 23:09:48 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 23:32:31 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 23:44:13 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 12 23:57:31 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 00:28:31 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 00:39:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 01:09:37 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 02:09:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 04:09:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 04:39:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 04:45:48 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 06:09:31 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 06:32:37 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 06:39:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 06:58:51 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 07:09:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 07:18:17 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 07:39:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 07:48:32 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 08:18:48 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 08:32:53 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 08:49:04 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 09:28:51 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 09:39:49 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 09:49:37 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 10:19:53 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 10:31:55 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 06:47:30 root rc.update_bogons.sh is beginning the update cycle.
    Mar 13 06:49:02 root Could not download https://files.pfsense.org/lists/fullbogons-ipv4.txt
    Mar 13 06:49:02 root Could not extract fullbogons-ipv4.txt
    Mar 13 06:50:34 root Could not download https://files.pfsense.org/lists/fullbogons-ipv6.txt
    Mar 13 06:50:34 root Could not extract fullbogons-ipv6.txt
    Mar 13 06:50:34 root rc.update_bogons.sh is starting up.
    Mar 13 06:50:34 root rc.update_bogons.sh is sleeping for 30859
    Mar 13 11:00:00 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 11:20:25 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 11:28:40 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 11:54:53 kernel arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!
    Mar 13 12:19:37 php-fpm 41310 /index.php: Successful login for user 'admin' from: 192.168.1.161

    Last 50 Gateways Log Entries. (Maximum 50)
    Mar 12 15:43:26 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:26 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:27 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:27 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:28 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:28 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:29 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:29 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:30 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:30 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:31 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:31 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:32 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:32 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:33 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:33 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:34 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:34 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:35 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:35 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:36 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:36 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:37 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:37 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:38 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:38 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:39 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:39 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:40 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:40 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:41 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:41 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:42 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:42 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:43 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:43 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:44 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:44 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:45 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:45 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:46 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:46 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:47 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:47 dpinger WANGW 104...6: sendto error: 64
    Mar 12 15:43:54 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 104...6 bind_addr 104...3 identifier "WANGW "
    Mar 12 15:44:25 dpinger WANGW 104...6: Alarm latency 1073us stddev 1701us loss 22%
    Mar 12 15:48:31 dpinger WANGW 104...6: Clear latency 985us stddev 1995us loss 13%
    Mar 12 15:48:40 dpinger WANGW 104...6: Alarm latency 1034us stddev 2097us loss 22%
    Mar 13 08:25:01 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 104...6 bind_addr 104...3 identifier "WANGW "
    Mar 13 08:25:04 dpinger WANGW 104...6: Alarm latency 0us stddev 0us loss 100%

    Last 50 Routing Log Entries. (Maximum 50)
    Mar 12 15:15:15 radvd 67395 no auto-selected prefix on interface rl0, disabling advertisements
    Mar 12 15:15:15 radvd 67395 resuming normal operation
    Mar 12 15:19:31 radvd 67395 attempting to reread config file
    Mar 12 15:19:31 radvd 67395 no auto-selected prefix on interface rl0, disabling advertisements
    Mar 12 15:19:31 radvd 67395 resuming normal operation
    Mar 12 15:22:31 radvd 67395 attempting to reread config file
    Mar 12 15:22:31 radvd 67395 no auto-selected prefix on interface rl0, disabling advertisements
    Mar 12 15:22:31 radvd 67395 resuming normal operation
    Mar 12 15:42:45 radvd 67395 Exiting, sigterm or sigint received.
    Mar 12 15:42:45 radvd 67395 sending stop adverts
    Mar 12 15:42:45 radvd 67395 removing /var/run/radvd.pid
    Mar 12 15:43:50 radvd 41418 version 1.9.1 started
    Mar 12 15:43:50 radvd 41418 no auto-selected prefix on interface rl0, disabling advertisements
    Mar 12 15:43:52 radvd 41776 attempting to reread config file
    Mar 12 15:43:52 radvd 41776 no auto-selected prefix on interface rl0, disabling advertisements
    Mar 12 15:43:52 radvd 41776 resuming normal operation
    Mar 13 08:20:47 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:20:47 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:21:51 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:21:51 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:22:02 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:22:02 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:22:05 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:22:05 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:22:08 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:22:08 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:22:34 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:22:34 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:22:53 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:22:53 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:25:22 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:25:22 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:25:25 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:25:25 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:25:41 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:25:41 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:25:54 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:25:54 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:25:58 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:25:58 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:26:02 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:26:02 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:26:41 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:26:41 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:27:42 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:27:42 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:28:45 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2
    Mar 13 08:28:45 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:29:07 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:ae6e
    Mar 13 08:29:07 radvd 41776 our AdvLinkMTU on rl0 doesn't agree with fe80::cab3:73ff:fe22:afc2

    Also I have removed all the firewall settings.



  • i havent come across anyone who's gateway goes offline after 1 minute

    please show configuration screenshots / show system logs / gateway logs / general system info (type of nics & installed packages)



  • Mar 12 21:00:06  kernel      arp: c8:b3:73:22:af:c3 is using my IP address 104...3 on fxp0!

    IP address conflict?  Which of your clients has the MAC c8:b3:73:22:af:c3?



  • Reinstalling won't do anything, you are doing something wrong.

    Ya, I don't like like that USING MY IP msg, it suggests the DHCP is seeing MAC conflict.  Find who's got that c8:b3:73:22:af:c3.  As impossible as it should be, I've seen 2 NICs with the same MAC.

    Do you have a flat subnet?  hooking up multiple switches fail-safe style without switches having fail-safe capability can cause weird stuff like this.



  • As impossible as it should be, I've seen 2 NICs with the same MAC.

    While supposedly unique, some manufactures have been known to recycle MAC addresses.  There's also the possibility of locally assigned MACs and many consumer routers can clone a MAC.  However, as long as they're not on the same local network, duplicate MACs are not a problem.