News: This forum is now permanently frozen.
Pages: [1]
Topic: m0n0wall losing WAN connection intermittently  (Read 1958 times)
« on: June 27, 2013, 21:41:18 »
mardev *
Posts: 1

I have two Soekris Net5501's in two different locations, one on Time Warner Cable Internet and one on Verizon DSL. Several months ago these systems began experiencing similar connectivity issues.

What will happen is that everything will be going fine, and then all of a sudden we won't be able to access anything external, either by IP or by domain. Our LAN still works fine, and I can access the m0n0wall front end. When I look at the system status, it tells me the WAN is up and operational, but we won't be able to access any sites or connect to any servers externally, just as if someone had physically unplugged the WAN cable. Rebooting the m0n0wall seems to fix the issue.

Has anyone had anything similar happen to their device?

The last time this happened, I was able to capture the log almost immediately after. Below is said log, right up until the moment our WAN stopped working. Note: I waited a good 15 minutes before rebooting it to ensure it wasn't just a momentary thing.  Monitoring the logs, the dhclient bit seems to happen about every half hour.

Code:
Jun 26 16:30:47 dhclient: bound to 67.xxx.xx.xxx -- renewal in 1432 seconds.
Jun 26 16:30:47 dhclient: New Routers: 67.243.56.1
Jun 26 16:30:47 dhclient: New Broadcast Address (vr0): 255.255.255.255
Jun 26 16:30:47 dhclient: New Subnet Mask (vr0): 255.255.252.0
Jun 26 16:30:47 dhclient: New IP Address (vr0): 67.xxx.xx.xxx
Jun 26 16:30:47 dhclient: New Broadcast Address: 255.255.255.255
Jun 26 16:30:47 dhclient: New Network Number: 67.243.56.0
Jun 26 16:30:47 dhclient: DHCPACK from 10.35.128.1
Jun 26 16:30:47 dhclient: DHCPREQUEST on vr0 to 255.255.255.255 port 67
Jun 26 16:30:47 dhclient: DHCPOFFER from 10.35.128.1
Jun 26 16:30:47 dhclient: DHCPDISCOVER on vr0 to 255.255.255.255 port 67 interval 6
Jun 26 16:30:40 dhclient: DHCPREQUEST on vr0 to 10.35.128.1 port 67
Jun 26 16:30:34 dhclient: DHCPREQUEST on vr0 to 10.35.128.1 port 67
Jun 26 12:15:31 /usr/local/bin/ez-ipupdate[123]: successful update for vr0->67.xxx.xx.xxx (office.mydomain.com)
Jun 26 12:11:35 kernel: arp: 10.1.0.198 moved from fc:25:3f:xx:xx:xx to cc:3a:61:xx:xx:xx on vr1
Jun 26 12:10:41 dhclient: bound to 67.xxx.xx.xxx -- renewal in 15593 seconds.
Jun 26 12:10:38 dhclient: New Routers: 67.243.56.1
Jun 26 12:10:38 dhclient: New Broadcast Address (vr0): 255.255.255.255
Jun 26 12:10:38 dhclient: New Subnet Mask (vr0): 255.255.252.0
Jun 26 12:10:38 dhclient: New IP Address (vr0): 67.xxx.xx.xxx
Jun 26 12:10:38 dhclient: New Broadcast Address: 255.255.255.255
Jun 26 12:10:38 dhclient: New Network Number: 67.243.56.0
Jun 26 12:10:38 dhclient: DHCPACK from 10.35.128.1
Jun 26 12:10:38 dhclient: DHCPREQUEST on vr0 to 255.255.255.255 port 67
Jun 26 12:10:38 dhclient: DHCPOFFER from 10.35.128.1
Jun 26 12:10:38 dhclient: DHCPDISCOVER on vr0 to 255.255.255.255 port 67 interval 7
Jun 26 12:10:31 mpd: [pt15] using interface ng16
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt14] using interface ng15
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt13] using interface ng14
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 /usr/local/bin/ez-ipupdate[123]: SIGHUP recieved, re-reading config file
Jun 26 12:10:31 mpd: [pt12] using interface ng13
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt11] using interface ng12
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt10] using interface ng11
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt9] using interface ng10
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt8] using interface ng9
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt7] using interface ng8
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt6] using interface ng7
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt5] using interface ng6
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt4] using interface ng5
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt3] using interface ng4
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt2] using interface ng3
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt1] using interface ng2
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: [pt0] using interface ng1
Jun 26 12:10:31 mpd: PPTP: waiting for connection on 0.0.0.0
Jun 26 12:10:31 mpd: process 144 started, version 4.4.1 (****@mb64.neon1.net 21:35 23-Jul-2009)
Jun 26 12:10:31 mpd:
Jun 26 12:10:31 mpd: Multi-link PPP daemon for FreeBSD
Jun 26 12:10:30 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Jun 26 12:10:30 dhcpd: All rights reserved.
Jun 26 12:10:30 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Jun 26 12:10:30 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
Jun 26 12:10:30 /usr/local/bin/ez-ipupdate[123]: failure to update vr0->0.0.0.0 (office.mydomain.com)
Jun 26 12:10:30 /usr/local/bin/ez-ipupdate[123]: got last update 67.xxx.xx.xxx on 2013/06/24 13:35 from cache file
Jun 26 12:10:30 /usr/local/bin/ez-ipupdate[123]: /usr/local/bin/ez-ipupdate started for interface vr0 host office.mydomain.com using server members.dyndns.org and service dyndns-custom
Jun 26 12:10:30 /usr/local/bin/ez-ipupdate[123]: ez-ipupdate Version 3.0.11b8, Copyright (C) 1998-2001 Angus Mackay.
Jun 26 12:10:30 kernel: Trying to mount root from ufs:/dev/md0
Jun 26 12:10:30 kernel: ad0: 1918MB <SanDisk SDCFH-002G HDX 5.04> at ata0-master PIO4
Jun 26 12:10:30 kernel: ad0: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>
Jun 26 12:10:30 kernel: md0: Preloaded image </mfsroot> 16777216 bytes at 0xc0835b54
Jun 26 12:10:30 kernel: IP Filter: v4.1.28 initialized. Default = block all, Logging = enabled
Jun 26 12:10:30 kernel: Fast IPsec: Initialized Security Association Processing.
Jun 26 12:10:30 kernel: Timecounters tick every 1.000 msec
Jun 26 12:10:30 kernel: Timecounter "TSC" frequency 499905186 Hz quality 800
Jun 26 12:10:30 kernel: sio1: type 16550A
Jun 26 12:10:30 kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0
Jun 26 12:10:30 kernel: sio0: type 16550A, console
Jun 26 12:10:30 kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
Jun 26 12:10:30 kernel: orm0: <ISA Option ROM> at iomem 0xc8000-0xd27ff on isa0
Jun 26 12:10:30 kernel: pmtimer0 on isa0
Jun 26 12:10:30 kernel: uhub1: 4 ports with 4 removable, self powered
Jun 26 12:10:30 kernel: uhub1: AMD EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
Jun 26 12:10:30 kernel: usb1: USB revision 2.0
Jun 26 12:10:30 kernel: usb1: <AMD CS5536 USB 2.0 controller> on ehci0
Jun 26 12:10:30 kernel: usb1: companion controller, 4 ports each: usb0
Jun 26 12:10:30 kernel: usb1: EHCI version 1.0
Jun 26 12:10:30 kernel: ehci0: [GIANT-LOCKED]
Jun 26 12:10:30 kernel: ehci0: <AMD CS5536 USB 2.0 controller> mem 0xa0006000-0xa0006fff irq 15 at device 21.1 on pci0
Jun 26 12:10:30 kernel: uhub0: 4 ports with 4 removable, self powered
Jun 26 12:10:30 kernel: uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
Jun 26 12:10:30 kernel: usb0: USB revision 1.0
Jun 26 12:10:30 kernel: usb0: <OHCI (generic) USB controller> on ohci0
Jun 26 12:10:30 kernel: usb0: OHCI version 1.0, legacy support
Jun 26 12:10:30 kernel: ohci0: [GIANT-LOCKED]
Jun 26 12:10:30 kernel: ohci0: <OHCI (generic) USB controller> mem 0xa0005000-0xa0005fff irq 15 at device 21.0 on pci0
Jun 26 12:10:30 kernel: ata1: <ATA channel 1> on atapci0
Jun 26 12:10:30 kernel: ata0: <ATA channel 0> on atapci0
Jun 26 12:10:30 kernel: atapci0: <AMD CS5536 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0
Jun 26 12:10:30 kernel: isa0: <ISA bus> on isab0
Jun 26 12:10:30 kernel: isab0: <PCI-ISA bridge> at device 20.0 on pci0
Jun 26 12:10:30 kernel: vr3: Ethernet address: 00:00:24:xx:xx:xx
Jun 26 12:10:30 kernel: ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Jun 26 12:10:30 kernel: ukphy3: <Generic IEEE 802.3u media interface> on miibus3
Jun 26 12:10:30 kernel: miibus3: <MII bus> on vr3
Jun 26 12:10:30 kernel: vr3: Quirks: 0x2
Jun 26 12:10:30 kernel: vr3: <VIA VT6105M Rhine III 10/100BaseTX> port 0xe400-0xe4ff mem 0xa0004300-0xa00043ff irq 12 at device 9.0 on pci0
Jun 26 12:10:30 kernel: vr2: Ethernet address: 00:00:24:cd:2c:32
Jun 26 12:10:30 kernel: ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Jun 26 12:10:30 kernel: ukphy2: <Generic IEEE 802.3u media interface> on miibus2
Jun 26 12:10:30 kernel: miibus2: <MII bus> on vr2
Jun 26 12:10:30 kernel: vr2: Quirks: 0x2
Jun 26 12:10:30 kernel: vr2: <VIA VT6105M Rhine III 10/100BaseTX> port 0xe300-0xe3ff mem 0xa0004200-0xa00042ff irq 9 at device 8.0 on pci0
Jun 26 12:10:30 kernel: vr1: Ethernet address: 00:00:24:cd:2c:31
Jun 26 12:10:30 kernel: ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Jun 26 12:10:30 kernel: ukphy1: <Generic IEEE 802.3u media interface> on miibus1
Jun 26 12:10:30 kernel: miibus1: <MII bus> on vr1
Jun 26 12:10:30 kernel: vr1: Quirks: 0x2
Jun 26 12:10:30 kernel: vr1: <VIA VT6105M Rhine III 10/100BaseTX> port 0xe200-0xe2ff mem 0xa0004100-0xa00041ff irq 5 at device 7.0 on pci0
Jun 26 12:10:30 kernel: vr0: Ethernet address: 00:00:24:cd:2c:30
Jun 26 12:10:30 kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Jun 26 12:10:30 kernel: ukphy0: <Generic IEEE 802.3u media interface> on miibus0
Jun 26 12:10:30 kernel: miibus0: <MII bus> on vr0
Jun 26 12:10:30 kernel: vr0: Quirks: 0x2
Jun 26 12:10:30 kernel: vr0: <VIA VT6105M Rhine III 10/100BaseTX> port 0xe100-0xe1ff mem 0xa0004000-0xa00040ff irq 11 at device 6.0 on pci0
Jun 26 12:10:30 kernel: pci0: <encrypt/decrypt, entertainment crypto> at device 1.2 (no driver attached)
Jun 26 12:10:30 kernel: Geode LX: Soekris net5501 comBIOS ver. 1.33 20070103 Copyright (C) 2000-2007
Jun 26 12:10:30 kernel: pci0: <PCI bus> on pcib0
Jun 26 12:10:30 kernel: pcib0: <Host to PCI bridge> pcibus 0 on motherboard
Jun 26 12:10:30 kernel: cpu0 on motherboard
Jun 26 12:10:30 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
Jun 26 12:10:30 kernel: K6-family MTRR support enabled (2 registers)
Jun 26 12:10:30 kernel: wlan: mac acl policy registered
Jun 26 12:10:30 kernel: avail memory = 499331072 (476 MB)
Jun 26 12:10:30 kernel: real memory = 536870912 (512 MB)
Jun 26 12:10:30 kernel: AMD Features=0xc0400000<MMX+,3DNow!+,3DNow!>
Jun 26 12:10:30 kernel: Features=0x88a93d<FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX>
Jun 26 12:10:30 kernel: Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2
Jun 26 12:10:30 kernel: CPU: Geode(TM) Integrated Processor by AMD PCS (499.91-MHz 586-class CPU)
Jun 26 12:10:30 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Jun 26 12:10:30 kernel: root@mb64.neon1.net:/usr/src/sys/i386/compile/M0N0WALL_EMBEDDED
Jun 26 12:10:30 kernel: FreeBSD 6.4-RELEASE-p5 #0: Sun Apr 11 18:51:47 CEST 2010
Jun 26 12:10:30 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Jun 26 12:10:30 kernel: The Regents of the University of California. All rights reserved.
Jun 26 12:10:30 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Jun 26 12:10:30 kernel: Copyright (c) 1992-2008 The FreeBSD Project.
Jun 26 12:10:30 syslogd: kernel boot file is /kernel

