WAN Access Restriction not working?

Post new topic   Reply to topic    DD-WRT Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Author Message
phlegmer
DD-WRT User


Joined: 14 Oct 2006
Posts: 296
Location: Sector 001

PostPosted: Thu Oct 22, 2020 2:33    Post subject: WAN Access Restriction not working? Reply with quote
Greetings,

I currently have r44048 installed on my 1900acv2. I have setup WAN Access Restriction based on client MAC address of an iPhone without a SIM (uses wifi only). Basically I have it setup to stop internet traffic at a certain time of the night and then re-enable itself in the morning.

I've noticed that sometimes, txt messaging still works while other WAN access things do not.

This has been an issue for me for a while. I don't flash my router all that often and I flashed it in August after using a January build in hoping that an update would solve this. It has not.

What I don't fully understand is sometimes the txting is blocked while other times it isn't. Could it be that if there is active txting going on while it spills over into the disabled mode, the active connection stays open?

Please advise.

Thanks
Sponsor
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 9157

PostPosted: Thu Oct 22, 2020 18:42    Post subject: Reply with quote
The problem w/ AR (Access Restrictions) is that it's an old implementation that hasn't kept up w/ the changes around it. For example, the L7-based keyword/url blocking assumes the use of *un*encrypted protocols (e.g., https), but almost all traffic these days is encrypted, making this type of blocking ineffective. We also have a long-standing issue of AR not blocking *existing* connections, due to the fact the AR chain (lan2wan) in the FORWARD chain of the filter table of the firewall is only checked for NEW connections (something that should have been addressed long ago). And most recently, we now have the problem of some OSes randomizing MAC addresses for privacy reasons!

As far as the lan2wan problem, you can fix that one by adding the following to the firewall script.

Code:
iptables -D FORWARD -j lan2wan
iptables -I FORWARD -j lan2wan


This moves that chain above the ESTABLISHED rule so it will now affect *all* connections.

But in general, combine all these problems, and well…, AR ain't what it used to be.

_________________
ddwrt-ovpn-split-basic.sh (UPDATED!) * ddwrt-ovpn-split-advanced.sh (UPDATED!) * ddwrt-ovpn-client-killswitch.sh * ddwrt-ovpn-client-watchdog.sh * ddwrt-ovpn-remote-access.sh * ddwrt-ovpn-client-backup.sh * ddwrt-mount-usb-drives.sh * ddwrt-blacklist-domains.sh * ddwrt-wol-port-forward.sh * ddwrt-dns-monitor.sh (NEW!)
phlegmer
DD-WRT User


Joined: 14 Oct 2006
Posts: 296
Location: Sector 001

PostPosted: Fri Oct 23, 2020 15:57    Post subject: Reply with quote
Most excellent response! I'll give that script a try. Would this need to be part of the router's startup script in case of reboots?

If AR isn't quite ready for modern times, I guess I could always wield the Phone's screen time limits as well.

Thanks!

EDIT: Strike that question for the Startup Script obviously...
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.) All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum