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

WRV54g Firmware 2.38

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by dumbo, Apr 13, 2005.

  1. dumbo

    dumbo Network Guru Member

    Can anybody verify this: When I tranfer large file 50MB between 2 PC on the LAN side - 1 with 802.1G and 1 with 802.1B, my router reboots!!

    This is the error I get:

    Tue Apr 12 18:55:08 2005
    estream_write_efd:797: socket 41: failed write()
    Tue Apr 12 18:54:17 2005
    Error resolving hostname: ""
    Tue Apr 12 18:54:17 2005
    SNMP: Binding agent on XX.XX.XX.XX
    Tue Apr 12 18:54:16 2005
    Error resolving hostname: ""
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 43
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: wala
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 42
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 17000019 long 1
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 41
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 10000006 ssid 2raurrdr
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 40
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: insmod watchdog_mod.o
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 39
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 10000002 ssid "xxxxxxxxx" Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 38
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 11000002 long 5
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 37
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 11000001 long 1F4
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 36
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 17000016 long 0
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 35
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 1700000a long 968b8482
    Tue Apr 12 18:54:15 2005
    rg_system_full:275: spawned PID 34
    Tue Apr 12 18:54:15 2005
    rg_system_full:255: setoid eth0 17000007 long 6
    Wed Jan 1 00:00:00 2003
    rg_system_full:275: spawned PID 33
    Wed Jan 1 00:00:00 2003
    rg_system_full:255: date -s 2005.4.12-18:53:75
    Wed Jan 1 00:00:00 2003
    mt_igmp_params_init:61: IGMP reconf: new lan interface: eth0 Wed Jan 1 00:00:00 2003
    mt_igmp_params_init:61: IGMP reconf: new lan interface: ixp0 Wed Jan 1 00:00:00 2003
    mt_igmp_params_init:61: IGMP reconf: new lan interface: br0
    Wed Jan 1 00:00:00 2003
    Failed to set device eth0 netmask: Cannot assign requested address Wed Jan 1 00:00:00 2003 Failed to set device ixp0 netmask: Cannot assign requested address Wed Jan 1 00:00:00 2003
    mt_igmp_params_init:61: IGMP reconf: new lan interface: eth0 Wed Jan 1 00:00:00 2003
    mt_igmp_params_init:61: IGMP reconf: new lan interface: ixp0 Wed Jan 1 00:00:00 2003
    mt_igmp_params_init:61: IGMP reconf: new lan interface: br0
    Wed Jan 1 00:00:00 2003
    SNMP: Binding agent on 10.92.110.1
    Wed Jan 1 00:00:00 2003
    Activated DHCP Server for dev br0
    Wed Jan 1 00:00:00 2003
    mt_igmp_changed:99: IGMP changed: interface: br0
    Wed Jan 1 00:00:00 2003
    rg_system_full:275: spawned PID 32
    Wed Jan 1 00:00:00 2003
    rg_system_full:255: pluto --nofork --debug-none --uniqueids
     
  2. richman

    richman Guest

    Or even better..... Explain what the hell the logs mean

    I updated my WRV54G to the current firmware and now I recieve dozens of mails a day like "estream_write_efd:797:" and have no idea what they mean.
    Is there a viewer or a manual anywhere that explains the output??
     
  3. JRB4773

    JRB4773 LI Guru Member

    I am having the same types of problems, but I'm only losing the air-interface. The LAN side of the router seems to stay "alive", but the air interface shuts down. When I pull a log of the router traffic, I see the "blocking mode" starting and stopping. I lose the air-interface for a bit (the example below looks to be about 13 seconds), then it comes back on it's own. I have the beacon turned on. When I look at my WLAN controller on my laptop, I don't see my AP on the list of APs in the area. If I wait it comes back, then I auto connect. I have a number of other APs in my area which I have excluded and I'm on a channel with a buffer of two channels between the other APs in my area.

    01-01-2007 17:38:28 Daemon.Error 192.168.1.1 Jan 1 17:38:30 2007 linksys estream_write_efd:797: socket 33: failed write()
    01-01-2007 17:36:51 Kernel.Warning 192.168.1.1 Jan 1 17:36:53 2007 linksys STP: ixp0 exits blocking mode
    01-01-2007 17:36:51 Kernel.Warning 192.168.1.1 Jan 1 17:36:53 2007 linksys STP: eth0 exits blocking mode
    01-01-2007 17:36:46 Daemon.Info 192.168.1.1 Dec 31 18:00:11 2002 linksys TOD got new time 1167694609
    01-01-2007 17:36:46 Daemon.Info 192.168.1.1 Dec 31 18:00:09 2002 linksys SNMP: Binding agent on [my WAN IP]
    01-01-2007 17:36:39 System0.Warning 192.168.1.1 Dec 31 18:00:03 2002 linksys Jan 1 00:00:03 pluto[34]: OpenPGP certificate file '/etc/pgpcert.pgp' not found
    01-01-2007 17:36:39 System0.Warning 192.168.1.1 Dec 31 18:00:03 2002 linksys Jan 1 00:00:03 pluto[34]: could not open my default X.509 cert file '/etc/x509cert.der'
    01-01-2007 17:36:38 System0.Warning 192.168.1.1 Dec 31 18:00:03 2002 linksys Jan 1 00:00:03 pluto[34]: Could not change to directory '/etc/ipsec.d/crls'
    01-01-2007 17:36:38 System0.Warning 192.168.1.1 Dec 31 18:00:03 2002 linksys Jan 1 00:00:03 pluto[34]: Warning: empty directory
    01-01-2007 17:36:38 System0.Warning 192.168.1.1 Dec 31 18:00:03 2002 linksys Jan 1 00:00:03 pluto[34]: Changing to directory '/etc/ipsec.d/cacerts'
    01-01-2007 17:36:38 System0.Warning 192.168.1.1 Dec 31 18:00:03 2002 linksys Jan 1 00:00:03 pluto[34]: including X.509 patch with traffic selectors (Version 0.9.21)
    01-01-2007 17:36:38 System0.Warning 192.168.1.1 Dec 31 18:00:03 2002 linksys Jan 1 00:00:03 pluto[34]: Starting Pluto (FreeS/WAN Version 1.99)
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys STP: ixp0 enters blocking mode
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys STP: eth0 enters blocking mode
    01-01-2007 17:36:38 Kernel.Info 192.168.1.1 Dec 31 18:00:02 2002 linksys device eth0 entered promiscuous mode
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys STP: ixp0 enters blocking mode
    01-01-2007 17:36:38 Kernel.Info 192.168.1.1 Dec 31 18:00:02 2002 linksys device ixp0 entered promiscuous mode
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys ixp0: Entering promiscuous mode
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys PHY 0 MAC address is:<009>00:0c:41:d6:39:64
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys PHY 1 MAC address is:<009>00:0c:41:d6:39:65
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys IP Filter: initialized. Default = block all
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys request_irq(28)
    01-01-2007 17:36:38 Kernel.Info 192.168.1.1 Dec 31 18:00:02 2002 linksys Loaded islpci, version 1.1.1.0
    01-01-2007 17:36:38 Kernel.Warning 192.168.1.1 Dec 31 18:00:02 2002 linksys IPV4 device driver registered

    (While writing this message my AP dropped the air-interface like I've been describing. It doesn't appear to happen when I'm not using it...)

    When I called support they started asking me to check packet fragmentation (MTU) and other things on my local machines, they didn't look at the AP at all. The problem started occurring with this firmware update. I'm not sure if Linksys is aware of this or not, but their support people haven't given me any information that leads me to believe they're working on the problem.

    To date, there hasn't been a response from my last inquiry about the status of my service request.
     
  4. TazUk

    TazUk Network Guru Member

    Which firmware update, 2.38?

    Have you tried the latest firmware 2.39.2?
     
  5. JRB4773

    JRB4773 LI Guru Member

    I am currently running 2.39.2, I'm considering going backward in versions (if it's possible). I have to admit that I perceive this to have started before the firmware update. It may have been happening all along and I just didn't notice it.

    I've had my Syslog running, the problem with the air interface occurrs even when I'm not at home (not using it). I see the same type of activity (although not as often) when I'm logging sysinfo but not home.

    These things are so frustrating. Especially when it's a more advanced problem than the generic user would have. I'll keep hacking away at this, if anyone has ideas, I'd love 'em. Like I said, I haven't had any luck with tech support. I'll keep saving logfiles on the off chance I decide to call in yet again. :)
     

Share This Page