<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers in Networking</title>
    <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507027#M4785</link>
    <description>&lt;P&gt;That helps eliminate hacker codes being installed. You likely have a stuck switch issue. These latest firmware updates are intensive due to security changes and can be difficult to get working correctly. I would try what I've already stated and even use a different setup for the networks. Even switching MLO off and on can sometimes clear a stuck switch. ASUS has made so many changes that even if you enable SSH and find a positive change that works, it will revert to default on any reboot. If none of this changes anything, it's best to leave SSH off, remote off, and keep your fingers crossed as it would be firmware related.&lt;/P&gt;</description>
    <pubDate>Tue, 21 Apr 2026 03:23:37 GMT</pubDate>
    <dc:creator>Alex52</dc:creator>
    <dc:date>2026-04-21T03:23:37Z</dc:date>
    <item>
      <title>RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/506947#M4747</link>
      <description>&lt;H3&gt;RT-BE82U: SDN firewall generating rogue MASQUERADE rule on br0 — breaks bridged VMs and containers&lt;/H3&gt;&lt;P&gt;Router Model: ASUS RT-BE82U&lt;BR /&gt;Firmware Version: 3.0.0.6.102_39254 (39254-gc155c5b_1531-g93455_BB0B)&lt;BR /&gt;Affected Branch: Potentially all ASUSWRT 5.0 / 3006.x branch models using the SDN firewall subsystem&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ISSUE&lt;/P&gt;&lt;P&gt;I've been troubleshooting an issue where inbound TCP connectivity to Proxmox VMs and Docker containers breaks after any firewall restart on my RT-BE82U. After digging into the iptables NAT table I found this rule being automatically generated:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;-A POSTROUTING -s 192.168.19.0/24 -d 192.168.19.0/24 -o br0 -j MASQUERADE&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;This appears to apply hairpin NAT to all traffic where source and destination are within the primary LAN subnet on br0. For users running Proxmox VMs, Docker containers, or any bridged virtual network interfaces, this breaks inbound TCP connectivity — destination hosts see the router's IP (192.168.19.1) as the source rather than the actual client, causing asymmetric routing and broken sessions.&lt;/P&gt;&lt;P&gt;Worth noting — ICMP (ping) continues to work fine, which makes this difficult to diagnose. Only stateful TCP connections fail, so it's easy to assume the network is healthy until you try to actually connect to something.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;TRIGGER CONDITIONS&lt;/P&gt;&lt;P&gt;The rule is re-injected not just on reboot but on any event that triggers a firewall restart, including:&lt;/P&gt;&lt;P&gt;- Router boot&lt;BR /&gt;- WAN connect/reconnect&lt;BR /&gt;- Any configuration save in the web UI that triggers firewall reload&lt;BR /&gt;- AiProtection enable/disable&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;WHAT I FOUND IN THE SOURCE&lt;/P&gt;&lt;P&gt;Looking at release/src/router/rc/firewall_sdn.c I noticed that the DoT block correctly uses an idx check to skip the main bridge (br0, idx=0):&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;#ifdef RTCONFIG_DNSPRIVACY
