LAN-to-LAN VPN, Using L3 IP routing

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
mithrandir
Posts: 5
Joined: Wed Jun 01, 2016 8:12 am

LAN-to-LAN VPN, Using L3 IP routing

Post by mithrandir » Wed Jun 01, 2016 8:59 am

I use Debian Linux (Jessie, https://www.debian.org/releases/jessie/).

I tied two networks based on the description posted on your website
https://www.softether.org/4-docs/1-manu ... Routing%29

I have a problem with it:
The two computers, which terminates the VPN, do not see the other side of the network of VPN.

Questions:
This is the expected operation, or I made a mistake?

Can it be resolved, and if yes how should these machines are able to
communicate with other machines via VPN?

Thanks your kindness,
mithrandir

mithrandir
Posts: 5
Joined: Wed Jun 01, 2016 8:12 am

Re: LAN-to-LAN VPN, Using L3 IP routing

Post by mithrandir » Wed Jun 01, 2016 1:16 pm

192.168.1.2: ping 192.168.7.148 and 192.168.7.254 - OK
192.168.1.95: ping 192.168.7.148 and 192.168.7.254 - OK
192.168.7.148: ping 192.168.1.2 and 192.168.1.95 - OK
192.168.7.254: ping 192.168.1.2 and 192.168.1.95 - OK

but
192.168.1.2: ping 192.168.7.253 - not response
192.168.1.95: ping 192.168.7.253 - not response
192.168.1.254: ping 192.168.7.148 - not response
192.168.1.254: ping 192.168.7.253 - not response
192.168.1.254: ping 192.168.7.254 - not response

192.168.7.148: ping 192.168.1.254 - not response
192.168.7.254: ping 192.168.1.254 - not response
192.168.7.253: ping 192.168.1.2 - not response
192.168.7.253: ping 192.168.1.95 - not response
192.168.7.253: ping 192.168.1.2 54- not response

A localbridged network device can't communicate with the virtualhub?
You do not have the required permissions to view the files attached to this post.

mithrandir
Posts: 5
Joined: Wed Jun 01, 2016 8:12 am

Re: LAN-to-LAN VPN, Using L3 IP routing

Post by mithrandir » Fri Jun 03, 2016 11:52 am

I have done a new network card (eth0) B-FW machine.
# ifconfig eth0 0.0.0.0
I remove local bridge eth1, configure local bridge new card (eth0).

Result:
192.168.1.254: ping 192.168.7.148 - OK
192.168.1.254: ping 192.168.7.254 - OK
192.168.7.148: ping 192.168.1.254 - OK
192.168.7.254: ping 192.168.1.254 - OK

http://www.softether.org/4-docs/1-manua ... r_Mac_OS_X
3.6.11 Points to Note when Local Bridging in Linux, FreeBSD, Solaris or Mac OS X
"Limitations within the Linux or UNIX operating system prevent communication with IP addresses assigned to the network adapter locally bridged from the VPN side (Virtual Hub side). The cause of this restriction lies with OS's internal kernel codes rather than with the SoftEther VPN. When wishing to communicate in any form with a UNIX computer used for local bridging from the VPN side (Virtual Hub side), (for instance, when running both the VPN Server / VPN Bridge service & the HTTP Server service and wishing to grant access to the server service from the VPN side as well), prepare and connect a local bridge network adapter and physically connect both it and the existing network adapter to the same segment (as explained in 3.6 Local Bridges, it is recommended to prepare a network adapter for exclusive use in local bridging for this and other situations)."
You do not have the required permissions to view the files attached to this post.

Post Reply