From: James (james@towardex.com)
Date: Tue Jul 13 2004 - 14:56:22 GMT-3
> Well, that's really just another way of writing it, so that would be a tough argument with a proctor to accept that answer. There is, however, another answer that differs in more than just symantics.
Hmmm... ok...
the requirement did not say I cannot use tunnel as you mentioned. but
it sounds like it has to be different than generic GRE :( the requirement
further did not say i cannot run any other routing protocols other than
RIP between the two routers, nor did it say i cannot use any static routes..
However it did say the updates must not be sourced from 10.0.0.0/24 le 32
and the update must be sourced from 11.x.x.x
Assuming I have understood the question properly at lack of coffee..
lets try something kind of messy.. :)
From R1:
06:10:40: RIP: received v2 update from 11.11.11.2 on Ethernet0/1
06:10:40: 11.11.11.1/32 via 0.0.0.0 in 1 hops
06:10:40: 65.65.65.0/24 via 0.0.0.0 in 1 hops
06:32:25: IP: s=11.11.11.2 (Ethernet0/1), d=11.11.11.1, len 172, rcvd 0
06:32:25: UDP src=520, dst=520
R1#no deb ip pack de
IP packet debugging is off (detailed)
R1#no deb ip rip
RIP protocol debugging is off
R1#sh ip ro ri
65.0.0.0/24 is subnetted, 1 subnets
R 65.65.65.0 [120/1] via 11.11.11.2, 00:00:11
R1#trac 65.65.65.65
Type escape sequence to abort.
Tracing the route to 65.65.65.65
1 10.0.0.2 4 msec 4 msec 0 msec
2
R1#sh ip ce 65.65.65.65
65.65.65.0/24, version 36
0 packets, 0 bytes
tag information set
local tag: 29
fast tag rewrite with Tu0, point2point, tags imposed: {}
via 11.11.11.2, 0 dependencies, recursive
next hop 11.11.11.2, Tunnel0 via 11.11.11.2/32
valid adjacency
tag rewrite with Tu0, point2point, tags imposed: {}
So... I think I am meeting the requirements, no? or did i overlook something..
Just so you know, the 65.x.x.x is the route I am using to test
"R2 has RIPv2 routes that it is receiving from an external source"
I guess this is probably one of the most weird duct-tape setup evar.. :)
-J
Configurations:
R1
ip cef
cln routing
mpls traffic-en tunnels
!
in loop0
ip add 192.168.1.1 255.255.255.255
ip router isis
!
in loop100
ip add 11.11.11.1 255.255.255.0
ip router isis
!
in tun0
ip unnum loop100
tun des 192.168.2.2
tun mode mpls traffic-eng
tun mpls traffic-en path-opt 1 explic name RIPhack
!
in e0/1
ip add 10.0.0.1 255.255.255.0
ip router isis
mpls traffic-en tun
tag-switch ip
!
router isis
net 49.0000.1921.6800.1001.00
is-type level-1
metric-sty wide tran
mpls traffic router-i loop0
mpls traffic level-1
!
router rip
vers 2
no valid
passive e0/0
passive e0/1
passive loop100
net 11.0.0.0
net 10.0.0.0
neigh 11.11.11.2
no auto
!
ip route 11.11.11.2 255.255.255.255 tun0
!
ip explicit-path name RIPhack en
next-addr 192.168.2.2
!
R2:
ip cef
cln routing
mpls traffic-eng tun
!
in loop0
ip add 192.168.2.2 255.255.255.255
ip router isis
!
in loop100
ip add 11.11.11.2 255.255.255.0
ip router isis
!
in loop200
ip add 65.65.65.1 255.255.255.0
des Test subject for RIP updates
!
in tun0
ip unnum loop100
tun des 192.168.1.1
tun mod mpls traffic-en
tun mpls traffic-en path-opt 1 explic name RIPhack
!
in e0/0
ip add 10.0.0.2 255.255.255.0
ip router isis
mpls traffic-en tun
trag-switch ip
!
router isis
net 49.0000.1921.6800.2002.00
is-type level-1
metric-sty wide tran
mpls traffic-en router-i loop0
mpls traffic-en level-1
!
router rip
vers 2
no valid
passive default
net 11.0.0.0
net 65.0.0.0
net 10.0.0.0
neigh 11.11.11.1
no auto
!
ip route 11.11.11.1 255.255.255.255 tun0
!
ip explicit-path name RIPhack en
next-addr 192.168.1.1
!
-- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:54 GMT-3