if (pmtl-&amp;gt;nw_t.idx) //ignore br0
{
// DoT DNS redirect logic
fprintf(fp, "-A PREROUTING ...");
}
#endif&lt;/LI-CODE&gt;&lt;P&gt;The NAT loopback block immediately following doesn't appear to have the same check.&lt;/P&gt;&lt;P&gt;Location: release/src/router/rc/firewall_sdn.c, approximately line 509 in the current main branch. Line numbers may vary by version — search for the comment "// NAT lookback" to locate the exact line.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ip2class((char *)(pmtl-&amp;gt;nw_t.addr), (char *)(pmtl-&amp;gt;nw_t.netmask), sdn_subnet_class);
// NAT lookback &amp;lt;-- possibly missing idx check here?
fprintf(fp, "-A POSTROUTING -s %s -d %s -o %s -j MASQUERADE\n",
sdn_subnet_class, sdn_subnet_class, pmtl-&amp;gt;nw_t.ifname);&lt;/LI-CODE&gt;&lt;P&gt;When idx=0 (the main br0 interface), this generates a MASQUERADE rule for LAN-to-LAN traffic which doesn't seem intentional — though I may be missing context about why this was done this way.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;POSSIBLE FIX&lt;/P&gt;&lt;P&gt;If this is indeed an oversight, adding the same idx check used by the DoT block above might resolve it:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ip2class((char *)(pmtl-&amp;gt;nw_t.addr), (char *)(pmtl-&amp;gt;nw_t.netmask), sdn_subnet_class);
// NAT lookback
if (pmtl-&amp;gt;nw_t.idx) //ignore br0
fprintf(fp, "-A POSTROUTING -s %s -d %s -o %s -j MASQUERADE\n",
sdn_subnet_class, sdn_subnet_class, pmtl-&amp;gt;nw_t.ifname);&lt;/LI-CODE&gt;&lt;P&gt;This would ensure NAT loopback only applies to guest/IoT/VPN SDN profiles (idx &amp;gt; 0) and leaves the primary bridge untouched.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;VERIFICATION&lt;/P&gt;&lt;P&gt;Manually deleting the rule immediately restores full VM/container connectivity:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;iptables -t nat -D POSTROUTING -s 192.168.19.0/24 -d 192.168.19.0/24 -o br0 -j MASQUERADE&lt;/LI-CODE&gt;&lt;P&gt;The rule returns on any firewall restart, confirming it is being procedurally generated rather than being a one-time misconfiguration.&lt;/P&gt;&lt;P&gt;Before fix — iptables POSTROUTING:&lt;/P&gt;&lt;P&gt;Chain POSTROUTING (policy ACCEPT 33 packets, 4922 bytes)&lt;BR /&gt;num pkts bytes target prot opt in out source destination&lt;BR /&gt;1 691 53710 MASQUERADE all -- * vlan201 ![public IP] 0.0.0.0/0&lt;BR /&gt;2 1598 148K MASQUERADE all -- * br0 192.168.19.0/24 192.168.19.0/24&lt;/P&gt;&lt;P&gt;Before fix — netstat on client (192.168.19.122 connecting to VM at 192.168.19.6):&lt;/P&gt;&lt;P&gt;TCP 192.168.19.122:49250 192.168.19.6:53 FIN_WAIT_1&lt;BR /&gt;TCP 192.168.19.122:49666 192.168.19.6:53 FIN_WAIT_1&lt;BR /&gt;TCP 192.168.19.122:49667 192.168.19.6:53 FIN_WAIT_1&lt;BR /&gt;TCP 192.168.19.122:49747 192.168.19.6:53 ESTABLISHED&lt;BR /&gt;TCP 192.168.19.122:49919 192.168.19.6:53 FIN_WAIT_1&lt;BR /&gt;TCP 192.168.19.122:50382 192.168.19.6:53 FIN_WAIT_1&lt;BR /&gt;TCP 192.168.19.122:50855 192.168.19.6:443 ESTABLISHED&lt;/P&gt;&lt;P&gt;Multiple TCP connections stuck in FIN_WAIT_1 — sessions cannot complete teardown. Wireshark shows a flood of TCP retransmissions.&lt;/P&gt;&lt;P&gt;After fix — iptables POSTROUTING:&lt;/P&gt;&lt;P&gt;Chain POSTROUTING (policy ACCEPT 43 packets, 4755 bytes)&lt;BR /&gt;num pkts bytes target prot opt in out source destination&lt;BR /&gt;1 950 82286 MASQUERADE all -- * vlan201 ![public IP] 0.0.0.0/0&lt;/P&gt;&lt;P&gt;After fix — netstat on client:&lt;/P&gt;&lt;P&gt;TCP 192.168.19.122:51783 192.168.19.6:53 TIME_WAIT&lt;BR /&gt;TCP 192.168.19.122:52022 192.168.19.6:8300 ESTABLISHED&lt;BR /&gt;TCP 192.168.19.122:52148 192.168.19.6:443 ESTABLISHED&lt;BR /&gt;TCP 192.168.19.122:52160 192.168.19.6:53 TIME_WAIT&lt;BR /&gt;TCP 192.168.19.122:52376 192.168.19.6:53 TIME_WAIT&lt;/P&gt;&lt;P&gt;Connections now completing normally — FIN_WAIT_1 replaced by clean TIME_WAIT states. Wireshark shows clean traffic with no retransmissions.&lt;/P&gt;&lt;P&gt;Hoping someone more familiar with the codebase can confirm whether this is intentional or an oversight.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;CURRENT WORKAROUND&lt;/P&gt;&lt;P&gt;For anyone hitting this in the meantime — a scheduled task running every few minutes on an always-on Linux host on your network:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ssh admin@192.168.19.1 'iptables -t nat -D POSTROUTING -s 192.168.19.0/24 -d 192.168.19.0/24 -o br0 -j MASQUERADE 2&amp;gt;/dev/null'&lt;/LI-CODE&gt;&lt;P&gt;This can be added to cron or run as a Home Assistant shell_command on a schedule.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;HAS ANYONE ELSE SEEN THIS?&lt;/P&gt;&lt;P&gt;I'm curious whether others have run into this, particularly those running:&lt;/P&gt;&lt;P&gt;- Proxmox or any hypervisor with bridged VMs&lt;BR /&gt;- Docker on a home server connected to an ASUS WiFi 7 router&lt;BR /&gt;- NAS devices running Docker containers (Synology, TrueNAS, Unraid)&lt;BR /&gt;- Any setup where devices have virtual MAC addresses behind a Linux bridge&lt;/P&gt;&lt;P&gt;The symptom is easy to miss — ping works fine but TCP connections to your VMs or containers fail or time out, and everything works perfectly if you switch to a different router. If you've experienced this and assumed it was a misconfiguration on your server side, it may actually be this rule.&lt;/P&gt;&lt;P&gt;Running the following on your router will show the rule if it's present:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;iptables -t nat -L POSTROUTING -n -v&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 19 Apr 2026 17:16:37 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/506947#M4747</guid>
      <dc:creator>geekweaver</dc:creator>
      <dc:date>2026-04-19T17:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/506978#M4767</link>
      <description>&lt;P&gt;Do you have SSH disabled per default. Have you checked for a system hack - if so, have you implemented repair and changed your passwords.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 03:46:38 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/506978#M4767</guid>
      <dc:creator>Alex52</dc:creator>
      <dc:date>2026-04-20T03:46:38Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/506994#M4771</link>
      <description>&lt;P&gt;While I am afraid I don't quite understand most of what you noted I do remember that hairpin NAT or NAT loopback has been a feature of all ASUS routers for a very long time.&amp;nbsp; So I would assume that it is unintendedly affecting your bridge.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 10:16:38 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/506994#M4771</guid>
      <dc:creator>jzchen</dc:creator>
      <dc:date>2026-04-20T10:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507015#M4777</link>
      <description>&lt;P&gt;I have enabled SSH so I could take a look at all of this on the router. I have tried various system hacks, but nothing seems to stick.&amp;nbsp; I may try some other things, but am hoping this may actually be a bug that could be fixed "officially".&amp;nbsp; Unfortunately Asuswrt-Merlin isn't supported on my router model, yet, but I believe it allows for some custom scripting that may be useful in mitigating this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 22:26:52 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507015#M4777</guid>
      <dc:creator>geekweaver</dc:creator>
      <dc:date>2026-04-20T22:26:52Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507016#M4778</link>
      <description>&lt;P&gt;I meant have you checked for a possible hacker having control of your router. SSH is a possible entry for a hacker to run code on your router. The current firmware may not be able to stop the attack. This could mean you need to do a full system firmware re-install and factory reset, starting from scratch also using a new password.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 22:58:44 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507016#M4778</guid>
      <dc:creator>Alex52</dc:creator>
      <dc:date>2026-04-20T22:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507017#M4779</link>
      <description>&lt;P&gt;Oh.. sorry. No hacker.&amp;nbsp; I have it locked down on the frontside.&amp;nbsp; I even reset to factory and disconnected from WAN to do some testing.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 23:40:10 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507017#M4779</guid>
      <dc:creator>geekweaver</dc:creator>
      <dc:date>2026-04-20T23:40:10Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507018#M4780</link>
      <description>&lt;P&gt;I should also have noted, this is the initial setup of this router. I was coming from an Orbi and all of this transpired on the initial setup of the AsusWRT.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 23:44:18 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507018#M4780</guid>
      <dc:creator>geekweaver</dc:creator>
      <dc:date>2026-04-20T23:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507025#M4783</link>
      <description>&lt;P&gt;That's my concern, but hoping it's just a bug.&amp;nbsp; I would imagine others running similar configurations to mine (with containers and VMs) would have come up against this before, but I found nothing else in my searches.&amp;nbsp; I don't have an overly complex network, so it all seems very odd.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 01:24:29 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507025#M4783</guid>
      <dc:creator>geekweaver</dc:creator>
      <dc:date>2026-04-21T01:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507026#M4784</link>
      <description>&lt;P&gt;Just doing a factory reset alone may not be enough to stop some hacker codes interfering with router operation. Also, you could have some stuck hidden switches that didn't reset in the last firmware download. Re-applying the firmware using the web GUI could help with this. Also, don't use remote setup.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 01:29:21 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507026#M4784</guid>
      <dc:creator>Alex52</dc:creator>
      <dc:date>2026-04-21T01:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507027#M4785</link>
      <description>&lt;P&gt;That helps eliminate hacker codes being installed. You likely have a stuck switch issue. These latest firmware updates are intensive due to security changes and can be difficult to get working correctly. I would try what I've already stated and even use a different setup for the networks. Even switching MLO off and on can sometimes clear a stuck switch. ASUS has made so many changes that even if you enable SSH and find a positive change that works, it will revert to default on any reboot. If none of this changes anything, it's best to leave SSH off, remote off, and keep your fingers crossed as it would be firmware related.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 03:23:37 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507027#M4785</guid>
      <dc:creator>Alex52</dc:creator>
      <dc:date>2026-04-21T03:23:37Z</dc:date>
    </item>
    <item>
      <title>Re: RT-BE82U: MASQUERADE rule on br0 breaks LAN connections to Proxmox VMs and Docker containers</title>
      <link>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507048#M4787</link>
      <description>&lt;P&gt;Thank you, I will give that a go and let you know the results. I hadn't tried turning too many knobs (like MLO), but good suggestions.&amp;nbsp; If I can get a native workable solution, I would love to disable ssh on the inside, and I don't enable remote at all; I feel like that's just asking for trouble.&amp;nbsp; Appreciate the reommendations!&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 13:31:50 GMT</pubDate>
      <guid>https://zentalk.asus.com/t5/networking/rt-be82u-masquerade-rule-on-br0-breaks-lan-connections-to/m-p/507048#M4787</guid>
      <dc:creator>geekweaver</dc:creator>
      <dc:date>2026-04-21T13:31:50Z</dc:date>
    </item>
  </channel>
</rss>

