Communicating across different subnets

[craiggory]

Hi

I have a layer 2 site-to-site connection established between two LAN's.
LAN 1: 10.0.0.0
LAN 2: 10.0.1.0

How can I get 10.0.0.0 addresses to communicate with 10.0.1.0 addresses and vice versa?
Currently devices can only communicate with devices on the others' network if I manually assign a static IP that is within the range of the remote networks addresses.

Please assist!

Thanks

[softether_fans]

You need to show your subnet netmask.

There are two ways:
1) Cascade connection between two softether servers;
2) L3 routing;

[craiggory]

I am using a subnet mask of 255.255.255.0

I would like to do option one and stay away from Layer 3 routing.
When you say cascade connection between two softether servers, does that mean that I need the server application installed on both networks? i.e. both sites hosting their own VPN's with site one connecting to site two's VPN, and then establishing another connection from site two back to site one's VPN? Or should I only have to connect one site to the other and that's it? Please elaborate...

Currently I have site 1 hosting the VPN, and site 2 connects back to site one. Is this setup incorrect for communication between the two networks both directions using their respective IP's?

Thanks for your help!!

[craiggory]

@jedipii Thanks for the response! That is definitely useful information! I took your advice and changed all of the subnet masks on static network clients to 255.255.254.0, and then on the DHCP servers as well. However, I am still unable to communicate between clients on the different networks.

Client 1:
Network site 1
IP: 10.0.0.x
Subnet Mask: 255.255.254.0
Default Gateway: 10.0.0.1

Client 2:
Network site 2
IP: 10.0.1.x
Subnet Mask: 255.255.254.0
Default Gateway: 10.0.1.1

Cascading connection made from site 2 back to site 1.
Both VPN server's have static IP's in their respective networks address range, and have the 255.255.254.0 subnet mask.

Neither VPN server can ping the other via IP address either. However, both servers report online and connected via the VPN server manager application.

Is their something else that I need to configure that I am missing?

Josh

[thisjun]

Did you make localbridges on both sides?

[craiggory]

Yes, local bridges were created on both sides, otherwise I wouldn't have been able to ping clients on the remote network after statically assigning IP addresses.

Somehow it magically started working without me modifying any setting between the time when it didn't work and when it did. What would have caused this? Could it be something to do with the discovery of routes in the routing tables or something? I don't know... I don't understand why it didn't work and then magically started working by itself. When I say started 'working', I am referring to being able to ping clients on the remote network i.e. ping client 10.0.1.1 from client 10.0.0.1.

[thisjun]

What OS did you use?