Hi,
So if I understood you correctly, you would want to build 2 L2L VPN connections from Kansas. One to Reno and one to Vermont? And you want users from Reno to be able to connect to Vermont through these connections?
There should be no problem doing this. There is no need for the traffic from Reno to go through the local network of Kansas. It will simply take a turn at the "outside" interface of Kansas and head out towards Vermont through the other L2L VPN connection.
Some things you have to take into considerations when configuring are
- Reno will need to define that the traffic destined to Kansas and Vermont LANs is defined on the L2L VPN connection towards Kansas
- Reno will need to define NAT0 configurations for the above mentioned traffic from Reno to Kansas and Reno to Vermont
- Kansas will need to have 2 L2L VPN configurations.
- Kansas will need to define that traffic between the Reno and Vermont networks is defined on both of the above mentioned L2L VPN configurations
- Kansas will need to have NAT0 configurations on its "outside" interface for the Reno and Vermont networks so that traffic between them will flow
- Kansas will also need the "same-security-traffic permit intra-interface" configuration. This will permit the traffic from Reno to head to Vermont through the same interface it entered from. This is because the traffic will enter from "outside" and will also leave from "outside"
- Vermont will naturally have the same kind of needs as Reno as its a spoke in the topology also.
Also I guess you always have the option to configure a L2L VPN directly between Reno and Vermont without Kansas having anything to do with that setup.
Hopefully the information was helpfull I am not sure if this is just at planning stages or if you had already tried to configure it and had some problems?
- Jouni
