From: Kenneth Wygand (KWygand@customonline.com)
Date: Mon Jul 12 2004 - 14:53:05 GMT-3
Andy,
If you can, try labbing this up and "debug ip rip".
Ken
--------------------------
Sent from my BlackBerry Wireless Handheld
-----Original Message-----
From: Edwards, Andrew M <andrew.m.edwards@boeing.com>
To: Kenneth Wygand <KWygand@customonline.com>
Sent: Mon Jul 12 12:45:15 2004
Subject: RE: Quiz Question of the Day 20040712
How about...
R1:
Int <link ID>
Ip address 10.0.0.1 255.255.255.0
Ip address 11.0.0.1 255.255.255.0 secondary
Router rip
No auto
Version 2
Passive default
No passive <link ID>
Neighbor 11.0.0.2
Network 11.0.0.0
R2:
Int <link ID>
Ip address 10.0.0.2 255.255.255.0
Ip address 11.0.0.2 255.255.255.0 secondary
Router rip
No auto
Version 2
Passive default
No pass <link ID>
Neighbor 11.0.0.1
Network 11.0.0.0
andy
----- Original message -----
From: "Kenneth Wygand" <KWygand@customonline.com>
To: ccielab@groupstudy.com
Date: Mon, 12 Jul 2004 11:04:20 -0400
Subject: Quiz Question of the Day 20040712
?
Here's your Monday Morning brain cruncher!
R1----10.0.0.x/24----R2
Link on R1 connecting to R2 is 10.0.0.1/24
Link on R2 connecting to R1 is 10.0.0.2/24
R2 has RIPv2 routes that it is receiving from an external source. You do
not have any information about what networks or subnets R2 is receiving.
R1 needs to receive these routes from R2.
RIP updates are NOT allowed to be sourced from any address in the
10.0.0.0/24 range.
RIP routes may only be sourced form the 11.0.0.0/24 network, which is
not currently defined anywhere.
You CANNOT change the primary IP address on the interfaces between R1
and R2.
Your configuration CANNOT include the following:
R1:
interface tunnel(x)
ip address 11.0.0.(x) 255.255.255.0
tunnel source 10.0.0.1
tunnel destination 10.0.0.2
How can this be accomplished?
Good Luck!! :)
Ken
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:53 GMT-3