Loopback NAT Policy

Jayser

Hello,

I don't know if this is the right place to ask this but...

I have created a few access rules "wan to lan" for web servers that are behind our firewall. I've created loopback NAT policy's that work too.

But recently, I put a server in a different zone. The access policy "wan to lan" works and the NAT Policy that allows the wan to zone2., works. But .loopback NAT policy doesn't.

I've created a access rule for zone1 to zone2 (generic names) and I can get to the server on zone2 using the local IP only. But when I create the loopback ( so I can use the dns name that resolve to wan IP ) , it does not. Is there issues or limitations that would stop this?

Hope that makes sense.

Thanks,

Jason

shiprasahu93

Hello Jayser,

Which zone are you testing the loopback IP from?

The best way to find what is going wrong will be by doing a packet capture on the firewall.

https://www.sonicwall.com/support/knowledge-base/how-can-i-setup-and-utilize-the-packet-monitor-feature-for-troubleshooting/170513143911627/

Also, there is no limitation that the loopback NAT will only work for LAN.

Thanks!

Jayser

Thank you,

I actually found a tech note about what I was trying to to.

I guess it's called a NAT reflection or hairpin.

Weird, I tried pulling up the doc again but it does not take me there any more.

I've attached what is looks like though (the description)

THNK

I have the Same issue here. Is this resolved already how?

TKWITS

Did you search the web?

https://www.sonicwall.com/support/knowledge-base/access-a-server-behind-the-sonicwall-from-internal-networks-using-public-ips-loopback-nat/170505780814635

cyberinv