From: Shaun Nicholson (Shaun.Nicholson@xxxxxx)
Date: Thu Aug 31 2000 - 19:54:50 GMT-3
You have to make the default network match a route on another router.
Lets say you have a router in your network running rip 3 hops away with an ethe
rnet int 195.120.130.1
On the redistributing router connected to your igrp router put the statement
ip default-network 195.120.130.0
Then go to your igrp router and bingo theres your route with a * next to it as
a candadate route.
You also need ip classless on your eigrp router.
This is how I always do it
Hope this helps
Now stop worrying and good luck
Shaun Nicholson
Simon.Baxter@au.logical.com on 08/31/2000 06:25:00 PM
To: ccielab@groupstudy.com@Internet
cc: (bcc: Shaun Nicholson/MD/KAIPERM)
Subject: LAST DAY...HELP!!!
IGRP.
this is what I have :
int lo0
ip add 47.47.47.47/24
int s1/0
ip add 2.2.2.1
router igrp 1
netw 2.0.0.0
pass s1/0
neigh 2.2.2.2
ip default-network 47.0.0.0
the show ip protocols says :
Routing Protocol is "igrp 1"
Sending updates every 90 seconds, next due in 75 seconds
Invalid after 270 seconds, hold down 0, flushed after 630
Outgoing update filter list for all interfaces is
Incoming update filter list for all interfaces is
Default networks flagged in outgoing updates <------------shouldn't this
do it?
Default networks accepted from incoming updates
IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
IGRP maximum hopcount 100
IGRP maximum metric variance 1
Redistributing: igrp 1
Neighbor(s):
2.2.2.2
Routing for Networks:
1.0.0.0
2.0.0.0
Passive Interface(s):
Serial1/0
Routing Information Sources:
Gateway Distance Last Update
2.2.2.2 100 00:00:18
Distance: (default is 100)
Why won't my neighbor 2.2.2.2 get the default route?
It's not because of the unicast updates, if I put a more specific ip
default-network statement in it creates a static route which can only be
removed with a reload.
PLEEEASE someone be awake in the southern hemisphere!!
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:34 GMT-3