Well, this is getting even weirder. Adding no ip split-horizon
seems to work, sort of. If I shut down the interfaces involved
and then bring them back up, all routes are advertised. Look
at the following:
C 172.16.20.0/24 is directly connected, Serial1
I 172.16.20.0/28 [100/1047
I thought I had discovered a way to do this but it didn't work,
either. It was a variation of the tunnel technique except the
tunnel is in a completely different classful network. For
example...
A(igrp)-B
The link is 172.16.1.0/28. I create a tunnel that is
4.0.0.1/8. On B, I con
people who coded this stuff.
Chuck
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
John Neiberger
Sent: Tuesday, December 18, 2001 11:12 PM
To: [EMAIL PROTECTED]
Subject: Re: RE: That Friday Follies Question... [7:29473]
I thought I had discovered a way to do this
ailto:[EMAIL PROTECTED]]On Behalf Of
>John Neiberger
>Sent: Tuesday, December 18, 2001 11:12 PM
>To: [EMAIL PROTECTED]
>Subject: Re: RE: That Friday Follies Question... [7:29473]
>
>
>I thought I had discovered a way to do this but it didn't work,
>either. It was a v
Warning, this is a bit longish...I'd be interested in feedback to see if
anyone agrees/disagrees, finds this at all helpful, etc. Part of this
exercise is to make sure I've got this straight in my head.
Here's a CCO link that may help:
http://www.cisco.com/warp/public/103/5.html
The scenario y
Excellent! That perfectly explains the behavior we were experiencing.
I was only able to make this work when the tunnel was in the same major
network. When I made the tunnel a part of a different major net, things
got a little weird.
You're correct, in the scenario I've been playing with IGRP
ent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Kevin Cullimore)
Subject: RE: RE: That Friday Follies Question... [7:29473]
Excellent! That perfectly explains the behavior we were experiencing.
I was only able to make this work when the tunnel was in the same major
network. When I mad
7 matches
Mail list logo
