Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 718 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

Version 18 and the Nat Rules

Alex Harding1

Hi Guys

Hoping someone can help me as I'm struggling a bit with V18 and the decoupling of NAT rules.
I know it works as its working on V17 without issue.

We have a vlan and within that vlan there is a device which requires WAN access.
I have created the firewall rule with the source zone being the vlan and the source device being the device we need to obtain WAN access along with the destination as WAN.
Now when the 3rd party run a tracert we can see its stopping at our XG


See below;

There is no web filtering etc for this device

Tested WAN Connectivity, nothing.
So I went ahead and created a NAT Rule

The NAT rule is linked to the correct firewall. Tested outbound WAN connection still nothing with the tracert failing at the same point. Our XG

So they I thought we need to create an SDWAN policy, so I did that too, however, that does not work either Disappointed

Anyone got any idea's what I have done wrong?



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    you could use your default Nat rule, there is no need for a specific Nat rule unless you have multiple wan interfaces.

    ian

  • 0 in reply to rfcat_vk

    Hi Ian

    Thanks for the reply.
    But I am unable to change the NAT rule the firewall rule is linked to.
    Should I delete both the Current NAT and Firewall rule and attempt to link to default?

    Please note I have not created a default NAT rule and the ones that are in place are from the migration of V17 to V18.

  • +1 in reply to Alex Harding1

    Hi Alex,

    during migration there would have been a number of linked rules created and a default NAT You can delete all the linked rules and rely on the default snat. Also there would have been a number of sd-wan rules created, you can delete them as well. You can delete the linked Nat rules without any issues as along as you have a default Nat rule.

    ian

Reply
  • +1 in reply to Alex Harding1

    Hi Alex,

    during migration there would have been a number of linked rules created and a default NAT You can delete all the linked rules and rely on the default snat. Also there would have been a number of sd-wan rules created, you can delete them as well. You can delete the linked Nat rules without any issues as along as you have a default Nat rule.

    ian

Children