- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: VSX - NAT Configuration
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VSX - NAT Configuration
Good morning,
nice to meet you.
It's my first time I configured VSX, and with humility, I I say I'm having problems configuring the NAT rules.
AS you can see we deployed two VSs (one Internal and one External).
We would like to simplify as much as possible the NAT rules.
For example, we tried to NAT management network (Static NAT rule) behind Public IP, but it does not work.
Any suggestions about and how to configure NAT rules and where (which VS) in the easiest way to see less logs in the SmartDashboard are really appreciated (maybe with some examples).
Is there something wrong? I am really grateful to you.
Thanks, best regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just a quick suggestion:
> we tried to NAT management network (Static NAT rule) behind Public IP, but it does not work.
This is your idea:
- Real SRC: mgmt network
- Real DST: Any
- Translated Source: the external IP of the firewall (so you configure a dynamic PAT, or "hidden", not "static")
- Translated DST: = (he same as the real DST)
You can use the "hide the traffic behind the external IP", but personally, I prefer an explicit manual NAT rule.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, I posted all screenshots, but I am lost on this configuration 😅, any suggestion about configuration?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you have screenshot of how rules are configured?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It was attached, and now it's deleted. The NAT rule on the screenshot was a static one from, for example, Net1 to Net1. Hence my note about PAT to the external iface.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, so, I posted all screenshots!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When using manual NAT, ensure that Proxy ARP is properly configured and that the "Merge manual proxy ARP configuration" option is selected in the Global Properties under NAT settings.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, as you can see I posted screenshots.
In case, which IP address do I need to use as a proxy ARP?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For outgoing PAT (to the external IP of the firewall/cluster) you do not need proxy ARP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi everyone,
so, at the end, today I simply created an automatic NAT rule (Oject and then Nite, Hide Behing the Gateway).
There is NAT on External VSX (enabled NAT, Hide behind the Gateway).
I think at the moment is the best solution!
