Static route IPv4 via FE80::2/64 and interface issue

[Douglas Fischer]

I'm just guessing here...

But it looks like some CNI for Kubernetes with some adapted way of renaming
the IFs.

Em qua., 14 de fev. de 2024 às 13:11, <netravnen+birdlist at gmail.com>
escreveu:

> 👋
>
> Which platform uses backslash in the interface name?
>
> Have you tried to rename the interface or add an interface alias? (using
> systemd or ude rules) to avoid the backslash in the interface name.
>
> On Wed, 14 Feb 2024, 11.11 Saklak, Marcin via Bird-users, <
> bird-users at network.cz> wrote:
>
>> Hello Bird Users,
>>
>>
>> I have an issue with adding static route and interfaces. I use two
>> different platform one has interface names like eth-1_1_32 and second
>> eth-1\1\64.
>> First one works as I would expect.
>>
>> First platform:
>> ifconfig eth-1_1_32
>>
>> eth-1_1_32: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>
>>
>> bird.conf:
>>  route 192.168.1.5/32 via fe80::2 % 'eth-1_1_32';
>>
>> ip r
>>
>> 192.168.1.5 via inet6 fe80::2 dev eth-1_1_32 proto bird metric 32
>>
>> but second platform with interfaces in eth-1\1\64 style didn’t work
>> ifconfig eth-1\\1\\64
>>
>> eth-1\1\64: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>
>> I’ve got an error message for  route 192.168.1.5/32 via fe80::2 %
>> 'eth-1\1\64';
>> birdc
>>
>> BIRD 2.13 ready.
>>
>> bird> configure
>>
>> Reading configuration from /mnt/storage/config/bird.conf
>>
>> /mnt/storage/config/bird.conf:29:45 Invalid character in apostrophed
>> symbol
>>
>> for:
>> route 192.168.1.5/32 via fe80::2 % "eth-1\1\64";
>> bird> configure
>>
>> Reading configuration from /mnt/storage/config/bird.conf
>>
>> /mnt/storage/config/bird.conf:29:51 syntax error, unexpected TEXT
>>
>>
>>
>> for:
>> route 192.168.1.5/32 via "fe80::2%eth-1\1\64";
>> no error and no entries in linux
>> I did also tests with
>> route 192.168.1.5/32 via "fe80::2%eth-1\\\1\\\64";
>> route 192.168.1.5/32 via "fe80::2%eth-1\\1\\64";
>>
>> route 192.168.1.5/32 via fe80::2 % ’eth-1\\\1\\\64’;
>> route 192.168.1.5/32 via fe80::2 % ’eth-1\\1\\64’;
>>
>> without any success
>>
>> Is it possible to make it work on both cases or there is some other way
>> to configure such static route?
>>
>>
>>
>> Thanks,
>> Marcin
>>
>>

-- 
Douglas Fernando Fischer
Engº de Controle e Automação
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20240214/523e66e4/attachment.htm>