From: John Neiberger (neiby@xxxxxxxxxx)
Date: Thu Mar 07 2002 - 19:24:28 GMT-3
For the first part I'm guessing that you used a secondary IP
address. Can you use subinterfaces on a regular ethernet
interface? Hmm.... that might also be a solution. I've never
tried it.
Assuming you're using secondary addressing, will the router at
least advertise both prefixes? Is the problem that the router
only uses the primary IP address to source routing updates but
you have routers that reside in both networks hanging off of
that interface?
Okay.... use RIP, and on the other routers add 'no validate-
update-source' to the RIP config. Since the updates are
broadcast (or multicast) this might allow them to at least get
updates that point back to the originating router.
This is interesting. Let us know what you find out!
John
---- On Thu, 07 Mar 2002, George Hansen
(HansenG@radiological.com) wrote:
> Here's a puzzle I came across in a production network:
>
> 1) Using one Ethernet port, configure a router to route
between network
> 10.1.0.0/16 and network 10.27.0.0/16. Both networks exist on
the same
> LAN. VLAN trunking is not allowed. One static route is
allowed.
>
> 2) Advertise a route to 10.27.0.0 to network 10.1.0.0 using
RIP or
> EIGRP.
>
> I've gotten part 1 to work, but haven't gotten part 2 yet.
>
> George Hansen, CCIE # 8546
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:56 GMT-3