the problem i have is : devices disconects because "there is not internet" however, they keep browsing and connected despite "connected, not internet" message, however!, after a while if i am afk it disconects from the network because android devices have connectivity check....
how can i solve this? tried a lot of stuff.. thank you
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:
There's a lot of non-standard configurations going on, including 802.11w, the use of sae (WPA3) encryption, and some DNS stuff, among other things...
My personal suggestion would be to do the following:
make a backup of your current configuration
reset the router to defaults
perform the basic configuration (i.e. minimal changes from default, but getting you to where you were in terms of the subnet and base wifi configs).
Test the android device.
Then, install one package at a time (such as OpenVPN, etc.) and test each time. As you get through each step, you'll eventually hit the package that is killing your connectivity on the android device -- then you can focus on the exact settings that are causing that problem.
That's how I would approach it, personally... process of elimination. It's a fair bit of work, but you may arrive at the solution faster than if you try a whole bunch of small changes here and there (unless someone spots the error right away).
802.11w is used for wpa3, i need wpa3 because wpa2 is not safer anymore
wpa3 is not safe too, but less unsafe than wpa2, so if it is possible for me to give a headache for the red team that is trying to get my back handed, i will do
can you please tell me what is non standard? i tried to modify the out of the box config cause i needed something more obscure, darker and discrete
factory resetted, and still getting the connected, not internet, still getting connection... but it will disconnect because "not internet" check... what can i do?
Obviously it's been a bit of effort, and I'm sorry that you had to reset your router and are still experiencing the issue... but that does begin to suggest that the issue is related to the android devices specifically. If you have another router that is not running OpenWrt (or if you want to try the stock firmware on your current device), you can always try swapping it out to see if the problem persists (which would conclusively point to the Android device). If you run this test, be sure to make a note of the WAN IP address on your router -- in many cases, a change of the WAN IP is related to the MAC address of the router, and in some situations, the problem could actually be due to one of the IPs having been blocked (such as from abuse, possibly from a previous user of that IP).
already tested with a non openwrt router, and it works flawesly , i do not think it is a common error, because someone out there would have been reporting it from long time ago and it is not normal such behaviour, so it is weird