this post was submitted on 05 Sep 2023
8 points (100.0% liked)
networking
2805 readers
1 users here now
Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My guess is responses aren’t NATing properly with the double NAT. Make sure you have a source NAT masquerade rule set up for traffic out, you may also need a masquerade to replace your client’s IP with the LAN gateway address on the way out.
Basically right now without masquerading as your LAN port the router loses the originating client’s IP when it src NATs, so the responses get delivered to the internal gateway address and never forwarded on to the client to establish the connection. Forcing it to masquerade will maintain that connection tracking.
That's exactly what it was. Thank you so much