Recent content by pjv

The iptables rule in the post above had no effect. So I went the YazFi route using DHCP reservations with dnsmasq.postconf per the link in Jack’s post above (#4). After re-writing all the home assistant configs that were addressing IOT devices with hard-coded IP addresses to use their new...

GSpock, I'm not sure when my next opportunity will be to monkey with the AX86U, but based on some researching, my next wild flail will be inserting this iptables rule: iptables -t filter -I PControls -i br0 -o br0 -j ACCEPT That rule exists on the AC68U but the corresponding rule on the AX86U...

I've now tried a lot of variations on the ebtables rules posted above, moving them to various tables and chains and had no good results. I've also tried inserting various iptables rules on the guess that maybe the ebtables ACCEPT targets might be dumping packets into the iptables tables and...

Thank you John. I did verify the ebtables rules were there and I also checked the broute table and it is identical on the AX and the AC. I also tried inserting an additional BROUTE rule using the IP address of the home assistant box: ebtables -t broute -I BROUTING -p IPv4 -i wl0.2 --ip-dst...

Off the top of my head, I think the DHCP assignment of reserved IPs is the only good reason. (One bad reason is lazily not wanting to have to scan through my entire lengthy set of home assistant config files and re-write all the device IP addresses in them, but I can suck that up). I do have a...

Thank you, Jack. I installed YazFi on the AX yesterday while I was looking for a quick fix. I seemed to run into a wall there with trying to keep my IOT devices on the same network numbers as my other stuff and be able to use static DHCP assignments for them (which I need to do). When I tried...

For the last couple years, I've been running an AC68U with 384.14_2. I just bought a new AX86U and have installed 386.3_2 on it. I configured everything from scratch / manually on the new AX so as not to push anything wonky from an old backup. Everything worked great except for one thing. I...

Wish I had some other ideas. Here is a page I found with a lot of practical information on troubleshooting bridges.

I don't know the answer to that question, but reboots are often helpful. I have the script being called from the `nat-start` script. The merlin wiki has good documentation on getting started with scripts, here. Edit: Are you sure that the device on your main network that you want to be able to...

here's what my ebtables look like pjv@rt-ac68u:/tmp/home/root# ebtables -L --Lx --Lmac2 ebtables -t filter -A FORWARD -s aa:bb:cc:dd:ee:ff -o wl0.1 -j ACCEPT ebtables -t filter -A FORWARD -d aa:bb:cc:dd:ee:ff -i wl0.1 -j ACCEPT ebtables -t filter -A FORWARD -i wl0.1 -j DROP ebtables -t filter...

Take a look at these two recent posts and see if they might help you: https://www.snbforums.com/threads/vlan-or-isolated-lan-for-ip-cameras-using-asus-rt-ac68u.61264/#post-542228 https://www.snbforums.com/threads/vlan-or-isolated-lan-for-ip-cameras-using-asus-rt-ac68u.61264/#post-542406

This happens enough for me since I started managing a client's AC86U that I created a bash alias using SSH to fix it from the command line. alias fix_router="ssh [email protected] service restart_httpd"

Ah so. Sorry I missed that part about the camera's being wired. So then this is off-topic, but my ebtables rules script looks like this: #!/bin/sh ## allow home assistant to talk to IoT devices on firewalled guest network MAC="XX:XX:XX:XX:XX:XX" # HA box ether mac address EBT=$(ebtables -L...

I use a guest network with the "access intranet" setting disabled for all my IOT devices. Then I have a single host on my LAN (in my case, it is a little server running Home Assistant) that is able to communicate with the IOT devices via some custom ebtables rules in the nat-start script.

I do this with various IOT devices. It works great.