overall bandwidth. It needs to decide the “Default Router” or “Remote Subnet” for packet flow. You can also define what
kind of traffic will pass through the L2TP tunnel in the “Default Router / Remote Subnet” parameter.
Figure 258 – L2TP
There are two options, "Default Gateway" and "Remote Subnet" for the "Default Gateway / Remote Subnet" configuration
item. When you choose "Remote Subnet", you need to specify one more setting: the remote subnet. This is for the Intranet
of the L2TP VPN server. At the L2TP client peer, the packets whose destination is in the dedicated subnet will be transferred
via the L2TP VPN tunnel. Others will be transferred based on the current routing policy of the security gateway at the L2TP
client peer. If you choose the "Default Gateway" option for the L2TP client peer, all packets will go through the established
L2TP VPN tunnel. That means the remote L2TP VPN server controls the flowing of any packets from the L2TP client peer.
6.1.3.1 L2TP tunnel.
For the L2TP client peer, a Remote Subnet item is required. This is for the Intranet of the L2TP server peer. At the L2TP client
peer, the packets whose destination is in the dedicated subnet will be transferred via the L2TP tunnel. Others will be
transferred based on the current routing policy of the router at L2TP client peer. If you entered 0.0.0.0/0 in the Remote
Subnet field, it will be treated as a "Default Router" setting for the L2TP client peer. All packets will go through the
established L2TP tunnel. That means the remote L2TP server peer controls the flow of any packets from the L2TP client peer.
To Next Page
Loading...
Need help?
General