[quagga-users 6732] Re: quagga 0.99.3 doesn't display interface ips with show running-conf but the ips are set by quagga

Gobbledegeek gobbledegeek at gmail.com
Tue Apr 11 09:18:56 IST 2006


If i remember right, I worked around this by compiling quagga without
netlink on fbsd last year.. my memory about it may be mistaken
though..


> ------------------------------
>
> Message: 6
> Date: Tue, 11 Apr 2006 02:28:08 +0100 (IST)
> From: Paul Jakma <paul at clubi.ie>
> Subject: [quagga-users 6731] Re: quagga 0.99.3 doesn't display
>
> To: Thomas Vogt <tv at solnet.ch>
> Cc: quagga-users at lists.quagga.net
> Message-ID: <Pine.LNX.4.64.0604110217350.5276 at sheen.jakma.org>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> On Thu, 6 Apr 2006, Thomas Vogt wrote:
>
> > Hello
> >
> > I've a strange problem with quagga 0.99.3 and FreeBSD 6.1-prerelease
> > (i386).
>
> Can you replicate with CVS? (I can't think of any relevant change,
> but just in case).
>
> > ifconfig after boot:
> > em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1546
> >        options=4b<RXCSUM,TXCSUM,VLAN_MTU,POLLING>
> >        inet6 fe80::230:48ff:fe2c:6b5d%em1 prefixlen 64 scopeid 0x2
> >        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
> >
> > But as you see the vtysh output from zebra doesn't show any ip
> > 192.168.0.1/24 for em1.
> >
> > vtysh output with show run:
> > interface em1
> > bandwidth 1000000
> > description VLAN4
> > ip ospf cost 55
> > ipv6 nd suppress-ra
> > link-detect
>
> So zebra 'lost' the IP? It used to be that zebra would completely
> delete state for an interface if the interface went down - including
> configured addresses. But I thought I had fixed that horrid
> behaviour..
>
> Did the interface go down at any stage?
>
> > Ok now i try to change the ip from 192.168.0.1/24 to 192.168.1.1/24
>
> > Now ifconfig on the system:
> > em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1546
> >        options=4b<RXCSUM,TXCSUM,VLAN_MTU,POLLING>
> >        inet6 fe80::230:48ff:fe2c:6b5d%em1 prefixlen 64 scopeid 0x2
> >        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
> >        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
>
> Yep. The zebra daemon no longer knows it configured the older
> address, so it doesn't know to delete it, nor does it let you
> specificy 'no ip ....' either.
>
> > Huge problem. If zebra doesn't show me the correct IP and I do a
> > "wr mem" it will save the wrong IPs. In the case after a reboot
> > zebra writes no IPs at all to the config if I do a wr mem.
>
> > Any idea?
>
> It's horrid horrid evil behaviour, which has been in GNU Zebra and
> Quagga for yonks, but it's /supposed/ to have been fixed. Can you try
> with CVS (I thought I'd fixed well before 0.99.3, but..) and if it
> occurs there please add:
>
> debug zebra kernel
> debug zebra event
> log file /somewhere/like/var/log/quagga/zebra.log
>
> to zebra.conf and get me the logs. Thanks!
>
> regards,
> --

>
>
> End of Quagga-users Digest, Vol 33, Issue 10
> ********************************************
>


--
Nonchalantly yours
GobbledeGeek
[Everything but Gobbledegook.. !!]



More information about the Quagga-users mailing list