Re: BGP - IP Blackhole

On 14 avril 2014 17:57:53 CEST, Tristan PILAT wrote: >match from any community 64514:888 set nexthop blackhole > Hi, Make sure you dont accept from any but eg from group customers, make sure the address *does* belong to your customers space (to avoid a customer installing a blackhole route on

Re: Keeping a carp backup connected to the internet

Ted Bullock a écrit : >CARP(ish) Question: > >I have a /30 transit network from my ISP, where there obviously isn't >room for both routers in the carp setup to have a dedicated IP address >in addition to the IP assigned to the carp interface. > >If it matters, I've assigned both routers private

Re: OpenBGP Issues. :-(

Alex Mathiasen a écrit : >Dear recipients, > >I have been using OpenBGP for a while with OpenBSD - And I am very >satisfied >with the performance and amazed by the ease of configuration. > >My BGPD is configured against a Danish ISP called TDC - And we were >previously >configured to receive a fu

Re: CARP compatibility between 5.1 and 5.2

R0me0 *** a écrit : >Hello misc, > >I've a OpenBSD 5.1 in production and I will put another OpenBSD 5.2 and >then configure CARP. >will I have some compatibility issue ? > >Thanks in advanced Hi I have such à setup running surtout issue. Cheers Laurent

Re: "No route to host"

"Loïc BLOT" a écrit : >Hello to OpenBSD users, > >i have a little problem, i think it's linked with PF, but i have no >proofs. System is OpenBSD 5.1 but OpenBSD 5.2 get the same things (with >different card, 5.1 uses bnx and 5.2 use em) >I have a router with squid proxy, named and isc-dhcpd. The

Re: OpenBGPd / Juniper 'bug' / BGP session flapping

Claudio Jeker a écrit : >I would prefer something like this. Since then we ensure that we do not >forward crap (as in we regard the RFC and send nothing with reserved >bits >set). AFAIK there is nothing out there that started to use the reserved >bits so I'm curious how that happend again. > >Onl