Closed hashcan closed 6 months ago
Probably not the best place to clone MAC address....
Probably not the best place to clone MAC address....
I changed the client's wireless network MAC to random :
The client interface looks like this after reboot :
Probably you need to use rnd mac in AP side to not consume uplink's dhcp pool in no time. Log should say that - basically set any channel on ap , not auto, since it is forced by supplicant on wwan.
Probably you need to use rnd mac in AP side to not consume uplink's dhcp pool in no time. Log should say that - basically set any channel on ap , not auto, since it is forced by supplicant on wwan.
The current bug is that wwan cannot obtain IP address at boot time. all will work good if I restart the wwan network manually in Luci after boot.
config/network and config/wireless would be nice.
config/network and config/wireless would be nice.
Config looks generic, like made from luci.
What is in logread -e upstairs:mac
and so on?
I did aporximately same you did, just that wireless file has sra and ap in reverse order.
What is in
logread -e upstairs:mac
and so on?
at boot I have :
and if I restart wwan from luci :
Full log file : logread.log dmesg.log
Permission denied - ujail, edit /etc/init.d/wpad and change /sbin/ujail to like /sbin/nonexistant, it will run wifi daemons withour sandbox still under user not root. It is ought to be cosmetic, but check
event 37 sh out of range
i do not have these. Your wifi driver is very common, and really nothing in config/network that looks like a range or even counter.
no indication it needs country code, but polite to have one per radio.
btw logread is superset of dmesg
Permission denied - ujail, edit /etc/init.d/wpad and change /sbin/ujail to like /sbin/nonexistant, it will run wifi daemons withour sandbox still under user not root.
root@OpenWrt:~# grep nonex /etc/init.d/wpad
[ -x /sbin/nonexistant -a -e /etc/capabilities/wpad.json ] && {
root@OpenWrt:~#
I haven't noticed any difference after changing this.
i do not have these. Your wifi driver is very common, and really nothing in config/network that looks like a range or even counter.
Yes I did everything through luci and tried to keep the config as minimum as possible.
event 37 sh out of range
not so sure what I should do with these.
I see messages in your logread not present in mine.
I redid everything on OpenWrt SNAPSHOT r25820-46efc77502 / LuCI Master git-24.089.54606~0ecb5ed
from a vanilla image from https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mediatek%2Ffilogic&id=xiaomi_mi-router-ax3000t-ubootmod and the issue still exists. like before.
Version OpenWRT Snapshot r25820-46efc77502
and as soon as I restart wwan from networks :
Set channel auto in radio config and maybe set country code. I have only country code...
Set channel auto in radio config
upstairs wifi is on channel 36. I set wifi channel to auto and set country code but no change. it doesn't connect at boot.
I got the same results while trying to connect it to two other access points.
I also tried both bands as you can see in the first test and latest one above.
I have different ordering in wireless file, ap first in file even entered later in luci.
and none of
daemon.notice netifd: radio1 (2113): sh: out of range
wpa_supplicant[1530]: phy1-sta0: Unknown event 37
in logread.
wwan is quite normal usage, cf travelmate...
I have different ordering in wireless file, ap first in file even entered later in luci.
reversing the order of wireless file from sta, ap to ap, sta also did not help.
daemon.notice netifd: radio1 (2113): sh: out of range wpa_supplicant[1530]: phy1-sta0: Unknown event 37
mentioning @nbd168 as listed for both maintainers of netifd and hostapd.
Atypical showings in the log: https://github.com/openwrt/openwrt/issues/15028#issuecomment-2040711004
Tested with OpenWrt SNAPSHOT r25915-c2f52e42b1 / LuCI Master 24.100.29615~1181915 and the issue still exists.
Wait for dev to come by and tell issue is considered. Your config is very generic, and log indications are atypical (on top of you say it does not work)
Wait for dev to come by and tell issue is considered. Your config is very generic, and log indications are atypical (on top of you say it does not work)
Think I found the underlying problem. Luci shows the right channel in here :
but when you join the network and pass this page :
you still get the wifi set to the previous channel despite checking the replace wifi configuration option.
all will be good if I manually set the channel to 6 instead of suggested channel "1" .
You need to choose one firewall zone for the network.
You need to choose one firewall zone for the network.
The issue is Luci not setting the right channel on the last photo of my previous message.
The issue is now resolved on latest snapshot. Thank you so much
This is happening again, wifi connection is ok, but the wwan interface not getting an IP address at boot, restarting the wwan interface works as a workaround.
OpenWrt SNAPSHOT r27419-3c152904c2
OpenWrt SNAPSHOT r27082-b733b6acb5
I'm having exactly the same issue. I tried to execute the command of "ifdown wwan && ifup wwan" in CLI but this didn't work. I also tried the "/etc/init.d/network restart", still got the same result. wwan won't get the IP address. I have to click on the restart button for wwan interface in Luci GUi, then wwan interface can get the IP address.
Edit: Installed OpenWrt SNAPSHOT r27497-1a288670d9. This version resolved the issue.
Describe the bug
Everything works perfect after connecting to another AP to get internet access from WWAN until you reboot the device. Then you need yo login to luci and restart the wwan network interface.
OpenWrt version
r25717-d7d94a8d91
OpenWrt release
SNAPSHOT
OpenWrt target/subtarget
mediatek/filogic
Device
Xiaomi Mi Router AX3000T
Image kind
Official downloaded image
Steps to reproduce
Create a wwan by Luci > Wireless > Scan > Join Network > Check "Replace wireless configuration" option and type down the passphrase > submit, save and apply. Add a new AP wireless network on the same radio. assign it to "lan" network .
Actual behaviour
After following the Steps to reproduce, WWAN successfully connects to upstream wifi router and automatically gets IP address from the upstream DHCP server. until you reboot the router and then this happens.
A manual wwan network restart in luci will solve the issue :
Expected behaviour
No response
Additional info
I've tested this scenario with WPA2-PSK and WPA3-SAE on both ends, nothing changed.
This does not happen if I don't add another Wireless AP on the same radio.
Diffconfig
No response
Terms