From: fwells12 (fwells12@xxxxxxxxxxx)
Date: Tue Apr 10 2001 - 15:33:34 GMT-3
You are absolutely right about not running IPX on the tunnels. I was hoping
to find a way to do it without having to specify an IPX network number on
the tunnels, but I could not get it to work. The only way I managed to get
it working was by putting IPX numbers on them after all. This defeated my
whole experiment of running IPX over tunnels using only one IPX network
number. I did find some mention of a multipoint tunnel in the archives, I
am only running 11.3 though and it is not an option in that IOS. So, being
able to tunnel IPX using only one IPX network number may yet be a
possibility.
BTW, I also had to source the hub tunnels from the sub-interface.
Thanks for everyone's input.
Final working configs:
r5
interface Tunnel25
no ip address
ipx network A
tunnel source Serial0.1
tunnel destination 133.6.10.22
!
interface Tunnel35
no ip address
ipx network B
tunnel source Serial0.1
tunnel destination 133.6.10.23
!
interface Serial0.1 multipoint
ip address 133.6.10.25 255.255.255.240
ipx network 35
r2
interface Tunnel25
no ip address
ipx network A
tunnel source Serial0
tunnel destination 133.6.10.25
!
interface Serial0
ip address 133.6.10.22 255.255.255.240
ipx network 35
r3
interface Tunnel35
no ip address
ipx network B
tunnel source Serial0
tunnel destination 133.6.10.25
!
interface Serial0
ip address 133.6.10.23 255.255.255.240
ipx network 35
----- Original Message -----
From: Chuck Larrieu <chuck@cl.cncdsl.com>
To: fwells12 <fwells12@hotmail.com>
Sent: Monday, April 09, 2001 8:03 AM
Subject: RE: More IPX tunnels over sub-interfaces.
> Ok, but you aren't running ipx on your tunnels. Not according to the
configs
> below. And if you were running ipx on your tunnels, them being
> point-to-point links, then you could not have a single ipx network
> connecting them.
>
> Chuck
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> fwells12
> Sent: Monday, April 09, 2001 7:30 AM
> To: ccielab@groupstudy.com
> Subject: Re: More IPX tunnels over sub-interfaces.
>
> No red-herrings Chuck.
> This is a tricky one. My idea was to get the three routers exchanging IPX
> using one IPX network number and not using the usual IPX EIGRP. I spent a
> couple of hours just trying to get the tunnels working, little did I know
I
> had them right from the beginning and it just took a reboot to get them
> working properly!
>
> r2s1 has IPX network 12 on it. I want to be able to see that network from
> r3.
>
> ----- Original Message -----
> From: Chuck Larrieu <chuck@cl.cncdsl.com>
> To: fwells12 <fwells12@hotmail.com>
> Sent: Monday, April 09, 2001 12:22 AM
> Subject: RE: More IPX tunnels over sub-interfaces.
>
>
> > Frank, I gather the tunnel interfaces are red herring?
> >
> > On R2 S1 interface is not shut down? This means line protocol is up, as
> well
> > as the physical interface? Same for the ethernet interface on R3? I'm
not
> > familiar with changing the ethernet mac address myself, but I presume
one
> > can do so.
> >
> > Other than that, everything looks fine to me.
> >
> > Chuck
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> > fwells12
> > Sent: Sunday, April 08, 2001 11:19 PM
> > To: ccielab@groupstudy.com
> > Subject: More IPX tunnels over sub-interfaces.
> >
> > Can anyone explain why I am able to see all IPX networks from the hub
(r5)
> > but
> > I am unable to see IPX network 34 on r3 from r2 and likewise, IPX
network
> 12
> > on r2 from r3? The spoke routers are r2 and r3, the hub router is r5.
I
> > can
> > ipx ping the spokes from each other. I am not running IPX EIGRP over
the
> > cloud in case your thinking split-horizon.
> >
> > Here are the relevant parts of the configs. TIA.
> >
> > interface Tunnel25
> > no ip address
> > tunnel source Serial0
> > tunnel destination 133.6.10.22
> > !
> > interface Tunnel35
> > no ip address
> > tunnel source Serial0
> > tunnel destination 133.6.10.23
> > !
> > interface Ethernet0
> > mac-address 0005.0005.0032
> > ip address 133.6.100.5 255.255.255.0
> > ipx network 32
> > !
> > interface Serial0
> > no ip address
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip mroute-cache
> > no frame-relay inverse-arp
> > frame-relay lmi-type ansi
> > !
> > interface Serial0.1 multipoint
> > ip address 133.6.10.25 255.255.255.240
> > ipx network 35
> > frame-relay map ip 133.6.10.22 102 broadcast
> > frame-relay map ip 133.6.10.23 103 broadcast
> >
> > r2
> > interface Tunnel25
> > no ip address
> > tunnel source Serial0
> > tunnel destination 133.6.10.25
> > !
> > interface Serial0
> > ip address 133.6.10.22 255.255.255.240
> > ipx network 35
> > !
> > interface Serial1
> > ipx network 12
> >
> > r3
> > interface Tunnel35
> > no ip address
> > tunnel source Serial0
> > tunnel destination 133.6.10.25
> > !
> > interface Serial0
> > ip address 133.6.10.23 255.255.255.240
> > ipx network 35
> > !
> > interface Ethernet0
> > mac-address 0003.0003.0034
> > ipx network 34
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:43 GMT-3