Re: help with bgpd error messages

2015-05-15 Thread Marko Cupać
On Thu, 7 May 2015 13:01:49 +0200 Marko Cupać wrote: > On Wed, 6 May 2015 10:53:38 + (UTC) > Stuart Henderson wrote: > > > Can you get a packet capture of TCP port 179 during a failure? > > > > tcpdump -i -w bgp.`date +%Y%m%d-%H%M`.pcap -s1500 tcp > > and port 179 > > > > It might be be

Re: help with bgpd error messages

2015-05-07 Thread Marko Cupać
On Wed, 6 May 2015 10:53:38 + (UTC) Stuart Henderson wrote: > Can you get a packet capture of TCP port 179 during a failure? > > tcpdump -i -w bgp.`date +%Y%m%d-%H%M`.pcap -s1500 tcp and > port 179 > > It might be best to run it from a script run from cron which pkills > tcpdump and rotat

Re: help with bgpd error messages

2015-05-06 Thread Claudio Jeker
On Wed, May 06, 2015 at 03:10:44PM +0200, Henning Brauer wrote: > * Marko Cupa?? [2015-05-06 12:01]: > > I am on 5.7 release + errata patches now, and bgpd crashed again: > > > > May 6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sync error > > > I guess bug is not solved in 5.7 re

Re: help with bgpd error messages

2015-05-06 Thread Henning Brauer
* Marko Cupać [2015-05-06 12:01]: > I am on 5.7 release + errata patches now, and bgpd crashed again: > > May 6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sync error > I guess bug is not solved in 5.7 release then. Maybe 5.7 stable? Sigh. THERE IS NO BUG. As I told you before,

Re: help with bgpd error messages

2015-05-06 Thread Stuart Henderson
On 2015-05-06, Marko Cupać wrote: > On Wed, 29 Apr 2015 11:02:09 +0200 > Marko Cupać wrote: > >> On Tue, 28 Apr 2015 15:11:21 +0200 >> Claudio Jeker wrote: >> >> > The "fatal in RDE: peer_up: bad state" bug is fixed in 5.7 IIRC. Not >> > sure if it was backported to 5.6. As a workaround you can

Re: help with bgpd error messages

2015-05-06 Thread Marko Cupać
On Wed, 29 Apr 2015 11:02:09 +0200 Marko Cupać wrote: > On Tue, 28 Apr 2015 15:11:21 +0200 > Claudio Jeker wrote: > > > The "fatal in RDE: peer_up: bad state" bug is fixed in 5.7 IIRC. Not > > sure if it was backported to 5.6. As a workaround you can disable > > the graceful restart capability

Re: help with bgpd error messages

2015-04-29 Thread Marko Cupać
On Tue, 28 Apr 2015 15:11:21 +0200 Claudio Jeker wrote: > The "fatal in RDE: peer_up: bad state" bug is fixed in 5.7 IIRC. Not > sure if it was backported to 5.6. As a workaround you can disable the > graceful restart capability to not trigger that code path. I was intending to upgrade on Friday

Re: help with bgpd error messages

2015-04-28 Thread Claudio Jeker
On Tue, Apr 28, 2015 at 11:28:31AM +0200, Marko Cupa?? wrote: > Hi, > > I have a pair of OpenBSD 5.6 firewalls running releases happily for > years (I think since 5.1). They are in CARP failover mode, running bgp > sessions with upstrem providers and filtering traffic. > > Few days ago I had Inte

help with bgpd error messages

2015-04-28 Thread Marko Cupać
Hi, I have a pair of OpenBSD 5.6 firewalls running releases happily for years (I think since 5.1). They are in CARP failover mode, running bgp sessions with upstrem providers and filtering traffic. Few days ago I had Internet outage (first in years), which appear to happen as a result of bgpd cra