You are not logged in.

#1 2011-06-19 11:30:03

jazz.arch
Member
From: Austria
Registered: 2008-09-20
Posts: 29

[Solved] rc.conf change - causes router malfunction?

Hey!

I've recently updated my system and changed rc.conf accordingly:

interface=eth0
address=
netmask=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

Since then, I can connect to my WLAN router normally, and it works for a few seconds. Then, it suddenly disconnects and the router malfunctions in a way that all devices are disconnected and can't connect again.

In /var/log/messages.log I see some strange happenings with iwlagn:

Jun 19 14:44:54 localhost NetworkManager[1012]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Jun 19 14:45:09 localhost NetworkManager[1012]: <info> (wlan0): IP6 addrconf timed out or failed.
Jun 19 14:45:09 localhost NetworkManager[1012]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) scheduled...
Jun 19 14:45:09 localhost NetworkManager[1012]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) started...
Jun 19 14:45:09 localhost NetworkManager[1012]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 19 14:45:09 localhost NetworkManager[1012]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) complete.
Jun 19 14:45:09 localhost NetworkManager[1012]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jun 19 14:45:10 localhost NetworkManager[1012]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Jun 19 14:45:10 localhost NetworkManager[1012]: <info> Policy set 'sputnik' (wlan0) as default for IPv4 routing and DNS.
Jun 19 14:45:10 localhost NetworkManager[1012]: <info> Activation (wlan0) successful, device activated.
Jun 19 14:45:10 localhost NetworkManager[1012]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 19 14:45:12 localhost kernel: [  108.809156] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 68:7f:74:9b:34:1e tid = 0
Jun 19 14:45:21 localhost kernel: [  118.293810] iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting
Jun 19 14:45:22 localhost kernel: [  118.359258] cfg80211: Calling CRDA to update world regulatory domain
Jun 19 14:45:22 localhost NetworkManager[1012]: <info> (wlan0): supplicant interface state: completed -> disconnected
Jun 19 14:45:22 localhost NetworkManager[1012]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jun 19 14:45:25 localhost NetworkManager[1012]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Jun 19 14:45:27 localhost NetworkManager[1012]: <info> (wlan0): roamed from BSSID 68:7F:74:9B:34:1E (sputnik) to (none) ((none))
Jun 19 14:45:37 localhost NetworkManager[1012]: <info> (wlan0): device state change: activated -> disconnected (reason 'supplicant-timeout') [100 30 11]
Jun 19 14:45:37 localhost NetworkManager[1012]: <info> (wlan0): deactivating device (reason: 11).
Jun 19 14:45:37 localhost dhcpcd[1342]: received SIGTERM, stopping
Jun 19 14:45:37 localhost dhcpcd[1342]: wlan0: removing interface
Jun 19 14:45:37 localhost NetworkManager[1012]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1342
Jun 19 14:45:37 localhost NetworkManager[1012]: <warn> (pid 1342) unhandled DHCP event for interface wlan0
Jun 19 14:45:37 localhost NetworkManager[1012]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Jun 19 14:45:37 localhost NetworkManager[1012]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.

As you can see, everything works fine until iwlagn starts interfering.

Wired connections work just fine.
I'm currently using network-manager, but using wicd produces the same results.

What could be wrong here?

Thanks!

Last edited by jazz.arch (2011-06-20 17:24:25)

Offline

#2 2011-06-20 17:23:57

jazz.arch
Member
From: Austria
Registered: 2008-09-20
Posts: 29

Re: [Solved] rc.conf change - causes router malfunction?

Alright, seems like the cause of the problems was my router itself.
Its a Linksys 160NL with ddwrt build 14896.

If some stumbles upon what could be the cause of that strange behavior, please let me know.

Offline

#3 2011-06-29 02:58:57

jholbrook
Member
Registered: 2010-07-08
Posts: 18

Re: [Solved] rc.conf change - causes router malfunction?

When you say it's solved could you please tell me what you did. I'm having the same problem with a Buffalo router running DD-WRT with my new ThinkPad laptop. All my other wireless devices work fine. As soon as I fire up my laptop and connect - BOOM the router dies and I have to physically unplug and plug it back in.

Offline

Board footer

Powered by FluxBB