On Mon, Mar 14, 2011 at 05:54:58PM -0500, Mark Felder wrote:
> On Mon, 14 Mar 2011 14:46:28 -0500, Stuart Henderson
> wrote:
>
> >Make sure your nexthops are valid: bgpctl sh nex
>
> I worked with my coworker on it this afternoon and he discovered the
> nexthops issue. We have resolved the probl
On 2011-03-14, Mark Felder wrote:
> On Mon, 14 Mar 2011 14:46:28 -0500, Stuart Henderson
> wrote:
>
>> Make sure your nexthops are valid: bgpctl sh nex
>
> I worked with my coworker on it this afternoon and he discovered the
> nexthops issue. We have resolved the problem for now.
>
> Out next
On Mon, 14 Mar 2011 14:46:28 -0500, Stuart Henderson
wrote:
Make sure your nexthops are valid: bgpctl sh nex
I worked with my coworker on it this afternoon and he discovered the
nexthops issue. We have resolved the problem for now.
Out next step is to figure out how to make OpenBGPD be
Make sure your nexthops are valid: bgpctl sh nex
Also check your logs (or run bgpd -vd and check the console display).
On 2011-03-12, Mark Felder wrote:
> Hi all,
>
> I work at an ISP and we are very interested in running OpenBGPD on the
> edges talking to our transport routers. They won't be
On Mon, 14 Mar 2011 02:56:09 -0500, Gregory Edigarov
wrote:
Not really sure (claudio@ will certainly correct me), but I know that
OpenBGPD in FreeBSD's ports is never fresh enough. And there was
changes afecting the behaviour of OpenBSD's version.
So I think you should just install OpenBSD
Hi Mark,
Not really sure (claudio@ will certainly correct me), but I know that
OpenBGPD in FreeBSD's ports is never fresh enough. And there was
changes afecting the behaviour of OpenBSD's version.
So I think you should just install OpenBSD instead of Freebsd and try
again.
On Sat, 12 Mar 201
6 matches
Mail list logo
