- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: Translate destination on client side
- 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
Translate destination on client side
Hi CheckMates,
Per sk85460 says:
Detailed example:
Server side scenario:
If the correct static host/network route for "Destination/Server" was added into the routing table of the underlying operating system, the packet will be routed corrected to the outbound interface eth1.
I add 172.16.0.100 as below, but not work.
In this case, what routed I should add ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the NAT IP is 172.16.0.100 and the real IP is 10.0.0.100, you would add a route for 172.16.0.100 with 10.0.0.100 configured as the nexthop.
That said, I'm not sure why you're doing this as the the default configuration (with Translate Destination on Client Side enabled) does not require a route like this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi PhoneBoy,
I just LAB (Translate destination on client side / Translate destination on server side), because in this case (Translate destination on server side) I can not LAB success.
"If the correct static host/network route for "Destination/Server" was added into the routing table of the underlying operating system, the packet will be routed corrected to the outbound interface eth1."
- 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
My Lab topology is show as below:
I create 2 NAT rule :
When translate on client side is check, I can revived web portal. fw monitor show as below:
When translate on client side is uncheck, fw monitor show as below:
but O is not current, it should be eth0, show I add routing as below:
fw monitor:
now it looks current interface, but still can't received web portal.
so I add web server second IP 10.8.2.80. and it is work. I can received web portal. fw monitor is show as below
In my lab, is it connection or route issue with access web portal even I add route?
or this is current configuration for this lab (translate on server side) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My Lab topology is show as below:
I create 2 NAT rule :
When translate on client side is check, I can revived web portal. fw monitor show as below:
When translate on client side is uncheck, fw monitor show as below:
but O is not current, it should be eth0, show I add routing as below:
fw monitor:
now it looks current interface, but still can't received web portal.
so I add web server second IP 10.8.2.80. and it is work. I can received web portal. fw monitor is show as below
In my lab, is it connection or route issue with access web portal even I add route?
or this is current configuration for this lab (translate on server side) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please remove this manual route and configure Static NAT in the properties of the Object of your server entering it's "Public" IP in the NAT tab.
This will create an automatic Proxy ARP entry on the "external" interface and will accept and forward traffic to the destination.
As far as routes go, both, Internal and External networks are going to be shown in your "Connected Routes".