Table of contents
Combined revision comparison
...
If you have forgotten the administrator password for your VPN Server, refer to 3.3 VPN Server Administration#3.3.7# and delete the following lines from the VPN Server configuration file with a text editor:
...
You can reset the administrator password for VPN Bridge by using the same method used for VPN Server. Refer to section 11.1.11,#11.1.11#, changing vpn_server.config to vpn_bridge.config where appropriate.
...
If you have used the methods described in section #10.5 Build a LAN-to-LAN VPN (Using L2 Bridge)# to to connect multiple network segments together with a layer 2 connection by using VPN Server and VPN Bridge, but can still not communicate between the computers on these networks, use the following method to determine if the networks are properly connected at a layer 2 level.
- If you are dealing with two LANs you can try this test. Set up one computer on LAN A with an unused IP address (for example, 192.168.222.1) and a computer on LAN B with an unused IP address on the same IP network as the computer you set up on LAN A (such as 192.168.222.2). Now try the ping command on both computers to see if they can ping each other. If they succeeded in communicating with each other, both networks are properly connected at a layer 2 level and the problem lies in the configuration of the rest of the computers. Remember that both LANs are logically functioning as a single Ethernet segment, so check settings such as TCP/IP, etc. very carefully.
- If the computers failed to communicate with each other by using the method above, you have probably made a mistake somewhere in the process of setting up your LAN-to-LAN VPN. In this situation, refer to sections
#10.5 Build a LAN-to-LAN VPN (Using L2 Bridge)#, #3#,, 3. SoftEther VPN Server Manual, or 5. SoftEther VPN Bridge Manual#5#and confirm your VPN configuration. - If each LAN has a different IP network structure and you want to allow communication between the computers on each LAN, refer to the method described in section
#10.6Build a LAN-to-LAN VPN (Using L3 IP Routing)#..
...
Normally you can just ignore this message with no problems, but if there are many FreeBSD machines on the same segment this could cause problems for the administrator of those machines. In this situation you can stop these polling packets from being sent. For instructions on how to stop a Virtual Hub from sending polling packets to confirm the existence of an IP address, please refer to section #3.4.8#.3.4 Virtual Hub Functions.
Version from 18:11, 4 Mar 2013
...
If you have forgotten the administrator password for your VPN Server, refer to #3.3.7# and delete the following lines from the VPN Server configuration file with a text editor:
...
You can reset the administrator password for VPN Bridge by using the same method used for VPN Server. Refer to section #11.1.11#, changing vpn_server.config to vpn_bridge.config where appropriate.
...
If you have used the methods described in section #10.5# to connect multiple network segments together with a layer 2 connection by using VPN Server and VPN Bridge, but can still not communicate between the computers on these networks, use the following method to determine if the networks are properly connected at a layer 2 level.
- If you are dealing with two LANs you can try this test. Set up one computer on LAN A with an unused IP address (for example, 192.168.222.1) and a computer on LAN B with an unused IP address on the same IP network as the computer you set up on LAN A (such as 192.168.222.2). Now try the ping command on both computers to see if they can ping each other. If they succeeded in communicating with each other, both networks are properly connected at a layer 2 level and the problem lies in the configuration of the rest of the computers. Remember that both LANs are logically functioning as a single Ethernet segment, so check settings such as TCP/IP, etc. very carefully.
- If the computers failed to communicate with each other by using the method above, you have probably made a mistake somewhere in the process of setting up your LAN-to-LAN VPN. In this situation, refer to sections
#10.5#, #3#,or#5#and confirm your VPN configuration. - If each LAN has a different IP network structure and you want to allow communication between the computers on each LAN, refer to the method described in section
#10.6#.
...
Normally you can just ignore this message with no problems, but if there are many FreeBSD machines on the same segment this could cause problems for the administrator of those machines. In this situation you can stop these polling packets from being sent. For instructions on how to stop a Virtual Hub from sending polling packets to confirm the existence of an IP address, please refer to section #3.4.8#.
Version as of 18:13, 4 Mar 2013
...
If you have forgotten the administrator password for your VPN Server, refer to 3.3 VPN Server Administration and delete the following lines from the VPN Server configuration file with a text editor:
...
You can reset the administrator password for VPN Bridge by using the same method used for VPN Server. Refer to section 11.1.11, changing vpn_server.config to vpn_bridge.config where appropriate.
...
If you have used the methods described in section 10.5 Build a LAN-to-LAN VPN (Using L2 Bridge) to connect multiple network segments together with a layer 2 connection by using VPN Server and VPN Bridge, but can still not communicate between the computers on these networks, use the following method to determine if the networks are properly connected at a layer 2 level.
- If you are dealing with two LANs you can try this test. Set up one computer on LAN A with an unused IP address (for example, 192.168.222.1) and a computer on LAN B with an unused IP address on the same IP network as the computer you set up on LAN A (such as 192.168.222.2). Now try the ping command on both computers to see if they can ping each other. If they succeeded in communicating with each other, both networks are properly connected at a layer 2 level and the problem lies in the configuration of the rest of the computers. Remember that both LANs are logically functioning as a single Ethernet segment, so check settings such as TCP/IP, etc. very carefully.
- If the computers failed to communicate with each other by using the method above, you have probably made a mistake somewhere in the process of setting up your LAN-to-LAN VPN. In this situation, refer to sections 10.5 Build a LAN-to-LAN VPN (Using L2 Bridge), 3. SoftEther VPN Server Manual, or 5. SoftEther VPN Bridge Manual and confirm your VPN configuration.
- If each LAN has a different IP network structure and you want to allow communication between the computers on each LAN, refer to the method described in section 10.6Build a LAN-to-LAN VPN (Using L3 IP Routing).
...
Normally you can just ignore this message with no problems, but if there are many FreeBSD machines on the same segment this could cause problems for the administrator of those machines. In this situation you can stop these polling packets from being sent. For instructions on how to stop a Virtual Hub from sending polling packets to confirm the existence of an IP address, please refer to section 3.4 Virtual Hub Functions.
