OpenBGPD selecting wrong nexthop over openvpn tunnel

2007-11-21 Thread Casey Ransom
Hi all, I've been doing some testing with OpenBGPD to possibly replace quagga/ zebra on some of our host based routers. One problem I have found is that when it is connecting to a peer over a tun device (we use openvpn), the bgp daemon gets the proper nexthop information but when it is a

OpenBGPD not inserting correct nexthop over openvpn tunnel

2007-11-21 Thread Casey Ransom
Hi all, I'm having some issues with OpenBGPD across a point-to-point openvpn link. Some quick background: we have a number of quagga based FreeBSD machines doing BGP sessions for our redundancy and due to some recent backstabbing by quagga, want to test out openbgpd. It worked well in a

Re: OpenBGPD selecting wrong nexthop over openvpn tunnel

2007-11-21 Thread Casey Ransom
Also pardon the double post that will soon follow. I thought my mail client had fed this mail to a black hole so I sent another. -casey On Nov 21, 2007, at 9:51 AM, Casey Ransom wrote: Hi all, I've been doing some testing with OpenBGPD to possibly replace quagga/zebra on some o

Re: OpenBGPD selecting wrong nexthop over openvpn tunnel

2007-11-21 Thread Casey Ransom
On Nov 21, 2007, at 3:30 PM, Henning Brauer wrote: what does "route -n get 10.8.1.2" show? I suspect there's a bug with tun not setting the ifindexin the routing message (*sigh*, another one) gw0# route -n get 10.8.1.2 route to: 10.8.1.2 destination: 10.8.1.2 interface: tun0 flags:

Re: OpenBGPD selecting wrong nexthop over openvpn tunnel

2007-11-22 Thread Casey Ransom
On Nov 22, 2007, at 2:42 AM, Henning Brauer wrote: bgpctl show nexthop probably does not list tun0 for 10.8.1.2? in the logs, you'll see a "nexthop 10.8.1.2 now valid" message, what does it say exactly? I do have tun0 listed in the nexthop: gw0# bgpctl sh nexthop Nexthop State 10.

as-override equivalent for OpenBGPD

2010-04-06 Thread Casey Ransom
Hi All, I'm currently implementing some multi-site redundancy across data centers and I'm planning on doing it with a single AS. I can do it on my other JunOS routers via as-override (allows routes originating from an AS to be accepted by a router residing in the same AS), which is not the defaul