DHCP on WAN suddenly started failing



  • Short version: I have pfsense configured behind my work's VPN appliance at home.  Pfsense DHCP's an address on its WAN interface from the VPN device.  This has been working fine for a long, long time. After upgrading to pfsense 2.0.2 a few days ago, we had a power outage this morning and all my gear rebooted when power came back.  After this reboot, pfsense will no longer successfully DHCP from the VPN device (although other devices will DHPC from that VPN device just fine).

    More details:

    I've been running pfsense for quite a long time (a few years?) and it's been great; many thanks for a wonderful product.

    My pfsense box is an old Dell desktop with 2 NICs in it.  It sits behind my work VPN hardware appliance (a Cisco 891 VPN router).  The upstream/WAN link from pfsense DHCPs from the Cisco 891.  This has been working fine for a long, long time.

    After the power outage-induced reboot, I couldn't get upstream anymore from the network behind pfsense.  However, if I unplugged pfsense from the 891 and plugged a laptop directly into the 891, the laptop is able to DHCP just fine and then get out to the greater VPN/intranet/internet.

    After doing some troubleshooting with pfsense, I can see that it is not DHCP'ing successfully from the 891 (see logs, below).  If I configure the pfsense WAN interface to be static and give it an IP address in the right range and the correct default gateway route, then everything in works fine (i.e., I can continue using the network behind my pfsense box as I have for a long time).

    Here's the system logs from pfsense unsuccessfully trying to DHCP to the Cisco 891 (read from the bottom to the top):

    Dec 31 11:28:34 dhclient[23198]: bound: renewal in 2640 seconds.
    Dec 31 11:28:34 dhclient: Deleting old routes
    Dec 31 11:28:34 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:28:34 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:28:23 dhclient: New Routers (sk0): 10.0.2.1
    Dec 31 11:28:22 dhclient: New Routers (sk0): 10.0.2.1
    Dec 31 11:28:22 dhclient: New Broadcast Address (sk0): 10.0.2.255
    Dec 31 11:28:22 dhclient: New Subnet Mask (sk0): 255.255.255.0
    Dec 31 11:28:22 dhclient: New IP Address (sk0): 10.0.2.3
    Dec 31 11:28:22 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:28:22 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:28:22 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:28:22 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:28:22 dhclient: ifconfig sk0 inet 10.0.2.3 netmask 255.255.255.0 broadcast 10.0.2.255
    Dec 31 11:28:22 dhclient: Starting add_new_address()
    Dec 31 11:28:22 dhclient: TIMEOUT
    Dec 31 11:28:22 dhclient[23198]: Trying recorded lease 10.0.2.3
    Dec 31 11:28:22 dhclient[23198]: No DHCPOFFERS received.
    Dec 31 11:28:12 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 10
    Dec 31 11:28:04 sshd[58005]: Accepted keyboard-interactive/pam for admin from 192.168.10.8 port 51430 ssh2
    Dec 31 11:28:02 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 10
    Dec 31 11:27:54 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 8
    Dec 31 11:27:44 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 10
    Dec 31 11:27:34 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 10
    Dec 31 11:27:28 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 6
    Dec 31 11:27:23 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 5
    Dec 31 11:27:21 dhclient[23198]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 2
    Dec 31 11:27:13 dhclient[23198]: DHCPREQUEST on sk0 to 255.255.255.255 port 67
    Dec 31 11:27:09 dhclient[23198]: DHCPREQUEST on sk0 to 255.255.255.255 port 67
    Dec 31 11:27:09 dhclient[23198]: DHCPREQUEST on sk0 to 255.255.255.255 port 67
    Dec 31 11:27:09 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:27:09 miniupnpd[46228]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=15): No route to host
    Dec 31 11:27:09 kernel: sk0: link state changed to UP
    Dec 31 11:27:09 dhclient: PREINIT
    Dec 31 11:27:07 kernel: sk0: link state changed to DOWN
    Dec 31 11:27:07 php: : HOTPLUG: Configuring interface wan

    Note that 10.0.2.3 is the last IP address that it was able to DHCP, so it seems to fail to DHCP and then say "heck with it, let's try the last DHCP lease IP address that I had before: 10.0.2.3".

    But that doesn't even seem to work.  Specifically, if I ssh in to the pfsense box and look at the ifconfig for sk0 (my WAN link) from the shell prompt, its IPv4 address is not set:

    sk0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    options=8000b <rxcsum,txcsum,vlan_mtu,linkstate>ether 00:26:5a:05:aa:82
    inet6 fe80::226:5aff:fe05:aa82%sk0 prefixlen 64 scopeid 0x1
    nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
    status: active

    (and, of course, while it's trying to DHCP, if I "ifconfig sk0", it shows the IPv4 IP/inet address as 0.0.0.0 (which seems normal).)

    As I mentioned above, I can physically plug other devices into the Cisco 891 and they will DHCP successfully (e.g., they'll get 10.0.2.4, 10.0.2.5, …etc.).  So the 891's DHCP capabilities seem to be working ok.  This implies that it may be pfsense that is failing to DHCP properly.

    I can certainly run with my pfsense WAN link set to a static IP address, but that's a little less than optimal (e.g., in case the IT guys ever decide to change the DHCP address range on my Cisco 891).

    Did something change in 2.0.2 that might cause the DHCP on my WAN link to fail, perchance?  Even this would seem like an odd explanation, because after I upgraded to 2.0.2, I rebooted my pfsense box and all was still working fine...</full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,linkstate></up,broadcast,running,simplex,multicast>



  • Same WAN DHCP woes here - started soon after the upgrade to 2.0.2 as well.  I have been running PfSense for years and this specific rig for 140+ days before I updated to 2.0.2 and never an issue.

    Two times in the last 3 weeks my WAN connection has gone dead and scanning the logs points to DHCP issues.  First time I rebooted and just now simply reset the WAN to DHCP on the console and it fixed it.  At the time of failure I find this in the log…

    Jan 18 09:53:47	php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf em3 > /tmp/em3_output > /tmp/em3_error_output' returned exit code '15', the output was ''
    Jan 18 09:53:47	dhclient[37235]: exiting.
    Jan 18 09:53:47	dhclient[37235]: exiting.
    Jan 18 09:53:47	dhclient[37235]: connection closed
    Jan 18 09:53:47	dhclient[37235]: connection closed
    Jan 18 09:53:47	php: : DEVD Ethernet detached event for wan
    Jan 18 09:53:47	kernel: em3: link state changed to UP
    Jan 18 09:53:47	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:46	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:46	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:46	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:46	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:46	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:46	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:46	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:45	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:45	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:45	check_reload_status: Linkup starting em3
    Jan 18 09:53:45	kernel: em3: link state changed to DOWN
    Jan 18 09:53:45	kernel: arpresolve: can't allocate llinfo for 50.129.xxx.x
    Jan 18 09:53:45	dhclient[36947]: DHCPREQUEST on em3 to 255.255.255.255 port 67
    

    Not sure if going back to 2.0.1 or grabbing a non stable update makes the most sense.  Having an unreliable connection on this box is killing me in the interim…



  • DHCP Client is exiting soon after it starts. Perhaps it is reporting why. Please post the output of pfSense shell command```
    cat /tmp/em3*



  • Bump.  Does anyone have any thoughts on the original problem posted in this thread?  (it seems like jwu42's problem is different than mine)



  • I had a similar problem in 2.0.2 but I do not have the logs anymore as I rolled back to 2.0.1. What would happen is that when the lease expired from my cable modem it would not renew until I went into the gui and renewed it myself.

    It's a shame, because 2.0.2 fixed the upnp issue I had.. but I can't use it because a reliable dhcp lease is more important.


  • Rebel Alliance Developer Netgate



  • I'm trying out this guy:
    pfSense-Full-Update-2.0.3-PRERELEASE-i386-20130129-0807.tgz

    I'll let you know if I have any issues. Thanks.



  • FWIW, I don't see anything in https://github.com/bsdperimeter/pfsense/commits/RELENG_2_0?page=1 that would seem to indicate that something has changed with regards to the WAN DHCP client.

    Also FWIW, I notice that if I run dhclient myself, it's just not getting anything back:

    
    [2.0.2-RELEASE][admin@pfsense.squyres.com]/(8): dhclient -c /var/etc/dhclient_wan.conf -d sk0
    dhclient: PREINIT
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 1
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 1
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 2
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 3
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 13
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 14
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 12
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.
    
    

    This tends to imply that it's dhclient itself – or perhaps the driver for my NIC -- that is borked. Not pfsense core/proper.

    Is there a way to tell if dhclient or the NIC driver has been updated since 2.0.1?  My IP interface is sk0, if that helps identify the driver (sorry, I don't know anything about the BSD OS...).



  • I have the same problem as before in 2.0.3. my link loses the ip address and my internet is down until I renew the IP through the gui.

    Below is a tail of my system.logs
    Jan 31 02:56:11 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:12 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:12 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:14 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:14 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:14 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:15 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:15 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1
    Jan 31 02:56:16 pfsense kernel: arpresolve: can't allocate llinfo for 72.208.8.1

    Note that my internet went down several hours later, at 08:14. I don't think these are significant but i'll let you decide.. If you'd like me to get any other logs please provide me with the log location.

    Thanks
    Matt


  • Rebel Alliance Developer Netgate

    Start with the rest of the system log, especially at/near the time of the actual failure.



  • Well I'm pretty sure the time of failure was 8 am and the snippet I pasted you was the output from tail, thus the most recent. However given that it is the first thing in the morning I may be mistaken about it actually working.

    Here are some other noteworthy logs I saw:
    Jan 31 02:52:23 pfsense kernel: rl1: link state changed to DOWN
    Jan 31 02:52:23 pfsense check_reload_status: Linkup starting rl1

    Jan 31 02:52:24 pfsense php: : DEVD Ethernet attached event for wan
    Jan 31 02:52:24 pfsense php: : HOTPLUG: Configuring interface wan

    Jan 31 02:52:24 pfsense check_reload_status: Reloading filter

    Jan 31 02:52:25 pfsense kernel: rl1: link state changed to UP
    Jan 31 02:52:25 pfsense dhclient: PREINIT

    Jan 31 02:52:25 pfsense dhclient[21193]: DHCPREQUEST on rl1 to 255.255.255.255 port 67
    Jan 31 02:52:26 pfsense dhclient[21193]: DHCPREQUEST on rl1 to 255.255.255.255 port 67

    Jan 31 02:52:30 pfsense dhclient[21193]: DHCPREQUEST on rl1 to 255.255.255.255 port 67
    Jan 31 02:52:30 pfsense php: : DEVD Ethernet detached event for wan
    Jan 31 02:52:30 pfsense dhclient[21722]: connection closed
    Jan 31 02:52:30 pfsense dhclient[21722]: connection closed
    Jan 31 02:52:30 pfsense dhclient[21722]: exiting.
    Jan 31 02:52:30 pfsense dhclient[21722]: exiting.
    Jan 31 02:52:30 pfsense php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf rl1 > /tmp/rl1_output > /tmp/rl1_error_output' returned exit code '15', the output was ''

    Note that I have omitted the lines from arpresolve only.



  • And here are the details from ifconfig, so you can see which interface is what:
    rl0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=8 <vlan_mtu>ether 00:01:c0:03:dc:77
            inet 192.168.0.254 netmask 0xffffff00 broadcast 192.168.0.255
            inet6 fe80::201:c0ff:fe03:dc77%rl0 prefixlen 64 scopeid 0x1
            nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    rl1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=8 <vlan_mtu>ether 00:01:c0:03:d3:dc
            inet6 fe80::201:c0ff:fe03:d3dc%rl1 prefixlen 64 scopeid 0x2
            inet 72.208.12.250 netmask 0xfffff800 broadcast 72.208.15.255
            nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active</full-duplex></performnud,accept_rtadv></vlan_mtu></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></vlan_mtu></up,broadcast,running,simplex,multicast>


  • Rebel Alliance Developer Netgate

    Odd that if you look at the log, it appears that the devd events are reversed for what they should be.

    Jan 31 02:52:23 pfsense kernel: rl1: link state changed to DOWN
    Jan 31 02:52:24 pfsense php: : DEVD Ethernet attached event for wan
    Jan 31 02:52:24 pfsense php: : HOTPLUG: Configuring interface wan
    Jan 31 02:52:25 pfsense kernel: rl1: link state changed to UP
    Jan 31 02:52:30 pfsense php: : DEVD Ethernet detached event for wan
    

    Though when I test that on my VM with em NICs, it gets it right.

    Can you watch the log and see if when you unplug the NIC it does the same thing each time?

    When you unplug it should log an "ethernet detached" event.
    When you plug it in, it should log an "ethernet attached" event.



  • It's happening to me as well on 2.0.3 (just as it is on 2.1). Log below is in reverse time order:

    Feb 3 11:19:21 kernel: arpresolve: can't allocate llinfo for 75.131.112.1 
    Feb 3 11:19:15 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:15 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:15 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:15 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:15 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:15 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:14 kernel: em0: link state changed to UP 
    Feb 3 11:19:14 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf em0 > /tmp/em0_output > /tmp/em0_error_output' returned exit code '15', the output was '' 
    Feb 3 11:19:14 dhclient[40067]: exiting. 
    Feb 3 11:19:14 dhclient[40067]: exiting. 
    Feb 3 11:19:14 dhclient[40067]: connection closed 
    Feb 3 11:19:14 dhclient[40067]: connection closed 
    Feb 3 11:19:14 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:19:12 kernel: em0: link state changed to DOWN 
    Feb 3 11:19:12 check_reload_status: Linkup starting em0 
    Feb 3 11:19:12 dhclient[39818]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:19:10 kernel: arpresolve: can't allocate llinfo for 75.131.112.1 
    Feb 3 11:19:10 dhclient[39818]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:19:10 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:10 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:10 dhclient: PREINIT 
    Feb 3 11:19:10 php: : HOTPLUG: Configuring interface wan 
    Feb 3 11:19:10 php: : DEVD Ethernet attached event for wan 
    
    


  • I suspect @swinn:

    
    Feb 3 11:19:14 kernel: em0: link state changed to UP 
    
    

    should have triggered a restart of dhclient. There is no sign of that happening, but that might be because you didn't show enough of the log file.

    Because the previous incarnation of dhclient exited and dhclient (apparently) wasn't restarted it appears there is no running dhclient to issue a DHCP request for configuration.

    MAYBE there are too many link state transitions in too short a period.



  • Here is the log from the time the interface went down to the time I logged in and pressed the renew dhcp button. This is in reverse order again:

    Feb 3 14:21:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:21:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:21:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:21:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:13:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:13:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:13:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:13:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:13:53 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 14:13:53 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 14:06:47 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:06:47 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:06:47 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:06:47 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:06:46 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 14:06:46 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 14:05:29 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:57:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:57:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:57:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:57:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:56:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:52 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:52 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:52 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:52 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:12 miniupnpd[53901]: upnp_event_send: send(): Broken pipe 
    Feb 3 13:52:12 miniupnpd[53901]: upnp_event_send: send(): Broken pipe 
    Feb 3 13:52:12 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:12 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:12 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:52:12 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:51:03 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 13:51:03 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 13:51:02 kernel: em0: link state changed to UP 
    Feb 3 13:51:02 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf em0 > /tmp/em0_output > /tmp/em0_error_output' returned exit code '15', the output was '' 
    Feb 3 13:51:02 dhclient[50586]: exiting. 
    Feb 3 13:51:02 dhclient[50586]: exiting. 
    Feb 3 13:51:02 dhclient[50586]: connection closed 
    Feb 3 13:51:02 dhclient[50586]: connection closed 
    Feb 3 13:51:02 php: : DEVD Ethernet detached event for wan 
    Feb 3 13:51:00 dhclient[50273]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 13:50:59 kernel: em0: link state changed to DOWN 
    Feb 3 13:50:59 check_reload_status: Linkup starting em0 
    Feb 3 13:50:59 dhclient[50273]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 13:50:58 dhclient[50273]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 13:50:57 dhclient[50273]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 13:50:57 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 13:50:57 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 13:50:57 dhclient: PREINIT 
    Feb 3 13:50:57 php: : HOTPLUG: Configuring interface wan 
    Feb 3 13:50:57 php: : DEVD Ethernet attached event for wan 
    Feb 3 13:50:55 kernel: em0: link state changed to UP 
    Feb 3 13:50:55 check_reload_status: Linkup starting em0 
    Feb 3 13:50:44 php: : DEVD Ethernet detached event for wan 
    Feb 3 13:50:42 kernel: em0: link state changed to DOWN 
    Feb 3 13:50:42 check_reload_status: Linkup starting em0 
    Feb 3 13:47:20 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:47:20 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:47:20 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:47:20 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:38:45 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:38:45 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:38:45 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:38:45 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:38:45 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 13:38:45 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 13:38:33 dnsmasq[37297]: read /etc/hosts - 21 addresses 
    Feb 3 13:32:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:32:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:32:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:32:53 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:32:53 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 13:32:53 miniupnpd[53901]: upnp_event_recv: recv(): Connection reset by peer 
    Feb 3 13:18:16 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:18:16 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:18:16 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:18:16 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:11:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:11:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:11:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:11:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:02:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:02:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:02:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 13:02:04 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:47:55 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:47:55 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:47:55 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:47:55 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:41:35 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:41:35 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:41:35 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:41:35 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:36:14 dnsmasq[37297]: read /etc/hosts - 21 addresses 
    Feb 3 12:32:50 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:32:50 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:32:50 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:32:50 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerSpamhausEDrop does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerBluetackDShield does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerBluetackHijacked does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerZeusBlocklist does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerDShieldAttackers does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerSpamhausDrop does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerTopSpammers does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerEurope does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerAsia does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: pfBlockerAfrica does not need updated. 
    Feb 3 12:30:54 php: : /etc/rc.update_urltables: Starting URL table alias updates 
    Feb 3 12:30:00 php: : /etc/rc.update_urltables: Sleeping for 54 seconds. 
    Feb 3 12:30:00 php: : /etc/rc.update_urltables: Starting up. 
    Feb 3 12:28:19 miniupnpd[53901]: HTTP Connection closed unexpectedly 
    Feb 3 12:28:19 miniupnpd[53901]: HTTP Connection closed unexpectedly 
    Feb 3 12:27:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:27:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:27:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 12:27:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:47:31 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:47:31 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:47:30 kernel: em0: link state changed to UP 
    Feb 3 11:47:30 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf em0 > /tmp/em0_output > /tmp/em0_error_output' returned exit code '15', the output was '' 
    Feb 3 11:47:30 dhclient[21788]: exiting. 
    Feb 3 11:47:30 dhclient[21788]: exiting. 
    Feb 3 11:47:30 dhclient[21788]: connection closed 
    Feb 3 11:47:30 dhclient[21788]: connection closed 
    Feb 3 11:47:30 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:47:29 dhclient[21773]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:47:28 kernel: em0: link state changed to DOWN 
    Feb 3 11:47:28 check_reload_status: Linkup starting em0 
    Feb 3 11:47:27 dhclient[21773]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:47:26 dhclient[21773]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:47:26 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:47:26 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:47:26 dhclient: PREINIT 
    Feb 3 11:47:26 php: : HOTPLUG: Configuring interface wan 
    Feb 3 11:47:26 php: : DEVD Ethernet attached event for wan 
    Feb 3 11:47:23 kernel: em0: link state changed to UP 
    Feb 3 11:47:23 check_reload_status: Linkup starting em0 
    Feb 3 11:47:12 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:47:10 kernel: em0: link state changed to DOWN 
    Feb 3 11:47:10 check_reload_status: Linkup starting em0 
    Feb 3 11:36:38 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:36:38 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:36:38 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:36:38 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:36:38 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:36:38 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:30:21 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:30:21 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:30:20 kernel: em0: link state changed to UP 
    Feb 3 11:30:20 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf em0 > /tmp/em0_output > /tmp/em0_error_output' returned exit code '15', the output was '' 
    Feb 3 11:30:20 dhclient[32235]: exiting. 
    Feb 3 11:30:20 dhclient[32235]: exiting. 
    Feb 3 11:30:20 dhclient[32235]: connection closed 
    Feb 3 11:30:20 dhclient[32235]: connection closed 
    Feb 3 11:30:20 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:30:19 dhclient[31973]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:30:18 kernel: em0: link state changed to DOWN 
    Feb 3 11:30:18 check_reload_status: Linkup starting em0 
    Feb 3 11:30:17 dhclient[31973]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:30:16 dhclient[31973]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:30:16 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:30:16 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:30:16 dhclient: PREINIT 
    Feb 3 11:30:16 php: : HOTPLUG: Configuring interface wan 
    Feb 3 11:30:16 php: : DEVD Ethernet attached event for wan 
    Feb 3 11:30:13 kernel: em0: link state changed to UP 
    Feb 3 11:30:13 check_reload_status: Linkup starting em0 
    Feb 3 11:30:03 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:30:00 kernel: em0: link state changed to DOWN 
    Feb 3 11:30:00 check_reload_status: Linkup starting em0 
    Feb 3 11:25:20 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:24:16 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:23:12 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:22:35 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:22:32 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:22:32 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:22:32 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:22:32 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:22:32 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:22:32 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:22:31 dnsmasq[37297]: read /etc/hosts - 20 addresses 
    Feb 3 11:22:08 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:21:47 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:21:04 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:21:03 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:21:03 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:21:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:21:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:20:59 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:20:14 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:20:11 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:20:10 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:50 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:49 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:36 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:30 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:30 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:26 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:23 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:23 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:22 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:21 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:21 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:21 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:21 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:21 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:21 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:15 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:15 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:15 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:15 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:15 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:15 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:14 kernel: em0: link state changed to UP 
    Feb 3 11:19:14 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf em0 > /tmp/em0_output > /tmp/em0_error_output' returned exit code '15', the output was '' 
    Feb 3 11:19:14 dhclient[40067]: exiting. 
    Feb 3 11:19:14 dhclient[40067]: exiting. 
    Feb 3 11:19:14 dhclient[40067]: connection closed 
    Feb 3 11:19:14 dhclient[40067]: connection closed 
    Feb 3 11:19:14 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:19:12 kernel: em0: link state changed to DOWN 
    Feb 3 11:19:12 check_reload_status: Linkup starting em0 
    Feb 3 11:19:12 dhclient[39818]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:19:10 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:19:10 dhclient[39818]: DHCPREQUEST on em0 to 255.255.255.255 port 67 
    Feb 3 11:19:10 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:10 miniupnpd[53901]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host 
    Feb 3 11:19:10 dhclient: PREINIT 
    Feb 3 11:19:10 php: : HOTPLUG: Configuring interface wan 
    Feb 3 11:19:10 php: : DEVD Ethernet attached event for wan 
    Feb 3 11:19:09 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:09 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:09 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:09 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:08 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:08 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:08 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:07 kernel: em0: link state changed to UP 
    Feb 3 11:19:07 check_reload_status: Linkup starting em0 
    Feb 3 11:19:05 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:05 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:05 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:05 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:05 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:05 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:05 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:05 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:03 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:03 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:19:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:19:03 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:18:59 kernel: arpresolve: can't allocate llinfo for 75.131.xxx.xxx 
    Feb 3 11:18:59 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:18:59 miniupnpd[53901]: Failed to get ip address for interface em0 
    Feb 3 11:18:59 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:18:59 miniupnpd[53901]: ioctl(s, SIOCGIFADDR, ...): Can't assign requested address 
    Feb 3 11:18:56 dhclient[4995]: exiting. 
    Feb 3 11:18:56 dhclient[4995]: exiting. 
    Feb 3 11:18:56 dhclient[4995]: connection closed 
    Feb 3 11:18:56 dhclient[4995]: connection closed 
    Feb 3 11:18:56 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:18:54 kernel: em0: link state changed to DOWN 
    Feb 3 11:18:54 check_reload_status: Linkup starting em0 
    Feb 3 11:18:47 check_reload_status: Reloading filter 
    Feb 3 11:18:37 apinger: ALARM: WAN(75.131.xxx.xxx) *** down *** 
    
    

  • Rebel Alliance Developer Netgate

    I flipped these log entries around because trying to follow the flow of messages in reverse-order logs is bothersome…

    Feb 3 11:19:12 kernel: em0: link state changed to DOWN 
    Feb 3 11:19:14 php: : DEVD Ethernet detached event for wan 
    Feb 3 11:19:14 kernel: em0: link state changed to UP 
    
    

    If I had to guess I'd say that the link cycled too fast and either DEVD did not fire the event to bring it back up or the event was lost somewhere in between devd and check_reload_status.

    Are you spoofing a MAC on that interface? Or setting any other custom values other than the interface name and setting it for DHCP?



  • No MAC spoofing or anything unusual. It is a very basic home setup.


  • Rebel Alliance Developer Netgate

    Could be something sketchy happening at the modem then…

    Ermal is looking into a fix, I started a ticket here: https://redmine.pfsense.org/issues/2792



  • It looks like anytime the cable goes out or I get a T4 error (causes modem reboot), it happens. It's a Motorola 6120. We had an all out outage yesterday which caused the log I posted above. Sometimes I'll get a T4 error which causes the modem to reboot and pfSense doesn't recover. pfSense 2.0.1 would recover just fine.

    I'm actually going to buy a new modem today in hopes it will fix something. If not I'll go back to 2.0.1 but wanted to remain on the newer versions to help fix it. I can't have the wife with no Internet while I'm at work - I get nasty calls :)


  • Rebel Alliance Developer Netgate

    OK, snaps up now should have a potential fix in for this.

    2.0.3 snaps can be found here: http://forum.pfsense.org/index.php/topic,58203.msg311614.html#msg311614
    2.1 snaps are on http://snapshots.pfsense.org/



  • It's awful bug! But to install a "snap" it's much more unsafely IMHO.
    You can use my temp solution:
    Repeat every minute by cron smth like this

    $ cat /root/renew-ip.sh
    #!/bin/sh
    
    GW=`netstat -rn | grep default | egrep -o "[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}"`
    lan_inf="em1"
    
    ping -c 5 -i 0.1 -q $GW >/dev/null
      if [ $? != 0 ]; then
        logger "GW:$GW sucks"
        ping -c 5 -q ya.ru >/dev/null 
          if [ $? != 0 ]; then
             /sbin/dhclient $lan_inf
            logger "GW:$GW Crash!"
    	sleep 30
          fi
      fi
    exit 1
    

    It works for me since 2.0.2 upgrade comes


  • Rebel Alliance Developer Netgate

    2.0.3 snaps are safe. Releases are just snapshots we deemed worthy of being called releases.

    The only thing holding back 2.0.3 from release right now is that we're waiting on FreeBSD to issue an OpenSSL security advisory any time now, and we have to account for that once it comes out.



  • I upgraded to the latest snap image today (Feb 13 1243), and I am still having the problem that originally started this thread.


  • Rebel Alliance Developer Netgate

    Gather the info again (the syslog logs, etc) and post it again from the new snapshot.



  • Just to be clear: my interface was not going up/down.  That seems like a different issue than the one I initially reported.  My issue is that dhclient never got an IP address to begin with – it didn't exit, but kept trying forever to get a lease.  Each time, it would eventually timeout and say that it hadn't received any DHCP offers.  Please re-read my first post on this thread.

    The behavior has now changed.  dhclient is now re-launching every few seconds, and the link status (according to pfsense) is flapping.  dhclient is now exiting every 1-2 seconds and re-trying.  This is new.  The link itself is not flapping, however.  Here's a bunch of the logs; you can see multiple iterations of the flapping:

    
    Feb 16 15:01:07	kernel: sk0: link state changed to DOWN
    Feb 16 15:01:07	check_reload_status: Linkup starting sk0
    Feb 16 15:01:07	php: : HOTPLUG: Configuring interface wan
    Feb 16 15:01:07	php: : DEVD Ethernet attached event for wan
    Feb 16 15:01:06	kernel: arpresolve: can't allocate llinfo for 10.0.2.1
    Feb 16 15:01:05	php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf sk0 > /tmp/sk0_output > /tmp/sk0_error_output' returned exit code '15', the output was ''
    Feb 16 15:01:05	dhclient[20134]: exiting.
    Feb 16 15:01:05	dhclient[20134]: exiting.
    Feb 16 15:01:05	dhclient[20134]: connection closed
    Feb 16 15:01:05	dhclient[20134]: connection closed
    Feb 16 15:01:05	php: : DEVD Ethernet detached event for wan
    Feb 16 15:01:04	dhclient[19667]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 2
    Feb 16 15:01:04	dhclient[19667]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 1
    Feb 16 15:01:04	dhclient: PREINIT
    Feb 16 15:01:04	dhclient: Deleting old routes
    Feb 16 15:01:04	dhclient: EXPIRE
    Feb 16 15:01:04	dhclient: PREINIT
    Feb 16 15:01:04	kernel: sk0: link state changed to UP
    Feb 16 15:01:04	check_reload_status: Linkup starting sk0
    Feb 16 15:01:02	kernel: sk0: link state changed to DOWN
    Feb 16 15:01:02	check_reload_status: Linkup starting sk0
    Feb 16 15:01:02	php: : HOTPLUG: Configuring interface wan
    Feb 16 15:01:02	php: : DEVD Ethernet attached event for wan
    Feb 16 15:01:01	kernel: arpresolve: can't allocate llinfo for 10.0.2.1
    Feb 16 15:01:00	php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf sk0 > /tmp/sk0_output > /tmp/sk0_error_output' returned exit code '15', the output was ''
    Feb 16 15:01:00	dhclient[14425]: exiting.
    Feb 16 15:01:00	dhclient[14425]: exiting.
    Feb 16 15:01:00	dhclient[14425]: connection closed
    Feb 16 15:01:00	dhclient[14425]: connection closed
    Feb 16 15:01:00	php: : DEVD Ethernet detached event for wan
    Feb 16 15:01:00	dhclient[13908]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 5
    Feb 16 15:01:00	dhclient[13908]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 2
    Feb 16 15:01:00	dhclient: PREINIT
    Feb 16 15:01:00	check_reload_status: Linkup starting sk0
    Feb 16 15:01:00	dhclient: Deleting old routes
    Feb 16 15:01:00	dhclient: EXPIRE
    Feb 16 15:01:00	kernel: sk0: link state changed to UP
    Feb 16 15:01:00	dhclient: PREINIT
    Feb 16 15:00:58	kernel: sk0: link state changed to DOWN
    Feb 16 15:00:58	check_reload_status: Linkup starting sk0
    Feb 16 15:00:58	php: : HOTPLUG: Configuring interface wan
    Feb 16 15:00:58	php: : DEVD Ethernet attached event for wan
    Feb 16 15:00:56	dhclient[8419]: exiting.
    Feb 16 15:00:56	dhclient[8419]: exiting.
    Feb 16 15:00:56	dhclient[8419]: connection closed
    Feb 16 15:00:56	dhclient[8419]: connection closed
    Feb 16 15:00:56	php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf sk0 > /tmp/sk0_output > /tmp/sk0_error_output' returned exit code '15', the output was ''
    Feb 16 15:00:56	php: : DEVD Ethernet detached event for wan
    Feb 16 15:00:56	kernel: arpresolve: can't allocate llinfo for 10.0.2.1
    Feb 16 15:00:56	dhclient[7818]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 2
    
    

    Here's a sample of output from /tmp/sk0_error_output (sk0_output and sk0_default_gateway always remain empty):

    
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 1
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 1
    DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 2
    sk0: no link .... got link
    dhclient: PREINIT
    
    

    sk0_error_output keeps getting overwritten every time dhclient gets run; the output is essentially the same every time.


  • Rebel Alliance Developer Netgate

    The link was flapping in the logs you posted in the OP of this thread. It showed sk0's link state going up/down which is the link flapping. If it's still happening, there may be something else going on that is completely unrelated to dhclient itself.

    Are you spoofing a MAC address on WAN or setting any other interface parameters?



  • No, I'm not spoofing or anything like that.

    It's just a plain, vanilla DHCP from upstream.  Is there any config or something I can share so you can see my specific setup?

    The first logs I posted were from an initial boot of pfsense – the DOWN state was the initial state, and then the UP state was where it stayed.  IIRC (it's been a little while now), it would run forever trying to get an address, and periodically report timeout -- it got no DHOFFERS.  Then it would start trying again.



  • Seeing pretty much the same problem. I've tried going to a 2.1 snap, and am now back on 2.0.1 and seem to still be seeing the issue now and then. I've swapped out the Cablemodem (needed to upgrade to DOCSIS 3.0 anyway…), the SiiG USB Ethernet adaptor, and the ethernet cable.  Waiting now to see if it happens again. I've removed all installed packages. The only remnant really of the other versions is that I used a config backup from 2.1 to restore from after I did a clean (nanobsd) install of 2.0.1.

    Next step I guess will be to try 2.0.3 if the problem happens again.

    (ISP is Comcast BTW - this has been happening for me about a week now I guess. It's possible it may have started after I upgraded to 2.0.2, but I didn't keep notes on that...  :-[



  • Well, 2.0.3 snapshot seems to be a bust as well.

    system.log output from when things go per shaped (first few iterations, it'll go on like this forever):

    Feb 28 02:40:48 gw dnsmasq[59395]: read /etc/hosts - 26 addresses
    Feb 28 02:46:12 gw dnsmasq[59395]: read /etc/hosts - 26 addresses
    Feb 28 02:51:33 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:33 gw kernel: ue0: link state changed to DOWN
    Feb 28 02:51:33 gw kernel: ue0: link state changed to UP
    Feb 28 02:51:33 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:35 gw php: : DEVD Ethernet detached event for wan
    Feb 28 02:51:35 gw dhclient[7830]: connection closed
    Feb 28 02:51:35 gw dhclient[7830]: connection closed
    Feb 28 02:51:35 gw dhclient[7830]: exiting.
    Feb 28 02:51:35 gw dhclient[7830]: exiting.
    Feb 28 02:51:35 gw php: : DEVD Ethernet attached event for wan
    Feb 28 02:51:35 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 02:51:35 gw kernel: ue0: link state changed to DOWN
    Feb 28 02:51:35 gw dhclient: PREINIT
    Feb 28 02:51:36 gw kernel: ue0: link state changed to DOWN
    Feb 28 02:51:36 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:36 gw dhclient[26875]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 02:51:36 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:36 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:37 gw dhclient[26875]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 02:51:37 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:37 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:38 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:38 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:38 gw kernel: ue0: link state changed to UP
    Feb 28 02:51:38 gw php: : DEVD Ethernet detached event for wan
    Feb 28 02:51:38 gw dhclient[26886]: connection closed
    Feb 28 02:51:38 gw dhclient[26886]: connection closed
    Feb 28 02:51:38 gw dhclient[26886]: exiting.
    Feb 28 02:51:38 gw dhclient[26886]: exiting.
    Feb 28 02:51:38 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''
    Feb 28 02:51:38 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:39 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:39 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:39 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:40 gw php: : DEVD Ethernet attached event for wan
    Feb 28 02:51:40 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:40 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 02:51:41 gw dhclient: PREINIT
    Feb 28 02:51:41 gw kernel: ue0: link state changed to DOWN
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:41 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:41 gw kernel: ue0: link state changed to DOWN
    Feb 28 02:51:41 gw dhclient[29928]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:41 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:42 gw dhclient[29928]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 02:51:42 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:42 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:43 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:43 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:43 gw kernel: ue0: link state changed to UP
    Feb 28 02:51:43 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:43 gw php: : DEVD Ethernet detached event for wan
    Feb 28 02:51:43 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:43 gw dhclient[30147]: connection closed
    Feb 28 02:51:43 gw dhclient[30147]: connection closed
    Feb 28 02:51:43 gw dhclient[30147]: exiting.
    Feb 28 02:51:43 gw dhclient[30147]: exiting.
    Feb 28 02:51:43 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''
    Feb 28 02:51:43 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:44 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:44 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:44 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:44 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:45 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:45 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:45 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:45 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:45 gw php: : DEVD Ethernet attached event for wan
    Feb 28 02:51:45 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 02:51:45 gw apinger: ALARM: COMCAST(76.21.128.1) *** down ***
    Feb 28 02:51:45 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:45 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:45 gw dhclient: PREINIT
    Feb 28 02:51:45 gw kernel: ue0: link state changed to DOWN
    Feb 28 02:51:46 gw dhclient[32914]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 02:51:46 gw kernel: ue0: link state changed to DOWN
    Feb 28 02:51:46 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:46 gw dhclient[32914]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 02:51:46 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:47 gw dhclient[32914]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 02:51:47 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:47 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:47 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:47 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:47 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:48 gw kernel: arpresolve: can't allocate llinfo for 68.48.154.1
    Feb 28 02:51:48 gw check_reload_status: Linkup starting ue0
    Feb 28 02:51:48 gw kernel: ue0: link state changed to UP
    Feb 28 02:51:48 gw php: : DEVD Ethernet detached event for wan
    Feb 28 02:51:48 gw dhclient[33032]: connection closed

    And some tcpdump on the WAN interface while this is happening:

    3:07:08.179613 ARP, Request who-has 96.159.231.104 tell 96.159.224.1, length 46
    03:07:08.255915 ARP, Request who-has 69.255.98.63 tell 69.255.98.1, length 46
    03:07:08.265409 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffd8:3eae: ICMP6, neighbor solicitation, who has fe80::103a:146a:c8d8:3eae, length 32
    03:07:08.281166 ARP, Request who-has 68.33.165.136 tell 68.33.164.1, length 46
    03:07:08.332951 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff0f:3169: ICMP6, neighbor solicitation, who has fe80::20d:56ff:fe0f:3169, length 32
    03:07:08.354737 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354746 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354751 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354755 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354760 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354765 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354770 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354776 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354781 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354786 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.376346 IP 73.129.106.1.bootps > 68.48.155.52.bootpc: BOOTP/DHCP, Reply, length 310
    03:07:08.399605 ARP, Request who-has 73.135.29.90 tell 73.135.28.1, length 46
    03:07:08.442380 ARP, Request who-has 76.21.131.12 tell 76.21.128.1, length 46
    03:07:08.516027 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffe8:585e: ICMP6, neighbor solicitation, who has fe80::f4f2:2722:9e8:585e, length 32
    03:07:08.517774 ARP, Request who-has 69.251.11.67 tell 69.251.11.1, length 46
    03:07:08.556795 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb3:1451: ICMP6, neighbor solicitation, who has fe80::c2c1:c0ff:feb3:1451, length 32
    03:07:08.674110 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffa0:1a00: ICMP6, neighbor solicitation, who has fe80::3ed9:2bff:fea0:1a00, length 32
    03:07:08.684109 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb8:7ab6: ICMP6, neighbor solicitation, who has fe80::8d76:e28f:41b8:7ab6, length 32
    03:07:08.696366 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff78:d9e: ICMP6, neighbor solicitation, who has fe80::748e:b8b7:3278:d9e, length 32
    03:07:08.836688 ARP, Request who-has 73.132.81.206 tell 73.132.80.1, length 46
    03:07:08.914100 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff93:f82e: ICMP6, neighbor solicitation, who has fe80::221:5aff:fe93:f82e, length 32
    03:07:08.915224 ARP, Request who-has 76.100.105.141 tell 76.100.105.1, length 46
    03:07:08.928980 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff47:f53a: ICMP6, neighbor solicitation, who has fe80::9989:14eb:6747:f53a, length 32
    ç03:07:09.011660 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff0e:e6ef: ICMP6, neighbor solicitation, who has fe80::dd8a:aba8:7a0e:e6ef, length 32



  • @TravisD:

    Well, 2.0.3 snapshot seems to be a bust as well.

    Which 2.0.3 snapshot?

    @TravisD:

    system.log output from when things go per shaped (first few iterations, it'll go on like this forever):

    Feb 28 02:51:38 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''

    I don't know if the double redirection is what causes dhclient to exit. I feel sure I saw the double redirection error reported some weeks ago. Maybe it needs an "official" problem report to get fixed.

    @TravisD:

    And some tcpdump on the WAN interface while this is happening:

    03:07:08.354737 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354746 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354751 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354755 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354760 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354765 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354770 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354776 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354781 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.354786 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    03:07:08.376346 IP 73.129.106.1.bootps > 68.48.155.52.bootpc: BOOTP/DHCP, Reply, length 310

    The interval between the DHCP broadcasts seems far too short. But there is a reply. Unfortunately the timestamps in the tcpdump don't correspond to the timestamps in the system log so its not much help to understand what is actually happening. System log entries correlated to tcpdump timestamps would probably be much more useful.



  • Yeah, sorry about the out of sync logs - I was lazy :)

    Surprisingly, knock on wood, it hasn't happened today yet. Version wise, I'm running:

    2.0.3-PRERELEASE (i386)
    built on Thu Feb 21 18:45:45 EST 2013

    though now I need to figure out how to fix my screwup which is installing a non-VGA nanobsd image onto a box with no serial ports. Guess I'll be re-installing again…

    EDIT: Just a minute of so after I replied here, it died again.

    Synchronized system.log and tcpdump output:

    Feb 28 17:48:00 gw dhclient[4459]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:02 gw dhclient[4459]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:02 gw kernel: ue0: link state changed to UP
    Feb 28 17:48:02 gw php: : DEVD Ethernet detached event for wan
    Feb 28 17:48:02 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:02 gw dhclient[4665]: connection closed
    Feb 28 17:48:02 gw dhclient[4665]: connection closed
    Feb 28 17:48:02 gw dhclient[4665]: exiting.
    Feb 28 17:48:02 gw dhclient[4665]: exiting.
    Feb 28 17:48:02 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''
    Feb 28 17:48:04 gw php: : DEVD Ethernet attached event for wan
    Feb 28 17:48:04 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 17:48:04 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:04 gw dhclient: PREINIT
    Feb 28 17:48:05 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:05 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:05 gw dhclient[7585]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:06 gw dhclient[7585]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:07 gw kernel: ue0: link state changed to UP
    Feb 28 17:48:07 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:07 gw php: : DEVD Ethernet detached event for wan
    Feb 28 17:48:07 gw dhclient[7668]: connection closed
    Feb 28 17:48:07 gw dhclient[7668]: connection closed
    Feb 28 17:48:07 gw dhclient[7668]: exiting.
    Feb 28 17:48:07 gw dhclient[7668]: exiting.
    Feb 28 17:48:07 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''
    Feb 28 17:48:09 gw php: : DEVD Ethernet attached event for wan
    Feb 28 17:48:09 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 17:48:09 gw dhclient: PREINIT
    Feb 28 17:48:09 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:10 gw dhclient[10424]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:10 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:10 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:10 gw dhclient[10424]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:11 gw dhclient[10424]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:12 gw kernel: ue0: link state changed to UP
    Feb 28 17:48:12 gw php: : DEVD Ethernet detached event for wan
    Feb 28 17:48:12 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:12 gw dhclient[10449]: connection closed
    Feb 28 17:48:12 gw dhclient[10449]: connection closed
    Feb 28 17:48:12 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''
    Feb 28 17:48:12 gw dhclient[10449]: exiting.
    Feb 28 17:48:12 gw dhclient[10449]: exiting.
    Feb 28 17:48:14 gw php: : DEVD Ethernet attached event for wan
    Feb 28 17:48:14 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 17:48:14 gw dhclient: PREINIT
    Feb 28 17:48:14 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:15 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:15 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:15 gw dhclient[35457]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:16 gw dhclient[35457]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:17 gw kernel: ue0: link state changed to UP
    Feb 28 17:48:17 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:17 gw php: : DEVD Ethernet detached event for wan
    Feb 28 17:48:17 gw dhclient[35587]: connection closed
    Feb 28 17:48:17 gw dhclient[35587]: connection closed
    Feb 28 17:48:17 gw dhclient[35587]: exiting.
    Feb 28 17:48:17 gw dhclient[35587]: exiting.
    Feb 28 17:48:17 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''
    Feb 28 17:48:19 gw php: : DEVD Ethernet attached event for wan
    Feb 28 17:48:19 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 17:48:19 gw dhclient: PREINIT
    Feb 28 17:48:19 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:20 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:20 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:20 gw dhclient[38619]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:20 gw dhclient[38619]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:22 gw dhclient[38619]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:22 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:22 gw kernel: ue0: link state changed to UP
    Feb 28 17:48:22 gw php: : DEVD Ethernet detached event for wan
    Feb 28 17:48:22 gw dhclient[38727]: connection closed
    Feb 28 17:48:22 gw dhclient[38727]: connection closed
    Feb 28 17:48:22 gw dhclient[38727]: exiting.
    Feb 28 17:48:22 gw dhclient[38727]: exiting.
    Feb 28 17:48:22 gw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output > /tmp/ue0_error_output' returned exit code '15', the output was ''
    Feb 28 17:48:24 gw php: : DEVD Ethernet attached event for wan
    Feb 28 17:48:24 gw php: : HOTPLUG: Configuring interface wan
    Feb 28 17:48:24 gw dhclient: PREINIT
    Feb 28 17:48:24 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:25 gw dhclient[41277]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:25 gw kernel: ue0: link state changed to DOWN
    Feb 28 17:48:25 gw check_reload_status: Linkup starting ue0
    Feb 28 17:48:25 gw dhclient[41277]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:26 gw dhclient[41277]: DHCPREQUEST on ue0 to 255.255.255.255 port 67
    Feb 28 17:48:26 gw kernel: ue0: promiscuous mode disabled

    17:47:59.520569 ARP, Request who-has 96.159.230.112 tell 96.159.224.1, length 46
    17:48:01.779331 ARP, Request who-has 76.21.132.40 tell 76.21.128.1, length 46
    17:48:01.799067 ARP, Request who-has 96.159.227.14 tell 96.159.224.1, length 46
    17:48:01.819440 ARP, Request who-has 96.70.23.11 tell 96.70.22.1, length 46
    17:48:01.824065 ARP, Request who-has 96.159.128.77 tell 96.159.128.1, length 46
    17:48:01.859585 ARP, Request who-has 73.132.253.104 tell 73.132.248.1, length 46
    17:48:01.948192 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffca:3076: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:feca:3076, length 32
    17:48:02.013267 IP 73.129.106.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 306
    17:48:02.013806 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013814 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013818 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013822 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013826 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013830 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013834 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013838 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013842 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013846 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013850 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013855 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013859 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013863 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013867 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.013871 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.043541 IP 73.129.106.1.bootps > 68.48.155.52.bootpc: BOOTP/DHCP, Reply, length 310
    17:48:02.043721 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.043728 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.043732 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.043736 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.043741 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.043745 IP 68.48.155.52.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:b6:59:70:f5 (oui Unknown), length 300
    17:48:02.072446 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff54:34af: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe54:34af, length 32
    17:48:02.073806 IP 73.129.106.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 325
    17:48:02.073881 ARP, Request who-has 76.21.129.69 tell 76.21.128.1, length 46
    17:48:02.165780 ARP, Request who-has 73.132.251.7 tell 73.132.248.1, length 46
    17:48:02.242441 ARP, Request who-has 73.132.85.146 tell 73.132.80.1, length 46
    17:48:02.242455 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff98:ca0e: ICMP6, neighbor solicitation, who has fe80::d157:bf8:f998:ca0e, length 32
    17:48:02.243632 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffa8:536f: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fea8:536f, length 32
    17:48:02.243657 IP 68.71.224.5.sae-urn > 68.48.155.52.41389: isakmp-nat-keep-alive
    17:48:02.243721 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff9f:1978: ICMP6, neighbor solicitation, who has fe80::c45d:72e3:939f:1978, length 32
    17:48:02.272392 ARP, Request who-has 73.132.85.81 tell 73.132.80.1, length 46
    17:48:02.305747 ARP, Request who-has 69.140.212.124 tell 69.140.212.1, length 46
    17:48:02.306566 ARP, Request who-has 96.207.164.175 tell 96.207.164.1, length 46
    17:48:02.337028 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff96:c279: ICMP6, neighbor solicitation, who has fe80::889a:5f6c:e96:c279, length 32
    17:48:02.439571 ARP, Request who-has 73.132.85.42 tell 73.132.80.1, length 46
    17:48:02.459069 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff8e:a1d: ICMP6, neighbor solicitation, who has fe80::5a6d:8fff:fe8e:a1d, length 32
    17:48:02.479192 IP6 fe80::201:5cff:fe22:1281 > ff02::1: ICMP6, router advertisement, length 80
    17:48:02.529441 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff7c:554b: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe7c:554b, length 32
    17:48:02.560191 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:02.626316 ARP, Request who-has 76.21.128.4 tell 76.21.128.1, length 46
    17:48:02.690066 ARP, Request who-has 68.48.14.95 tell 68.48.14.1, length 46
    17:48:02.708317 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff88:cbbe: ICMP6, neighbor solicitation, who has fe80::2860:48cd:4588:cbbe, length 32
    17:48:02.743941 ARP, Request who-has 73.132.83.166 tell 73.132.80.1, length 46
    17:48:02.858091 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff47:35d0: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:216:92ff:fe47:35d0, length 32
    17:48:02.929084 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff47:35c6: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:216:92ff:fe47:35c6, length 32
    17:48:02.940943 ARP, Request who-has 76.21.135.167 tell 76.21.128.1, length 46
    17:48:03.047089 ARP, Request who-has 96.70.22.233 tell 96.70.22.1, length 46
    17:48:03.073070 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb0:34d9: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:feb0:34d9, length 32
    17:48:03.145442 ARP, Request who-has 73.135.81.117 tell 73.135.80.1, length 46
    17:48:03.209192 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff9f:1978: ICMP6, neighbor solicitation, who has fe80::c45d:72e3:939f:1978, length 32
    17:48:03.329221 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff96:c279: ICMP6, neighbor solicitation, who has fe80::889a:5f6c:e96:c279, length 32
    17:48:03.354783 ARP, Request who-has 73.132.82.40 tell 73.132.80.1, length 46
    17:48:03.360942 IP 173.194.43.22.https > 68.48.155.52.15802: Flags [P.], ack 1, win 1400, options [nop,nop,TS val 630727156 ecr 182277980], length 55
    17:48:03.490571 ARP, Request who-has 69.140.215.181 tell 69.140.212.1, length 46
    17:48:03.513567 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:ab42: ICMP6, neighbor solicitation, who has fe80::f54f:ebff:7910:ab42, length 32
    17:48:03.529444 ARP, Request who-has 96.70.22.39 tell 96.70.22.1, length 46
    17:48:03.530564 IP 108.160.160.165.http > 68.48.155.52.13355: Flags [P.], ack 1962977884, win 83, options [nop,nop,TS val 2887055233 ecr 182271951], length 179
    17:48:03.559068 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:03.559940 ARP, Request who-has 68.33.164.32 tell 68.33.164.1, length 46
    17:48:03.629319 ARP, Request who-has 69.140.213.60 tell 69.140.212.1, length 46
    17:48:03.660068 ARP, Request who-has 73.137.142.118 tell 73.137.142.1, length 46
    17:48:03.672566 ARP, Request who-has 69.140.215.250 tell 69.140.212.1, length 46
    17:48:03.699193 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff88:cbbe: ICMP6, neighbor solicitation, who has fe80::2860:48cd:4588:cbbe, length 32
    17:48:03.725317 ARP, Request who-has 68.33.164.182 tell 68.33.164.1, length 46
    17:48:03.741318 IP 108.160.160.165.http > 68.48.155.52.15197: Flags [P.], ack 1, win 83, options [nop,nop,TS val 2887055286 ecr 392569968], length 179
    17:48:03.821318 IP 108.160.160.165.http > 68.48.155.52.13355: Flags [P.], ack 1, win 83, options [nop,nop,TS val 2887055306 ecr 182271951], length 179
    17:48:03.949709 ARP, Request who-has 74.29.118.70 tell 74.29.118.1, length 46
    17:48:03.977951 ARP, Request who-has 73.128.82.241 tell 73.128.80.1, length 46
    17:48:04.052938 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff32:100e: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe32:100e, length 32
    17:48:04.068684 IP 173.194.76.125.jabber-client > 68.48.155.52.30445: Flags [P.], ack 1, win 1179, options [nop,nop,TS val 2867094343 ecr 182244974], length 292
    17:48:04.079183 IP 73.129.106.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 325
    17:48:04.112808 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff3c:b18f: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe3c:b18f, length 32
    17:48:04.116809 ARP, Request who-has 76.21.133.145 tell 76.21.128.1, length 46
    17:48:04.118308 ARP, Request who-has 74.146.129.59 tell 74.146.129.1, length 46
    17:48:04.130058 ARP, Request who-has 68.50.233.188 tell 68.50.232.1, length 46
    17:48:04.187934 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff6a:93db: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:fe6a:93db, length 32
    17:48:04.192683 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff7c:5398: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe7c:5398, length 32
    17:48:04.212434 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff17:f39f: ICMP6, neighbor solicitation, who has fe80::d0af:9ba:5717:f39f, length 32
    17:48:04.275067 ARP, Request who-has 73.135.29.154 tell 73.135.28.1, length 46
    17:48:04.313559 ARP, Request who-has 98.47.118.222 tell 98.47.118.1, length 46
    17:48:04.395444 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff96:c279: ICMP6, neighbor solicitation, who has fe80::889a:5f6c:e96:c279, length 32
    17:48:04.396601 ARP, Request who-has 76.21.135.146 tell 76.21.128.1, length 46
    17:48:04.396617 ARP, Request who-has 76.21.133.90 tell 76.21.128.1, length 46
    17:48:04.407188 ARP, Request who-has 76.21.128.6 tell 76.21.128.1, length 46
    17:48:04.409056 IP 108.160.160.165.http > 68.48.155.52.13355: Flags [P.], ack 1, win 83, options [nop,nop,TS val 2887055453 ecr 182271951], length 179
    17:48:04.509073 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:ab42: ICMP6, neighbor solicitation, who has fe80::f54f:ebff:7910:ab42, length 32
    17:48:04.559197 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:04.574815 ARP, Request who-has 73.135.80.14 tell 73.135.80.1, length 46
    17:48:04.577436 ARP, Request who-has 76.100.105.8 tell 76.100.105.1, length 46
    17:48:04.662456 ARP, Request who-has 68.48.14.138 tell 68.48.14.1, length 46
    17:48:04.663564 ARP, Request who-has 69.244.78.37 tell 69.244.78.1, length 46
    17:48:04.699066 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff88:cbbe: ICMP6, neighbor solicitation, who has fe80::2860:48cd:4588:cbbe, length 32
    17:48:04.730942 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff46:f4a0: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:216:92ff:fe46:f4a0, length 32
    17:48:04.755032 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffab:2218: ICMP6, neighbor solicitation, who has fe80::f1d6:aa8b:86ab:2218, length 32
    17:48:06.979208 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffa3:b740: ICMP6, neighbor solicitation, who has fe80::bc19:6f47:66a3:b740, length 32
    17:48:06.990563 ARP, Request who-has 73.128.82.101 tell 73.128.80.1, length 46
    17:48:06.995561 ARP, Request who-has 69.140.214.111 tell 69.140.212.1, length 46
    17:48:06.998561 ARP, Request who-has 69.143.255.245 tell 69.143.255.1, length 46
    17:48:07.052821 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff2e:b353: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe2e:b353, length 32
    17:48:07.139201 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffea:a7ca: ICMP6, neighbor solicitation, who has fe80::f961:5ae5:6eea:a7ca, length 32
    17:48:07.169572 IP 68.71.224.5.sae-urn > 68.48.155.52.41389: isakmp-nat-keep-alive
    17:48:07.182689 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff54:30ad: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe54:30ad, length 32
    17:48:07.221324 ARP, Request who-has 68.50.234.57 tell 68.50.232.1, length 46
    17:48:07.232652 ARP, Request who-has 76.151.58.184 tell 76.151.58.1, length 46
    17:48:07.236685 ARP, Request who-has 68.33.164.182 tell 68.33.164.1, length 46
    17:48:07.295925 ARP, Request who-has 69.136.231.214 tell 69.136.231.1, length 46
    17:48:07.296820 ARP, Request who-has 73.128.81.224 tell 73.128.80.1, length 46
    17:48:07.309598 ARP, Request who-has 69.140.215.250 tell 69.140.212.1, length 46
    17:48:07.322962 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb2:f77f: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:feb2:f77f, length 32
    17:48:07.328971 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffba:8056: ICMP6, neighbor solicitation, who has fe80::a00:37ff:feba:8056, length 32
    17:48:07.335848 IP 97.125.108.193.56857 > 68.48.155.52.8022: Flags [P.], ack 2078116778, win 8192, options [nop,nop,TS val 1604729038 ecr 3507339575], length 64
    17:48:07.340103 ARP, Request who-has 68.33.165.112 tell 68.33.164.1, length 46
    17:48:07.432717 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffe3:4e9a: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:218:68ff:fee3:4e9a, length 32
    17:48:07.499207 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:ab42: ICMP6, neighbor solicitation, who has fe80::f54f:ebff:7910:ab42, length 32
    17:48:07.508819 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff51:642e: ICMP6, neighbor solicitation, who has fe80::5491:29b7:2251:642e, length 32
    17:48:07.517443 ARP, Request who-has 76.21.133.12 tell 76.21.128.1, length 46
    17:48:07.532196 ARP, Request who-has 69.244.78.9 tell 69.244.78.1, length 46
    17:48:07.569213 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:07.570188 ARP, Request who-has 69.250.36.46 tell 69.250.36.1, length 46
    17:48:07.593946 ARP, Request who-has 73.135.28.209 tell 73.135.28.1, length 46
    17:48:07.636194 ARP, Request who-has 76.21.130.14 tell 76.21.128.1, length 46
    17:48:07.649323 ARP, Request who-has 23.70.189.113 tell 23.70.189.1, length 46
    17:48:07.655945 ARP, Request who-has 76.151.58.184 tell 76.151.58.1, length 46
    17:48:07.669444 ARP, Request who-has 69.244.78.37 tell 69.244.78.1, length 46
    17:48:07.705078 ARP, Request who-has 69.244.87.242 tell 69.244.87.1, length 46
    17:48:07.745476 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff28:26df: ICMP6, neighbor solicitation, who has fe80::d841:5ae4:2f28:26df, length 32
    17:48:07.749950 IP 208.91.175.36.http > 68.48.155.52.7336: Flags [F.], seq 1280995650, ack 1535050770, win 8190, length 0
    17:48:07.759949 ARP, Request who-has 68.33.164.182 tell 68.33.164.1, length 46
    17:48:07.772696 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffe3:4ede: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:218:68ff:fee3:4ede, length 32
    17:48:07.779447 ARP, Request who-has 68.48.155.244 tell 68.48.154.1, length 46
    17:48:07.823197 IP 97.125.108.193.56857 > 68.48.155.52.8022: Flags [P.], ack 1, win 8192, options [nop,nop,TS val 1604729638 ecr 3507339575], length 64
    17:48:07.828197 ARP, Request who-has 74.29.118.119 tell 74.29.118.1, length 46
    17:48:07.872698 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff54:303b: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe54:303b, length 32
    17:48:07.901823 ARP, Request who-has 96.159.226.40 tell 96.159.224.1, length 46
    17:48:07.904697 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff75:dd74: ICMP6, neighbor solicitation, who has fe80::6c6e:d888:4775:dd74, length 32
    17:48:07.925322 IP 108.160.160.165.http > 68.48.155.52.13355: Flags [P.], ack 1, win 83, options [nop,nop,TS val 2887056332 ecr 182271951], length 179
    17:48:07.932821 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffdd:347d: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fedd:347d, length 32
    17:48:07.969236 ARP, Request who-has 73.132.84.109 tell 73.132.80.1, length 46
    17:48:07.979095 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffa3:b740: ICMP6, neighbor solicitation, who has fe80::bc19:6f47:66a3:b740, length 32
    17:48:07.991456 ARP, Request who-has 96.159.224.16 tell 96.159.224.1, length 46
    17:48:08.006975 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff3c:4cbe: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fe3c:4cbe, length 32
    17:48:08.092968 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff49:ef05: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fe49:ef05, length 32
    17:48:08.094074 ARP, Request who-has 76.21.134.168 tell 76.21.128.1, length 46
    17:48:08.097695 ARP, Request who-has 96.70.22.91 tell 96.70.22.1, length 46
    17:48:08.099068 ARP, Request who-has 76.21.129.69 tell 76.21.128.1, length 46
    17:48:08.127574 ARP, Request who-has 68.50.233.255 tell 68.50.232.1, length 46
    17:48:08.136948 ARP, Request who-has 76.21.134.239 tell 76.21.128.1, length 46
    17:48:08.139069 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffea:a7ca: ICMP6, neighbor solicitation, who has fe80::f961:5ae5:6eea:a7ca, length 32
    17:48:08.169198 ARP, Request who-has 69.140.213.105 tell 69.140.212.1, length 46
    17:48:08.187698 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffee:e44c: ICMP6, neighbor solicitation, who has fe80::7ae7:d1ff:feee:e44c, length 32
    17:48:08.205573 ARP, Request who-has 73.132.255.209 tell 73.132.248.1, length 46
    17:48:08.269080 ARP, Request who-has 98.47.131.30 tell 98.47.131.1, length 46
    17:48:08.289452 ARP, Request who-has 96.207.164.175 tell 96.207.164.1, length 46
    17:48:08.359211 ARP, Request who-has 76.21.135.4 tell 76.21.128.1, length 46
    17:48:08.432574 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb3:892: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:feb3:892, length 32
    17:48:08.469325 ARP, Request who-has 76.151.58.184 tell 76.151.58.1, length 46
    17:48:08.498948 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:ab42: ICMP6, neighbor solicitation, who has fe80::f54f:ebff:7910:ab42, length 32
    17:48:08.499947 ARP, Request who-has 73.245.125.64 tell 73.245.124.1, length 46
    17:48:08.503945 ARP, Request who-has 96.70.22.4 tell 96.70.22.1, length 46
    17:48:08.509194 ARP, Request who-has 69.244.94.35 tell 69.244.94.1, length 46
    17:48:08.554949 ARP, Request who-has 96.159.128.161 tell 96.159.128.1, length 46
    17:48:08.597949 ARP, Request who-has 73.132.81.228 tell 73.132.80.1, length 46
    17:48:08.739082 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff28:26df: ICMP6, neighbor solicitation, who has fe80::d841:5ae4:2f28:26df, length 32
    17:48:08.753450 ARP, Request who-has 23.70.189.248 tell 23.70.189.1, length 46
    17:48:08.762447 IP 208.91.175.36.http > 68.48.155.52.7336: Flags [F.], seq 0, ack 1, win 8190, length 0
    17:48:08.789449 ARP, Request who-has 69.140.212.124 tell 69.140.212.1, length 46
    17:48:08.807700 ARP, Request who-has 73.132.83.185 tell 73.132.80.1, length 46
    17:48:08.842573 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffd9:cb14: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fed9:cb14, length 32
    17:48:08.851447 ARP, Request who-has 68.33.165.44 tell 68.33.164.1, length 46
    17:48:08.875574 IP 97.125.108.193.56857 > 68.48.155.52.8022: Flags [P.], ack 1, win 8192, options [nop,nop,TS val 1604730636 ecr 3507339575], length 64
    17:48:08.899075 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff75:dd74: ICMP6, neighbor solicitation, who has fe80::6c6e:d888:4775:dd74, length 32
    17:48:08.909448 ARP, Request who-has 73.128.80.50 tell 73.128.80.1, length 46
    17:48:08.967576 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff09:cd05: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:fe09:cd05, length 32
    17:48:08.971697 ARP, Request who-has 76.21.166.45 tell 76.21.166.1, length 46
    17:48:08.999218 IP6 fe80::201:5cff:fe22:1281 > ff02::1: ICMP6, router advertisement, length 80
    17:48:09.111970 ARP, Request who-has 73.132.85.101 tell 73.132.80.1, length 46
    17:48:09.179201 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffee:e44c: ICMP6, neighbor solicitation, who has fe80::7ae7:d1ff:feee:e44c, length 32
    17:48:09.182700 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffd9:cb50: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fed9:cb50, length 32
    17:48:09.208951 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb1:b473: ICMP6, neighbor solicitation, who has fe80::ec7f:aded:74b1:b473, length 32
    17:48:09.221705 ARP, Request who-has 73.132.252.71 tell 73.132.248.1, length 46
    17:48:09.282709 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fff8:eb9b: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fef8:eb9b, length 32
    17:48:09.327972 ARP, Request who-has 69.244.94.219 tell 69.244.94.1, length 46
    17:48:09.383407 ARP, Request who-has 68.33.165.239 tell 68.33.164.1, length 46
    17:48:09.392840 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff8c:8810: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:ceff:fe8c:8810, length 32
    17:48:09.410093 ARP, Request who-has 69.250.36.252 tell 69.250.36.1, length 46
    17:48:09.417476 ARP, Request who-has 96.159.227.215 tell 96.159.224.1, length 46
    17:48:09.476843 ARP, Request who-has 73.135.81.61 tell 73.135.80.1, length 46
    17:48:09.526093 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff50:afaf: ICMP6, neighbor solicitation, who has fe80::6587:8f0c:e050:afaf, length 32
    17:48:09.560590 ARP, Request who-has 69.138.93.132 tell 69.138.93.1, length 46
    17:48:09.573095 IP 108.160.160.165.http > 68.48.155.52.15197: Flags [P.], ack 1, win 83, options [nop,nop,TS val 2887056744 ecr 392569968], length 179
    17:48:09.587969 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:09.642076 ARP, Request who-has 73.132.253.236 tell 73.132.248.1, length 46
    17:48:09.652823 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff4c:ae67: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fe4c:ae67, length 32
    17:48:11.928966 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffbc:6d36: ICMP6, neighbor solicitation, who has fe80::e941:b200:74bc:6d36, length 32
    17:48:11.969696 ARP, Request who-has 76.21.134.72 tell 76.21.128.1, length 46
    17:48:12.011448 IP6 fe80::201:5cff:fe22:1281 > ff02::1: ICMP6, router advertisement, length 80
    17:48:12.012569 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffa3:b740: ICMP6, neighbor solicitation, who has fe80::bc19:6f47:66a3:b740, length 32
    17:48:12.012585 ARP, Request who-has 68.48.154.147 tell 68.48.154.1, length 46
    17:48:12.066569 ARP, Request who-has 69.138.93.233 tell 69.138.93.1, length 46
    17:48:12.119214 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffcf:4c15: ICMP6, neighbor solicitation, who has fe80::e06c:212f:47cf:4c15, length 32
    17:48:12.180861 ARP, Request who-has 73.132.255.250 tell 73.132.248.1, length 46
    17:48:12.346431 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff96:c279: ICMP6, neighbor solicitation, who has fe80::889a:5f6c:e96:c279, length 32
    17:48:12.347606 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffbb:8bd5: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:febb:8bd5, length 32
    17:48:12.347643 ARP, Request who-has 68.48.14.32 tell 68.48.14.1, length 46
    17:48:12.416736 ARP, Request who-has 69.244.94.219 tell 69.244.94.1, length 46
    17:48:12.452536 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffe2:252a: ICMP6, neighbor solicitation, who has fe80::219a:6cd9:2e2:252a, length 32
    17:48:12.473373 ARP, Request who-has 76.21.131.202 tell 76.21.128.1, length 46
    17:48:12.495123 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffbc:85f6: ICMP6, neighbor solicitation, who has fe80::2e76:8aff:febc:85f6, length 32
    17:48:12.495577 ARP, Request who-has 96.159.224.85 tell 96.159.224.1, length 46
    17:48:12.509099 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:ab42: ICMP6, neighbor solicitation, who has fe80::f54f:ebff:7910:ab42, length 32
    17:48:12.510352 ARP, Request who-has 73.132.252.71 tell 73.132.248.1, length 46
    17:48:12.547956 ARP, Request who-has 69.140.213.113 tell 69.140.212.1, length 46
    17:48:12.583204 ARP, Request who-has 68.50.234.26 tell 68.50.232.1, length 46
    17:48:12.599697 ARP, Request who-has 73.132.85.17 tell 73.132.80.1, length 46
    17:48:12.612943 IP 108.160.160.165.http > 68.48.155.52.13355: Flags [P.], ack 1, win 83, options [nop,nop,TS val 2887057504 ecr 182271951], length 179
    17:48:12.670944 ARP, Request who-has 69.143.255.193 tell 69.143.255.1, length 46
    17:48:12.709317 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc8:2f1d: ICMP6, neighbor solicitation, who has fe80::13a:e4bd:68c8:2f1d, length 32
    17:48:12.719193 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffaf:7d74: ICMP6, neighbor solicitation, who has fe80::9a4b:e1ff:feaf:7d74, length 32
    17:48:12.768818 ARP, Request who-has 69.250.39.85 tell 69.250.39.1, length 46
    17:48:12.789442 ARP, Request who-has 73.132.252.219 tell 73.132.248.1, length 46
    17:48:12.798943 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff40:b6b5: ICMP6, neighbor solicitation, who has fe80::b829:574b:e440:b6b5, length 32
    17:48:12.809192 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff88:cbbe: ICMP6, neighbor solicitation, who has fe80::2860:48cd:4588:cbbe, length 32
    17:48:12.919319 ARP, Request who-has 76.151.58.138 tell 76.151.58.1, length 46
    17:48:12.929068 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffbc:6d36: ICMP6, neighbor solicitation, who has fe80::e941:b200:74bc:6d36, length 32
    17:48:13.011200 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffa3:b740: ICMP6, neighbor solicitation, who has fe80::bc19:6f47:66a3:b740, length 32
    17:48:13.077272 ARP, Request who-has 76.21.135.146 tell 76.21.128.1, length 46
    17:48:13.077613 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff1e:6e8d: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:fe1e:6e8d, length 32
    17:48:13.079341 ARP, Request who-has 69.143.255.152 tell 69.143.255.1, length 46
    17:48:13.087192 ARP, Request who-has 73.132.85.241 tell 73.132.80.1, length 46
    17:48:13.112985 ARP, Request who-has 73.129.106.251 tell 73.129.106.1, length 46
    17:48:13.119105 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffcf:4c15: ICMP6, neighbor solicitation, who has fe80::e06c:212f:47cf:4c15, length 32
    17:48:13.131597 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc6:1a9e: ICMP6, neighbor solicitation, who has fe80::3137:f58c:36c6:1a9e, length 32
    17:48:13.157456 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff7b:8aa7: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe7b:8aa7, length 32
    17:48:13.189577 ARP, Request who-has 76.21.134.250 tell 76.21.128.1, length 46
    17:48:13.222335 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc5:4f5c: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fec5:4f5c, length 32
    17:48:13.252454 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb3:cd6: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:feb3:cd6, length 32
    17:48:13.339330 ARP, Request who-has 69.140.215.250 tell 69.140.212.1, length 46
    17:48:13.359588 IP 173.194.43.22.https > 68.48.155.52.15802: Flags [P.], ack 1, win 1400, options [nop,nop,TS val 630737156 ecr 182277980], length 55
    17:48:13.395832 ARP, Request who-has 73.132.253.152 tell 73.132.248.1, length 46
    17:48:13.462329 ARP, Request who-has 74.146.143.155 tell 74.146.143.1, length 46
    17:48:13.478954 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffbc:85f6: ICMP6, neighbor solicitation, who has fe80::2e76:8aff:febc:85f6, length 32
    17:48:13.497455 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff31:48b5: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe31:48b5, length 32
    17:48:13.519604 IP 69.171.248.16.https > 68.48.155.52.13449: Flags [P.], ack 1771718455, win 181, options [nop,nop,TS val 955790016 ecr 392564464], length 387
    17:48:13.622214 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb0:2c87: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:feb0:2c87, length 32
    17:48:13.686082 ARP, Request who-has 76.21.131.12 tell 76.21.128.1, length 46
    17:48:13.692204 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffad:c42: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fead:c42, length 32
    17:48:13.697954 ARP, Request who-has 96.159.224.117 tell 96.159.224.1, length 46
    17:48:13.709204 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc8:2f1d: ICMP6, neighbor solicitation, who has fe80::13a:e4bd:68c8:2f1d, length 32
    17:48:13.719078 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffaf:7d74: ICMP6, neighbor solicitation, who has fe80::9a4b:e1ff:feaf:7d74, length 32
    17:48:13.735952 IP 97.125.108.193.56857 > 68.48.155.52.8022: Flags [P.], ack 1, win 8192, options [nop,nop,TS val 1604735425 ecr 3507339575], length 64
    17:48:13.752704 ARP, Request who-has 76.21.128.127 tell 76.21.128.1, length 46
    17:48:13.783207 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:958: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fe10:958, length 32
    17:48:13.869580 ARP, Request who-has 73.132.253.104 tell 73.132.248.1, length 46
    17:48:13.959831 ARP, Request who-has 73.132.84.109 tell 73.132.80.1, length 46
    17:48:13.979206 ARP, Request who-has 76.151.58.184 tell 76.151.58.1, length 46
    17:48:13.982327 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffd9:cf10: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fed9:cf10, length 32
    17:48:14.000580 ARP, Request who-has 73.132.251.148 tell 73.132.248.1, length 46
    17:48:14.011329 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffa3:b740: ICMP6, neighbor solicitation, who has fe80::bc19:6f47:66a3:b740, length 32
    17:48:14.017703 IP 73.129.106.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 306
    17:48:14.069714 ARP, Request who-has 68.50.234.75 tell 68.50.232.1, length 46
    17:48:14.129299 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc6:1a9e: ICMP6, neighbor solicitation, who has fe80::3137:f58c:36c6:1a9e, length 32
    17:48:14.144276 ARP, Request who-has 68.50.235.106 tell 68.50.232.1, length 46
    17:48:14.149107 ARP, Request who-has 98.47.121.8 tell 98.47.121.1, length 46
    17:48:14.197214 IP 204.232.150.63.http > 68.48.155.52.43409: Flags [F.], seq 975048260, ack 1578453613, win 8273, options [nop,nop,TS val 569086910 ecr 182273072], length 0
    17:48:14.201205 IP 204.232.150.63.http > 68.48.155.52.23698: Flags [F.], seq 3853289778, ack 2306751934, win 8163, options [nop,nop,TS val 569086914 ecr 182273076], length 0
    17:48:14.208204 IP 204.232.150.63.http > 68.48.155.52.17900: Flags [F.], seq 580536805, ack 916038199, win 7820, options [nop,nop,TS val 569086920 ecr 182273081], length 0
    17:48:14.213837 IP 204.232.150.63.http > 68.48.155.52.6421: Flags [F.], seq 2453619885, ack 19772434, win 5153, options [nop,nop,TS val 569086926 ecr 182273087], length 0
    17:48:14.214820 IP 204.232.150.63.http > 68.48.155.52.2620: Flags [F.], seq 1049280173, ack 1312288235, win 8147, options [nop,nop,TS val 569086926 ecr 182273086], length 0
    17:48:14.230575 ARP, Request who-has 69.143.255.152 tell 69.143.255.1, length 46
    17:48:14.231567 ARP, Request who-has 68.33.165.136 tell 68.33.164.1, length 46
    17:48:14.303457 ARP, Request who-has 73.132.82.238 tell 73.132.80.1, length 46
    17:48:14.313069 ARP, Request who-has 73.128.80.109 tell 73.128.80.1, length 46
    17:48:14.326195 ARP, Request who-has 76.21.133.108 tell 76.21.128.1, length 46
    17:48:14.350445 ARP, Request who-has 98.47.131.27 tell 98.47.131.1, length 46
    17:48:14.372196 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff7b:abb3: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe7b:abb3, length 32
    17:48:14.379194 ARP, Request who-has 76.151.58.184 tell 76.151.58.1, length 46
    17:48:14.388075 IP 204.232.150.63.http > 68.48.155.52.18592: Flags [F.], seq 681242843, ack 3147457817, win 7349, options [nop,nop,TS val 569087100 ecr 182273253], length 0
    17:48:14.419448 ARP, Request who-has 76.21.129.212 tell 76.21.128.1, length 46
    17:48:14.487570 ARP, Request who-has 69.140.213.119 tell 69.140.212.1, length 46
    17:48:14.586913 ARP, Request who-has 68.50.234.16 tell 68.50.232.1, length 46
    17:48:14.592862 ARP, Request who-has 69.250.36.168 tell 69.250.36.1, length 46
    17:48:14.604491 ARP, Request who-has 73.132.86.90 tell 73.132.80.1, length 46
    17:48:14.616968 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff77:c098: ICMP6, neighbor solicitation, who has fe80::f8e6:7fdb:2377:c098, length 32
    17:48:14.662349 ARP, Request who-has 96.159.129.17 tell 96.159.128.1, length 46
    17:48:14.697101 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffac:d4d: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:feac:d4d, length 32
    17:48:14.739726 ARP, Request who-has 96.201.244.184 tell 96.201.244.1, length 46
    17:48:14.794348 IP 208.91.175.36.http > 68.48.155.52.7336: Flags [F.], seq 0, ack 1, win 8190, length 0
    17:48:14.796088 ARP, Request who-has 73.132.255.1 tell 73.132.248.1, length 46
    17:48:17.039217 ARP, Request who-has 96.159.224.16 tell 96.159.224.1, length 46
    17:48:17.051824 ARP, Request who-has 73.132.82.1 tell 73.132.80.1, length 46
    17:48:17.086965 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff98:f5fc: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:218:68ff:fe98:f5fc, length 32
    17:48:17.137955 IP 173.194.76.125.jabber-client > 68.48.155.52.16260: Flags [P.], ack 4268834270, win 1002, options [nop,nop,TS val 3145789386 ecr 392471642], length 37
    17:48:17.158950 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff98:ca0e: ICMP6, neighbor solicitation, who has fe80::d157:bf8:f998:ca0e, length 32
    17:48:17.189337 ARP, Request who-has 68.50.235.106 tell 68.50.232.1, length 46
    17:48:17.195950 ARP, Request who-has 73.137.142.47 tell 73.137.142.1, length 46
    17:48:17.227221 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff78:d9e: ICMP6, neighbor solicitation, who has fe80::748e:b8b7:3278:d9e, length 32
    17:48:17.228950 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff74:4165: ICMP6, neighbor solicitation, who has fe80::7cb3:8bd6:da74:4165, length 32
    17:48:17.229824 ARP, Request who-has 98.47.131.27 tell 98.47.131.1, length 46
    17:48:17.299204 ARP, Request who-has 76.21.133.108 tell 76.21.128.1, length 46
    17:48:17.327458 ARP, Request who-has 69.140.215.144 tell 69.140.212.1, length 46
    17:48:17.329197 ARP, Request who-has 73.128.80.109 tell 73.128.80.1, length 46
    17:48:17.413482 ARP, Request who-has 68.50.234.75 tell 68.50.232.1, length 46
    17:48:17.414613 ARP, Request who-has 73.235.159.181 tell 73.235.159.1, length 46
    17:48:17.414629 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb3:f91: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:feb3:f91, length 32
    17:48:17.416950 IP 173.194.76.125.jabber-client > 68.48.155.52.16260: Flags [P.], ack 1, win 1002, options [nop,nop,TS val 3145789665 ecr 392471642], length 37
    17:48:17.429109 ARP, Request who-has 76.21.134.250 tell 76.21.128.1, length 46
    17:48:17.459222 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff12:90d1: ICMP6, neighbor solicitation, who has fe80::1ec1:deff:fe12:90d1, length 32
    17:48:17.475339 ARP, Request who-has 73.132.253.243 tell 73.132.248.1, length 46
    17:48:17.558963 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff50:afaf: ICMP6, neighbor solicitation, who has fe80::6587:8f0c:e050:afaf, length 32
    17:48:17.591962 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:17.597329 IP 204.232.150.63.http > 68.48.155.52.43409: Flags [F.], seq 0, ack 1, win 8273, options [nop,nop,TS val 569090310 ecr 182273072], length 0
    17:48:17.600953 IP 204.232.150.63.http > 68.48.155.52.23698: Flags [F.], seq 0, ack 1, win 8163, options [nop,nop,TS val 569090314 ecr 182273076], length 0
    17:48:17.607832 IP 204.232.150.63.http > 68.48.155.52.17900: Flags [F.], seq 0, ack 1, win 7820, options [nop,nop,TS val 569090320 ecr 182273081], length 0
    17:48:17.614329 IP 204.232.150.63.http > 68.48.155.52.2620: Flags [F.], seq 0, ack 1, win 8147, options [nop,nop,TS val 569090326 ecr 182273086], length 0
    17:48:17.615328 IP 204.232.150.63.http > 68.48.155.52.6421: Flags [F.], seq 0, ack 1, win 5153, options [nop,nop,TS val 569090326 ecr 182273087], length 0
    17:48:17.661083 ARP, Request who-has 96.159.230.22 tell 96.159.224.1, length 46
    17:48:17.717958 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff78:c3cf: ICMP6, neighbor solicitation, who has fe80::86c9:b2ff:fe78:c3cf, length 32
    17:48:17.729581 ARP, Request who-has 68.33.164.182 tell 68.33.164.1, length 46
    17:48:17.787358 IP 204.232.150.63.http > 68.48.155.52.18592: Flags [F.], seq 0, ack 1, win 7349, options [nop,nop,TS val 569090500 ecr 182273253], length 0
    17:48:17.808350 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff40:b6b5: ICMP6, neighbor solicitation, who has fe80::b829:574b:e440:b6b5, length 32
    17:48:17.826712 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff48:a8a4: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fe48:a8a4, length 32
    17:48:17.833709 ARP, Request who-has 69.140.213.210 tell 69.140.212.1, length 46
    17:48:17.939211 ARP, Request who-has 96.70.23.37 tell 96.70.22.1, length 46
    17:48:17.959709 ARP, Request who-has 76.21.129.255 tell 76.21.128.1, length 46
    17:48:17.966958 ARP, Request who-has 96.159.231.246 tell 96.159.224.1, length 46
    17:48:17.974333 IP 173.194.76.125.jabber-client > 68.48.155.52.16260: Flags [P.], ack 1, win 1002, options [nop,nop,TS val 3145790223 ecr 392471642], length 37
    17:48:18.108626 ARP, Request who-has 96.159.129.17 tell 96.159.128.1, length 46
    17:48:18.151356 ARP, Request who-has 76.21.133.33 tell 76.21.128.1, length 46
    17:48:18.159087 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff98:ca0e: ICMP6, neighbor solicitation, who has fe80::d157:bf8:f998:ca0e, length 32
    17:48:18.199215 IP6 fe80::201:5cff:fe22:1281 > ff02::1: ICMP6, router advertisement, length 80
    17:48:18.209297 ARP, Request who-has 68.48.154.100 tell 68.48.154.1, length 46
    17:48:18.219231 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff78:d9e: ICMP6, neighbor solicitation, who has fe80::748e:b8b7:3278:d9e, length 32
    17:48:18.272355 ARP, Request who-has 96.139.43.197 tell 96.139.42.1, length 46
    17:48:18.392842 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffd9:c38e: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fed9:c38e, length 32
    17:48:18.421959 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffd9:23b1: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fed9:23b1, length 32
    17:48:18.423709 ARP, Request who-has 73.132.248.69 tell 73.132.248.1, length 46
    17:48:18.431459 ARP, Request who-has 76.21.132.35 tell 76.21.128.1, length 46
    17:48:18.513210 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:ab42: ICMP6, neighbor solicitation, who has fe80::f54f:ebff:7910:ab42, length 32
    17:48:18.558961 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff50:afaf: ICMP6, neighbor solicitation, who has fe80::6587:8f0c:e050:afaf, length 32
    17:48:18.576209 ARP, Request who-has 73.128.83.93 tell 73.128.80.1, length 46
    17:48:18.589207 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:18.596957 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc5:6312: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fec5:6312, length 32
    17:48:18.625087 ARP, Request who-has 69.140.213.210 tell 69.140.212.1, length 46
    17:48:18.639207 ARP, Request who-has 96.70.23.11 tell 96.70.22.1, length 46
    17:48:18.710210 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc8:2f1d: ICMP6, neighbor solicitation, who has fe80::13a:e4bd:68c8:2f1d, length 32
    17:48:18.719835 ARP, Request who-has 96.217.123.246 tell 96.217.123.1, length 46
    17:48:18.742709 ARP, Request who-has 96.70.22.156 tell 96.70.22.1, length 46
    17:48:18.801714 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff40:b6b5: ICMP6, neighbor solicitation, who has fe80::b829:574b:e440:b6b5, length 32
    17:48:18.886583 ARP, Request who-has 96.139.42.108 tell 96.139.42.1, length 46
    17:48:18.889074 ARP, Request who-has 76.21.130.116 tell 76.21.128.1, length 46
    17:48:18.900825 ARP, Request who-has 73.132.87.141 tell 73.132.80.1, length 46
    17:48:18.959326 ARP, Request who-has 73.135.80.36 tell 73.135.80.1, length 46
    17:48:18.989200 ARP, Request who-has 73.132.252.71 tell 73.132.248.1, length 46
    17:48:19.008325 ARP, Request who-has 76.21.132.50 tell 76.21.128.1, length 46
    17:48:19.069351 ARP, Request who-has 69.143.255.152 tell 69.143.255.1, length 46
    17:48:19.071829 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff8d:e15f: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:fe8d:e15f, length 32
    17:48:19.081455 ARP, Request who-has 73.135.81.213 tell 73.135.80.1, length 46
    17:48:19.089948 IP 173.194.76.125.jabber-client > 68.48.155.52.16260: Flags [P.], ack 1, win 1002, options [nop,nop,TS val 3145791339 ecr 392471642], length 37
    17:48:19.096574 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb0:80b1: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:feb0:80b1, length 32
    17:48:19.134092 ARP, Request who-has 68.48.155.215 tell 68.48.154.1, length 46
    17:48:19.169204 ARP, Request who-has 98.47.40.53 tell 98.47.40.1, length 46
    17:48:19.203461 ARP, Request who-has 96.159.128.224 tell 96.159.128.1, length 46
    17:48:19.218955 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff78:d9e: ICMP6, neighbor solicitation, who has fe80::748e:b8b7:3278:d9e, length 32
    17:48:19.239238 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff6a:b3d5: ICMP6, neighbor solicitation, who has fe80::b0c8:3c93:506a:b3d5, length 32
    17:48:19.289604 ARP, Request who-has 73.132.84.215 tell 73.132.80.1, length 46
    17:48:19.301960 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff8c:213f: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:fe8c:213f, length 32
    17:48:19.307461 ARP, Request who-has 68.50.235.83 tell 68.50.232.1, length 46
    17:48:19.315832 ARP, Request who-has 76.151.58.138 tell 76.151.58.1, length 46
    17:48:19.329334 ARP, Request who-has 96.70.23.113 tell 96.70.22.1, length 46
    17:48:19.336712 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffbc:c069: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:febc:c069, length 32
    17:48:19.353712 ARP, Request who-has 96.70.22.67 tell 96.70.22.1, length 46
    17:48:19.369459 ARP, Request who-has 69.140.215.253 tell 69.140.212.1, length 46
    17:48:19.512276 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff22:5b49: ICMP6, neighbor solicitation, who has fe80::5604:a6ff:fe22:5b49, length 32
    17:48:19.512583 ARP, Request who-has 73.132.248.69 tell 73.132.248.1, length 46
    17:48:19.512594 ARP, Request who-has 73.128.80.100 tell 73.128.80.1, length 46
    17:48:19.512598 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff10:ab42: ICMP6, neighbor solicitation, who has fe80::f54f:ebff:7910:ab42, length 32
    17:48:19.512615 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffdd:428a: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fedd:428a, length 32
    17:48:19.549215 ARP, Request who-has 68.33.164.182 tell 68.33.164.1, length 46
    17:48:19.587086 ARP, Request who-has 96.159.128.94 tell 96.159.128.1, length 46
    17:48:19.588827 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fffe:c22e: ICMP6, neighbor solicitation, who has fe80::7158:a0b3:6efe:c22e, length 32
    17:48:19.631840 ARP, Request who-has 73.132.84.62 tell 73.132.80.1, length 46
    17:48:19.667837 IP 173.252.110.27.http > 68.48.155.52.54418: Flags [F.], seq 4243209529, ack 3843342176, win 34, options [nop,nop,TS val 4094500237 ecr 182223985], length 0
    17:48:19.669578 ARP, Request who-has 68.48.154.147 tell 68.48.154.1, length 46
    17:48:19.674831 IP 173.252.110.27.http > 68.48.155.52.57754: Flags [F.], seq 4258383674, ack 3610175037, win 34, options [nop,nop,TS val 4094532387 ecr 182223990], length 0
    17:48:19.708835 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc8:2f1d: ICMP6, neighbor solicitation, who has fe80::13a:e4bd:68c8:2f1d, length 32
    17:48:19.759214 ARP, Request who-has 96.159.225.82 tell 96.159.224.1, length 46
    17:48:19.799083 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff40:b6b5: ICMP6, neighbor solicitation, who has fe80::b829:574b:e440:b6b5, length 32
    17:48:19.802830 ARP, Request who-has 73.132.253.78 tell 73.132.248.1, length 46
    17:48:19.872278 ARP, Request who-has 96.159.227.83 tell 96.159.224.1, length 46
    17:48:19.896332 IP 173.252.110.27.http > 68.48.155.52.54418: Flags [F.], seq 0, ack 1, win 34, options [nop,nop,TS val 4094500466 ecr 182223985], length 0
    17:48:19.910963 IP 173.252.110.27.http > 68.48.155.52.57754: Flags [F.], seq 0, ack 1, win 34, options [nop,nop,TS val 4094532624 ecr 182223990], length 0
    17:48:22.106598 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff2a:47dd: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:fe2a:47dd, length 32
    17:48:22.124581 ARP, Request who-has 73.128.81.74 tell 73.128.80.1, length 46
    17:48:22.149209 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffea:a7ca: ICMP6, neighbor solicitation, who has fe80::f961:5ae5:6eea:a7ca, length 32
    17:48:22.240595 ARP, Request who-has 73.132.80.196 tell 73.132.80.1, length 46
    17:48:22.269456 ARP, Request who-has 96.70.22.67 tell 96.70.22.1, length 46
    17:48:22.319351 ARP, Request who-has 96.70.23.113 tell 96.70.22.1, length 46
    17:48:22.445355 ARP, Request who-has 96.159.128.47 tell 96.159.128.1, length 46
    17:48:22.507608 ARP, Request who-has 68.33.164.182 tell 68.33.164.1, length 46
    17:48:22.511961 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff41:43e: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:cfff:fe41:43e, length 32
    17:48:22.522468 ARP, Request who-has 76.151.58.138 tell 76.151.58.1, length 46
    17:48:22.553719 ARP, Request who-has 73.137.142.23 tell 73.137.142.1, length 46
    17:48:22.619096 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fff8:e9f8: ICMP6, neighbor solicitation, who has fe80::b6b5:2fff:fef8:e9f8, length 32
    17:48:22.629087 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff77:c098: ICMP6, neighbor solicitation, who has fe80::f8e6:7fdb:2377:c098, length 32
    17:48:22.639210 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff8a:b658: ICMP6, neighbor solicitation, who has fe80::fd83:ffd4:2e8a:b658, length 32
    17:48:22.661591 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fff5:4738: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:216:92ff:fef5:4738, length 32
    17:48:22.736340 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff31:676c: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe31:676c, length 32
    17:48:22.741586 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb3:637d: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:feb3:637d, length 32
    17:48:22.758216 ARP, Request who-has 96.159.229.149 tell 96.159.224.1, length 46
    17:48:22.821255 IP 208.91.175.36.http > 68.48.155.52.7336: Flags [F.], seq 0, ack 1, win 8190, length 0
    17:48:22.874093 ARP, Request who-has 73.132.80.132 tell 73.132.80.1, length 46
    17:48:22.900836 ARP, Request who-has 68.50.234.8 tell 68.50.232.1, length 46
    17:48:22.955081 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff82:8cc6: ICMP6, neighbor solicitation, who has fe80::d0c1:8015:6182:8cc6, length 32
    17:48:22.969330 ARP, Request who-has 96.159.227.83 tell 96.159.224.1, length 46
    17:48:22.976204 ARP, Request who-has 98.47.118.196 tell 98.47.118.1, length 46
    17:48:22.983203 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffee:c38c: ICMP6, neighbor solicitation, who has fe80::b4b9:3943:e8ee:c38c, length 32
    17:48:23.043330 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff6c:5362: ICMP6, neighbor solicitation, who has fe80::22aa:4bff:fe6c:5362, length 32
    17:48:23.049205 ARP, Request who-has 68.33.164.182 tell 68.33.164.1, length 46
    17:48:23.110330 IP 173.252.110.27.http > 68.48.155.52.54418: Flags [F.], seq 0, ack 1, win 34, options [nop,nop,TS val 4094503680 ecr 182223985], length 0
    17:48:23.119353 ARP, Request who-has 76.21.129.212 tell 76.21.128.1, length 46
    17:48:23.149216 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffea:a7ca: ICMP6, neighbor solicitation, who has fe80::f961:5ae5:6eea:a7ca, length 32
    17:48:23.167594 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff75:6fd3: ICMP6, neighbor solicitation, who has fe80::21f0:c95b:cb75:6fd3, length 32
    17:48:23.182963 ARP, Request who-has 73.137.142.99 tell 73.137.142.1, length 46
    17:48:23.227966 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffdd:887e: ICMP6, neighbor solicitation, who has fe80::c2c1:c0ff:fedd:887e, length 32
    17:48:23.229830 ARP, Request who-has 69.143.255.152 tell 69.143.255.1, length 46
    17:48:23.235085 IP 173.252.110.27.http > 68.48.155.52.57754: Flags [F.], seq 0, ack 1, win 34, options [nop,nop,TS val 4094535948 ecr 182223990], length 0
    17:48:23.236331 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffb0:a3f4: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:feb0:a3f4, length 32
    17:48:23.269583 ARP, Request who-has 68.48.14.244 tell 68.48.14.1, length 46
    17:48:23.299494 ARP, Request who-has 73.128.80.109 tell 73.128.80.1, length 46
    17:48:23.360603 IP 173.194.43.22.https > 68.48.155.52.15802: Flags [P.], ack 1, win 1400, options [nop,nop,TS val 630747156 ecr 182277980], length 55
    17:48:23.495595 ARP, Request who-has 73.132.255.194 tell 73.132.248.1, length 46
    17:48:23.510215 ARP, Request who-has 73.132.84.132 tell 73.132.80.1, length 46
    17:48:23.573097 IP 173.252.110.27.https > 68.48.155.52.47128: Flags [FP.], seq 4199784415:4199784479, ack 2754966691, win 46, options [nop,nop,TS val 4093480760 ecr 182224596], length 64
    17:48:23.618968 IP6 fe80::201:5cff:fe22:1281 > ff02::1:fff8:e9f8: ICMP6, neighbor solicitation, who has fe80::b6b5:2fff:fef8:e9f8, length 32
    17:48:23.621465 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff82:544: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d1ff:fe82:544, length 32
    17:48:23.629089 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff77:c098: ICMP6, neighbor solicitation, who has fe80::f8e6:7fdb:2377:c098, length 32
    17:48:23.629965 ARP, Request who-has 98.47.121.78 tell 98.47.121.1, length 46
    17:48:23.701217 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff6a:a29b: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:a4ff:fe6a:a29b, length 32
    17:48:23.728338 ARP, Request who-has 98.47.40.171 tell 98.47.40.1, length 46
    17:48:23.739213 ARP, Request who-has 69.140.213.210 tell 69.140.212.1, length 46
    17:48:23.807713 ARP, Request who-has 96.159.128.10 tell 96.159.128.1, length 46
    17:48:23.820934 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ffc5:2724: ICMP6, neighbor solicitation, who has 2001:558:4083:2d:215:d0ff:fec5:2724, length 32
    17:48:23.949223 IP6 fe80::201:5cff:fe22:1281 > ff02::1:ff82:8cc6: ICMP6, neighbor solicitation, who has fe80::d0c1:8015:6182:8cc6, length 32

    Going to throw 2.0.1 onto an entirely new box now and see if there's any change.

    Any more debug info I should be gathering? More detailed tcpdump (to a binary file)



  • Wow, I'm running out of things to change here.

    New box, new USB (SiiG) ethernet adaptor on wan side, new cablemodem (SB6141), new Ethernet cable.
    I've tried 2.0.1, 2.0.2, 2.0.3, 2.1-PRE all with the same outcome.

    Latest iteration is 2.0.1, freshly installed onto a new USB stick.

    Packet capture: http://www.tubas.net/pf/ue0.pcap
    System Log excerpt: http://www.tubas.net/pf/ue0_fail_system.log
    (these overlap, but aren't exact)

    The only thing I can think of that might at this point be polluting this would be my configuration backup. Is there anything in there that could be affecting this? I've restored it to the new system whenever I've had to start from scratch.



  • The packet capture shows bursts of DHCP requests going out at intervals of a few microsoeconds but the system logs shows a most two in  burst.

    The packet capture shows DHCP replies and the system log shows dhclient exiting at the "same time" (but the granularity of the system log timestamp is not sufficiently fine). My suspicion is that dhclient is provoked into exiting by something in the DHCP reply. That dhclient sends some requests suggests to me the configuration file is probably OK UNLESS the problem is caused when dhclient tries to act on the reply using something from the configuration file.

    dhclint has its standard output redirected to /tmp/ue0_output and its output redirected to /tmp/ue0_error_output. (Presumably stdout should be redirected to the first file and stderr to the second file.) Please post the contents of these files.

    In a further attempt to capture what could be causing the problem, I suggest you
    1. Capture the contents of pfSense file /var/etc/dhclient_wan.conf
    2. Change the WAN interface type from DHCP to None
    3. Reboot
    4. Start a packet capture on the WAN interface, highly detailed and filtering on port 67 (DHCP traffic only)
    5. In a SSH session to your pfSense box check the file /var/etc/dhclient_wan.conf hasn't changed (if it has, restore it) then issue the shell command /sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 and capture the output.



  • Noted.

    I just did a 100% new built using the latest 2.1 snapshot. Didn't bring in any config from the old install - I only have a handful of NATs so not a big deal to recreate. We'll see if there's any change here.



  • Another failure…but this time different output.

    And, I relized I've been crapping up multiple threads  :-[ with this, so since I'm back on 2.1, I put the latest into over there:

    http://forum.pfsense.org/index.php/topic,58819.0.html



  • In my opinion, here is no dhcp issue.
    My wan connection failed with static address too in the same way (wan interface detached/connected again and again).
    Only apply/reset filter works. (My script does it for now)

    It can be kernel issue. Is it?

    P.s. my LAN/wan interfaces are build-in , so can't being detached



  • Has there been any updates to this issue?

    I'm a newbie (less than a month) to pfSense and I'm having similar problems on 2.0.2.  I lose my WAN connection at least once a day and the logs seem to indicate a DHCP failure. A simple "renew" restores connectivity. It doesn't appear that anyone has posted to this thread for the last month so I'm wondering if the issue was resolved in a "snap" or if the work-around script is the way to go (for now).



  • I ended up abandoning ship - replaced it with an AirPort Extreme. I miss all the features of pfSense, but got tired of fiddling with it. Perhaps I will try again on the future.



  • I had a similar problem that I resolved by changing the gateway monitor IP to Google's DNS servers (8.8.8.8).  Haven't had an issue since.


Log in to reply