Interfaces randomly stop working
-
Hi,
everyday this happens to our firewall (pfsense 2.0.1) and I'm sick of being told by colleagues that were offline. :(I think somewhat is wrong there. I rebooted pfsense, then it works fine till at random time, then it happens again. I noticed kernel watchdog bited. But I dunno what to do/check as next?
Please look into following syslog, maybe you could help me please? I'm using loadbalancing for em0 (=WAN1) and em1 (=WAN2). Because of same Gateway of our connection to ISP WAN2 is connected over NAT (Loadbalancing doesn't work with same gateway).
If you need more information, let me know please and I'll provide you missing informations.
Syslog (I think problem begins at "Jan 20 11:39:30"):
Jan 20 11:29:06 syslogd: kernel boot file is /boot/kernel/kernel Jan 20 11:29:06 kernel: Copyright (c) 1992-2010 The FreeBSD Project. Jan 20 11:29:06 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 20 11:29:06 kernel: The Regents of the University of California. All rights reserved. Jan 20 11:29:06 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Jan 20 11:29:06 kernel: FreeBSD 8.1-RELEASE-p6 #1: Mon Dec 12 18:43:24 EST 2011 Jan 20 11:29:06 kernel: root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64 Jan 20 11:29:06 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Jan 20 11:29:06 kernel: CPU: AMD Athlon(tm) II X2 215 Processor (2700.02-MHz K8-class CPU) Jan 20 11:29:06 kernel: Origin = "AuthenticAMD" Id = 0x100f62 Family = 10 Model = 6 Stepping = 2 Jan 20 11:29:06 kernel: Features=0x178bfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,htt>Jan 20 11:29:06 kernel: Features2=0x802009 <sse3,mon,cx16,popcnt>Jan 20 11:29:06 kernel: AMD Features=0xee500800 <syscall,nx,mmx+,ffxsr,page1gb,rdtscp,lm,3dnow!+,3dnow!>Jan 20 11:29:06 kernel: AMD Features2=0x37ff <lahf,cmp,svm,extapic,cr8,abm,sse4a,mas,prefetch,osvw,ibs,skinit,wdt>Jan 20 11:29:06 kernel: TSC: P-state invariant Jan 20 11:29:06 kernel: real memory = 2147483648 (2048 MB) Jan 20 11:29:06 kernel: avail memory = 2017783808 (1924 MB) Jan 20 11:29:06 kernel: ACPI APIC Table: <011510 APIC0934> Jan 20 11:29:06 kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Jan 20 11:29:06 kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) Jan 20 11:29:06 kernel: cpu0 (BSP): APIC ID: 0 Jan 20 11:29:06 kernel: cpu1 (AP): APIC ID: 1 Jan 20 11:29:06 kernel: ioapic0 <version 1.1=""> irqs 0-23 on motherboard Jan 20 11:29:06 kernel: netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling Jan 20 11:29:06 kernel: wlan: mac acl policy registered Jan 20 11:29:06 kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. Jan 20 11:29:06 kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. Jan 20 11:29:06 kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80470e10, 0) error 1 Jan 20 11:29:06 kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/. Jan 20 11:29:06 kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf. Jan 20 11:29:06 kernel: module_register_init: MOD_LOAD (wpi_fw, 0xffffffff806548d0, 0) error 1 Jan 20 11:29:06 kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. Jan 20 11:29:06 kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. Jan 20 11:29:06 kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80470cd0, 0) error 1 Jan 20 11:29:06 kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. Jan 20 11:29:06 kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. Jan 20 11:29:06 kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80470d70, 0) error 1 Jan 20 11:29:06 kernel: kbd1 at kbdmux0 Jan 20 11:29:06 kernel: cryptosoft0: <software crypto=""> on motherboard Jan 20 11:29:06 kernel: padlock0: No ACE support. Jan 20 11:29:06 kernel: acpi0: <011510 RSDT0934> on motherboard Jan 20 11:29:06 kernel: acpi0: [ITHREAD] Jan 20 11:29:06 kernel: acpi0: Power Button (fixed) Jan 20 11:29:06 kernel: acpi0: reservation of fee01000, ff000 (3) failed Jan 20 11:29:06 kernel: acpi0: reservation of fec00000, 1000 (3) failed Jan 20 11:29:06 kernel: acpi0: reservation of fee00000, 1000 (3) failed Jan 20 11:29:06 kernel: acpi0: reservation of 0, a0000 (3) failed Jan 20 11:29:06 kernel: acpi0: reservation of 100000, 7ff00000 (3) failed Jan 20 11:29:06 kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 Jan 20 11:29:06 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x2008-0x200b on acpi0 Jan 20 11:29:06 kernel: cpu0: <acpi cpu=""> on acpi0 Jan 20 11:29:06 kernel: cpu1: <acpi cpu=""> on acpi0 Jan 20 11:29:06 kernel: acpi_hpet0: <high precision="" event="" timer=""> iomem 0xfed00000-0xfed003ff on acpi0 Jan 20 11:29:06 kernel: Timecounter "HPET" frequency 25000000 Hz quality 900 Jan 20 11:29:06 kernel: pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0 Jan 20 11:29:06 kernel: pci0: <acpi pci="" bus=""> on pcib0 Jan 20 11:29:06 kernel: pci0: <memory, ram=""> at device 0.0 (no driver attached) Jan 20 11:29:06 kernel: isab0: <pci-isa bridge=""> port 0x2f00-0x2fff at device 1.0 on pci0 Jan 20 11:29:06 kernel: isa0: <isa bus=""> on isab0 Jan 20 11:29:06 kernel: pci0: <serial bus,="" smbus=""> at device 1.1 (no driver attached) Jan 20 11:29:06 kernel: pci0: <memory, ram=""> at device 1.2 (no driver attached) Jan 20 11:29:06 kernel: pci0: <processor> at device 1.3 (no driver attached) Jan 20 11:29:06 kernel: pci0: <memory, ram=""> at device 1.4 (no driver attached) Jan 20 11:29:06 kernel: ohci0: <ohci (generic)="" usb="" controller=""> mem 0xfce7f000-0xfce7ffff irq 22 at device 2.0 on pci0 Jan 20 11:29:06 kernel: ohci0: [ITHREAD] Jan 20 11:29:06 kernel: usbus0: <ohci (generic)="" usb="" controller=""> on ohci0 Jan 20 11:29:06 kernel: ehci0: <ehci (generic)="" usb="" 2.0="" controller=""> mem 0xfce7ec00-0xfce7ecff irq 23 at device 2.1 on pci0 Jan 20 11:29:06 kernel: ehci0: [ITHREAD] Jan 20 11:29:06 kernel: usbus1: EHCI version 1.0 Jan 20 11:29:06 kernel: usbus1: <ehci (generic)="" usb="" 2.0="" controller=""> on ehci0 Jan 20 11:29:06 kernel: ohci1: <ohci (generic)="" usb="" controller=""> mem 0xfce7d000-0xfce7dfff irq 20 at device 4.0 on pci0 Jan 20 11:29:06 kernel: ohci1: [ITHREAD] Jan 20 11:29:06 kernel: usbus2: <ohci (generic)="" usb="" controller=""> on ohci1 Jan 20 11:29:06 kernel: ehci1: <ehci (generic)="" usb="" 2.0="" controller=""> mem 0xfce7e800-0xfce7e8ff irq 21 at device 4.1 on pci0 Jan 20 11:29:06 kernel: ehci1: [ITHREAD] Jan 20 11:29:06 kernel: usbus3: EHCI version 1.0 Jan 20 11:29:06 kernel: usbus3: <ehci (generic)="" usb="" 2.0="" controller=""> on ehci1 Jan 20 11:29:06 kernel: atapci0: <nvidia nforce="" mcp77="" udma133="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 6.0 on pci0 Jan 20 11:29:06 kernel: ata0: <ata 0="" channel=""> on atapci0 Jan 20 11:29:06 kernel: ata0: [ITHREAD] Jan 20 11:29:06 kernel: ata1: <ata 1="" channel=""> on atapci0 Jan 20 11:29:06 kernel: ata1: [ITHREAD] Jan 20 11:29:06 kernel: pci0: <multimedia, hda=""> at device 7.0 (no driver attached) Jan 20 11:29:06 kernel: pcib1: <acpi pci-pci="" bridge=""> at device 8.0 on pci0 Jan 20 11:29:06 kernel: pci1: <acpi pci="" bus=""> on pcib1 Jan 20 11:29:06 kernel: em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3=""> port 0xcc00-0xcc3f mem 0xfcfe0000-0xfcffffff,0xfcfc0000-0xfcfdffff irq 16 at device 6.0 on pci1 Jan 20 11:29:06 kernel: em0: [FILTER] Jan 20 11:29:06 kernel: em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3=""> port 0xc880-0xc8bf mem 0xfcf80000-0xfcf9ffff,0xfcf60000-0xfcf7ffff irq 17 at device 8.0 on pci1 Jan 20 11:29:06 kernel: em1: [FILTER] Jan 20 11:29:06 kernel: atapci1: <nvidia nforce="" mcp77="" sata300="" controller=""> port 0xb480-0xb487,0xb400-0xb403,0xb080-0xb087,0xb000-0xb003,0xac00-0xac0f mem 0xfce76000-0xfce77fff irq 23 at device 9.0 on pci0 Jan 20 11:29:06 kernel: atapci1: [ITHREAD] Jan 20 11:29:06 kernel: atapci1: AHCI v1.20 controller with 6 3Gbps ports, PM supported Jan 20 11:29:06 kernel: ata2: <ata 0="" channel=""> on atapci1 Jan 20 11:29:06 kernel: ata2: [ITHREAD] Jan 20 11:29:06 kernel: ata3: <ata 1="" channel=""> on atapci1 Jan 20 11:29:06 kernel: ata3: [ITHREAD] Jan 20 11:29:06 kernel: ata4: <ata 2="" channel=""> on atapci1 Jan 20 11:29:06 kernel: ata4: [ITHREAD] Jan 20 11:29:06 kernel: ata5: <ata 3="" channel=""> on atapci1 Jan 20 11:29:06 kernel: ata5: [ITHREAD] Jan 20 11:29:06 kernel: ata6: <ata 4="" channel=""> on atapci1 Jan 20 11:29:06 kernel: ata6: [ITHREAD] Jan 20 11:29:06 kernel: ata7: <ata 5="" channel=""> on atapci1 Jan 20 11:29:06 kernel: ata7: [ITHREAD] Jan 20 11:29:06 kernel: pcib2: <acpi pci-pci="" bridge=""> at device 11.0 on pci0 Jan 20 11:29:06 kernel: pci2: <acpi pci="" bus=""> on pcib2 Jan 20 11:29:06 kernel: vgapci0: <vga-compatible display=""> port 0xdc00-0xdc7f mem 0xfd000000-0xfdffffff,0xf0000000-0xf7ffffff,0xf8000000-0xf9ffffff irq 20 at device 0.0 on pci2 Jan 20 11:29:06 kernel: pcib3: <acpi pci-pci="" bridge=""> irq 16 at device 16.0 on pci0 Jan 20 11:29:06 kernel: pci3: <acpi pci="" bus=""> on pcib3 Jan 20 11:29:06 kernel: pcib4: <acpi pci-pci="" bridge=""> irq 17 at device 18.0 on pci0 Jan 20 11:29:06 kernel: pci4: <acpi pci="" bus=""> on pcib4 Jan 20 11:29:06 kernel: re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" pcie="" gigabit="" ethernet=""> port 0xe800-0xe8ff mem 0xfbfff000-0xfbffffff,0xfbff8000-0xfbffbfff irq 17 at device 0.0 on pci4 Jan 20 11:29:06 kernel: re0: Using 1 MSI messages Jan 20 11:29:06 kernel: re0: Chip rev. 0x28000000 Jan 20 11:29:06 kernel: re0: MAC rev. 0x00000000 Jan 20 11:29:06 kernel: miibus0: <mii bus=""> on re0 Jan 20 11:29:06 kernel: rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface=""> PHY 1 on miibus0 Jan 20 11:29:06 kernel: rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto Jan 20 11:29:06 kernel: re0: [FILTER] Jan 20 11:29:06 kernel: pcib5: <acpi pci-pci="" bridge=""> irq 18 at device 19.0 on pci0 Jan 20 11:29:06 kernel: pci5: <acpi pci="" bus=""> on pcib5 Jan 20 11:29:06 kernel: pcib6: <acpi pci-pci="" bridge=""> irq 19 at device 20.0 on pci0 Jan 20 11:29:06 kernel: pci6: <acpi pci="" bus=""> on pcib6 Jan 20 11:29:06 kernel: acpi_button0: <power button=""> on acpi0 Jan 20 11:29:06 kernel: acpi_tz0: <thermal zone=""> on acpi0 Jan 20 11:29:06 kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Jan 20 11:29:06 kernel: uart0: [FILTER] Jan 20 11:29:06 kernel: ppc0: <parallel port=""> port 0x378-0x37f irq 7 on acpi0 Jan 20 11:29:06 kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Jan 20 11:29:06 kernel: ppc0: [ITHREAD] Jan 20 11:29:06 kernel: ppbus0: <parallel port="" bus=""> on ppc0 Jan 20 11:29:06 kernel: plip0: <plip network="" interface=""> on ppbus0 Jan 20 11:29:06 kernel: plip0: [ITHREAD] Jan 20 11:29:06 kernel: lpt0: <printer> on ppbus0 Jan 20 11:29:06 kernel: lpt0: [ITHREAD] Jan 20 11:29:06 kernel: lpt0: Interrupt-driven port Jan 20 11:29:06 kernel: ppi0: <parallel i="" o=""> on ppbus0 Jan 20 11:29:06 kernel: atrtc0: <at realtime="" clock=""> port 0x70-0x71 on acpi0 Jan 20 11:29:06 kernel: orm0: <isa option="" roms=""> at iomem 0xcd800-0xce7ff,0xce800-0xcf7ff on isa0 Jan 20 11:29:06 kernel: sc0: <system console=""> at flags 0x100 on isa0 Jan 20 11:29:06 kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jan 20 11:29:06 kernel: vga0: <generic isa="" vga=""> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jan 20 11:29:06 kernel: atkbdc0: <keyboard controller="" (i8042)=""> at port 0x60,0x64 on isa0 Jan 20 11:29:06 kernel: atkbd0: <at keyboard=""> irq 1 on atkbdc0 Jan 20 11:29:06 kernel: kbd0 at atkbd0 Jan 20 11:29:06 kernel: atkbd0: [GIANT-LOCKED] Jan 20 11:29:06 kernel: atkbd0: [ITHREAD] Jan 20 11:29:06 kernel: hwpstate0: <cool`n'quiet 2.0=""> on cpu0 Jan 20 11:29:06 kernel: Timecounters tick every 1.000 msec Jan 20 11:29:06 kernel: IPsec: Initialized Security Association Processing. Jan 20 11:29:06 kernel: usbus0: 12Mbps Full Speed USB v1.0 Jan 20 11:29:06 kernel: usbus1: 480Mbps High Speed USB v2.0 Jan 20 11:29:06 kernel: usbus2: 12Mbps Full Speed USB v1.0 Jan 20 11:29:06 kernel: usbus3: 480Mbps High Speed USB v2.0 Jan 20 11:29:06 kernel: ad0: 76319MB <seagate st380020a="" 3.34=""> at ata0-master UDMA100 Jan 20 11:29:06 kernel: ugen0.1: <nvidia> at usbus0 Jan 20 11:29:06 kernel: uhub0: <nvidia 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0 Jan 20 11:29:06 kernel: ugen1.1: <nvidia> at usbus1 Jan 20 11:29:06 kernel: uhub1: <nvidia 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus1 Jan 20 11:29:06 kernel: ugen2.1: <nvidia> at usbus2 Jan 20 11:29:06 kernel: uhub2: <nvidia 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus2 Jan 20 11:29:06 kernel: ugen3.1: <nvidia> at usbus3 Jan 20 11:29:06 kernel: uhub3: <nvidia 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus3 Jan 20 11:29:06 kernel: acd0: DVDR <optiarc dvd="" rw="" ad-7240s="" 1.03=""> at ata4-master UDMA100 SATA 1.5Gb/s Jan 20 11:29:06 kernel: SMP: AP CPU #1 Launched! Jan 20 11:29:06 kernel: Root mount waiting for: usbus3 usbus2 usbus1 usbus0 Jan 20 11:29:06 kernel: uhub0: 6 ports with 6 removable, self powered Jan 20 11:29:06 kernel: uhub2: 6 ports with 6 removable, self powered Jan 20 11:29:06 kernel: Root mount waiting for: usbus3 usbus1 Jan 20 11:29:06 kernel: uhub1: 6 ports with 6 removable, self powered Jan 20 11:29:06 kernel: Root mount waiting for: usbus3 Jan 20 11:29:06 kernel: uhub3: 6 ports with 6 removable, self powered Jan 20 11:29:06 kernel: Trying to mount root from ufs:/dev/ad0s1a Jan 20 11:29:06 kernel: pflog0: promiscuous mode enabled Jan 20 11:29:06 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:29:06 php: : Removing static route for monitor 8.8.8.8 and adding a new route through 192.168.1.1 Jan 20 11:29:07 apinger: Starting Alarm Pinger, apinger(45713) Jan 20 11:29:08 php: : rc.newwanip: Informational is starting em0. Jan 20 11:29:08 php: : rc.newwanip: on (IP address: YY.YY.YY.YY) (interface: wan) (real interface: em0). Jan 20 11:29:08 php: : ROUTING: setting default route to 178.26.47.254 Jan 20 11:29:08 php: : Removing static route for monitor 8.8.8.8 and adding a new route through 192.168.1.1 Jan 20 11:29:08 apinger: Exiting on signal 15. Jan 20 11:29:09 check_reload_status: Reloading filter Jan 20 11:29:09 apinger: Starting Alarm Pinger, apinger(53181) Jan 20 11:29:09 php: : ROUTING: setting default route to 178.26.47.254 Jan 20 11:29:09 check_reload_status: Updating all dyndns Jan 20 11:29:09 dnsmasq[60461]: started, version 2.55 cachesize 10000 Jan 20 11:29:09 dnsmasq[60461]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP Jan 20 11:29:09 dnsmasq[60461]: reading /etc/resolv.conf Jan 20 11:29:09 dnsmasq[60461]: using nameserver 8.8.4.4#53 Jan 20 11:29:09 dnsmasq[60461]: using nameserver 8.8.8.8#53 Jan 20 11:29:09 dnsmasq[60461]: using nameserver 83.169.184.225#53 Jan 20 11:29:09 dnsmasq[60461]: using nameserver 83.169.184.161#53 Jan 20 11:29:09 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:29:09 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:29:09 dnsmasq[60461]: read /etc/hosts - 2 addresses Jan 20 11:29:09 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:29:10 php: : OpenNTPD is starting up. Jan 20 11:29:10 php: : rc.newwanip: Informational is starting em1. Jan 20 11:29:10 php: : rc.newwanip: on (IP address: 192.168.1.2) (interface: opt1) (real interface: em1). Jan 20 11:29:11 php: : Removing static route for monitor 8.8.8.8 and adding a new route through 192.168.1.1 Jan 20 11:29:11 apinger: Exiting on signal 15. Jan 20 11:29:11 dnsmasq[60461]: reading /etc/resolv.conf Jan 20 11:29:11 dnsmasq[60461]: using nameserver 8.8.4.4#53 Jan 20 11:29:11 dnsmasq[60461]: using nameserver 8.8.8.8#53 Jan 20 11:29:11 dnsmasq[60461]: using nameserver 83.169.184.225#53 Jan 20 11:29:11 dnsmasq[60461]: using nameserver 83.169.184.161#53 Jan 20 11:29:11 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:29:11 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:29:12 check_reload_status: Reloading filter Jan 20 11:29:12 apinger: Starting Alarm Pinger, apinger(22256) Jan 20 11:29:12 check_reload_status: Restarting ipsec tunnels Jan 20 11:29:14 php: : Gateways status could not be determined, considering all as up/active. Jan 20 11:29:14 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:29:14 php: : Creating rrd update script Jan 20 11:29:14 php: : DynDns: updatedns() starting Jan 20 11:29:14 php: : DynDns debug information: XX.XX.XX.XX extracted from checkip.dyndns.org Jan 20 11:29:14 php: : DynDns: Current WAN IP: XX.XX.XX.XX Cached IP: XX.XX.XX.XX Jan 20 11:29:14 php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jan 20 11:29:15 php: : Restarting/Starting all packages. Jan 20 11:29:15 php: : DynDns: updatedns() starting Jan 20 11:29:15 php: : DynDns debug information: YY.YY.YY.YY extracted from local system. Jan 20 11:29:16 php: : DynDns: Current WAN IP: YY.YY.YY.YY Cached IP: YY.YY.YY.YY Jan 20 11:29:16 php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jan 20 11:29:16 login: login on ttyv0 as root Jan 20 11:29:16 sshlockout[4510]: sshlockout/webConfigurator v3.0 starting up Jan 20 11:29:17 php: : DynDns: updatedns() starting Jan 20 11:29:17 php: : DynDns debug information: XX.XX.XX.XX extracted from checkip.dyndns.org Jan 20 11:29:17 php: : DynDns: Current WAN IP: XX.XX.XX.XX Cached IP: XX.XX.XX.XX Jan 20 11:29:17 php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jan 20 11:29:17 php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing. Jan 20 11:29:22 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:30:12 apinger: Error while feeding rrdtool: Broken pipe Jan 20 11:30:12 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s. Jan 20 11:39:30 apinger: ALARM: WAN1(178.26.47.254) *** down *** Jan 20 11:39:40 check_reload_status: Reloading filter Jan 20 11:39:45 php: : MONITOR: WAN1 is down, removing from routing group Jan 20 11:39:45 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:48:10 apinger: ALARM: WAN2(8.8.8.8) *** down *** Jan 20 11:48:10 kernel: em1: Watchdog timeout -- resetting Jan 20 11:48:10 kernel: em1: link state changed to DOWN Jan 20 11:48:10 check_reload_status: Linkup starting em1 Jan 20 11:48:12 check_reload_status: Linkup starting em1 Jan 20 11:48:12 kernel: em1: link state changed to UP Jan 20 11:48:12 apinger: alarm canceled: WAN2(8.8.8.8) *** down *** Jan 20 11:48:15 php: : DEVD Ethernet detached event for opt1 Jan 20 11:48:15 dhclient[17629]: connection closed Jan 20 11:48:15 dhclient[17629]: connection closed Jan 20 11:48:15 dhclient[17629]: exiting. Jan 20 11:48:15 dhclient[17629]: exiting. Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:16 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 php: : DEVD Ethernet attached event for opt1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 php: : HOTPLUG: Configuring interface opt1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 dhclient: PREINIT Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 dhclient[46970]: DHCPREQUEST on em1 to 255.255.255.255 port 67 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:17 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 dhclient[46970]: DHCPACK from 192.168.1.1 Jan 20 11:48:18 dhclient: REBOOT Jan 20 11:48:18 dhclient: Starting add_new_address() Jan 20 11:48:18 dhclient: ifconfig em1 inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255 Jan 20 11:48:18 dhclient: New IP Address (em1): 192.168.1.2 Jan 20 11:48:18 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:48:18 dhclient: New Subnet Mask (em1): 255.255.255.0 Jan 20 11:48:18 dhclient: New Broadcast Address (em1): 192.168.1.255 Jan 20 11:48:18 dhclient: New Routers (em1): 192.168.1.1 Jan 20 11:48:18 dhclient: Adding new routes to interface: em1 Jan 20 11:48:18 dhclient: Creating resolv.conf Jan 20 11:48:18 check_reload_status: rc.newwanip starting em1 Jan 20 11:48:18 dhclient[46970]: bound to 192.168.1.2 -- renewal in 41659 seconds. Jan 20 11:48:20 check_reload_status: Reloading filter Jan 20 11:48:21 apinger: ALARM: WAN2(8.8.8.8) *** delay *** Jan 20 11:48:22 check_reload_status: Reloading filter Jan 20 11:48:23 apinger: alarm canceled: WAN2(8.8.8.8) *** delay *** Jan 20 11:48:23 php: : rc.newwanip: Informational is starting em1. Jan 20 11:48:23 php: : rc.newwanip: on (IP address: 192.168.1.2) (interface: opt1) (real interface: em1). Jan 20 11:48:23 php: : Removing static route for monitor 8.8.8.8 and adding a new route through 192.168.1.1 Jan 20 11:48:23 apinger: Exiting on signal 15. Jan 20 11:48:24 apinger: Starting Alarm Pinger, apinger(63233) Jan 20 11:48:25 php: : Gateways status could not be determined, considering all as up/active. Jan 20 11:48:25 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:48:30 dnsmasq[60461]: reading /etc/resolv.conf Jan 20 11:48:30 dnsmasq[60461]: using nameserver 8.8.4.4#53 Jan 20 11:48:30 dnsmasq[60461]: using nameserver 8.8.8.8#53 Jan 20 11:48:30 dnsmasq[60461]: using nameserver 83.169.184.225#53 Jan 20 11:48:30 dnsmasq[60461]: using nameserver 83.169.184.161#53 Jan 20 11:48:30 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:48:30 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:48:32 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:48:34 apinger: ALARM: WAN1(178.26.47.254) *** down *** Jan 20 11:48:42 kernel: em1: discard frame w/o leading ethernet header (len 0 pkt len 1514) Jan 20 11:48:44 check_reload_status: Reloading filter Jan 20 11:48:50 php: : MONITOR: WAN1 is down, removing from routing group Jan 20 11:48:50 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:49:57 kernel: em1: Watchdog timeout -- resetting Jan 20 11:49:57 kernel: em1: link state changed to DOWN Jan 20 11:49:57 check_reload_status: Linkup starting em1 Jan 20 11:49:57 apinger: ALARM: WAN2(8.8.8.8) *** down *** Jan 20 11:49:59 check_reload_status: Linkup starting em1 Jan 20 11:49:59 kernel: em1: link state changed to UP Jan 20 11:50:00 apinger: alarm canceled: WAN2(8.8.8.8) *** down *** Jan 20 11:50:02 php: : DEVD Ethernet detached event for opt1 Jan 20 11:50:02 dhclient[47022]: connection closed Jan 20 11:50:02 dhclient[47022]: connection closed Jan 20 11:50:02 dhclient[47022]: exiting. Jan 20 11:50:02 dhclient[47022]: exiting. Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:03 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 php: : DEVD Ethernet attached event for opt1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 php: : HOTPLUG: Configuring interface opt1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 dhclient: PREINIT Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 dhclient[10110]: DHCPREQUEST on em1 to 255.255.255.255 port 67 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:04 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:05 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:06 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:06 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:06 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:06 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:06 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:50:06 dhclient[10110]: DHCPACK from 192.168.1.1 Jan 20 11:50:06 dhclient: REBOOT Jan 20 11:50:06 dhclient: Starting add_new_address() Jan 20 11:50:06 dhclient: ifconfig em1 inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255 Jan 20 11:50:06 dhclient: New IP Address (em1): 192.168.1.2 Jan 20 11:50:06 dhclient: New Subnet Mask (em1): 255.255.255.0 Jan 20 11:50:06 dhclient: New Broadcast Address (em1): 192.168.1.255 Jan 20 11:50:06 dhclient: New Routers (em1): 192.168.1.1 Jan 20 11:50:06 dhclient: Adding new routes to interface: em1 Jan 20 11:50:06 dhclient: Creating resolv.conf Jan 20 11:50:06 check_reload_status: rc.newwanip starting em1 Jan 20 11:50:06 dhclient[10110]: bound to 192.168.1.2 -- renewal in 41605 seconds. Jan 20 11:50:07 check_reload_status: Reloading filter Jan 20 11:50:10 check_reload_status: Reloading filter Jan 20 11:50:11 php: : rc.newwanip: Informational is starting em1. Jan 20 11:50:11 php: : rc.newwanip: on (IP address: 192.168.1.2) (interface: opt1) (real interface: em1). Jan 20 11:50:11 php: : Removing static route for monitor 8.8.8.8 and adding a new route through 192.168.1.1 Jan 20 11:50:11 apinger: Exiting on signal 15. Jan 20 11:50:12 apinger: Starting Alarm Pinger, apinger(20484) Jan 20 11:50:13 php: : Gateways status could not be determined, considering all as up/active. Jan 20 11:50:13 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:50:20 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:50:21 dnsmasq[60461]: reading /etc/resolv.conf Jan 20 11:50:21 dnsmasq[60461]: using nameserver 8.8.4.4#53 Jan 20 11:50:21 dnsmasq[60461]: using nameserver 8.8.8.8#53 Jan 20 11:50:21 dnsmasq[60461]: using nameserver 83.169.184.225#53 Jan 20 11:50:21 dnsmasq[60461]: using nameserver 83.169.184.161#53 Jan 20 11:50:21 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:50:21 dnsmasq[60461]: ignoring nameserver 127.0.0.1 - local interface Jan 20 11:50:22 apinger: ALARM: WAN1(178.26.47.254) *** down *** Jan 20 11:50:32 check_reload_status: Reloading filter Jan 20 11:50:37 php: : MONITOR: WAN1 is down, removing from routing group Jan 20 11:50:37 php: : Not installing nat reflection rules for a port range > 500 Jan 20 11:51:02 kernel: em1: Watchdog timeout -- resetting Jan 20 11:51:02 kernel: em1: link state changed to DOWN Jan 20 11:51:02 check_reload_status: Linkup starting em1 Jan 20 11:51:02 apinger: ALARM: WAN2(8.8.8.8) *** down *** Jan 20 11:51:03 check_reload_status: Linkup starting em1 Jan 20 11:51:03 kernel: em1: link state changed to UP Jan 20 11:51:03 apinger: alarm canceled: WAN2(8.8.8.8) *** down *** Jan 20 11:51:07 php: : DEVD Ethernet detached event for opt1 Jan 20 11:51:07 dhclient[10122]: connection closed Jan 20 11:51:07 dhclient[10122]: connection closed Jan 20 11:51:07 dhclient[10122]: exiting. Jan 20 11:51:07 dhclient[10122]: exiting. Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 php: : DEVD Ethernet attached event for opt1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 php: : HOTPLUG: Configuring interface opt1 Jan 20 11:51:08 dhclient: PREINIT Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 dhclient[54112]: DHCPREQUEST on em1 to 255.255.255.255 port 67 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:08 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:09 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 kernel: arpresolve: can't allocate llinfo for 192.168.1.1 Jan 20 11:51:10 dhclient[54112]: DHCPACK from 192.168.1.1 Jan 20 11:51:10 dhclient: REBOOT Jan 20 11:51:10 dhclient: Starting add_new_address() Jan 20 11:51:10 dhclient: ifconfig em1 inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255 Jan 20 11:51:10 dhclient: New IP Address (em1): 192.168.1.2 Jan 20 11:51:10 dhclient: New Subnet Mask (em1): 255.255.255.0 Jan 20 11:51:10 dhclient: New Broadcast Address (em1): 192.168.1.255 Jan 20 11:51:10 dhclient: New Routers (em1): 192.168.1.1 Jan 20 11:51:10 dhclient: Adding new routes to interface: em1 Jan 20 11:51:10 dhclient: Creating resolv.conf Jan 20 11:51:10 check_reload_status: rc.newwanip starting em1 Jan 20 11:51:10 dhclient[54112]: bound to 192.168.1.2 -- renewal in 41573 seconds. Jan 20 11:51:12 check_reload_status: Reloading filter Jan 20 11:51:13 apinger: ALARM: WAN2(8.8.8.8) *** delay ***</optiarc></nvidia></nvidia></nvidia></nvidia></nvidia></nvidia></nvidia></nvidia></seagate></cool`n'quiet></at></keyboard></generic></system></isa></at></parallel></printer></plip></parallel></parallel></thermal></power></acpi></acpi></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></acpi></acpi></vga-compatible></acpi></acpi></ata></ata></ata></ata></ata></ata></nvidia></intel(r)></intel(r)></acpi></acpi></multimedia,></ata></ata></nvidia></ehci></ehci></ohci></ohci></ehci></ehci></ohci></ohci></memory,></processor></memory,></serial></isa></pci-isa></memory,></acpi></acpi></high></acpi></acpi></software></version></lahf,cmp,svm,extapic,cr8,abm,sse4a,mas,prefetch,osvw,ibs,skinit,wdt></syscall,nx,mmx+,ffxsr,page1gb,rdtscp,lm,3dnow!+,3dnow!></sse3,mon,cx16,popcnt></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,htt>cu
-
Because of max Text-length, here the 2nd part of post:
It looks like if only em0 and em1 is not working anymore. Both are exact same card (Intel Pro 1000). LAN which doesn't have any problem is an onboard chip (Realtek?).
cu Floh
-
Could be that your WAN is failing an and your modem is handing you an IP in 192.168.1.x and a gateway of 192.168.1.1. If your LAN is still 192.168.1.x I would expect that to blow up quite badly.
Given the messages in the log it does appear that your WAN interface is going up/down.
See if you can get into your CPE and make sure it's LAN subnet is not also 192.168.1.x, even in half-bridge or pass-thru mode devices like that will still conflict if they lose sync.
My cable modem is bad about this if it loses signal from the carrier, it flips to 192.168.100.x until the cable link comes back up.
-
Hi, thank you for your reply.
LAN is of course not 192.168.1.X (would be bad in my case) but 192.168.0.X.
What do you mean by CPE?
cu Floh
-
CPE = Customer Premises Equipment, meaning your DSL or Cable modem. Whatever the first device is to which the wire from your ISP connects.
-
I can access my modem by using 192.168.100.1 so its subet is 192.168.100.0.
Could it be a problem if both modems are using same ip-Address 192.168.100.1 (but they're physically separated!)?
cu Floh
-
Could it be a problem if both modems are using same ip-Address 192.168.100.1 (but they're physically separated!)?
Yes, which modem is 192.168.100.1? (Both is not an acceptable answer! Unless you take special care with your configuration each computer on your network needs to have a unique IP address.)
Please provide the output of pfSense shell commands netstat -r -n and ifconfig -a
Your question says that you have a broken configuration but doesn't say how badly it is broken.
-
Sorry, but both modem have 192.168.100.1. I don't have access to settings of these modem.
To make more clear I made a picture. Please see attached picture. In pfSense WAN1 and WAN2 are grouped and I use that group as gateway (see 2nd picture).
As you asked I entered the command you wished:
[2.0.1-RELEASE][admin@r2d2.verbavoice.local]/root(1): netstat -r -n Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 178.26.47.254 UGS 0 422 em0 8.8.4.4 11:aa:bb:cc:dd:ee UHS 0 328 em1 8.8.8.8 192.168.1.1 UGHS 0 1091 em1 83.169.184.161 00:aa:bb:cc:dd:ee UHS 0 328 em0 83.169.184.225 00:aa:bb:cc:dd:ee UHS 0 328 em0 127.0.0.1 link#8 UH 0 31 lo0 178.26.40.0/21 link#1 U 0 1103 em0 178.26.41.70 link#1 UHS 0 0 lo0 192.168.0.0/24 link#3 U 0 21839 re0 192.168.0.1 link#3 UHS 0 0 lo0 192.168.1.0/24 link#2 U 0 4 em1 192.168.1.2 link#2 UHS 0 0 lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%em0/64 link#1 U em0 fe80::21b:21ff:febb:3527%em0 link#1 UHS lo0 fe80::%em1/64 link#2 U em1 fe80::21b:21ff:febb:342a%em1 link#2 UHS lo0 fe80::%re0/64 link#3 U re0 fe80::230:67ff:fe2c:1c32%re0 link#3 UHS lo0 fe80::%lo0/64 link#8 U lo0 fe80::1%lo0 link#8 UHS lo0 ff01:1::/32 fe80::21b:21ff:febb:3527%em0 U em0 ff01:2::/32 fe80::21b:21ff:febb:342a%em1 U em1 ff01:3::/32 fe80::230:67ff:fe2c:1c32%re0 U re0 ff01:8::/32 ::1 U lo0 ff02::%em0/32 fe80::21b:21ff:febb:3527%em0 U em0 ff02::%em1/32 fe80::21b:21ff:febb:342a%em1 U em1 ff02::%re0/32 fe80::230:67ff:fe2c:1c32%re0 U re0 ff02::%lo0/32 ::1 U lo0 [2.0.1-RELEASE][admin@r2d2.verbavoice.local]/root(2): ifconfig -a em0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 00:aa:bb:cc:dd:ee inet6 fe80::21b:21ff:febb:3527%em0 prefixlen 64 scopeid 0x1 inet 178.26.41.70 netmask 0xfffff800 broadcast 178.26.47.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active em1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 11:aa:bb:cc:dd:ee inet6 fe80::21b:21ff:febb:342a%em1 prefixlen 64 scopeid 0x2 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active re0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=389b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic>ether 33:aa:bb:cc:dd:ee inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::230:67ff:fe2c:1c32%re0 prefixlen 64 scopeid 0x3 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active plip0: flags=8810 <pointopoint,simplex,multicast>metric 0 mtu 1500 pflog0: flags=100 <promisc>metric 0 mtu 33664 pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 syncok: 1 enc0: flags=0<> metric 0 mtu 1536 lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384 options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 nd6 options=3<performnud,accept_rtadv></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></promisc></pointopoint,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast>cu Floh
-
OK, NAT will work to hide replicated IP addresses.
Looking back at the syslog extract you posted I see only em1 reported going down then up. There seems to be some intermittent blockage on em0 but of a different nature to that on em1. I would suspect the link down on em1 due to it losing carrier perhaps due to the NAT router restarting its LAN interface. Do the systems upstream of pfSense record any log information? Are the circuits upstream of the modems in good state? I have had my home ADSL service misbehave when the phone service developed a noticeable crackle which was rectified by something the phone company did.
-
Hi,
I'm suspecting that the LAN-cable of the building has poor quality. Now I'm using different WLAN-Router (for NAT) at different place (better Cable-quality).Let see some days then I'll report if it helped.
cu Floh
-
Unfortunatelly I have still same problem. This time WAN1 went down and I have to reboot Firewall.
I cannot post log about WAN1 failure because this happened at weekend and when I was in office logs about WAN1 failure was already "flooded away" by dhpc- & arping-logs.
Some idea?
cu Floh
