From: Jay Hennigan (jay@west.net)
Date: Tue Jul 15 2003 - 14:36:02 GMT-3
On Mon, 14 Jul 2003 polarccie@yahoo.co.uk wrote:
> thank you for the answer...
> does that mean, we should grab an ip address from the allowed range and assign it to the tunnel interfaces...
>
> say i have
> r1----r2----r3
>
> FR nbma, hub and spoke
> all have ips 192.168.123.x where x is the router id.if i want to tunnel between r1 and r3....
>
> should i have sthg like
>
> on R1
> int tunnel 0
> tunnel source 192.168.123.1
> tunnel destination 192.168.123.3
> ip add 192.168.13.1 255.255.255.0
>
> and
> int tunnel 0
> tunnel source 192.168.123.3
> tunnel destination 192.168.123.1
> ip add 192.168.13.3 255.255.255.0
> on R3?
This will work.
> and will i allow this route to be seen on other routers routing tables?
If you're referring to the 192.168.13.0/24 network, there is no need to
allow it, and it won't show up unless you redistribute connected or make it
part of a routing protocol. The addresses of the tunnel itself are, ummm...
"tunneled" through the IP network that connects the source and destination.
The tunnel looks like one hop.
-- Jay Hennigan - CCIE #7880 - Network Administration - jay@west.net WestNet: Connecting you to the planet. 805 884-6323 WB6RDV NetLojix Communications, Inc. - http://www.netlojix.com/
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:40 GMT-3