bird vs zebra
Ramon Martinez Palomares
rampa at encomix.ad
Thu Sep 16 17:49:54 CEST 2004
show ospf nei
MyOSPF:
Router ID Pri State DTime Router IP
Interface
10.72.255.253 1 full/ptp 00:31 172.16.72.153 tun0
194.143.194.245 1 full/ptp 00:34 172.16.72.157 tun1
bird> show inter
lo up (index=1)
MultiAccess AdminUp LinkUp Loopback Ignored MTU=16436
127.0.0.1/8 (Primary, broadcast 127.255.255.255, scope host)
eth0 up (index=3)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
10.72.1.97/27 (Primary, broadcast 10.72.1.127, scope site)
tun0 up (index=4)
PtP Multicast AdminUp LinkUp MTU=1500
172.16.72.154/32 (Primary, broadcast 172.16.72.153, opposite
172.16.72.153, scope site, unnumbered)
tun1 up (index=5)
PtP Multicast AdminUp LinkUp MTU=1500
172.16.72.158/32 (Primary, broadcast 172.16.72.157, opposite
172.16.72.157, scope site, unnumbered)
show ospf inter
MyOSPF:
Interface "tun0":
Type: point-to-point
Area: 0.0.0.0 (0)
State: point-to-point
Priority: 1
Cost: 10
Hello timer: 10
Wait timer: 40
Dead timer: 40
Retransmit timer: 5
Interface "tun1":
Type: point-to-point
Area: 0.0.0.0 (0)
State: point-to-point
Priority: 1
Cost: 10
Hello timer: 10
Wait timer: 40
Dead timer: 40
Retransmit timer: 5
bird> show ospf
MyOSPF:
RFC1583 compatibility: disabled
RT scheduler tick: 2
Number of areas: 1
Number of LSAs in DB: 17
Area: 0.0.0.0 (0) [BACKBONE]
Stub: No
Transit: No
Number of interfaces: 2
Number of neighbors: 2
Number of adjacent neighbors: 2
Area networks:
10.72.1.96/27 Advertise
172.16.72.154/32 Advertise Active
172.16.72.158/32 Advertise
show route count
12 of 12 routes for 12 networks
bird>
on the zebra side.
sho ip ospf ne
Neighbor ID Pri State Dead Time Address
Interface RXmtL RqstL DBsmL
194.143.194.245 1 Full/DROther 00:00:39 172.16.79.254
tun0:172.16.79.253 0 0 0
10.72.0.129 1 Full/DROther 00:00:39 172.16.72.10
tun1:172.16.72.9 0 0 0
10.72.0.161 1 Full/DROther 00:00:34 172.16.72.18
tun2:172.16.72.17 0 0 0
10.72.2.162 1 Full/DROther 00:00:34 172.16.72.34
tun3:172.16.72.33 0 0 0
10.72.3.65 1 Full/DROther 00:00:33 172.16.72.66
tun7:172.16.72.65 0 0 0
10.72.0.33 1 Full/DROther 00:00:30 172.16.72.82
tun9:172.16.72.81 0 0 0
10.72.3.97 1 Full/DROther 00:00:30 172.16.72.90
tun10:172.16.72.89 0 0 0
10.72.2.65 1 Full/DROther 00:00:32 172.16.72.138
tun13:172.16.72.137 0 0 0
10.72.1.193 1 Full/DROther 00:00:30 172.16.72.146
tun14:172.16.72.145 2 0 0
172.16.72.158 1 Full/DROther 00:00:33 172.16.72.154
tun15:172.16.72.153 0 0 0
(the bird is the last one)
there is not show ip ospf lsa (zebra 0.94 in show version)
i cannot see the route in sh ip route but in sh ip ospf database, i can
see the route like E2
10.72.1.96 172.16.72.158 1095 0x80000001 0x4e17 E2 10.72.1.96/27
[0x0]
El 16/09/2004, a las 17:27, Ondrej Filip escribió:
> On Thu, 16 Sep 2004, Ramon Martinez Palomares wrote:
>
>> still having any problems with zebra and OSPF.
>>
>> is anybody using bird to intercommunicate with zebra in a
>> pointopoint link?
>>
>> bird is connected to the zebras but i cant see any route coming from
>> bird to zebra.
>>
>> (sorry if this is a FAQ but i am new to the list and i havent seen an
>> archive)
>
> Zebra should communicate with BIRD over PTP. (The only known problem
> is with virtual link over unnumberd, but that is problem of OSPF
> design.)
>
> So there could be some bug in routing table calculation (probably next
> hop) of zebra of a bug in LSA export in BIRD. Can you give me more
> information?
>
> BIRD: show ospf neighbors, show interfaces, show ospf interfaces, show
> ospf, show route count
>
> Zebra: show ip ospf neighbors, show ip ospf lsa <routerid>
>
> (Use both routerids: of BIRD and routerid of Zebra)
>
> I hope, I can help with such information.
>
> Feela
>
>
>>
>>
>>
>> El 15/09/2004, a las 21:07, Ramon Martinez Palomares escribió:
>>
>>> Hello all!
>>> while trying to comunicate zebra and bird in a tunnel (pointopoint)
>>> conection, all the time bird keeps saying that:
>>> Sep 15 21:06:20 bell bird: Bad OSPF hello packet from 172.16.72.157
>>> received: bad netma
>>> sk 0.0.0.0.
>>> after looking at hello.c i have commented the return after the log
>>> message. and bird is working really fine.
>>> What this error really means? is it a bird or a zebra issue?
>>> -ramon-
More information about the Bird-users
mailing list