Chuck,
OH YES!! It's going to be a good day! LOL
Your analysis of the serial/ethernet is right on: this is exactly what I
had in mind. This is actually an idea a friend of mine came up with to link
EIGRP over disparate and wildly varying routing protocols: he came up with
3
I've actually done something like this in a lab. I wrote about it on the
list a few months back. I am e-mailing you the configs in a separate
message. ( too big for Paul to let through to the list ) but a relevant
excerpt follows:
Router A
interface Tunnel0
ip address 172.17.1.1 255.255.0.0
Of course, Charles, I'll lay odds you won't get end to end ip connectivity
anyway, given that mess you have created in the middle! :-
Chuck
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Cthulu, CCIE Candidate
Sent: Monday, November 13, 2000 5:15
Chuck,
Bless you for the configs, though I am put out that this one did not give
you pause...damn, I must be slipping;]I think I could attain
connectivity with this...reliability, stability, usuability, routability,
now that is another matter!
Many thanks again, I will be looking over the
On Mon, 13 Nov 2000, Cthulu, CCIE Candidate wrote:
Anyways, I got another one:
Given:
EIGRP 1 RTRA OSPF RTB BGP RTR C OSPF RTRD EIGRP1
I want RTRD and RTRA to become EIGRP peers and do the exchange routing
update thing. Granted, they are not directly
You know, Charles, I've been pondering this setup for a while now. ( See -
you did too get me after all! :- )
Now I already posted the wisecrack about the mess in the middle, and whether
or not you would even be able to get IP connectivity end to end here.
RouterA: ethernet EIGRP, serial=OSPF
6 matches
Mail list logo
