Wireless Problems

[amorak]

Hi guys,

I have the same problem with 2 different RT-n66U's, running either the latest Merlin or the latest stock Firmwares...

The wifi works for a bit, then gets super slow... my pings go from sub 20ms to 500+ms, and speeds of 1-2kbps from 3,000kbps (external speed test just to illustrate the difference).

Any thoughts on what setting ai need to change to get this stable?

 

[amorak]

*bump* for thoughts

 

[seth_space]

2,4 of 5 Ghz?

Lots of different wireless cleints and AP in the surrounding?
Other possible sources of distortion?

Did you look with a programm like:
http://www.metageek.net/products/inssider/

Did you used the auto setting or did you manually set the config?

Lots of questions and lots of possible causes i am afraid.

some tips: (or use google)

http://www.webopedia.com/DidYouKnow...orking/wireless_lan_network_optimization.html

http://www.howtogeek.com/howto/2113...ter-channel-to-optimize-your-wireless-signal/

 

[amorak]

Both 24ghz and 5ghz become unreachable randomly. SSID is still broadcast, but connection drops. A reboot helps.

ANy links to best settings for the N66u fore wireless stability?

 

[amorak]

What are acceptable temps? I am seeing 80-90C.... On both my new RT-N66U and my old one... Same connection problems... I am in AP mode...

Any suggestions?

 

[RMerlin]

80C-90C is definitely abnormal and too high. The chip will throttle in speed when it gets THAT high, which might explain your problem.

You shouldn't get over 65C in normal uses (highest I got myself during the summer was 62C or 63C).

 

[amorak]

I put it on the floor upside down in the basement (cement) to try and keep it cool, see if the connection gets any cooler

It's weird, I am having the same problem regardless of my old RT-N66U and the replacement I bought... They work fine (wireless) for an hour, then the connections are dropped...

SSID are still broadcast, but you can't connect, and if you can, there is liek 1-2kbps of data transferred...

I recently upgraded the firmware on my ISP-provided router (RT-N66U are in AP mode), could that be doing anything? I don't see how it could be making the RT-N66U wireless unreachable (i'd understand if I had internet connection problems, but not wireless connection problems)...

A reboot and cool down gets it working again without fail.

Really odd that this is on two different RT-N66Us, either firmware (doubtful, as this worked fine for months before hand), or something else...

I am leading myself to believe it's my ISP router, somehow, as I have run tomato and other firmwares and had the exact same problem... Just can't figure out how the ISP router could be messing up the AP's ability to have clients connect wirelessly?

Thoughts?

 

[amorak]

5 minutes later: Router is unconnectable again. Tempruatures are under 50C per the "Performance Tuning" tab.

Could this really be the ISP router update doing this to the RT-n66U router?!

 

[KevTech]

You should run a line quality test.

http://www.dslreports.com/linequality

You must be pingable to run the test.

 

[TonyH]

5 minutes later: Router is unconnectable again. Tempruatures are under 50C per the "Performance Tuning" tab.

Could this really be the ISP router update doing this to the RT-n66U router?!

Hi,
LAN port has same issues?
Was it working fine B4 you updated f/w for the ISP supplied router/modem? If you can, ask your ISP to turn the router into bridge mode and only use your ASUS router, If they won't then there is a way to do it your self. My ISP downloaded a different firmware permanently turning it into bridge mode only for me. You should try that and if not Google how to do it your self using DMZ.

 

[amorak]

Does any of the below help anyone?

