RE: Routing without routing protocol

From: Kenneth Wygand (KWygand@customonline.com)
Date: Tue Jun 22 2004 - 15:37:39 GMT-3


Scott,

I agree with your "don't think too deep" philosophy, and in fact wish I
had adopted it on my previous lab attempts.

However, in this case, Tim stated the requirements will not allow him to
disable IP routing on the Cat3550.

Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"The only unattainable goal is the one not attempted."
-Anonymous

-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Tuesday, June 22, 2004 2:22 PM
To: 'ccie2be'; 'Jolly, Sean'; Kenneth Wygand; 'Group Study'
Subject: RE: Routing without routing protocol

What about "default-gateway"???

At that point, you'll need to disable ip routing, but does that fall
within
the confines of what you are or are not allowed to do?

Things don't always have a big convoluted fancy solution! Particularly
if
the notation in your lab for 3550 reachability is someplace in the early
LAN/Catalyst section... Labs are fairly logically written in that
regard
(for the most part).

So while NAT/PAT, or some other interesting solution may work (you still
need to get to the router before NAT takes place), think of the simple
things.

Just my opinion...

 
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP,
JNCIP, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
 
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Tuesday, June 22, 2004 11:33 AM
To: Jolly, Sean; 'Kenneth Wygand'; Group Study
Subject: Re: Routing without routing protocol

Sorry, no cigar. That, along with additional static routes, default
routes,
default networks are not allowed.

----- Original Message -----
From: "Jolly, Sean" <sjolly@scrippsops.com>
To: "'Kenneth Wygand'" <KWygand@customonline.com>; "ccie2be"
<ccie2be@nyc.rr.com>; "Group Study" <ccielab@groupstudy.com>
Sent: Tuesday, June 22, 2004 11:05 AM
Subject: RE: Routing without routing protocol

> PBR.
>
>
>
> -----Original Message-----
> From: Kenneth Wygand [mailto:KWygand@customonline.com]
> Sent: Tuesday, June 22, 2004 10:40 AM
> To: ccie2be; Group Study
> Subject: RE: Routing without routing protocol
>
> Tim,
>
> How about providing a static route on R5 pointing to the Loopback
> interface on the 3550. Then NAT all traffic on R5 destined for the
> 3550's Loopback interface through E0/1 to the IP address on its E0/1
> interface, which the 3550 will see as directly connected.
>
> If you need your 3550 to be able to initiate pings to other addresses
> and you are not allowed a static default, you can do that by disabling
> IP routing and providing a default gateway to R5's E0/1 (provided the
> rules allow this).
>
> Kenneth E. Wygand
> Systems Engineer, Project Services
> CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
> Network+, A+
> Custom Computer Specialists, Inc.
> "The only unattainable goal is the one not attempted."
> -Anonymous
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> ccie2be
> Sent: Tuesday, June 22, 2004 10:10 AM
> To: Group Study
> Subject: Routing without routing protocol
>
> Hi All,
>
> This one got me.
>
> 3550 has routing enabled but no routing protocols enabled.
>
> It's only path to the rest of the network is via R5. All other
routers
> on the
> other side of R5 must be able to ping the 3550's loopback.
>
> I'm allowed to use one static route on R5.
>
> This is what it looks like:
>
> 3550 lo0 fa0/5 ------- e0/1 R5 ----- rest of network
>
> How do I provide reachabiltiy to the 3550's lo0 without violating lab
> rules ie
> no default routes or default networks and
> no static routes except the one explicitly allowed here?
>
> Please tell me what I'm missing. Thanks, Tim
>
>



This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:47 GMT-3