-------- Original-Nachricht -------- > Datum: Mon, 2 Jan 2012 12:43:45 +0100 > Von: Henning Brauer <[email protected]> > An: [email protected] > Betreff: Re: openbgpd: change req not in table
> * Donald Reichert <[email protected]> [2012-01-02 08:04]: > > Watching the log file, I see sometimes lines like this: > > > > Jan 2 07:51:19 rt-beta bgpd[4344]: change req for 38.21.12.48/25: not > in table > > > > I didn't find any clue what happens here; I found the part of source > code, where 'change req for' can be seen, but I don't really understand what > it's telling me. > > bgpd saw a route change message on the routing socket for said > destination. which means something changed said kernel route. > bgpd then figures out that it doesn't have such a route in its copy of > the kernel routing table. > now of course the question is why. could be a bug somewhere, could be > rdaomains related if you use them (speculation!), could be a missed > message on the routing socket. or sth else. Thank you very much for your fast reply, Henning. The machine runs learning BGP, but set with net.inet.ip.forwarding=0 because I'm still figuring out how to replace the Ciscos doing the job at the moment. Maybe this could be the reason? There's ospfd running in parallel learning internal routes. Best, Donald -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
