How to allow L2TP VPN when WAN interface doesn't exist in default WAN trunk?
Options
Zyxel_James
Posts: 624 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
- 397 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 81 Nebula Status and Incidents
- 5.1K Security
- 87 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 916 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 211 Service & License
- 337 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2K FAQ
- 913 Nebula FAQ
- 421 Security FAQ
- 237 Switch FAQ
- 207 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 139 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 72 About Community
- 62 Security Highlight