Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 17 replies
  • Subscribers 29 subscribers
  • Views 3485 views
  • Users 0 members are here
Options
Suggested
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

SNAT not working, getting NAT 0

Anthony Anderson

Help please, 

I have internal server 192.168.99.168 SNAT to x.x.x.168

I have internal server 192.168.99.169 SNAT to x.x.x.169

I have both x.x.x.168 and x.x.x.169 setup as aliases on WAN1 

Here is the SNAT rule and its setup identically for the .169

When they try to send email this is the packet capture showing NAT rule 0 is being applied and it's NOT leaving the device as evidenced by no outgoing port. You also see the DNAT is working. 

Any ideas? Please help



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to emmosophos

    Emmo, 

    Thanks alot for that. I did a show route precedence and I see

    console> system route_precedence show
    Default routing Precedence:
    1. SD-WAN policy routes
    2. VPN routes
    3. Static routes

    We do have a SD-WAN policy in place to load balance Https as well. The thing is you can see from my packet capture that the incoming connection initiated the connection on port 37544 and the 192.168.99.168 server responds to it but it doesn't have an Out Interface listed so the packet doesn't even leave the XG. Riddle me that.