Posted: Mon Apr 12, 2021 15:26 Post subject: WRT3200ACM 5G Ip Address
Hi Guys
I used DD-WRT back in the day of the LInksys WRT54G. Recently i purchased a Linksys WRT3200ACM. This weekend just gone, i installed DD-WRT onto my 3200.
My intension was to setup a router, as a VPN client for NORD. The VPN config went a breeze, and i have no issues with devices that are cabled in. Wifi i really struggled to get going and found a post which pointed out Build 40009 as a know working ver. After installing 40009, i managed to get Wifi working with the following settings:
Im facing an issue, where i struggle to get connected to Wifi. The 1st connection worked straight away, and i noticed that my device switches from 2.4G to 5G. Initially on the router, i see both 2.4G and 5G lights active, and then 2.4G turns off and my connection remains active on 5G.
When i disconnect and try reconnect, the device is defaulting to 5G. I can see the connection beign made with the router, but eventually the connection fails to obtain an IP address. When i get lucky enough, my device authenticates over 2.4G, i get an IP, and then it switches back to 5G without any issue.
Is this a know issue and would anyone have any idea how i could correct the behaviour so that i can obtain an ip on 5G?
Hopefully i've provided enough info, but please let me know if anything is missing.
Posted: Mon Apr 12, 2021 17:42 Post subject: syslog
Not sure if this will help at all ... I tried turning on syslog to see if it pointed at anything useful. Seems clean although it does show how the device bounces around
Initially tried to connect on ath0 (5G) - Authentication Successful, but no IP
Apr 12 18:17:27 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f MLME: auth request, signal -65 (Accepted)
Apr 12 18:17:27 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f MLME: assoc request, signal -65 (Accepted)
Apr 12 18:17:27 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f IEEE 802.11: associated (aid 1)
Apr 12 18:17:28 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f RADIUS: starting accounting session DB1F73D4F6177883
Apr 12 18:17:28 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f WPA: pairwise key handshake completed (RSN)
Apr 12 18:17:28 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f IEEE 802.11: authenticated
The device then connects on ath1 (2.4G) - this time obtaining an IP.
Apr 12 18:18:07 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f MLME: auth request, signal -65 (Accepted)
Apr 12 18:18:07 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f MLME: assoc request, signal -69 (Accepted)
Apr 12 18:18:07 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f IEEE 802.11: associated (aid 1)
Apr 12 18:18:08 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f RADIUS: starting accounting session B41C72F78BDC75F7
Apr 12 18:18:08 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f WPA: pairwise key handshake completed (RSN)
Apr 12 18:18:09 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f IEEE 802.11: authenticated
The connection flicks back to ath0 (5G) - the device retains its IP
Apr 12 18:20:19 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f MLME: auth request, signal -70 (Accepted)
Apr 12 18:20:19 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f MLME: assoc request, signal -70 (Accepted)
Apr 12 18:20:19 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f IEEE 802.11: associated (aid 1)
Apr 12 18:20:19 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f RADIUS: starting accounting session BBA36971FFB2E15F
Apr 12 18:20:19 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f WPA: pairwise key handshake completed (RSN)
Apr 12 18:20:19 DD-WRT daemon.info hostapd: ath0: STA 91:09:cf:6e:c9:0f IEEE 802.11: authenticated
The device drops its connection to ath1 (2.4G) in favour of ath0 (5G) - The connection remains stable on the device
Apr 12 18:25:30 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f IEEE 802.11: disassociated due to inactivity
Apr 12 18:25:31 DD-WRT daemon.info hostapd: ath1: STA 91:09:cf:6e:c9:0f IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Its just the initial hurdle of getting connected which I'd like to get resolved.
If you use smart home automation devices, IoT, smart switch, doorbell etc. this router's wifi is problematic.
To configure around this problem try disabling LDPC (old method was disable WMM), or BG-Mixed / G-Only.
Thanks a stack blkt, really appreciate all the help and info! Ill give 44048 a go when I next get some time spare and report back (May only be at the weekend).
I've noticed the Unit runs pretty hot (CPU 73.6 / WL0 44.9 / WL1 46.6) despite the load being next to nothing. Is this normal and have you got any recommendations for cooling?
So updated to 44048 and found the problem still existed. I could associate to 5G, but I just wouldn't obtain an IP address. 2.4G still worked fine.
I reset nvram and rebuilt the lot only to find i still had the same problem over 5G. At that stage, I figured it must be something to do with the 5G Antenna cos the syslog shows the authentication was fine so started changing antenna settings, and i got it WORKING! Woohoo!