On Thu, Feb 27, 2020 at 10:16:38PM +0100, Mattia Milani wrote:
> Hello bird users, I'm sorry to bother you but I have a question about the
> implementation of a piece of the RFC 4271 that I found a little bit fuzzy.
>
> I'm in a eBGP situation and suppose that I have more connections with other
>
Hello bird users, I'm sorry to bother you but I have a question about
the implementation of a piece of the RFC 4271 that I found a little bit
fuzzy.
I'm in a eBGP situation and suppose that I have more connections with
other different AS peers.
Giving the fact that my import and export filters
On Wed, Jan 29, 2020 at 03:29:47PM +0100, Adam KuĊagowski wrote:
> Hi,
>
> I've found that It is supported since 4.14:
>
> https://github.com/torvalds/linux/commit/8917a777be3ba566377be05117f71b93a5fd909d
Hi
Fixed in latest commit [*], now TCP_MD5SIG should work with ranges. Did
not try 0.0.0.0
On Thu, 27 Feb 2020, Ondrej Zajicek wrote:
> You need group foo to access /var/lib/foo/, that is part of secondary
> groups for bird user (as reported by 'id') and these secondary groups are
> assigned e.g. when 'su - bird' is used.
>
> But when you run 'bird -u bird -g bird', it only set UID (-u)
On Thu, 27 Feb 2020, Chriztoffer Hansen wrote:
> > Is the above under any circumstances valid in any BIRD 1.x version? I did
> > not use BIRD 1.x much, but I thought it is strictly either IPv4 or IPv6...
>
> Correct,
>
> what you fx. can do is:
Okay, while I'm using something similar for BIRD 2.
Hi,
Robert Scheck skrev:
> Hello Maria,
>
> as of writing, OpenBSD rpki-client produces an output file for BIRD 1.x
> like the following, where IPv4 and IPv6 end up in the same table. For me
> this ends with "This is an IPv4 router, therefore IPv6 addresses are not
> supported" error on BIRD 1.x
