1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WRV54G Reboots Often

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by czeman, Jul 2, 2005.

  1. czeman

    czeman Network Guru Member

    Comcast installed an SMC 8013WG Cable Modem/Router at my location. I installed a WRV54G router and connected it to the SMC garbage, and configured the SMC so the WRV54G was the DMZ host.

    I'm still working on making a successful VPN connection, but more disturbing is the fact that the WRV54G reboots every few minutes or so. I had to upgrade to v2.38 out of desperation. I didn't want to because the last time I did that I ended up exchanging for a new router. It doesn't matter what firmware version I use, the router has behaved this way with all of them.

    I'm hoping someone has an idea of what else I could check. This is extrememely frustrating. I'm confident the router will prove to be a great purchase, I just need to solve the problems I'm having.

    Thanks,
    Chris
     
  2. TazUk

    TazUk Network Guru Member

    Sounds like a defective router :?
     
  3. czeman

    czeman Network Guru Member

    Yeah, second one in a row. Now it's really defective. I bricked it last night and Monday morning it's getting shipped back for a replacement. We'll see how #3 is. If #3 turns out to be a piece of garbage to, I'm looking elsewhere for a VPN router. I absolutely HATE D-Link after what we went through with their DWL-2100's, but they have a VPN router I may end up having to try.
     
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Damn,

    two in a row?!?!?! The next one you get, PM me with your email address and I'll email you firmware 2.37.13 (unless you've already tried it). That one has been pretty stable for me. I've had no reboot issues, plus I've always been able to use quickvpn without problems.

    2.37.13 is a winner in my books...

    Doc
     
  5. czeman

    czeman Network Guru Member

    I'll do that, Doc. Thanks. The second unit arrived with 2.36, or something like that anyways. I upgraded to 2.37 hoping that maybe the rebooting issue would go away and it didn't. I then tried 2.38 and although it didn't solve the rebooting issue, I was able to at least get to "Verifying Network" while attempting to establish a VPN tunnel from home. I should have my replacement unit on Wednesday.

    I think this time I'll try getting it to run at home before I install it at work. I'll PM you my email address. Thanks, Doc!


    Chris
     
  6. TazUk

    TazUk Network Guru Member

    An alternative setup would be to use a Linksys BEFVP41 with a seperate AP such as the WAG54G. It's two boxes instead of one but should work out slightly cheaper and the BEFVP41 is a far less problematic router. If you've had enough of Linksys then The Zyxel Pretige P334W looks like a suitable alternative.
     
  7. stoic-one

    stoic-one Network Guru Member

    I had a similar problem with my WRV, I installed a UPS and it quit rebooting. Not having a power problem are you?? I noticed my unit was very sensitive to very small power fluctuations......
     
  8. czeman

    czeman Network Guru Member

    Ya know what?!?!?! I think you may be right. :lol: The power where I work can fluctuate quite a bit. I've seen the power get up to 130V when we're closed, and drop quite a bit when we're open. I'll have to look into that. I currently have a WRT54GS in the WRV's place till my replacement WRV arrives, and it's working great. It might not be as sensitive to that. I'll have to monitor the power for a little while when I get to work tonight.

    Thanks,
    Chris
     
  9. czeman

    czeman Network Guru Member

    Well, I've tried two different UPS units, and plugging into outlets on different phases, and no luck. I downloaded Wall Watcher and saved the log of the unit starting up. There are some entries that appear to me as disturbing.

    The first thing I have to wonder about, is why it appears to change hostnames partially into the log. The hostname is supposed to be "cyberrouter", but it changes to "yberrouter".

    There are a number of other messages that bug me:

    "no such device"

    "warning: bad configuration page, trying to continue"

    "memory range 0x1fff000-0x2000000 is excluded because of pci dma bug"

    "error: ipsec_hwaccel_add_service: invalid function pointers!"

    "error resolving hostname: '0.0.0.0/0'" <- Huh? Why is it doing that?

    I'm guessing this has to be a joke:
    "all bugs added by david s. miller <davem@redhat.com>"


    Anyways, the log file is below. I'm hoping someone can tell me what the hell is going on. :? I'm on router #3. It can sit on my desk with the WAN or one of the LAN ports plugged into my network. Soon after installing it so it's our internet router, it starts screwing up. :evil:



    Code:
    2005/07/12	20:16:44.96	M			cyberrouter klogd: task started			
    2005/07/12	20:16:45.37	M			cyberrouter rg_system_full:255: pluto --nofork --debug-none --uniqueids			
    2005/07/12	20:16:45.37	M			cyberrouter wrv54gfw-conf: configuration started (mode: activate)			
    2005/07/12	20:16:45.37	M			cyberrouter rg_system_full:275: spawned pid 33			
    2005/07/12	20:16:45.37	M			cyberrouter wrv54gfw-conf: configuration completed (status: success)			
    2005/07/12	20:16:45.38	M			cyberrouter mt_igmp_changed:99: igmp changed: interface: ixp0			
    2005/07/12	20:16:45.38	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips0'			
    2005/07/12	20:16:45.40	M			cyberrouter snmp: binding agent on 10.1.10.10			
    2005/07/12	20:16:45.40	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips54'			
    2005/07/12	20:16:45.57	M			cyberrouter snmp: binding agent on 172.16.1.6			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips53'			
    2005/07/12	20:16:45.57	M			cyberrouter failed to set device ixp0 netmask: cannot assign requested address		
    
    	
    2005/07/12	20:16:45.57	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips52'			
    2005/07/12	20:16:45.57	M			cyberrouter failed to set device eth0 netmask: cannot assign requested address		
    
    	
    2005/07/12	20:16:45.57	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips51'			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips50'			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ppp0'			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ixp0.3'			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.57	M			cyberrouter wrv54gfw-conf: configuration started (mode: activate)			
    2005/07/12	20:16:45.57	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.57	M			cyberrouter wrv54gfw-conf: configuration completed (status: success)			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips0'			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips54'			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter route: failed to add route to dst(0.0.0.0) dev() gw(0x0) net(0.0.0.0) by ioctl: no such device			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips53'			
    2005/07/12	20:16:45.59	M			cyberrouter mt_igmp_params_init:61: igmp reconf: new lan interface: ixp0		
    
    	
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips52'			
    2005/07/12	20:16:45.59	M			cyberrouter mt_igmp_params_init:61: igmp reconf: new lan interface: eth0		
    
    	
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips51'			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:255: date -s 2005.7.12-18:21:47			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ips50'			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:275: spawned pid 35			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ppp0'			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:255: setoid eth0 17000007 long 3			
    2005/07/12	20:16:45.59	M			
    
    cyberrouter ipf_check_interface:306: wrv54gfw-conf: failed ioctl (siocadddv - no such device) on dev 'ixp0.3'			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:275: spawned pid 36			
    2005/07/12	20:16:45.59	O	udp	10.1.10.1		53	10.1.10.10	1024
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:255: setoid eth0 12000000 long 2			
    2005/07/12	20:16:45.59	O	udp	68.87.66.196		53	10.1.10.10	1024
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:275: spawned pid 37			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:255: setoid eth0 1700000a long 968b8482			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:275: spawned pid 38			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:255: setoid eth0 17000016 long 0			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:275: spawned pid 39			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:255: setoid eth0 10000002 ssid '<censored>'			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:275: spawned pid 40			
    2005/07/12	20:16:45.59	M			cyberrouter rg_system_full:255: setoid eth0 17000019 long 1			
    2005/07/12	20:16:45.60	M			cyberrouter rg_system_full:275: spawned pid 41			
    2005/07/12	20:16:45.60	M			cyberrouter rg_system_full:255: wala			
    2005/07/12	20:16:45.60	M			cyberrouter rg_system_full:275: spawned pid 42			
    2005/07/12	20:16:45.60	M			cyberrouter rg_system_full:255: /bin/watchdog			
    2005/07/12	20:16:45.60	M			cyberrouter rg_system_full:275: spawned pid 43			
    2005/07/12	20:16:45.60	M			yberrouter linux version 2.4.19openrg-rmk6-ds1 #341 fri jan 28 15:24:24 cst 2005	
    
    		
    2005/07/12	20:16:45.60	M			yberrouter cpu: intel xscale-ixp425 revision 1			
    2005/07/12	20:16:45.60	M			yberrouter machine: gemtek ixp425 wx5715			
    2005/07/12	20:16:45.60	M			yberrouter warning: bad configuration page, trying to continue			
    2005/07/12	20:16:45.60	M			
    
    yberrouter initrd (0xc01b1000 - 0xc01b7000) extends beyond physical memory - disabling initrd			
    2005/07/12	20:16:45.60	M			yberrouter memory range 0x1fff000-0x2000000 is excluded because of pci dma bug		
    
    	
    2005/07/12	20:16:45.60	M			
    
    yberrouter security risk: creating user accessible mapping for 0xc8000000 at 0xff000000			
    2005/07/12	20:16:45.60	M			
    
    yberrouter security risk: creating user accessible mapping for 0xc0000000 at 0xff00c000			
    2005/07/12	20:16:45.60	M			
    
    yberrouter security risk: creating user accessible mapping for 0xc4000000 at 0xff00d000			
    2005/07/12	20:16:45.60	M			yberrouter on node 0 totalpages: 8192			
    2005/07/12	20:16:45.60	M			yberrouter zone(0): 8192 pages.			
    2005/07/12	20:16:45.60	M			yberrouter zone(1): 0 pages.			
    2005/07/12	20:16:45.60	M			yberrouter zone(2): 0 pages.			
    2005/07/12	20:16:45.60	M			yberrouter kernel command line: console=ttys1,115200 root=/dev/ram0 rw nohalt		
    
    	
    2005/07/12	20:16:45.60	M			yberrouter using ixp425 timer 0 as timer source			
    2005/07/12	20:16:45.60	M			yberrouter calibrating delay loop... 266.24 bogomips			
    2005/07/12	20:16:45.60	M			yberrouter memory: 32mb = 32mb total			
    2005/07/12	20:16:45.62	M			yberrouter memory: 26004kb available (1395k code, 4757k data, 216k init)		
    
    	
    2005/07/12	20:16:45.62	M			yberrouter xscale cache/tlb locking copyright(c) 2001 montavista software, inc.		
    
    	
    2005/07/12	20:16:45.62	M			yberrouter dentry cache hash table entries: 4096 (order: 3, 32768 bytes)		
    
    	
    2005/07/12	20:16:45.62	M			yberrouter inode cache hash table entries: 2048 (order: 2, 16384 bytes)			
    2005/07/12	20:16:45.62	M			yberrouter mount-cache hash table entries: 512 (order: 0, 4096 bytes)			
    2005/07/12	20:16:45.62	M			yberrouter buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)			
    2005/07/12	20:16:45.62	M			yberrouter page-cache hash table entries: 8192 (order: 3, 32768 bytes)			
    2005/07/12	20:16:45.62	M			yberrouter posix conformance testing by unifix			
    2005/07/12	20:16:45.62	M			yberrouter pci: bus0: fast back to back transfers enabled			
    2005/07/12	20:16:45.62	M			yberrouter linux net4.0 for linux 2.4			
    2005/07/12	20:16:45.62	M			yberrouter based upon swansea university computer society net3.039			
    2005/07/12	20:16:45.62	M			yberrouter initializing rt netlink socket			
    2005/07/12	20:16:45.62	M			yberrouter starting kswapd			
    2005/07/12	20:16:45.62	M			yberrouter			
    2005/07/12	20:16:45.62	M			yberrouter random: 0xfa032fed			
    2005/07/12	20:16:45.62	M			yberrouter pty: 256 unix98 ptys configured			
    2005/07/12	20:16:45.62	M			
    
    yberrouter serial driver version 5.05c (2001-07-08) with many_ports share_irq serial_pci enabled			
    2005/07/12	20:16:45.62	M			yberrouter ttys00 at 0xff000003 (irq = 15) is a ixp425 uart			
    2005/07/12	20:16:45.62	M			yberrouter ttys01 at 0xff001003 (irq = 13) is a ixp425 uart			
    2005/07/12	20:16:45.62	M			
    
    yberrouter ramdisk driver initialized: 16 ram disks of 16384k size 1024 blocksize			
    2005/07/12	20:16:45.62	M			yberrouter loop: loaded (max 8 devices)			
    2005/07/12	20:16:45.62	M			yberrouter ppp generic driver version 2.4.2			
    2005/07/12	20:16:45.62	M			yberrouter net4: linux tcp/ip 1.0 for net4.0			
    2005/07/12	20:16:45.62	M			yberrouter ip protocols: icmp, udp, tcp, igmp			
    2005/07/12	20:16:45.63	M			yberrouter ip: routing cache hash table of 512 buckets, 4kbytes			
    2005/07/12	20:16:45.63	M			yberrouter tcp: hash tables configured (established 2048 bind 2048)			
    2005/07/12	20:16:45.63	M			yberrouter net4: unix domain sockets 1.0/smp for linux net4.0.			
    2005/07/12	20:16:45.63	M			yberrouter ipv6 v0.8 for net4.0			
    2005/07/12	20:16:45.63	M			yberrouter ipv6 over ipv4 tunneling driver			
    2005/07/12	20:16:45.63	M			yberrouter 802.1q vlan support v1.7 ben greear <greearb@candelatech.com>		
    
    	
    2005/07/12	20:16:45.63	M			yberrouter all bugs added by david s. miller <davem@redhat.com>			
    2005/07/12	20:16:45.63	M			yberrouter netwinder floating point emulator v0.95 (c) 1998-1999 rebel.com		
    
    	
    2005/07/12	20:16:45.63	M			yberrouter ppp mppe compression module registered			
    2005/07/12	20:16:45.63	M			yberrouter klips_info:ipsec_init: klips startup, frees/wan ipsec version: 1.99		
    
    	
    2005/07/12	20:16:45.63	M			yberrouter ramdisk: compressed image found at block 0			
    2005/07/12	20:16:45.63	M			yberrouter freeing initrd memory: 24k			
    2005/07/12	20:16:45.63	M			yberrouter vfs: mounted root (ext2 filesystem).			
    2005/07/12	20:16:45.63	M			yberrouter freeing init memory: 216k			
    2005/07/12	20:16:45.63	M			yberrouter mounting cramfs image at 'cramfs'			
    2005/07/12	20:16:45.63	M			yberrouter using buffer write method			
    2005/07/12	20:16:45.63	M			yberrouter using predefined mtd partitions.			
    2005/07/12	20:16:45.63	M			yberrouter creating 1 mtd partitions on 'ixp425 flash':			
    2005/07/12	20:16:45.63	M			yberrouter 0x00000000-0x00800000 : 'openrg'			
    2005/07/12	20:16:45.63	M			yberrouter ppp deflate compression module registered			
    2005/07/12	20:16:45.63	M			yberrouter ppp bsd compression module registered			
    2005/07/12	20:16:45.63	M			yberrouter intel csr module init.			
    2005/07/12	20:16:45.63	M			yberrouter error: ipsec_hwaccel_add_service: invalid function pointers!			
    2005/07/12	20:16:45.63	M			yberrouter intel csr qmgr & npe(s) init done.			
    2005/07/12	20:16:45.63	M			yberrouter initializing ixp425_eth driver 0.0.8			
    2005/07/12	20:16:45.65	M			yberrouter phy 0 mac address is:	04:04:04:04:04:04			
    2005/07/12	20:16:45.65	M			yberrouter phy 1 mac address is:	06:06:06:06:06:06			
    2005/07/12	20:16:45.65	M			yberrouter ipv4 device driver registered			
    2005/07/12	20:16:45.65	M			yberrouter loaded islpci, version 1.1.1.0			
    2005/07/12	20:16:45.65	M			yberrouter request_irq(28)			
    2005/07/12	20:16:45.66	M			yberrouter ip filter: initialized.  default = block all			
    2005/07/12	20:16:45.66	M			yberrouter phy 1 mac address is:	<censored>			
    2005/07/12	20:16:45.66	M			yberrouter phy 0 mac address is:	<censored>			
    2005/07/12	20:16:45.66	M			yberrouter ixp0: entering promiscuous mode			
    2005/07/12	20:16:45.66	M			yberrouter device ixp0 entered promiscuous mode			
    2005/07/12	20:16:45.66	M			yberrouter stp: ixp0 enters blocking mode			
    2005/07/12	20:16:45.66	M			yberrouter device eth0 entered promiscuous mode			
    2005/07/12	20:16:45.66	M			yberrouter stp: eth0 enters blocking mode			
    2005/07/12	20:16:45.66	M			yberrouter stp: ixp0 enters blocking mode			
    2005/07/12	20:16:45.66	M			cyberrouter error resolving hostname: ''			
    2005/07/12	20:16:45.66	M			cyberrouter dns: trying forwarder 68.87.66.196.			
    2005/07/12	20:16:45.66	M			starting pluto (frees/wan version 1.99)			
    2005/07/12	20:16:45.66	M			including x.509 patch with traffic selectors (version 0.9.21)			
    2005/07/12	20:16:45.66	M			changing to directory '/etc/ipsec.d/cacerts'			
    2005/07/12	20:16:45.66	M			warning: empty directory			
    2005/07/12	20:16:45.66	M			could not change to directory '/etc/ipsec.d/crls'			
    2005/07/12	20:16:45.66	M			could not open my default x.509 cert file '/etc/x509cert.der'			
    2005/07/12	20:16:45.66	M			openpgp certificate file '/etc/pgpcert.pgp' not found			
    2005/07/12	20:16:45.66	M			cyberrouter dns: trying forwarder 68.87.66.196.			
    2005/07/12	20:16:45.68	M			cyberrouter dns: trying forwarder 68.87.66.196.			
    2005/07/12	20:16:45.68	M			cyberrouter error resolving hostname: '0.0.0.0/0'			
    2005/07/12	20:16:45.68	M			cyberrouter error resolving hostname: '0.0.0.0/0'			
    2005/07/12	20:16:45.68	M			cyberrouter error resolving hostname: '0.0.0.0/0'[/quote]
     
  10. czeman

    czeman Network Guru Member

    So I brought the router home and it works great here! lol Could the reboots be caused by a large amount of network traffic?
     

Share This Page