This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG V19 port forwarding but getting Local ACL Violation

Good Day,

I'm trying to set up a port forward (RDP) from my WAN interface to a device on my LAN.  The rule migrated from V18 MR4 isn't functioning, and neither are any rules I set up from scratch.  Any FW/NAT rules I set up show zero on their counters.  A packet capture on the port shows traffic hitting FW Rule 0 and NAT rule 0, with Violation: Local_ACL as the reason.  Yes, I know that exposing RDP to the cloud is a horrible practice, but I have a single use case for this with RDP restricted to a single incoming IP and port forwarding from a high port instead of 3389.  Just want to know why upgrading to v19 changed this behavior.

Thanks in advance!



This thread was automatically locked due to age.

Top Replies

Parents Reply
  • This is true.  Since this is a home lab, the home modem router NATs the ISP's IP to a 192, and the XG NATs between that and my home (10.x) network.  I know double NATing can be a little sticky, but it's not been an issue before.    Worth it to raise with support?

Children