OpenWrt Forum Archive

Topic: WRT54G Wireless unstable

The content of this topic has been archived on 29 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello,
Im having a strange problem with my WRT54G V2. The wireless signal is unstable and I can't connect. If I try to scan with netstumbler I get the following:

http://img526.imageshack.us/img526/2581/clipboard01mn3.th.jpg

I already tried to reboot the router without success.

Here's my nvram config for wireless:

wl0_akm=psk psk2
wl0_infra=1
wl0_ifname=eth1
wl0_mode=ap
wl0_ssid=MyHome
wl0id=0x4320
wl0_closed=0
wl0gpio2=0
wl0gpio3=0
wl0_wpa_psk=[cut]
wl0_radio=1
wl0_channel=11
wl0_crypto=tkip

Here's some interesting log messages:

Jan  1 01:00:08 (none) kern.warn kernel: eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.37.0
Jan  1 01:00:08 (none) user.info : Using /lib/modules/2.4.30/wl.o
Jan  1 01:00:08 (none) user.info : Warning: loading wl will taint the kernel: no license
Jan  1 01:00:08 (none) user.info :   See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/wlcompat.o
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/switch-core.o
Jan  1 01:00:09 (none) user.info : insmod: A module named switch-core already exists
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth0: No Robo switch in managed mode found
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth1: [switch-robo.c:90] SIOCGETCPHYRD failed!
Jan  1 01:00:09 (none) kern.warn kernel: [switch-robo.c:90] SIOCGETCPHYRD failed!
Jan  1 01:00:09 (none) kern.warn kernel: No Robo switch in managed mode found
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth2: No such device
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth3: No such device
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/switch-robo.o
Jan  1 01:00:09 (none) user.info : insmod: init_module: switch-robo: No such device
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/switch-adm.o
Jan  1 01:00:09 (none) user.info : insmod: A module named switch-adm already exists
vinx wrote:

Im having a strange problem with my WRT54G V2. The wireless signal is unstable and I can't connect. If I try to scan with netstumbler I get the following:

Could be interference; hard to track down "my wifi won't work" issues remotely.

Jan  1 01:00:08 (none) kern.warn kernel: eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.37.0
Jan  1 01:00:08 (none) user.info : Using /lib/modules/2.4.30/wl.o
Jan  1 01:00:08 (none) user.info : Warning: loading wl will taint the kernel: no license
Jan  1 01:00:08 (none) user.info :   See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/wlcompat.o
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/switch-core.o
Jan  1 01:00:09 (none) user.info : insmod: A module named switch-core already exists
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth0: No Robo switch in managed mode found
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth1: [switch-robo.c:90] SIOCGETCPHYRD failed!
Jan  1 01:00:09 (none) kern.warn kernel: [switch-robo.c:90] SIOCGETCPHYRD failed!
Jan  1 01:00:09 (none) kern.warn kernel: No Robo switch in managed mode found
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth2: No such device
Jan  1 01:00:09 (none) kern.warn kernel: Probing device eth3: No such device
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/switch-robo.o
Jan  1 01:00:09 (none) user.info : insmod: init_module: switch-robo: No such device
Jan  1 01:00:09 (none) user.info : Using /lib/modules/2.4.30/switch-adm.o
Jan  1 01:00:09 (none) user.info : insmod: A module named switch-adm already exists

Normal, and unrelated. (these aren't actually errors)

mbm wrote:

Could be interference; hard to track down "my wifi won't work" issues remotely.

hmmm... I don't think I have also a WL500Gp and if I connect this One, the wireless works, the problem is that signal is weak (I already opened a thread for this).

The discussion might have continued from here.