* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2005-11-28 01:41]:
>
> your only workaround is to not send any capability it does not grok.
> this is guesswork. you might want to try to not announce v4 unicast
> capabilities...
>
>
> I was wondering exactly how this was specified in the bgpd.conf file?
your only workaround is to not send any capability it does not grok.
this is guesswork. you might want to try to not announce v4 unicast
capabilities...
I was wondering exactly how this was specified in the bgpd.conf file?
Since I was trying to do the same thing to connect to he.net and try out
On Mon, Sep 19, 2005 at 10:30:29AM +0200, Henning Brauer wrote:
>
> the peer is broken and needs to be fixed.
>
> your only workaround is to not send any capability it does not grok.
> this is guesswork. you might want to try to not announce v4 unicast
> capabilities.
that did it.
---
4801a
* jared r r spiegel <[EMAIL PROTECTED]> [2005-09-18 06:50]:
> tried it a while ago (~3.6?) with openbsd bgpd and it
> would bomb on me complaining of unsupported capability.
> Sep 17 23:08:02 4801a bgpd[21303]: neighbor 2001:470:1f01:::122 (he.net):
> re
> ceived notification: error in OP
4 matches
Mail list logo