Posted: Mon May 15, 2023 9:18 Post subject: DHCP / Wi-Fi not working
Hello,
On a WRT3200 ACM with r51741 which has been installed for a while, I can't get the Wi-Fi / DHCP. My regular computer is connected with cable to the router. I can reach the router if I set a static IP, but not DHCP.
I upgraded to r52569 but this did not help.
I noticed these ones after I tried to add a new virtual AP:
Code:
[ 522.122344] br0: port 6(wlan0) entered blocking state
[ 522.127421] br0: port 6(wlan0) entered forwarding state
[ 534.376435] br0: port 2(wlan2) entered disabled state
[ 539.405942] br0: port 2(wlan2) entered blocking state
[ 539.411020] br0: port 2(wlan2) entered forwarding state
[ 539.419567] br0: port 7(wlan2.1) entered blocking state
[ 539.424832] br0: port 7(wlan2.1) entered disabled state
[ 539.430219] device wlan2.1 entered promiscuous mode
[ 539.435371] br0: port 7(wlan2.1) entered blocking state
[ 539.435373] br0: port 7(wlan2.1) entered forwarding state
[ 539.469481] br0: port 8(wlan2.2) entered blocking state
[ 539.474790] br0: port 8(wlan2.2) entered disabled state
[ 539.480178] device wlan2.2 entered promiscuous mode
[ 539.485317] br0: port 8(wlan2.2) entered blocking state
[ 539.485320] br0: port 8(wlan2.2) entered forwarding state
[ 539.527146] mwifiex_sdio mmc0:0001:1: cannot create multiple AP ifaces
[ 539.550195] br0: port 8(wlan2.2) entered disabled state
[ 539.555839] device wlan2.2 left promiscuous mode
[ 539.560478] br0: port 8(wlan2.2) entered disabled state
[ 539.609660] br0: port 7(wlan2.1) entered disabled state
[ 539.615393] device wlan2.1 left promiscuous mode
[ 539.621060] br0: port 7(wlan2.1) entered disabled state
[ 540.492349] br0: port 2(wlan2) entered disabled state
Note: The WRT3200ACM Firmware has a third WLAN (ath2). While some have had limited success enabling it it is recommended that it be Disabled. It was intended for DFS Radar Detection.
_________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Thanks a lot for your reply. I have disabled it. I have created again new Virtual APs. The connection goes fine, but here, the DHCP fails. I had a 169* address. I switched to static in the configuration of the cellphone, and it was fine.
The computer connected with cable also needs to have a static adress.
Could possibly be some settings amiss. Screenshots may help. Keep in mind that the dhcp server for LAN is dnsmasq. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Sorry for the late reply. Using a static IP address.
I am about to reset the nvram. I would like to use the nvram command to set back the most important settings in place. I have many subnets that I want block as soon as possible. As there are several lines (much more than these), how should the command look like to be run in a "copy/paste" prior the commit?
Code:
rc_firewall=iptables -t filter -I FORWARD 1 --destination 8.8.4.0/24 -j DROP
iptables -t filter -I FORWARD 1 --destination 8.8.8.0/24 -j DROP
iptables -t filter -I FORWARD 1 --destination 8.34.208.0/20 -j DROP
iptables -t filter -I FORWARD 1 --destination 8.35.192.0/20 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.164.145.0/24 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.227.33.0/24 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.227.34.0/23 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.227.36.0/24 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.227.40.0/21 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.227.48.0/21 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.227.60.0/23 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.227.62.0/24 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.228.128.0/18 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.236.48.0/20 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.251.128.0/19 -j DROP
iptables -t filter -I FORWARD 1 --destination 23.255.128.0/17 -j DROP
iptables -t filter -I FORWARD 1 --destination 34.64.0.0/10 -j DROP
iptables -t filter -I FORWARD 1 --destination 34.128.0.0/10 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.184.0.0/13 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.192.0.0/14 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.196.0.0/15 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.198.0.0/16 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.199.0.0/17 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.199.128.0/18 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.200.0.0/13 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.208.0.0/12 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.224.0.0/12 -j DROP
iptables -t filter -I FORWARD 1 --destination 35.240.0.0/13 -j DROP
