ospf interoperability problems with cisco and other errors

Csaba Szép csszep at gmail.com
Sat Oct 3 22:14:26 CEST 2009


Hi!

thx for the quick answer.

With tap up:

bird> show interfaces
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=2)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        10.1.16.196/20 (Primary, broadcast 10.1.31.255, scope site)
vmnet1 up (index=3)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        192.168.253.1/24 (Primary, broadcast 192.168.253.255, scope site)
vmnet2 up (index=4)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        192.168.252.1/24 (Primary, broadcast 192.168.252.255, scope site)
vmnet8 up (index=5)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        192.168.254.1/24 (Primary, broadcast 192.168.254.255, scope site)
dummy0 DOWN (index=6)
        MultiAccess Broadcast Multicast AdminUp LinkDown MTU=1500
        1.2.3.4/24 (Primary, broadcast 1.2.3.255, scope univ)
tap1 up (index=22)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        1.0.0.2/24 (Primary, broadcast 1.0.0.255, scope univ)
        192.0.2.1/32 (Unselected, broadcast 192.0.2.1, opposite
192.0.2.1, scope univ, unnumbered)
        192.0.2.2/32 (Unselected, broadcast 192.0.2.2, opposite
192.0.2.2, scope univ, unnumbered)
tap2 up (index=23)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2.0.0.2/24 (Primary, broadcast 2.0.0.255, scope univ)

bird> show ospf state ospf1

area 0.0.0.0

        router 1.0.0.2
                network 1.0.0.0/24 metric 10
                external 192.0.2.1/32 metric2 10000
                external 192.0.2.2/32 metric2 10000

        router 3.0.0.1
                network 1.0.0.0/24 metric 1
                external 0.0.0.0/0 metric2 1 tag 00000001

        network 1.0.0.0/24
                dr 3.0.0.1
                router 3.0.0.1
                router 1.0.0.2

without secondary adresses (ifconfig tap1:0 down, ifconfig tap1:1 down):


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=2)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        10.1.16.196/20 (Primary, broadcast 10.1.31.255, scope site)
vmnet1 up (index=3)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        192.168.253.1/24 (Primary, broadcast 192.168.253.255, scope site)
vmnet2 up (index=4)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        192.168.252.1/24 (Primary, broadcast 192.168.252.255, scope site)
vmnet8 up (index=5)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        192.168.254.1/24 (Primary, broadcast 192.168.254.255, scope site)
dummy0 DOWN (index=6)
        MultiAccess Broadcast Multicast AdminUp LinkDown MTU=1500
        1.2.3.4/24 (Primary, broadcast 1.2.3.255, scope univ)
tap1 up (index=22)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        1.0.0.2/24 (Primary, broadcast 1.0.0.255, scope univ)
tap2 up (index=23)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2.0.0.2/24 (Primary, broadcast 2.0.0.255, scope univ)

bird> show ospf state ospf1

area 0.0.0.0

        router 1.0.0.2
                network 1.0.0.0/24 metric 10

        router 3.0.0.1
                network 1.0.0.0/24 metric 1
                external 0.0.0.0/0 metric2 1 tag 00000001

        network 1.0.0.0/24
                dr 3.0.0.1
                router 3.0.0.1
                router 1.0.0.2

And the cisco:

     1.0.0.0/24 is subnetted, 1 subnets
C       1.0.0.0 is directly connected, FastEthernet0/0
     3.0.0.0/32 is subnetted, 1 subnets
C       3.0.0.1 is directly connected, Loopback0
O E2 192.0.2.0/24 [110/10000] via 1.0.0.2, 00:07:57, FastEthernet0/0
S*   0.0.0.0/0 is directly connected, Loopback0


crazy?

thx again


2009/10/3 Ondrej Zajicek <santiago at crfreenet.org>:
> On Sat, Oct 03, 2009 at 07:39:55PM +0200, Csaba Szép wrote:
>> Hi All!
>
> Hello
>
>> First, the HELLO packet ignored with "Bad OSPF hello packet from
>> 1.0.0.1 received: options mismatch (0x12)." if i use the cisco default
>> ospf configuration.
>>
>> With "ip ospf lls disable" option everything is ok.
>
> This is probably inappropriate options handling in BIRD, we will fix
> it.
>
>> Second, i advertise some alias IP from the pc to the cisco router, but
>> if i remove the alias address from the interface some OSPF routes
>> still present in the cisco router.
>
> So i suppose the problem is just the route 192.0.2.0/24 ?
> I am not sure where it comes from. Could you send me output of command
> 'show interfaces' and  'show ospf state' on BIRD?
>
> --
> Elen sila lumenn' omentielvo
>
> Ondrej 'SanTiago' Zajicek (email: santiago at crfreenet.org)
> OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
> "To err is human -- to blame it on a computer is even more so."
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkrHmYsACgkQw1GB2RHercPcRwCdEKZ5qvQMPsv9AfkEaK92hMmE
> E/sAn0NC0cYKnJPpod7tggz0v0NrrAMp
> =n3gv
> -----END PGP SIGNATURE-----
>
>



More information about the Bird-users mailing list