This same issue happens less frequently on another m0n0wall we have set up at a different location. I wasn't able to capture the log file for that one, but logging in I do see the same dhclient bit happening less frequently (every few hours instead of every half hour).

Apologies if this is somewhat of a n00b question; networking is not my strong point, it's only fallen on me because our actual sys-admin left 8 months ago!

Thanks in advance!
« Reply #1 on: June 28, 2013, 17:45:05 »
Lee Sharp *****
Posts: 517

You are pulling a new IP address and it is valid.  So you will need o do some testing.  While it is down, go to the Ping/Traceroute page, and the Arp Table page.  Make sure you can ping the gateway, and try a traceroute to 4.2.2.2  There are lots of things that can cause "Internet Down" and I like to start with the basics.
« Reply #2 on: July 15, 2013, 00:46:44 »
yowsers *
Posts: 49

i am also on time warner cable.  i was having the exact same issue on hardware Neoware E140 running version 1.34 (rebooting fixed the issue.)  basically WAN connectivity would stop.  i would get the new IP from time warner (which was the same IP as I previously had) yet there was no WAN connectivity.  could not ping the WAN gateway, timewarner DNS, nothing.  from LAN side I could ping the LAN interface from my own PC and vice versa and could also ping my monowall WAN interface from inside the LAN but doing anything outside WAN interface on monowall was dead.  Symptom seemed to be that the IP address that the dhcp client received was incorrect (ie: IP address, subnet range, or whatever was not valid since a simple reboot would cause me to get a new IP address.)

I did a hardware swap to a PC running monowall 1.8 beta 540 and no longer have the issue.

it is odd that you have the same issue with two different ISPs.  the only commonality we have is the symptom/resolution and time warner cable Smiley

i thought about upgrading the Neoware E140 to monowall 1.8 beta 540 to see if the issue still existed but got too lazy after I got it working on different PC hardware.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines