How to allow L2TP VPN when WAN interface doesn't exist in default WAN trunk?
Options
Zyxel_James
Posts: 809
Zyxel Employee
Zyxel Employee
in VPN
QUESTION
In this scenario, the WAN interface for L2TP connection does not exist in the default WAN trunk, how to allow L2TP VPN such a WAN interface that is not in the default WAN trunk?
ANSWER
You can add policy routes to resolve this situation because policy route priority is higher than the default WAN trunk.
Policy route:
(1) Incoming: L2TP VPN, Source: L2TP VPN subnet, Next-Hop: Auto, SNAT: Outgoing-interface.
(2) Incoming: ZyWALL, Source: WAN interface, Source Port: UDP1701, Next-Hop: L2TP VPN tunnel, SNAT: none.
(3) Incoming: ZyWALL, Source: WAN interface, Next-Hop: WAN interface, SNAT: none
Please note thatSince UDP1701 port belongs to ESP packets, it must be routed into VPN tunnel.
0
Categories
- All Categories
- 442 Beta Program
- 2.9K Nebula
- 220 Nebula Ideas
- 128 Nebula Status and Incidents
- 6.5K Security
- 606 USG FLEX H Series
- 344 Security Ideas
- 1.7K Switch
- 84 Switch Ideas
- 1.4K Wireless
- 52 Wireless Ideas
- 7K Consumer Product
- 298 Service & License
- 482 News and Release
- 92 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 4.8K FAQ
- 34 Documents
- 87 About Community
- 105 Security Highlight