Static routes on (active) interfaces without IP address set
Hi, Is there any specific reason why bird (1.6.0 @linux in particular) does not process static routes like: route 10.101.0.0/24 via "eth1"; when eth1 has no assigned IP address (but is up & active)? This route is completely legal but it is invisible anywhere, simply ignored (even does not appear in debug messages). Once eth1 gets IP address, the route is added, but not otherwise... -- With best regards, Alexander.
On Sat, Jun 18, 2016 at 01:06:29AM +0200, Alexander Demenshin wrote:
Hi,
Is there any specific reason why bird (1.6.0 @linux in particular) does not process static routes like:
route 10.101.0.0/24 via "eth1";
when eth1 has no assigned IP address (but is up & active)?
This route is completely legal but it is invisible anywhere, simply ignored (even does not appear in debug messages).
That is true. For historical reasons, BIRD handles interface without IP addresses as down. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On 2016-06-19 17:59, Ondrej Zajicek wrote:
That is true. For historical reasons, BIRD handles interface without IP addresses as down.
Well... does it mean that it has to stay like this or it makes sense to fix this behavior? At least, an option in config would be nice, if changing actual behavior is not desirable. Best regards, Alexander.
On Sun, 19 Jun 2016, Alexander Demenshin wrote:
On 2016-06-19 17:59, Ondrej Zajicek wrote:
That is true. For historical reasons, BIRD handles interface without IP addresses as down.
Well... does it mean that it has to stay like this or it makes sense to fix this behavior? At least, an option in config would be nice, if changing actual behavior is not desirable.
I agree; I've had it that community :666 couldn't be set without having them up, so had to create an interface with 253 IP's to still have those blocked at the upstream. Leo Vandewoestijne.
On Sun, 19 Jun 2016 19:09:20 +0000, Leo Vandewoestijne wrote:
I agree; I've had it that community :666 couldn't be set without having them up, so had to create an interface with 253 IP's to still have those blocked at the upstream.
For this purpose I install RTBH routes recursively via 192.0.2.1, then route 192.0.2.0/24 to a blackhole. -- Michael Fincham
participants (4)
-
Alexander Demenshin -
Leo Vandewoestijne -
Michael Fincham -
Ondrej Zajicek