How to route outbound IP USG100.
Options
Hi,
I managed to configure a Virtual IP on a WAN Port for incoming connections.
xxx.xxx.xxx.100 -> 192.168.10.10 (machine01)
xxx.xxx.xxx.101 -> 192.168.10.11 (machine02)
The problem is, that the outbound IP for the machines are the same (xxx.xxx.xxx.100) and I need machine01 outbound at 100 and machine02 outbound on 101.
How can I achieve that?
Thanks for your help!
Dan
I managed to configure a Virtual IP on a WAN Port for incoming connections.
xxx.xxx.xxx.100 -> 192.168.10.10 (machine01)
xxx.xxx.xxx.101 -> 192.168.10.11 (machine02)
The problem is, that the outbound IP for the machines are the same (xxx.xxx.xxx.100) and I need machine01 outbound at 100 and machine02 outbound on 101.
How can I achieve that?
Thanks for your help!
Dan
0
Accepted Solution
-
Make a routing rule with:
incoming = Interface
member = lan1 or where 192.168.10.11 is
source address = 192.168.10.11
Source network address translation = xxx.xxx.xxx.101
1
All Replies
-
Make a routing rule with:
incoming = Interface
member = lan1 or where 192.168.10.11 is
source address = 192.168.10.11
Source network address translation = xxx.xxx.xxx.101
1 -
Thank you!0
-
Hi @Dani2323
Policy Route rules are able to fulfill your requirement.
You can create IP objects for your machines and public IP addresses first.
And configure then with correct rule and enable Address Translation(SNAT) setting.
1 -
0
Categories
- All Categories
- 384 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 80 Nebula Status and Incidents
- 5.1K Security
- 79 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 909 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 209 Service & License
- 335 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 1.9K FAQ
- 898 Nebula FAQ
- 415 Security FAQ
- 234 Switch FAQ
- 205 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 137 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 73 About Community
- 62 Security Highlight