On Fri, 12 Oct 2018, Chris Boot wrote:
Except it doesn't really make any odds for Debian repositories, where
the contents is signed using GPG. Transport encryption doesn't add
anything if the data is already signed at source, and just makes
mirroring and caching harder.
Newer versions of Apt (c
Except it doesn't really make any odds for Debian repositories, where
the contents is signed using GPG. Transport encryption doesn't add
anything if the data is already signed at source, and just makes
mirroring and caching harder.
Newer versions of Apt (coming in Debian buster) have the https tra
I had to install apt-transport-https on debian 9 to reach the repositories.
Personally, i was more surprised debian didn't support HTTPS by default
rather than surprised that BIRD is deprecating HTTP. The deprecation of
HTTP is happening everywhere.
Jonathan
On Fri, Oct 12, 2018 at 10:12 AM Ada
We have embedded debian instalations using the debian bird package.
However the repo url http://bird.network.cz/debian/ is redirected to
https. This causes a problems, because our installations do not have https
and apt ends with:
The method driver /usr/lib/apt/methods/https could not be found
> The key question is - how to make Bird announcing 0/0 for OSPF ALWAYS?
Create a static, low-preference „Unreachable“ route for 0/0. If there’s a
„real“ (functioning) route it’ll override this one and otherwise „unreachable“
is always there („reachable“ … [sic]) so you *always* have a 0/0 in y
Hello Ondrej,
Thank you for prompt answer.
First remark - suggested setup is that both BGP1 and BGP2 is part of OSPF
domain, do not propagate BGP routes, but both propagate default route,
locally configured as 'unreachable'.
I don't find Bird propagates unreachable 0/0. I made a few tests and
