IPv6 BGP debugging
andreev.peter at gmail.com
Thu Apr 10 10:33:00 CEST 2014
2014-04-10 12:24 GMT+04:00 Ondrej Zajicek <santiago at crfreenet.org>:
> On Wed, Apr 09, 2014 at 01:36:31PM +0400, Peter Andreev wrote:
> > Hi everybody,
> > I'm trying to set up bird 1.4.2 on FreeBSD 9.1 and stuck on the
> > PTTlg BGP master start 13:10:24 Connect Socket:
> > argument
> > MLPA1 BGP master start 13:10:24 Connect Socket:
> > Operation timed out
> > MLPA2 BGP master start 13:10:24 Connect Socket:
> > argument
> > All these BGP protocols are inherited from one template. The only
> > difference is that those are established, use another source address
> > is configured on virtual interface.
> > However my question is how to find out what's going on and how to detect
> > problem? Setting "log syslog all;" is not very helpful - it only fills
> > log file with a lot of "bird6: KRT: Error sending route 2c0f:fb50::/0 to
> > kernel: No such process" messages.
> Socket errors are usually errors reported by OS kernel related to TCP
> (for BGP) socket, so there is not much to debug in BIRD. You could add
> 'debug all' to that BGP protocols, but i would guess these errors
> are just reactions to connect() syscall.
You're right, there is no much info.
> 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)
> -----END PGP SIGNATURE-----
Is there any problem Exterminatus cannot solve? I have not found one yet.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bird-users