WAN interface keeps dropping 1-5 times a day



  • It seems that my WAN interface will drop several times a day, I'm not entirely sure why. I'm using the latest pfsense release. I think it may have to do with DHCP release/renew, I read another forum user had a problem where the DHCP would not accept renew request to the cable modem (Rogers for those of you from Canada).

    Has anyone had a similar problem and know how to fix? Unfortunately I don't have that much time to sit around and wait, probing it with commands.

    Log:

    
    Last 50 system log entries
    May 22 09:57:30	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    May 22 09:57:31	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    May 22 09:57:32	dhclient[13560]: DHCPREQUEST on em1 to 255.255.255.255 port 67
    May 22 09:57:33	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    May 22 09:57:37	apinger: ALARM: WAN(192.168.100.1) *** down ***
    May 22 09:57:37	dhclient[13560]: DHCPREQUEST on em1 to 255.255.255.255 port 67
    May 22 09:57:44	kernel: arpresolve: can't allocate llinfo for 184.1**Sensored for forum post**
    May 22 09:57:47	dhclient[13560]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 1
    May 22 09:57:47	dhclient[13560]: DHCPOFFER from 10.126.25.**
    May 22 09:57:47	dhclient: ARPSEND
    May 22 09:57:47	kernel: arpresolve: can't allocate llinfo for 184.1**Sensored for forum post**
    May 22 09:57:47	apinger: Error while feeding rrdtool: Broken pipe
    May 22 09:57:47	check_reload_status: Reloading filter
    May 22 09:57:49	dhclient: ARPCHECK
    May 22 09:57:49	dhclient[13560]: DHCPREQUEST on em1 to 255.255.255.255 port 67
    May 22 09:57:49	dhclient[13560]: DHCPACK from 10.126.25.**
    May 22 09:57:49	dhclient: BOUND
    May 22 09:57:49	dhclient: Deleting old routes
    May 22 09:57:49	dhclient: Starting add_new_address()
    May 22 09:57:49	dhclient: ifconfig em1 inet 184.175.**.** netmask 255.255.255.224 broadcast 255.255.255.255
    May 22 09:57:49	dhclient: New IP Address (em1): 184.175.**.**
    May 22 09:57:49	dhclient: New Subnet Mask (em1): 255.255.255.224
    May 22 09:57:49	dhclient: New Broadcast Address (em1): 255.255.255.255
    May 22 09:57:49	dhclient: New Routers (em1): 184.1**Sensored for forum post**
    May 22 09:57:49	dhclient: Adding new routes to interface: em1
    May 22 09:57:49	dhclient: /sbin/route add default 184.1**Sensored for forum post**
    May 22 09:57:49	dhclient: Creating resolv.conf
    May 22 09:57:49	check_reload_status: rc.newwanip starting em1
    May 22 09:57:49	dhclient[13560]: bound to 184.175.**.** -- renewal in 302398 seconds.
    May 22 09:57:51	php: : rc.newwanip: Informational is starting em1.
    May 22 09:57:51	php: : rc.newwanip: on (IP address: 184.175.**.**) (interface: wan) (real interface: em1).
    May 22 09:57:51	php: : ROUTING: setting default route to 184.1**Sensored for forum post**
    May 22 09:57:51	apinger: Exiting on signal 15.
    May 22 09:57:52	dnsmasq[37673]: reading /etc/resolv.conf
    May 22 09:57:52	dnsmasq[37673]: using nameserver 206.248.154.**#53
    May 22 09:57:52	dnsmasq[37673]: using nameserver 206.248.154.**#53
    May 22 09:57:52	dnsmasq[37673]: ignoring nameserver 127.0.0.1 - local interface
    May 22 09:57:52	dnsmasq[37673]: ignoring nameserver 127.0.0.1 - local interface
    May 22 09:57:52	apinger: Starting Alarm Pinger, apinger(31072)
    May 22 09:57:57	php: : Resyncing OpenVPN instances for interface WAN.
    May 22 09:57:57	php: : Creating rrd update script
    May 22 09:58:00	ntpdate[9069]: adjust time server 94.23.93.4 offset -0.000706 sec
    May 22 09:58:00	php: : pfSense package system has detected an ip change 192.168.100.10 -> 184.175.**.** ... Restarting packages.
    May 22 09:58:00	check_reload_status: Starting packages
    May 22 09:58:02	php: : Restarting/Starting all packages.
    May 22 09:58:28	apinger: ALARM: WAN(184.1**Sensored for forum post**) *** delay ***
    May 22 09:58:36	apinger: alarm canceled: WAN(184.1**Sensored for forum post**) *** delay ***
    May 22 09:58:38	check_reload_status: Reloading filter
    May 22 09:58:52	apinger: Error while feeding rrdtool: Broken pipe
    May 22 09:59:52	apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    
    


  • I suspect your modem might be losing synchronisation with its upstream equipment and then dropping ethernet carrier which would trigger the exchange in the log extract. You would probably need to discuss this with your ISP. If the synchronisation losses are fairly brief you might be able to get around it by putting a switch between pfSense WAN interface and modem (to hold up ethernet carrier) BUT that won't help if the sync loss is "too long" because apinger will detect loss of response to pings and take the interface down.


  • Netgate Administrator

    2 things I can see here.

    First your modem is one that starts handing out private IPs when it looses link upstream. This is helpful as it allows access to the modem diagnostics but it can cause problems. Some pfSense installs get stuck with the private IP afterwards. That doesn't seem to be happening to you but something to watchout for.

    Second the DHCP server you're talking to is at a private IP address. Is that right?

    However I agree with Wallabybob it looks like just the modem loosing sync and then coming back. Is this something that just started happening?

    Steve


Locked