I've just setup OpenWRT (latest version) on my WRT3200ACM V1, and perfectly worked all day... but after about 8h, all the wi-fi interfaces went down, and cannot revive them no matter what I do (LAN and internet connectivity through WAN still work):
Any ideas on what could have suddenly happened? I haven't tweaked with any network settings once all got running 8h ago!
Thanks for any help.
PS: reverting back to the original Lynksys FW partition (thinking it could have been a HW failure), got all working, so it's definitively must be an OpenWRT configuration issue.
To complement with a real access point is also a viable long term solution for that router.
The router it self is not bad, but the wifi chip is not so good.
Building a "train" of three components (modem, router, AP) is going to be a bit overkill. Also because the Wi-Fi of this router is very powerful and fast.
The stock firmware is instead flawless, and has great performance... It's just old and probably insecure.
Therefore, I wouldn't say that the Wi-Fi chip itself is bad, because otherwise stock firmware would have problems as well... I'd believe the problem is the driver implementation that is embedded in OpenWRT.
Because the stock firmware is open source, wonder if those drivers from that codebase were transplanted into the WRT3200ACM port of OpenWRT...
What version of OpenWrt. This is not an issue I have seen reported before for this device. Both TX power and CC (country) are ignored and pulled from the EEPROM as per the device locale. If you want to use auto, maybe try some variation on:
Apologies, which logs should look?
kernel & System logs are completely crumbled with these repeating continuously:
[ 943.845165] ieee80211 phy0: buffer is NULL for tx done ring
[ 943.845209] ieee80211 phy0: adapter does not exist
[ 943.855637] ieee80211 phy0: adapter does not exist
[ 943.860475] ieee80211 phy0: adapter does not exist
[ 943.865295] ieee80211 phy0: adapter does not exist
[ 943.870108] ieee80211 phy0: adapter does not exist
[ 943.874917] ieee80211 phy0: adapter does not exist
[ 943.955532] ieee80211 phy0: buffer is NULL for tx done ring
[ 943.995231] ieee80211 phy1: buffer is NULL for tx done ring
[ 944.055258] ieee80211 phy1: buffer is NULL for tx done ring
[ 944.095275] ieee80211 phy0: buffer is NULL for tx done ring
[ 944.155303] ieee80211 phy0: buffer is NULL for tx done ring
[ 944.195322] ieee80211 phy1: buffer is NULL for tx done ring
[ 944.255349] ieee80211 phy1: buffer is NULL for tx done ring
Wow that's interesting, indeed I did tweak some LED configurations... may it be that?
All LED configurations actually do work, but should I try removing them?
config system
option ttylogin '0'
option log_size '64'
option urandom_seed '0'
option compat_version '1.1'
option hostname 'gta-router'
option log_proto 'udp'
option conloglevel '8'
option cronloglevel '5'
option zonename 'America/Vancouver'
option timezone 'PST8PDT,M3.2.0,M11.1.0'
config timeserver 'ntp'
list server '0.openwrt.pool.ntp.org'
list server 'time.google.com'
list server 'time.windows.com'
config led
option name 'Power'
option sysfs 'rango:white:power'
option trigger 'heartbeat'
config led 'led_wan'
option name 'WAN'
option sysfs 'pca963x:rango:white:wan'
option trigger 'netdev'
option dev 'wan'
list mode 'link'
config led
option sysfs 'rango:white:wlan_2g'
option trigger 'netdev'
option dev 'wlan1'
list mode 'tx'
list mode 'rx'
option name 'WLAN 2.4GHz'
config led
option name 'WLAN 5GHz'
option sysfs 'rango:white:wlan_5g'
option trigger 'netdev'
option dev 'wlan0'
list mode 'tx'
list mode 'rx'
config led 'led_usb1'
option name 'USB 1'
option sysfs 'pca963x:rango:white:usb2'
option trigger 'usbport'
list port 'usb1-port1'
config led 'led_usb2'
option name 'USB 2'
option sysfs 'pca963x:rango:white:usb3_1'
option trigger 'usbport'
list port 'usb2-port1'
list port 'usb3-port1'
config led 'led_usb2_ss'
option name 'USB 2 SS'
option sysfs 'pca963x:rango:white:usb3_2'
option trigger 'usbport'
list port 'usb3-port1'
Country Code (CC) as in Canada (CA) , I see Vancouver in your TZ setting, but US in the WIFI setup, whiich should be ignored. mwlwifi will grab CC from your EEPROM, so if a CA unit mwlwifi will be CA, but the third radio will default to US, so be sure to set CC.
