If that is set to accept, it will allow those networks to communicate with each other unless there are any other rules filtering/prohibiting those connections. The firewall is a rather complex piece of software, it's very easy to get that wrong These is the rule as it show in luci Fowarded ipv4 and ipv6 from *lan*, mac Xyz to *wan* (protocol any) reject foward the device a has an update feature to fetch last release from github, so i try to get last update and it still was able to. The firewall is part of the kernel, it's not an independent process, and there is nothing running while the firewall is active
What the firewall service does is to load the rules from the config files, configure the rules in the kernel, and finish. Only manually defined iptables code firewall rules would be relevant here A dedicated wireless access point will be located downstream from the router. A lot has changed with sonos and their recent (controversial) software and networking updates, making most previous sonos vlan discussion obsolete in 2025 The above github link contains a complete step by step guide that will walk you through getting a 100% functional sonos system in most common lan + guest access to iot vlan scenarios (including airplay, spotify, new device discovery etc. I have a device running the last version of openwrt, which seem to work so far
My preliminary tests seem to work, and are replacing the firewall rules accordingly However, i would like to know, if i can disable the web interfaces that manage the firewall rules. I would like in my home lan to block internet access to some devices in an ip range I have created an entry in the firewall, but still i can access the internet.
OPEN