Jan 1 00:00:08 kernel: br0: starting userspace STP failed, staring kernel STP
Jan 1 00:00:08 kernel: vlan1: dev_set_promiscuity(master, 1)
Jan 1 00:00:08 kernel: device eth0 entered promiscuous mode
Jan 1 00:00:08 kernel: device vlan1 entered promiscuous mode
Jan 1 00:00:08 kernel: usb 1-1.4: configuration #1 chosen from 1 choice
Jan 1 00:00:08 kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Jan 1 00:00:09 kernel: device eth1 entered promiscuous mode
Jan 1 00:00:10 kernel: scsi 0:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0
Jan 1 00:00:10 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Jan 1 00:00:10 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan 1 00:00:10 kernel: device eth2 entered promiscuous mode
Jan 1 00:00:10 kernel: br0: port 3(eth2) entering listening state
Jan 1 00:00:10 kernel: br0: port 2(eth1) entering listening state
Jan 1 00:00:10 kernel: br0: port 1(vlan1) entering listening state
Jan 1 00:00:10 kernel: br0: port 3(eth2) entering learning state
Jan 1 00:00:10 kernel: br0: port 2(eth1) entering learning state
Jan 1 00:00:10 kernel: br0: port 1(vlan1) entering learning state
Jan 1 00:00:10 kernel: br0: topology change detected, propagating
Jan 1 00:00:10 kernel: br0: port 3(eth2) entering forwarding state
Jan 1 00:00:10 kernel: br0: topology change detected, propagating
Jan 1 00:00:10 kernel: br0: port 2(eth1) entering forwarding state
Jan 1 00:00:10 kernel: br0: topology change detected, propagating
Jan 1 00:00:10 kernel: br0: port 1(vlan1) entering forwarding state
Jan 1 00:00:10 RT-N66U: start httpd
Jan 1 00:00:11 notify_rc : stop_dnsmasq
Jan 1 00:00:11 notify_rc : start_dnsmasq
Jan 1 00:00:11 rc_service: start_dnsmasq is waitting stop_dnsmasq...
Jan 1 00:00:11 disk monitor: be idle
Jan 1 00:00:13 notify_rc : stop_ntpc
Jan 1 00:00:13 rc_service: stop_ntpc is waitting start_dnsmasq...
Jan 1 00:00:14 notify_rc : start_ntpc
Jan 1 00:00:14 rc_service: start_ntpc is waitting stop_ntpc...
Dec 17 04:38:28 notify_rc : restart_diskmon
Dec 17 04:38:28 disk monitor: be idle
Dec 17 04:39:24 notify_rc : set_wltxpower;restart_wireless
Dec 17 04:39:28 kernel: Ebtables v2.0 registered
Dec 17 04:39:28 kernel: device eth1 left promiscuous mode
Dec 17 04:39:28 kernel: br0: port 2(eth1) entering disabled state
Dec 17 04:39:28 kernel: device eth2 left promiscuous mode
Dec 17 04:39:29 kernel: br0: port 3(eth2) entering disabled state
Dec 17 04:39:29 kernel: wl_module_init: passivemode set to 0x0
Dec 17 04:39:29 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:39:29 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:39:30 kernel: device eth1 entered promiscuous mode
Dec 17 04:39:30 kernel: br0: port 2(eth1) entering listening state
Dec 17 04:39:31 kernel: br0: port 2(eth1) entering learning state
Dec 17 04:39:31 kernel: br0: topology change detected, propagating
Dec 17 04:39:31 kernel: br0: port 2(eth1) entering forwarding state
Dec 17 04:39:32 kernel: device eth2 entered promiscuous mode
Dec 17 04:39:32 kernel: br0: port 3(eth2) entering listening state
Dec 17 04:39:32 kernel: br0: port 3(eth2) entering learning state
Dec 17 04:39:32 kernel: br0: topology change detected, propagating
Dec 17 04:39:32 kernel: br0: port 3(eth2) entering forwarding state
Dec 17 04:41:13 notify_rc : restart_wireless
Dec 17 04:41:14 kernel: device eth1 left promiscuous mode
Dec 17 04:41:14 kernel: br0: port 2(eth1) entering disabled state
Dec 17 04:41:15 kernel: device eth2 left promiscuous mode
Dec 17 04:41:15 kernel: br0: port 3(eth2) entering disabled state
Dec 17 04:41:15 kernel: wl_module_init: passivemode set to 0x0
Dec 17 04:41:15 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:41:15 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:41:16 kernel: device eth1 entered promiscuous mode
Dec 17 04:41:16 kernel: br0: port 2(eth1) entering listening state
Dec 17 04:41:17 kernel: br0: port 2(eth1) entering learning state
Dec 17 04:41:17 kernel: br0: topology change detected, propagating
Dec 17 04:41:17 kernel: br0: port 2(eth1) entering forwarding state
Dec 17 04:41:18 kernel: device eth2 entered promiscuous mode
Dec 17 04:41:18 kernel: br0: port 3(eth2) entering listening state
Dec 17 04:41:18 kernel: br0: port 3(eth2) entering learning state
Dec 17 04:41:18 kernel: br0: topology change detected, propagating
Dec 17 04:41:18 kernel: br0: port 3(eth2) entering forwarding state
Dec 17 04:44:00 notify_rc : set_wltxpower;restart_wireless
Dec 17 04:44:02 kernel: device eth1 left promiscuous mode
Dec 17 04:44:02 kernel: br0: port 2(eth1) entering disabled state
Dec 17 04:44:02 kernel: device eth2 left promiscuous mode
Dec 17 04:44:02 kernel: br0: port 3(eth2) entering disabled state
Dec 17 04:44:02 kernel: wl_module_init: passivemode set to 0x0
Dec 17 04:44:02 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:44:02 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:44:04 kernel: device eth1 entered promiscuous mode
Dec 17 04:44:04 kernel: br0: port 2(eth1) entering listening state
Dec 17 04:44:04 kernel: br0: port 2(eth1) entering learning state
Dec 17 04:44:04 kernel: br0: topology change detected, propagating
Dec 17 04:44:04 kernel: br0: port 2(eth1) entering forwarding state
Dec 17 04:44:05 kernel: device eth2 entered promiscuous mode
Dec 17 04:44:05 kernel: br0: port 3(eth2) entering listening state
Dec 17 04:44:05 kernel: br0: port 3(eth2) entering learning state
Dec 17 04:44:05 kernel: br0: topology change detected, propagating
Dec 17 04:44:05 kernel: br0: port 3(eth2) entering forwarding state
Dec 17 04:44:27 notify_rc : set_wltxpower;restart_wireless
Dec 17 04:44:29 kernel: device eth1 left promiscuous mode
Dec 17 04:44:29 kernel: br0: port 2(eth1) entering disabled state
Dec 17 04:44:29 kernel: device eth2 left promiscuous mode
Dec 17 04:44:29 kernel: br0: port 3(eth2) entering disabled state
Dec 17 04:44:29 kernel: wl_module_init: passivemode set to 0x0
Dec 17 04:44:29 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:44:29 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 17 04:44:31 kernel: device eth1 entered promiscuous mode
Dec 17 04:44:31 kernel: br0: port 2(eth1) entering listening state
Dec 17 04:44:31 kernel: br0: port 2(eth1) entering learning state
Dec 17 04:44:31 kernel: br0: topology change detected, propagating
Dec 17 04:44:31 kernel: br0: port 2(eth1) entering forwarding state
Dec 17 04:44:32 kernel: device eth2 entered promiscuous mode
Dec 17 04:44:32 kernel: br0: port 3(eth2) entering listening state
Dec 17 04:44:32 kernel: br0: port 3(eth2) entering learning state
Dec 17 04:44:32 kernel: br0: topology change detected, propagating
Dec 17 04:44:32 kernel: br0: port 3(eth2) entering forwarding state

 

[RogerSC]

Does any of the below help anyone?

Nope, doesn't look familiar, but from the first couple of lines, I'd suggest seeing what happens if you turn off "Spanning-Tree Protocol" (Advanced Settings -> LAN -> LAN - Switch Control).

 

[RMerlin]

That warning is normal.