Can clients access a network using the same account when L2TP VPN has been configured on the AR router

0

The same user name can be used to access the network. There is no limitation on the specification.

Other related questions:
After the AR is configured with L2TP VPN, can clients use the same user name to access the network
Users can access the network using the same user name. By default, there is no limitation.

Does the AR router support the L2TP VPN accounting function
L2TP of the AR router does not support the accounting function. Accounting-stop packets are not generated after users are disconnected from the network. As a result, the RADIUS accounting function of L2TP users is not supported either. V200R007 and later versions support the RADIUS accounting function.

Method used to configure mutual access between remote clients of the L2TP VPN on the USG2000 and USG5000
The method used to configure mutual access between remote clients of the L2TP VPN on the USG2000 and USG5000 is as follows: Problem description: Simple networking: (192.168.10.2) USG2000 (branch network 1) USG5000 (HQ) USG2000 (branch network 2) (192.168.157.1) The address (192.168.10.2) of branch network 1 can be successfully pinged using the address (192.168.157.1) of branch network 2. Implementation flow: 1. The key configuration is as follows: Branch network 1: interface Virtual-Template1 ppp authentication-mode chap ppp chap user trustuser ppp chap password cipher %$%$W#p2p!0JS[T*E/71$]C:1%$%$ tunnel name trust start l2tp ip 222.240.248.210 fullusername trustuser ip route-static 192.168.148.0 255.255.255.0 10.12.1.1 ip route-static 192.168.157.0 255.255.255.0 10.12.1.5 Route to branch network 2 ip route-static 192.168.173.0 255.255.255.0 10.12.1.1 ip route-static 192.168.174.0 255.255.255.0 10.12.1.1 Branch network 2: interface Virtual-Template1 ppp authentication-mode chap ppp chap user trustuser ppp chap password cipher A!! ip address 10.12.1.5 255.255.255.0 call-lns local-user trustuser l2tp-group 1 tunnel password cipher -G=,LULZYDWJCK_%%<:`LQ!! tunnel name trust start l2tp ip 222.240.248.210 fullusername trustuser ip route-static 0.0.0.0 0.0.0.0 218.76.73.1 ip route-static 192.168.10.0 255.255.255.0 10.12.1.33 Route to branch network 1 ip route-static 192.168.148.0 255.255.255.0 10.12.1.1 track ip-link 1 HQ network: No additional route is required. interface Virtual-Template2 ppp authentication-mode chap ppp chap user trustuser ppp chap password cipher A!! ip address 10.12.1.1 255.255.255.0 remote address pool 2 l2tp-group 2 allow l2tp virtual-template 2 remote trust tunnel password cipher -G=,LULZYDWJCK_%%<:`LQ!! tunnel name trustlns aaa ip pool 2 10.12.1.60 10.12.1.254 ip route-static 192.168.157.0 255.255.255.0 10.12.1.5 track ip-link 18

Does the AR support the L2TP VPN accounting function
The AR does not support L2TP VPN accounting. After a user goes offline, accounting-stop packets are not sent. Therefore, the AR also does not support the accounting function of L2TP users on the RADIUS server. V200R007 and later versions support the accounting function through the RADIUS server.

WPA/WPA2 has been configured on the AR router successfully but does not take effect
The troubleshooting procedure is as follows: 1. Check whether you have run the dot1x enable command to enable 802.1x authentication globally. 2. Check whether the configuration of WPA/WPA2 is complete. 3. Check whether the user name and password are correct.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top