Hi,
Sometimes wireless network scan goes down and I can´t get it or my wireless connection working again. I currently have it set to dhcp but keep reporting less that 100% packets received. Can some one post what I need to check for/ modify in order to get it working again? Is there a connection between the amount of % and what I have configured correctly still need to configure?
Thanks,
Aaron
I have noticed a difference with network scan too.
On my 5ghz WiFI that is set up as a access point will scan but it takes a while to populate..
On my 2ghz it is set up as Wan WiFi and the only way to scan is to disable it, This was not the case in older versions of OpenWrt.
I am using a TP-Link TL-WDR4300 v1
Which version of OpenWrt are you using I am using 22.03.x.
Discussion on WiFi scanning:
Not sure what the leds have to do with the problem mentioned in the first post? I should point out that the wifi connection can drop even if the network connection have been established for some time.
As noted, the thread goes on to discuss WiFi scanning (not LEDs), but OK.
Aaah, that would be different and could be unrelated to scanning. What channel do you have selected?
Are you referring to WiFi scanning on the client when looking for the OpenWrt's SSID?
Or the scan feature on the OpenWrt?
Can you provide more detail?
Please provide your settings. Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
Can you provide a screenshot of what you're referencing?
The loading circle keeps going round and round then nothing!
The ping, etc usually shows a percent of how much of the packets are returned.
Network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdb6:85db:aecb::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.2.1'
option gateway '10.1.1.4'
config interface 'wan'
option device 'wan'
option proto 'dhcp'
config interface 'wan6'
option device 'wan'
option proto 'dhcpv6'
config interface 'wwan'
option device 'wlan0'
option proto 'dhcp'
config device
option type 'bridge'
option name 'brlanwan'
option bridge_empty '1'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'tun0'
list ports 'wan'
config interface 'vpn'
option proto 'dhcp'
option device 'tun0'
wireless
config wifi-device 'radio0'
option type 'mac80211'
option path 'platform/18000000.wmac'
option band '2g'
option htmode 'HT20'
option country 'AU'
option cell_density '0'
option channel 'auto'
config wifi-iface 'wifinet0'
option device 'radio0'
option mode 'sta'
option network 'wwan'
option ssid ' '
option bssid ' '
option encryption 'psk2'
option key ' '
dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option nonwildcard '1'
option localservice '1'
option ednspacket_max '1232'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
list ra_flags 'managed-config'
list ra_flags 'other-config'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
This seems normal (the config and the behavior).
Is the upstream AP configured to a set, static channel?
Yea, it seems you're disconnected from the Internet (i.e. WWAN) after you performed a WiFi scan. From the thread I linked:
You want the Rx to scan, so it changes chanels. The thread discusses how some OEMs and software seem to manage "fast scanning" - and this appears not to occur running those.
Also:
I unclearly noted in that thread "unhidden SSIDs" will be seen - but your radio will see any broadcasting BSSIDs on air, this includes APs with hidden SSIDs.
No, the wwan interface is using dhcp because when I set it to static and run the diagnostic the amount of packet percent wasn't always 100%.
Ok! I have just set the wwan to static and rebooted the system. So far everything seems to be working although, I will need to give it a few day to make sure it remains that way.
I'm not sure how DHCP/static IP settings are related to the issues with "WiFi scanning" (maybe it doesn't have to take time to obtain an IP after connecting); but I'm glad that "setting it to static" solved your issue.
Hopefully it remains!
Me neither nor do I understand the dhcp settings completely. Not sure if the device was just over heating or what?
Edit:
Maybe the problem with the wifi scanning has to do with Luci?
There's not much to understand...it would seem "static" was more complex; but glad you figured out.
It seems you didn't browse the threads I posted (or comments on WiFi scanning). Sure.
(I'm sure the commands can be tested on a CLI by someone. The other thread has more information on the underlying scanning invoked thru the web GUI. Since the other thread covers it well, feel free to explore/test yourself.)
I am running the newest stable
OpenWrt 22.03.2 r19803-9a599fee93 / LuCI openwrt-22.03 branch git-22.339.35241-4ca7a8d
For me something has changed, before I guess it would seamlessly put the card in a different mode fast and start scanning then when finished it would revert back it's original setting.
I am the only user n my network so I am guessing that it did shut down the WAN and switch modes but I did not notice it was down while scanning
Is there a way to update the wifi firmware? Maybe someone with more experience of this has the answer to that question.
Yes, upgrade your router firmware to the current version.*
*(If you mean the built-in WiFi chips, no. As it's only legal for the OEM to flash it - in most countries at least. Nor would that control "scanning". Not sure what you think that could solve, given the OEM software doesn't do this on most devices. Your comments really seem as if you didn't browse thru the thread I linked.)
You don't control all the APs on air (also using the space).
I was think of if I already have the lastest version of openwrt. Is that possible?
Stupid thing has happened again! This time with a static ip address.
The diagnostic results:
PING 10.1.1.1 (10.1.1.1): 56 data bytes
64 bytes from 10.1.1.1: seq=0 ttl=64 time=4.818 ms
64 bytes from 10.1.1.1: seq=1 ttl=64 time=6.200 ms
64 bytes from 10.1.1.1: seq=1 ttl=64 time=7.848 ms (DUP!)
64 bytes from 10.1.1.1: seq=2 ttl=64 time=3.446 ms
64 bytes from 10.1.1.1: seq=2 ttl=64 time=5.136 ms (DUP!)
64 bytes from 10.1.1.1: seq=3 ttl=64 time=4.270 ms
64 bytes from 10.1.1.1: seq=4 ttl=64 time=10.110 ms
--- 10.1.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 2 duplicates, 0% packet loss
round-trip min/avg/max = 3.446/5.975/10.110 ms
wwan interface config
config interface 'wwan'
option device 'wlan0'
option proto 'static'
option ipaddr '10.1.1.4'
option netmask '255.255.255.0'
Can you clearly state what's "happening again"?
The ping looks normal (except for the duplicates).
Duplicates?
Just to be clear - nothing you're showing seems related to: WiFi scanning, initialization of a WiFi scan, etc.
I am not sure what is causing the problem just reporting what I know.