Need help interpreting some log entries please…



  • I'm not sure if this is a hardware issue or if pfSense caught my cable modem rebooting early this morning but if anyone doesn't mind would you give me your opinion(s).

    System Specs:
    CPU: AMD Athlon™ II X2 245 Processor
    real memory = 4294967296 (4096 MB)
    WAN (nfe0): NVIDIA nForce MCP61 Networking Adapter
    LAN(msk0): Marvell Yukon 88E8053 Gigabit Ethernet

    http://pastebin.com/LvjY7ife

    
    Jan 3 08:34:37	check_reload_status: Linkup starting nfe0
    Jan 3 08:34:37	kernel: nfe0: link state changed to DOWN
    Jan 3 08:34:39	php: : DEVD Ethernet detached event for wan
    Jan 3 08:34:39	dhclient[6997]: connection closed
    Jan 3 08:34:39	dhclient[6997]: connection closed
    Jan 3 08:34:39	dhclient[6997]: exiting.
    Jan 3 08:34:39	dhclient[6997]: exiting.
    Jan 3 08:34:40	dhclient: FAIL
    Jan 3 08:34:40	dhclient: FAIL
    Jan 3 08:34:40	dhclient[8944]: connection closed
    Jan 3 08:34:40	dhclient[8944]: connection closed
    Jan 3 08:34:40	dhclient[8944]: exiting.
    Jan 3 08:34:40	dhclient[8944]: exiting.
    Jan 3 08:34:40	dhclient[55981]: connection closed
    Jan 3 08:34:40	dhclient[55981]: connection closed
    Jan 3 08:34:40	dhclient[55981]: exiting.
    Jan 3 08:34:40	dhclient[55981]: exiting.
    Jan 3 08:34:41	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:41	kernel: arpresolve: can't allocate llinfo for <wan gateway="">.... <edited for="" brevity="">Jan 3 08:34:51	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:51	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:51	kernel: nfe0: link state changed to UP
    Jan 3 08:34:51	check_reload_status: Linkup starting nfe0
    Jan 3 08:34:51	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:52	kernel: arpresolve: can't allocate llinfo for <wan gateway="">.... <edited for="" brevity="">Jan 3 08:34:53	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:53	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:53	php: : DEVD Ethernet attached event for wan
    Jan 3 08:34:54	php: : HOTPLUG: Configuring interface wan
    Jan 3 08:34:54	check_reload_status: Linkup starting nfe0
    Jan 3 08:34:54	kernel: nfe0: link state changed to DOWN
    Jan 3 08:34:54	kernel: nfe0: tx v2 error 0x6400 <lastpacket>Jan 3 08:34:54	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:54	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:34:55	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:55	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:56	php: : DEVD Ethernet detached event for wan
    Jan 3 08:34:56	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:56	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:34:57	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:57	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:57	kernel: nfe0: link state changed to UP
    Jan 3 08:34:57	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:58	dhclient: PREINIT
    Jan 3 08:34:58	dhclient[51104]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:34:58	dhclient[51104]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:34:58	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:58	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:34:58	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:58	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:59	dhclient[51104]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:34:59	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:34:59	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:00	dhclient[51104]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:35:00	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:00	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:35:01	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:01	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:02	dhclient[51104]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:35:02	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:02	dhclient[51104]: DHCPNAK from 192.168.100.1
    Jan 3 08:35:02	dhclient[51104]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 2
    Jan 3 08:35:02	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:02	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:35:02	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:03	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:03	dhclient[51104]: DHCPOFFER from 192.168.100.1
    Jan 3 08:35:03	dhclient: ARPSEND
    Jan 3 08:35:04	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:04	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:35:04	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:04	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:05	dhclient: ARPCHECK
    Jan 3 08:35:05	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:05	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:05	dhclient[51104]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:35:05	dhclient[51104]: DHCPACK from 192.168.100.1
    Jan 3 08:35:05	dhclient: BOUND
    Jan 3 08:35:05	dhclient: Starting add_new_address()
    Jan 3 08:35:05	dhclient: ifconfig nfe0 inet 192.168.100.10 netmask 255.255.255.0 broadcast 192.168.100.255
    Jan 3 08:35:05	dhclient: New IP Address (nfe0): 192.168.100.10
    Jan 3 08:35:05	dhclient: New Subnet Mask (nfe0): 255.255.255.0
    Jan 3 08:35:05	dhclient: New Broadcast Address (nfe0): 192.168.100.255
    Jan 3 08:35:05	dhclient: New Routers (nfe0):
    Jan 3 08:35:05	dhclient: Adding new routes to interface: nfe0
    Jan 3 08:35:05	dhclient: Creating resolv.conf
    Jan 3 08:35:05	check_reload_status: rc.newwanip starting nfe0
    Jan 3 08:35:05	dhclient[51104]: bound to 192.168.100.10 -- renewal in 30 seconds.
    Jan 3 08:35:05	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:05	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:35:06	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:07	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:07	php: : rc.newwanip: Informational is starting nfe0.
    Jan 3 08:35:07	php: : rc.newwanip: on (IP address: 192.168.100.10) (interface: wan) (real interface: nfe0).
    Jan 3 08:35:07	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:08	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:08	dnsmasq[2248]: reading /etc/resolv.conf
    Jan 3 08:35:08	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:08	dnsmasq[2248]: using nameserver 208.67.220.220#53
    Jan 3 08:35:08	dnsmasq[2248]: using nameserver 208.67.222.222#53
    Jan 3 08:35:08	dnsmasq[2248]: ignoring nameserver 127.0.0.1 - local interface
    Jan 3 08:35:08	dnsmasq[2248]: ignoring nameserver 127.0.0.1 - local interface
    Jan 3 08:35:08	check_reload_status: Reloading filter
    Jan 3 08:35:08	apinger: Starting Alarm Pinger, apinger(57957)
    Jan 3 08:35:08	apinger: No usable targets found, exiting
    Jan 3 08:35:08	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:08	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:35:12	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:13	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:13	php: : Resyncing OpenVPN instances for interface WAN.
    Jan 3 08:35:13	php: : Creating rrd update script
    Jan 3 08:35:13	php: : pfSense package system has detected an ip change <wan ip="">-> ... Restarting packages.
    Jan 3 08:35:13	check_reload_status: Starting packages
    Jan 3 08:35:13	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:13	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:14	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:14	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:14	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:14	ntpdate[18730]: can't find host tick.usno.navy.mil
    Jan 3 08:35:14	ntpdate[18730]: no servers can be used, exiting
    Jan 3 08:35:14	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:15	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:15	php: : Restarting/Starting all packages.
    Jan 3 08:35:15	php: : [filer] filer_xmlrpc_sync.php is starting.
    Jan 3 08:35:15	php: : [filer] filer_xmlrpc_sync.php is starting.
    Jan 3 08:35:15	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:15	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:35:20	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:20	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:20	ntpdate[22113]: can't find host tick.usno.navy.mil
    Jan 3 08:35:20	ntpdate[22113]: no servers can be used, exiting
    Jan 3 08:35:20	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:21	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:35:34	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:34	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:35	dhclient[57361]: DHCPREQUEST on nfe0 to 192.168.100.1 port 67
    Jan 3 08:35:35	dhclient[57361]: DHCPACK from 192.168.100.1
    Jan 3 08:35:35	dhclient: RENEW
    Jan 3 08:35:35	dhclient: Creating resolv.conf
    Jan 3 08:35:35	dhclient[57361]: bound to 192.168.100.10 -- renewal in 30 seconds.
    Jan 3 08:35:35	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:35:36	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:36:04	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:04	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:05	dhclient[57361]: DHCPREQUEST on nfe0 to 192.168.100.1 port 67
    Jan 3 08:36:06	dhclient[57361]: DHCPREQUEST on nfe0 to 192.168.100.1 port 67
    Jan 3 08:36:06	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:08	dhclient[57361]: DHCPREQUEST on nfe0 to 192.168.100.1 port 67
    Jan 3 08:36:09	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:09	kernel: arpresolve: can't allocate llinfo for <wan gateway="">....
    Jan 3 08:36:34	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:34	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:35	dhclient[57361]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:36:35	ntpd_intres[27291]: host name not found: tick.usno.navy.mil
    Jan 3 08:36:36	dhclient: EXPIRE
    Jan 3 08:36:36	dhclient: Deleting old routes
    Jan 3 08:36:36	dhclient: PREINIT
    Jan 3 08:36:36	dhclient[57361]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 2
    Jan 3 08:36:36	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:37	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:37	dhclient[57361]: DHCPOFFER from <wan address="">Jan 3 08:36:37	dhclient: ARPSEND
    Jan 3 08:36:38	kernel: arpresolve: can't allocate llinfo for <wan gateway="">Jan 3 08:36:39	dhclient: ARPCHECK
    Jan 3 08:36:39	dhclient[57361]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67
    Jan 3 08:36:39	dhclient[57361]: DHCPACK from <wan address="">Jan 3 08:36:39	dhclient: BOUND
    Jan 3 08:36:39	dhclient: Deleting old routes
    Jan 3 08:36:39	dhclient: Starting add_new_address()
    Jan 3 08:36:39	dhclient: ifconfig nfe0 inet <wan ip="">netmask 255.255.248.0 broadcast <wan address="">Jan 3 08:36:39	dhclient: New IP Address (nfe0): <wan ip="">Jan 3 08:36:39	dhclient: New Subnet Mask (nfe0): 255.255.248.0
    Jan 3 08:36:39	dhclient: New Broadcast Address (nfe0): <wan address="">Jan 3 08:36:39	dhclient: New Routers (nfe0): <wan gateway="">Jan 3 08:36:39	dhclient: Adding new routes to interface: nfe0
    Jan 3 08:36:39	dhclient: /sbin/route add default <wan gateway="">Jan 3 08:36:39	dhclient: Creating resolv.conf
    Jan 3 08:36:39	check_reload_status: rc.newwanip starting nfe0
    Jan 3 08:36:39	dhclient[57361]: bound to <wan ip="">-- renewal in 43200 seconds.
    Jan 3 08:36:41	php: : rc.newwanip: Informational is starting nfe0.
    Jan 3 08:36:41	php: : rc.newwanip: on (IP address: <wan ip="">) (interface: wan) (real interface: nfe0).
    Jan 3 08:36:41	php: : ROUTING: setting default route to <wan gateway="">Jan 3 08:36:42	check_reload_status: Reloading filter
    Jan 3 08:36:42	apinger: Starting Alarm Pinger, apinger(55190)
    Jan 3 08:36:43	dnsmasq[2248]: reading /etc/resolv.conf
    Jan 3 08:36:43	dnsmasq[2248]: using nameserver 208.67.220.220#53
    Jan 3 08:36:43	dnsmasq[2248]: using nameserver 208.67.222.222#53
    Jan 3 08:36:43	dnsmasq[2248]: using nameserver <isp dns="">#53
    Jan 3 08:36:43	dnsmasq[2248]: using nameserver <isp dns="">#53
    Jan 3 08:36:43	dnsmasq[2248]: using nameserver <isp dns="">#53
    Jan 3 08:36:43	dnsmasq[2248]: ignoring nameserver 127.0.0.1 - local interface
    Jan 3 08:36:43	dnsmasq[2248]: ignoring nameserver 127.0.0.1 - local interface
    Jan 3 08:36:47	php: : Resyncing OpenVPN instances for interface WAN.
    Jan 3 08:36:47	php: : Creating rrd update script
    Jan 3 08:36:47	php: : pfSense package system has detected an ip change 192.168.100.10 -> ... Restarting packages.
    Jan 3 08:36:47	check_reload_status: Starting packages
    Jan 3 08:36:48	ntpdate[13332]: adjust time server 192.5.41.40 offset -0.001555 sec
    Jan 3 08:36:49	php: : Restarting/Starting all packages.
    Jan 3 08:36:49	php: : [filer] filer_xmlrpc_sync.php is starting.
    Jan 3 08:36:49	php: : [filer] filer_xmlrpc_sync.php is starting.
    Jan 3 08:37:42	apinger: Error while feeding rrdtool: Broken pipe
    Jan 3 08:38:42	apinger: rrdtool respawning too fast, waiting 300s.</isp></isp></isp></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></wan></lastpacket></wan></wan></edited></wan></wan></wan></wan></edited></wan></wan> 
    


  • Your WAN lost link (most likely because your cable modem rebooted given the other logs), and upon regaining link, you got a lease from the modem itself, the private 192.168 IP. That's what happens when your modem loses connectivity with your provider. Some kind of issue with the cable modem or provider.



  • @cmb:

    Your WAN lost link (most likely because your cable modem rebooted given the other logs), and upon regaining link, you got a lease from the modem itself, the private 192.168 IP. That's what happens when your modem loses connectivity with your provider. Some kind of issue with the cable modem or provider.

    Thanks! That's what I thought it was but I wanted a second opinion. I'm not confident yet at interpreting the log files.



  • Check http://redmine.pfsense.org/issues/2704

    You could trying adding the "reject" directive (until a fix is included in base pfSense)


Locked