On 2009-05-24, Justin Credible wrote:
> On Sat, May 23, 2009 at 6:35 PM, Justin Credible
> *>199.185.136.0/2364.x.x.x 200 1 3549 812 812 812 812 3602
> 22512 i
> * 199.185.136.0/23212.x.x.x 100 500 3356 6453 812 3602 22512 i
> # route -n show | grep 199.185.136
> 19
On Sun, May 24, 2009 at 12:22 PM, Claudio Jeker
wrote:
> On Sun, May 24, 2009 at 11:54:37AM -0600, Justin Credible wrote:
>
>
>
>> I figured this one out. This particular problem was caused because i had set:
>>
>> nexthop qualify via bgp
>>
>
> Why did you set this? Just for fun or was there a r
On Sun, May 24, 2009 at 11:54:37AM -0600, Justin Credible wrote:
> I figured this one out. This particular problem was caused because i had set:
>
> nexthop qualify via bgp
>
Why did you set this? Just for fun or was there a reason behind it.
> I don't know why that setting in particular set
On Sat, May 23, 2009 at 8:55 PM, Justin Credible
wrote:
> On Sat, May 23, 2009 at 6:35 PM, Justin Credible
> wrote:
>>
>> Hi there,
>>
>> I am running OpenBSD 4.4 with OpenBGPD and multiple peers.
>>
>> For some reason the device is selecting Level3 as the default route for
absolutely everything
On Sat, May 23, 2009 at 6:35 PM, Justin Credible
wrote:
>
> Hi there,
>
> I am running OpenBSD 4.4 with OpenBGPD and multiple peers.
>
> For some reason the device is selecting Level3 as the default route for
absolutely everything which is not statically set.
>
> On Level3 config i have set:
>
> s
Hi there,
I am running OpenBSD 4.4 with OpenBGPD and multiple peers.
For some reason the device is selecting Level3 as the default route for
absolutely everything which is not statically set.
On Level3 config i have set:
set localpref 100
softreconfig in yes
max-prefix 100 restart 300
For the
6 matches
Mail list logo
