Hey everyone. I have a mesh network of three openwrt routers. They are all the dynalink dl-36.
Two are set up as dumb points.
When i am in the bed room and basement, my phone literary constantly disconnects from wlan and switches back to cellular, but also connects back again. Signal strength is great, also in the bedroom.
I made a video to show the problem. Note that this problem is not there in the living room, probably(?) Because its close to the main access point. In the bedroom, there's two that the phone can connect to, with approx the same signal strenth. Its a mesh network as i said, so all 3 devices run the same SSID.
What logs and data can i provide to help this?
Feel free to watch the video i made about it. Be sure to play it on 2x speed and look at the wifi signal top right.
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:
You can remove the video... it doesn't actually give us any useful information. What will be helpful is your config files and then we'll ask for more detail as needed.
config dnsmasq
option domainneeded '1'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option cachesize '1000'
option dnsforwardmax '350'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
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'
option ra_slaac '0'
option dns_service '0'
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'
config host
option name 'Samsung'
option ip '192.168.1.154'
option mac 'F4:FE:FB:9F:21:B6'
config host
option name 'HarmonyHub'
option ip '192.168.1.160'
option mac '00:04:20:FC:18:14'
config host
option name 'hubv3-4011035646'
option ip '192.168.1.179'
option mac '28:6D:97:A0:53:E8'
config host
option name 'Samsung'
option ip '192.168.1.151'
option mac '38:68:A4:28:D3:EC'
config host
option name 'everything-presence-st-fa2d68'
option ip '192.168.1.229'
option mac 'A0:B7:65:FA:2D:68'
config host
option name 'everything-presence-st-700718'
option ip '192.168.1.208'
option mac '08:B6:1F:70:07:18'
config host
option name 'everything-presence-st-7e8058'
option ip '192.168.1.171'
option mac '08:B6:1F:7E:80:58'
Firewall:
config defaults
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option synflood_protect '1'
option flow_offloading '1'
config zone
option name 'lan'
list network 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
config zone
option name 'wan'
list network 'wan'
list network 'wan6'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option mtu_fix '1'
option masq '1'
config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'
config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-IGMP'
option src 'wan'
option proto 'igmp'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-DHCPv6'
option src 'wan'
option proto 'udp'
option dest_port '546'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-MLD'
option src 'wan'
option proto 'icmp'
option src_ip 'fe80::/10'
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Input'
option src 'wan'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
list icmp_type 'router-solicitation'
list icmp_type 'neighbour-solicitation'
list icmp_type 'router-advertisement'
list icmp_type 'neighbour-advertisement'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Forward'
option src 'wan'
option dest '*'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-IPSec-ESP'
option src 'wan'
option dest 'lan'
option proto 'esp'
option target 'ACCEPT'
config rule
option name 'Allow-ISAKMP'
option src 'wan'
option dest 'lan'
option dest_port '500'
option proto 'udp'
option target 'ACCEPT'
config zone
option name 'surfshark'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
list network 'surfshark'
config include 'pbr'
option fw4_compatible '1'
option type 'script'
option path '/usr/share/pbr/pbr.firewall.include'
config rule
option name 'exceptions'
option src 'lan'
list src_ip '192.168.1.179'
list src_ip '192.168.1.151'
option dest 'wan'
option target 'ACCEPT'
option enabled '0'
config zone
option name 'ovpntest'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
list network 'surfsharkovpn'
option family 'ipv4'
config forwarding
option src 'lan'
option dest 'surfshark'
Out of all the above, the openvpn adapter is disabled. I am using the wireguard adapter. The only problem is that during some locations in the house, where reception shows as good, i am getting a lot of disconnections. The config shared above is the main router/device that gets internet from the bridge device. Is this helpful? I could also share the data of the mesh device? (both mesh devices are configured exactly the same, as dumb ap)
But thats a function that makes devices easily cross over into a other ap...? I'd rather not lose a function...besides it works good in most areas of the house.
Il try to use the same country code tommorow but i think i did that because of some bug that did not allow a normal channel to be used...
It's actually not a necessary standard in many cases. Standard roaming (without 802.11r) can work really well when properly tuned. In fact, I often recommend turning off all of the 'additions' (802.11 k / r / v) and spend a bit of time optimizing the radios for good standard roaming performance first, as it is necessary for this to be working well before adding any of the other standards on top. Then, if you want to make for a (theoretically) improved roaming experience, then add those in. I don't use 802.11r and I have nearly seamless roaming across multiple APs.
Thanks! Can i just disable it, also on the dumb ap's? Or do i have to disable or alter the mesh network then? The external routers are accessable through wireless mesh on a local ip, if i lose access to them with a wrong setting change, its quite some work to grab them and hook them up by a lan cable.
I updated the region settings but that unfortunately did not help.
I think you can just disable 802.11r.... although I'm not an expert on mesh -- I prefer to have all APs hardwired, so that's what I've done in my setups.
I assume that you're actually using mesh, and not confusing the terminology, right? Mesh specifically refers to the use of a wireless backhaul (i.e. one wired AP, the others are wirelessly conneted to the first). Many people think that mesh = roaming and that roaming = mesh. In actuality, client devices will roam from one node to another in a mesh network, but they can also roam from one node to another in a non-meshed network... roaming is simply the client moving between APs. Meshing is the wireless backhaul that makes up the connections between the APs.
I have noticed occasional WiFi firmware crashes in kernel log when WPA3 clients leave/disassociate. I first disabled WPA3 802.11r, and currently trying to test if "WPA2 only" is more stable.
I just disabled fast roaming on all devices and rebooted. Everything worked fine. Then later the issue started again.
A reboot then fixes it again....
How to proceed now...
