On Tue, 22 Jun 2004, RATM wrote:
Hi all,
Hello!
I apologize if this topic has already been discussed on the mailing list, but I couldn't find a message archive to check it out. And, I apoligize for my poor English.
My problem is that the BIRD RIPv2 daemon doesn't accept a worse metric coming from the router which is the nexthop for that entry. I'll paste some sniffed packet to give the whole idea. This network is very simple - 2 routers (200.0.0.1 and 200.0.0.2) with 4 interfaces each:
Frame 1 (106 bytes on wire, 106 bytes captured) Internet Protocol, Src Addr: 200.0.0.1 Dst Addr: 224.0.0.9 Routing Information Protocol IP Address: 200.0.6.0, Metric: 2 IP Address: 200.0.5.0, Metric: 2 IP Address: 200.0.4.0, Metric: 2
/* The metric is 2. */
Frame 3 (106 bytes on wire, 106 bytes captured) Arrival Time: Jun 16, 2004 18:19:14.496397000 Internet Protocol, Src Addr: 200.0.0.1 Dst Addr: 224.0.0.9 Routing Information Protocol IP Address: 200.0.6.0, Metric: 5 IP Address: 200.0.5.0, Metric: 5 IP Address: 200.0.4.0, Metric: 5
/* Here I changed the default metric to 5. And now 200.0.0.1 begins announcing its directly connected networks with a metric of 5; anyway, 200.0.0.2 (whose hostname is r1) doesn't change the metric in its route table as you can see below:
r1:~# birdc BIRD 1.0.6 ready. bird> show route 127.0.0.0/8 dev lo [direct1 18:12] (240) 200.0.0.0/24 dev eth0 [direct1 18:12] (240) 200.0.1.0/24 dev eth1 [direct1 18:12] (240) 200.0.2.0/24 dev eth2 [direct1 18:12] (240) 200.0.3.0/24 dev eth3 [direct1 18:12] (240) 200.0.4.0/24 via 200.0.0.1 on eth0 [MyRIP 18:25] (120/2) <---- 200.0.5.0/24 via 200.0.0.1 on eth0 [MyRIP 18:25] (120/2) <---- 200.0.6.0/24 via 200.0.0.1 on eth0 [MyRIP 18:25] (120/2) <----
I left the arrival time information in the second packet to let you compare it with the time displayed in the show route output. Any ideas?
Plase can you enable 'debug MyRIP all' on both routers and send it to me? Feela