Claudio and crew,
Unsure if this is a bug or intended. I was testing BGP triggered
blackholes, one of the routers that will perform the blackhole has
this rule in its bgpd.conf:
match from group GROUP-IBGP community 1234:666 set { localpref 200
origin igp nexthop blackhole }
Looking exclusively
Henning Brauer wrote:
>* Pete Vickers [2012-01-06 11:38]:
>> Just a quick question to see if anyone's working on implementing the above on
>> OpenBSD, and in particular it's integration with OpenBGPD/OpenOSPF ? Note
>> that
>> this is not a 'please can I have this feature for free' or suchlike,
Claudio and crew,
When you enable OSPF-TE (http://tools.ietf.org/html/rfc3630) on a
Cisco router, OpenOSPFD crashes with "Invalid LSA type". Assuming you
have a functional setup, adding this (the last line) will recreate:
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area
> From: Claudio Jeker
>
> Thanks for the log and tcpdumps. It seems you're the first person to try
> opaque LSA against ospfd. Can you give the following diff a spin?
> I think this will solve the problems.
Claudio,
Thanks for the patch. I've compiled this in a lab and indeed things
are indeed s
I put my first OpenBGPD device into production tonight. Everything
working well, one issue I came across was that I could not adjust the
'announce' setting on a neighbor on the fly with a soft refresh. I had
it 'announce self' and changed it to 'announce all', I could only get
it to take by doing a
On Thu, May 12, 2011 at 2:51 AM, wrote:
> I put my first OpenBGPD device into production tonight. Everything
> working well, one issue I came across was that I could not adjust the
> 'announce' setting on a neighbor on the fly with a soft refresh. I had
> it 'announce self' and changed it to 'anno
Had a strange issue overnight. In short I had two OpenBSD boxes acting
as routers denial of service my network with OSPFv3 multicast packets.
The setup is as follows:
Two OpenBSD 4.9 amd64 boxes running ospfd and ospf6d. Each box has two
NICs, each of which is on a separate subnet. Both of these
On Mon, May 23, 2011 at 9:59 AM, Chris Wopat wrote:
> Had a strange issue overnight. In short I had two OpenBSD boxes acting
> as routers denial of service my network with OSPFv3 multicast packets.
Also I've attached some logs below. They continue on like this until I
unplugged
On Mon, May 23, 2011 at 9:59 AM, Chris Wopat wrote:
> Had a strange issue overnight. In short I had two OpenBSD boxes acting
> as routers denial of service my network with OSPFv3 multicast packets.
This happened again today. This time it was on a third OpenBSD box.
The last time it happe
On Tue, May 24, 2011 at 3:11 PM, Claudio Jeker wrote:
>
> Are you running 4.9 or -current? Up until the code generating the LSA
> update packets (and sending them) did not change between 4.8 and 4.9.
> In -current this code got rewritten to fix a issue. IIRC the problem was
> that an LS Update got
Stuart Henderson wrote:
> If this is related to sending huge LS updates, I don't think many
> people currently running ospfd would hit it (you'd need to be announcing
> quite a lot of networks into ospf), so you probably wouldn't have read
> about it on the lists.
I was able to do some sniffing an
I was able to lab it up and confirm and recreate the bug. I realize
that this subject has been beaten to death now but I wanted to chime
in saying:
* Yes, it's definitely fixed in -current. This isn't new information
but good info for my organization.
* There's a simple way to reliable reproduce i
Is there a known issue with OpenBGPD ignoring MED during its path
selection? Note that the first item listed is best below and it has a
MED of 12. The others are 10 which should be preferred over 12. I'm
guessing that it's then going to a later stage of path selection where
it's choosing hte lowest
On Mon, Jun 13, 2011 at 10:39 AM, Chris Wopat wrote:
> Is there a known issue with OpenBGPD ignoring MED during its path
> selection? Note that the first item listed is best below and it has a
> MED of 12. The others are 10 which should be preferred over 12. I'm
> guessing that i
14 matches
Mail list logo
