Hello Remi,
Thanks for that, I saw a presentation from Paulo Lucende about
this. for us as an eyeball ISP, my request is slightly simpler,
because I can Advertise my routes to all peers / transit
so my downloads will happen, to sort the upload I need to
learn and install the routes. (content
OpenBGPd Feature Request / Question if the Feature Request
is something the community would use ?
Background,
Ideally we would run full tables so that we have visibility
on reachibility of a prefix via a transit provider,
Problem: routers that support this functionality Reliably
are quite
On Sat, Sep 22, 2018 at 08:22:52AM +0100, Tom Smyth wrote:
> OpenBGPd Feature Request / Question if the Feature Request
> is something the community would use ?
>
> Background,
> Ideally we would run full tables so that we have visibility
> on reachibility of a prefix via a transit provider,
>
On Fri, Sep 21, 2018 at 06:36:54PM -0700, Geoff Hill wrote:
> Hello tech,
>
> I noticed the event(3) manual pages don't mention the
> bufferevent_setwatermark(3) function and glosses over the details of
> watermarks, even though there's a few programs in userland that set both
> read and write
On 2018/09/22 09:21, Tom Smyth wrote:
> I like the NFsen idea, however I think for a simple eyeball ISP we could
> be able to achieve it by adding a default + exceptions summarisation
> to openBGPd ( I would rather not create more dependencies on our BGP
> )
> I want to install the minimum number
On Fri, Sep 21, 2018 at 11:19:52AM -0300, Martin Pieuchot wrote:
> The diff is simple, use the non-locked version of SRP lists, as it is
> already done in other paths in carp(4).
>
> Ok?
OK bluhm@
> Index: netinet/ip_carp.c
> ===
>
Hello Stuart,
Thanks for the feedback , I have responded to your feedback in line,
On Sat, 22 Sep 2018 at 10:07, Stuart Henderson wrote:
>
>
> Interesting idea but I think the method you're suggesting puts you at
> higher risk of things *not* reaching their destination - if you have
> good and
On Sat, Sep 22, 2018 at 10:15:21AM +0200, Anton Lindqvist wrote:
> On Fri, Sep 21, 2018 at 06:36:54PM -0700, Geoff Hill wrote:
> > Hello tech,
> >
> > I noticed the event(3) manual pages don't mention the
> > bufferevent_setwatermark(3) function and glosses over the details of
> > watermarks,
New patch included.
On Sat, Sep 22, 2018 at 07:09:44AM +0100, Jason McIntyre wrote:
> does the "ok" request mean you have commit access? (sorry, find it hard
> to keep track)
Nope, no commit access, just a user sending up a documentation fix.
> regarding the markup: there is no need to quote
Hi claudio,
Seems we are getting very close. Some suggestions to simplify the
experience for the end user.
Let's start with supporting just one (unnamed) roa-set, so far I've
really not come across a use case where multiple ROA tables are useful.
I say this having implemented origin validation
On Fri, Sep 21, 2018 at 05:29:24PM +0200, Claudio Jeker wrote:
> I currently use the RIPE RPKI validator to grab a JSON file (e.g.
> http://localcert.ripe.net:8088/export.json) and feed that to this perl
> script to convert it into bgpd syntax:
For now I recommend using
11 matches
Mail list logo
