Recent content by r000t

That might have worked! Thank you!

I just checked. This static route ... generates this IPTABLES record: 9 0 0 ACCEPT all -- br0 br0 10.0.1.0/24 8.8.8.8 If I remove the static route, IPTABLES record also disappears. A bit unexpected. I'll probably spend more time here. Thank you!

I am sorry, the Google IPTABLES rule was actually generated by the static route (i tried to route 8.8.8.8 traffic to router's LAN interface as a temporary measure). But here is the problem: /tmp/home/root# iptables -vnL FORWARD --line-numbers Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)...

hi, I have GT-AXE16000 with Merlin's 3004.388.8_2 FW, and recently I figured out that Netflix app on my LG smart TV doesnt want to use my Adguard DNS and sends DNS requests directly to 8.8.8.8. Somehow DNS Director works bad with my setup, so I blocked 8.8.8.8 using Network Services Filter...

#!/bin/sh #iptables -I YazFiFORWARD -i wl0.1 -o br0 -d 10.0.1.5 -j ACCEPT iptables -t nat -A POSTROUTING -o wl0.1 -s 10.0.1.5 -j MASQUERADE This worked for me where 10.0.1.5 - my Home Assistant server inside the home network. Yeelight's local mode now works with the guest network as intended.

Hi, I have some IoT devices on guest Wi-fi, which only accept connection if SRC IP belongs to the same network (e.g., Yeelight smart lights). I know it is possible to add custom IPTABLES commands to /jffs/addons/YazFi.d/userscripts.d/custom.sh, but I am not that skilled at IPTABLES and afraid...