Hi,
I have a VPN bridge connected via a cascade to a VPN server with a L3 router. I have defined two interfaces on the L3 router, one with a class B mask (192.168.12.220 / 255.255.0.0) and the other with a class B mask (172.30.210.210 / 255.255.0.0).
With a client connected to the bridge I can only ping machines on the remote network that have an address from 172.30.210.0 to 172.30.210.254.
I have double cheked the mask, it is 255.255.0.0 but it works as it was 255.255.255.0.
All machines are Windows XP os, with the latest version of SoftEther.
Bye.
Problem with L3 router and class B and C
-
- Posts: 551
- Joined: Wed Jul 24, 2013 12:09 pm
Re: Problem with L3 router and class B and C
I don't see any problem here.
Make sure you have pushed the routes to the clients of each side correctly.
[attachment=1]74.png[/attachment]
[attachment=0]75.png[/attachment]
Make sure you have pushed the routes to the clients of each side correctly.
[attachment=1]74.png[/attachment]
[attachment=0]75.png[/attachment]
You do not have the required permissions to view the files attached to this post.
-
- Posts: 3
- Joined: Mon Jul 27, 2015 12:37 pm
Re: Problem with L3 router and class B and C
Do I have to push the routes withe the SecureNAT menu ? They are handled by other DHCP servers.
By the way in your second image you have the same mask for the two interfaces, in my setup 192.168.12.220 has 255.255.255.0 and 172.30.210.210has 255.255.0.0
Thanks.
By the way in your second image you have the same mask for the two interfaces, in my setup 192.168.12.220 has 255.255.255.0 and 172.30.210.210has 255.255.0.0
Thanks.
-
- Posts: 551
- Joined: Wed Jul 24, 2013 12:09 pm
Re: Problem with L3 router and class B and C
No need to use SecureNAT if your DHCP server is able to push the static routes.
The subnet mask only affects the address space. Both 255.255.255.0 and 255.255.0.0 will work, but when you use 255.255.255.0 instead of 255.255.0.0, the DHCP scope, the L3 Switch etc. must also use 255.255.255.0 for that subnet and vice versa.
The subnet mask only affects the address space. Both 255.255.255.0 and 255.255.0.0 will work, but when you use 255.255.255.0 instead of 255.255.0.0, the DHCP scope, the L3 Switch etc. must also use 255.255.255.0 for that subnet and vice versa.
-
- Posts: 551
- Joined: Wed Jul 24, 2013 12:09 pm
Re: Problem with L3 router and class B and C
As pictures
[attachment=2]76.png[/attachment]
[attachment=1]77.png[/attachment]
[attachment=0]78.png[/attachment]
[attachment=2]76.png[/attachment]
[attachment=1]77.png[/attachment]
[attachment=0]78.png[/attachment]
You do not have the required permissions to view the files attached to this post.
Last edited by kh_tsang on Mon Jul 27, 2015 2:22 pm, edited 1 time in total.
-
- Posts: 551
- Joined: Wed Jul 24, 2013 12:09 pm
Re: Problem with L3 router and class B and C
Maximum attachments reached, start another reply.
[attachment=0]79.png[/attachment]
[attachment=0]79.png[/attachment]
You do not have the required permissions to view the files attached to this post.
-
- Posts: 3
- Joined: Mon Jul 27, 2015 12:37 pm
Re: Problem with L3 router and class B and C
I can ping the adresses that are virtual hosts. The problem is with the remote LAN, there is a local bridge with the physical LAN, and I can ping only 4 adresses, there are 100.
-
- Posts: 551
- Joined: Wed Jul 24, 2013 12:09 pm
Re: Problem with L3 router and class B and C
Are you sure the routes and the subnet masks are correct?
172.30.0.0/16(172.30.0.0/255.255.0.0) through 192.168.12.220 on the 192.168.12.0/24 side
192.168.12.0/24(192.168.12.0/24/255.255.255.0) through 172.30.210.210 on the 172.30.0.0/16 side
The interfaces of the L3 Switch:
1. 172.30.210.210/16
2. 192.168.12.220/24
172.30.0.0/16(172.30.0.0/255.255.0.0) through 192.168.12.220 on the 192.168.12.0/24 side
192.168.12.0/24(192.168.12.0/24/255.255.255.0) through 172.30.210.210 on the 172.30.0.0/16 side
The interfaces of the L3 Switch:
1. 172.30.210.210/16
2. 192.168.12.220/24