l3 lan-to-lan doesnt work

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
ixlabs
Posts: 8
Joined: Thu Dec 04, 2014 11:43 pm

l3 lan-to-lan doesnt work

Post by ixlabs » Wed Dec 10, 2014 3:40 pm

Hi Guys.

This is my schema:
On my office i have a server running the bridge, which is connected to the server outside (on digital ocean) and successfully connected, i can see the ip and mac tables so it seems is ok.
I follow the instructions about the L3-switching lan-to-lan but it seems it doesn't work.
I created on the server in digital ocean a VirtualHub with the address 192.168.10.0/24 named office, another named office-vpn with network 10.10.40.0/24 and a virtualswitch with two interfaces, 192.168.10.254 and 10.10.40.254.
DHCP is enabled on 10.10.40.254 and in the other is disabled (because the DHCP server is already in my office, a pfsense box).
Well, it says that the virtual switch with the address 192.168.10.254 should be listed on my office network and i think should be accessible from my office (due to the soft ether vpn client running in the machine that create the tunnel to my digital ocean server node). But no.

I dont know what do to. Of course i know a little about networking and it seems something is not working.

Version 4.12 9514 Linux on debian wheezy and bridge same version on debian wheezy x32

dajhorn
Posts: 137
Joined: Mon Mar 24, 2014 3:59 am

Re: l3 lan-to-lan doesnt work

Post by dajhorn » Mon Dec 15, 2014 3:50 am

IP addresses created by SoftEther, like the 10.10.40.254 and 192.168.10.254 router addresses, are not actually bound to the server.

Try this:

1. On the client computer, bridge the LAN into Virtual Hub 1.
2. On the Digital Ocean server, bridge a tap interface into Virtual Hub 2.
3. Create a cascade connection between Virtual Hub 1 and Virtual Hub 2.
4. On the Digital Ocean server, configure the tap interface as a DHCP client.
5. The Digital Ocean server should get a DHCP lease from the pfSense server and behave like it is on the LAN.

Post Reply