How to allow L2TP VPN when WAN interface doesn't exist in default WAN trunk?
Zyxel_James
Posts: 663 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
- 415 Beta Program
- 2.4K Nebula
- 151 Nebula Ideas
- 98 Nebula Status and Incidents
- 5.7K Security
- 277 USG FLEX H Series
- 277 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.4K Consumer Product
- 250 Service & License
- 395 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 75 Security Highlight