R. Gerrits
Very Senior Member
@Voxel see attached for a fix for the wl_lan_restricted_access for guest-wifi, that would also allow DNS over tcp.
@kamoj, I think you must probably also make some similar changes in /lib/wifi/qcawifi.sh
I'd say add some lines : if AdGuardHome = enabled then also add ebtables rules for 5300. -> this would handle the cases where the router reboots or where someone enables guest-wifi restricted access when AdGuardHome is already enabled.
And then also the script that enables AdGuardHome needs some changes. If AdGuardHome is started while restricted access is already up then the ebtables rules would have to be inserted from that script. (as re-executing qcawifi.sh causes a wifi interruption).
Or you could be lazy and just add the ebtables rules for 5300 in qcawifi.sh without any if statement, so that they are always added if restricted access is enabled, regardless if router is using AdGuard or not.
@kamoj, I think you must probably also make some similar changes in /lib/wifi/qcawifi.sh
I'd say add some lines : if AdGuardHome = enabled then also add ebtables rules for 5300. -> this would handle the cases where the router reboots or where someone enables guest-wifi restricted access when AdGuardHome is already enabled.
And then also the script that enables AdGuardHome needs some changes. If AdGuardHome is started while restricted access is already up then the ebtables rules would have to be inserted from that script. (as re-executing qcawifi.sh causes a wifi interruption).
Or you could be lazy and just add the ebtables rules for 5300 in qcawifi.sh without any if statement, so that they are always added if restricted access is enabled, regardless if router is using AdGuard or not.