DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
Route VPN to VPN
- gerry bulger
- Topic Author
- Offline
- New Member
Less
More
- Posts: 6
- Thank you received: 0
28 Apr 2015 16:16 #83285
by gerry bulger
Route VPN to VPN was created by gerry bulger
I cannot get this to work. LAN to LAN route. That is to reach the other PCs on the remote lan from mine. Cannot ping and the rest.
Set up:
2860vn 192.168.1.254 dials out and connects successfully (goes green) to 2820vn L2TP IPSEC 10.0.0.138
Dial out router 2860vn setting is set to do NAT
Dial in in router 2820, 10.0.0.138, 28 is set to route
The routing table of the dial out router looks like this.
Key: C - connected, S - static, R - RIP, * - default, ~ - private
* 0.0.0.0/ 0.0.0.0 via 2.128.238.160 WAN1
C 1.0.0.1/ 255.255.255.255 directly connected VPN-2
* 2.127.238.160/ 255.255.255.255 via 2.128.238.160 WAN1
S 5.76.47.0/ 255.255.255.0 via 1.0.0.1 VPN-2
C 10.0.0.138/ 255.255.255.255 directly connected VPN-3
S 10.0.0.0/ 255.255.255.0 via 10.0.0.138 VPN-3
S 87.81.144.98/ 255.255.255.255 via 87.81.144.98 WAN1
S 169.254.92.0/ 255.255.255.0 via 192.168.10.10 VPN-1
C 192.168.10.10/ 255.255.255.255 directly connected VPN-1
* 192.168.15.1/ 255.255.255.255 via 192.168.15.1 WAN2
C 192.168.15.0/ 255.255.255.0 directly connected WAN2
C~ 192.168.1.0/ 255.255.255.0 directly connected LAN1
The routing table of remote looks like this
Key: C - connected, S - static, R - RIP, * - default, ~ - private
* 0.0.0.0/ 0.0.0.0 via 203.40.253.1 WAN1
C~ 10.0.0.0/ 255.255.255.0 directly connected LAN
* 203.45.253.1/ 255.255.255.255 via 203.40.253.1 WAN1
C~ 192.168.10.10/ 255.255.255.255 directly connected VPN-1
S~ 192.168.10.0/ 255.255.255.0 via 192.168.10.10 VPN-1
C~ 192.168.1.254/ 255.255.255.255 directly connected VPN-2
S~ 192.168.1.0/ 255.255.255.0 via 192.168.1.254 VPN-2
S 203.45.26.7/ 255.255.255.255 via 203.45.26.7 WAN1
So how do you have the LAN to LAN route so 192.168.1.1 sees 10.0.0.1 etc? There is no route between the two at the moment. I assumed LAN to LAN set that up. You cannot put it in static routes as the menu options do not show the VPN connections.
I assume I am missing something bleeding obvious.
Gerry
Set up:
2860vn 192.168.1.254 dials out and connects successfully (goes green) to 2820vn L2TP IPSEC 10.0.0.138
Dial out router 2860vn setting is set to do NAT
Dial in in router 2820, 10.0.0.138, 28 is set to route
The routing table of the dial out router looks like this.
Key: C - connected, S - static, R - RIP, * - default, ~ - private
* 0.0.0.0/ 0.0.0.0 via 2.128.238.160 WAN1
C 1.0.0.1/ 255.255.255.255 directly connected VPN-2
* 2.127.238.160/ 255.255.255.255 via 2.128.238.160 WAN1
S 5.76.47.0/ 255.255.255.0 via 1.0.0.1 VPN-2
C 10.0.0.138/ 255.255.255.255 directly connected VPN-3
S 10.0.0.0/ 255.255.255.0 via 10.0.0.138 VPN-3
S 87.81.144.98/ 255.255.255.255 via 87.81.144.98 WAN1
S 169.254.92.0/ 255.255.255.0 via 192.168.10.10 VPN-1
C 192.168.10.10/ 255.255.255.255 directly connected VPN-1
* 192.168.15.1/ 255.255.255.255 via 192.168.15.1 WAN2
C 192.168.15.0/ 255.255.255.0 directly connected WAN2
C~ 192.168.1.0/ 255.255.255.0 directly connected LAN1
The routing table of remote looks like this
Key: C - connected, S - static, R - RIP, * - default, ~ - private
* 0.0.0.0/ 0.0.0.0 via 203.40.253.1 WAN1
C~ 10.0.0.0/ 255.255.255.0 directly connected LAN
* 203.45.253.1/ 255.255.255.255 via 203.40.253.1 WAN1
C~ 192.168.10.10/ 255.255.255.255 directly connected VPN-1
S~ 192.168.10.0/ 255.255.255.0 via 192.168.10.10 VPN-1
C~ 192.168.1.254/ 255.255.255.255 directly connected VPN-2
S~ 192.168.1.0/ 255.255.255.0 via 192.168.1.254 VPN-2
S 203.45.26.7/ 255.255.255.255 via 203.45.26.7 WAN1
So how do you have the LAN to LAN route so 192.168.1.1 sees 10.0.0.1 etc? There is no route between the two at the moment. I assumed LAN to LAN set that up. You cannot put it in static routes as the menu options do not show the VPN connections.
I assume I am missing something bleeding obvious.
Gerry
Please Log in or Create an account to join the conversation.
- sicon
- Offline
- Contributor
Less
More
- Posts: 642
- Thank you received: 0
28 Apr 2015 16:20 #83286
by sicon
Replied by sicon on topic Re: Route VPN to VPN
both ends need to be set to route and not NAT in the TCP/IP settings?
Please Log in or Create an account to join the conversation.
- gerry bulger
- Topic Author
- Offline
- New Member
Less
More
- Posts: 6
- Thank you received: 0
28 Apr 2015 16:23 #83287
by gerry bulger
Replied by gerry bulger on topic Re: Route VPN to VPN
Thanks. tried that. And every combination! Thanks In fact the receiving dial in does not allow NAT, only route the connection is set to dial in only.
Please Log in or Create an account to join the conversation.
Moderators: Chris, Sami
Copyright © 2024 DrayTek