Hi every body.
Let say we have a network
I intentionally used two different subnet on so on both routers.
ip address 10.10.11.1/24
ip address 184.108.40.206/24
Ping on R1 to R2's0 will be successful.
Let say we enabled ripv2 on both routers. Will R2 be able to exchange routes on s0 with R1 as so int on both are in different subnet?
I am just wondering because ospf or eigrp won't exchange routes in the above case. But how about ripv2?
correct, doesnt that remind you when you studied for ccie. it reminds me on the lab days. How to disable the route, turn off the neighbor-route.
That's the 'peer neighbor-route' knob that is enabled by default on PPP interfaces.
I don't think it's the book, rather this is the way Sarah learns ie. by reading the core stuff and then coming up with unusual scenarios to make sure she fully understands it.
And it keeps us all on out toes as well to be honest :-)
To add, to that if you advertise other networks, you will observe what ediortiz said:
Before the command no validate-update-source:
*Aug 20 00:19:42.178: RIP: ignored v2 update from bad source 10.10.10.1 on Serial
IP: received v2 update from 10.10.10.1 on Serial0/0/0:0
And then the route gets installed, so yes it will work
actually the routing table will show it as directly connected anyway:
Gateway of last resort is not set
220.127.116.11/30 is subnetted, 1 subnets
C 18.104.22.168 is directly connected, FastEthernet0/1
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.10.11.1/32 is directly connected, Serial0/0/0:0
C 10.10.10.0/24 is directly connected, Serial0/0/0:0
So rip is not even in use in the ppp scenario between r1 and r2
It's not a bad design scenario when you are forced to preserve IP addressing space and rely on 'ip unnumbered' on WAN interfaces.
With RIP you can actually accept routes without verifying the source IP but you have to turn off 'validate-update-source' which is enabled by default
No they can't exchange routes. Even though they do not form neighborships in the way EIGRP/OSPF do they still reject the routing update with the following message -
RIP: ignored V2 update from bad source - 10.10.10.1 on s0/0
the above was seen on R2 from your example.