Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Dec 1999 16:23:13 -0800 (PST)
From:      "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
To:        joe@pavilion.net (Josef Karthauser)
Cc:        joe@FreeBSD.org (Josef Karthauser), cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: ports/net/zebra Makefile ports/net/zebra/files md5
Message-ID:  <199912250023.QAA59496@gndrsh.dnsmgr.net>
In-Reply-To: <19991223221358.A3026@florence.pavilion.net> from Josef Karthauser at "Dec 23, 1999 10:13:58 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
...
> I've also got a secondary problem with ospfd which I don't understand.
> I hoped that 83a fixed it, but alas no!
> 
> The ospfd core dumps after a few seconds of running:

To shed some light on this, I find this in the TODO file:
                           Zebra TODO list
                          (random in order)

zebra:

o *BGP routing socket support.
o IPv6 router advertisement code finish.
o Pointopoint address configuration.
o Multiple (alias) address configuration for the interface when kernel
  support it.


So it seems as if they have not even started to address the issue of
aliased addresses on interfaces, and the code is probably not handling
it very gracefully :-(.

This won't be a big problem for us, but it is a problem non the less,
after I get past the ``static route needed for startup'' bug and get
some more testing done I'll take a look at this one...

(0.83a did not fix the ospfd startup bug when you have no routes, but
it changed some things, like at least it now recognizes the route to
the attached network when you do a show ip ospf route, which is one
step better than it was before :-().

> 
> Core was generated by `ospfd'.
> Program terminated with signal 10, Bus error.
> Reading symbols from /usr/lib/libcrypt.so.2...done.
> Reading symbols from /usr/lib/libc.so.3...done.
> Reading symbols from /usr/libexec/ld-elf.so.1...done.
> #0  0x8054742 in ospf_external_lsa (p=0x80a87c0, type=1 '\001', metric=1, 
>     tag=0, forward={s_addr = 0}, old=0x80a6440) at ospf_lsa.c:771
> 771          lsah->id = old->data->id;
> (gdb) bt
> #0  0x8054742 in ospf_external_lsa (p=0x80a87c0, type=1 '\001', metric=1, 
>     tag=0, forward={s_addr = 0}, old=0x80a6440) at ospf_lsa.c:771
> #1  0x805de17 in ospf_asbr_check_lsas () at ospf_asbr.c:327
> #2  0x805df41 in ospf_asbr_check () at ospf_asbr.c:398
> #3  0x8059227 in ospf_spf_calculate_timer (t=0xbfbfdc3c) at ospf_spf.c:972
> #4  0x80653b4 in thread_call (thread=0xbfbfdc3c) at thread.c:697
> #5  0x8049899 in main (argc=1, argv=0xbfbfdc8c) at ospf_main.c:248
> #6  0x8049585 in _start ()
> 
> It started happening as I increased the number of IP addresses that was
> bound to the fxp1 interface.  I asked the zebra list, but no-one replied,
> and I've not found the time to look deeper yet.  I've backed off and added
> static routes to the router upstream until this gets fixed.
> 
> Joe
> -- 
> Josef Karthauser	FreeBSD: Take the red pill and we'll show you just how
> Technical Manager	deep the rabbit hole goes. (http://www.uk.freebsd.org)
> Pavilion Internet plc.  [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk]
> 


-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)               rgrimes@gndrsh.dnsmgr.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912250023.QAA59496>