From: Scott Morris (swm@emanon.com)
Date: Mon Aug 20 2007 - 03:32:05 ART
It has nothing to do with egress. It's an INGRESS interface (exception to
the RPF check).
If you real lab doesn't want you using "ip mroute" it should explicitly
state that. But an mroute is NOT a static route in any way, shape or form
as it has nothing to do with egress on any router.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
A Cisco Learning Partner - We Accept Learning Credits!
smorris@ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Ben
Holko
Sent: Monday, August 20, 2007 2:22 AM
To: ccielab@groupstudy.com
Subject: IEWB 4.1 Lab 1 - really a general question regarding lab rules
The general rules in the lab do's and don'ts is that you are not allowed to
add any static routes to any devices
Task 5.3 indicates a static mroute - while I understand that this is not the
same as a static unicast route, as it defines the egress interface rather
than a routing next-hop, it is nevertheless still a static route, so how is
it considered to be within the rules?
Ben
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:12 ART