Unable to add a static IPv6 route with fe80 next-hop
Hi, It’s the first time I try to do such a configuration, but I can’t find the right syntax. route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8%enp3s0f1.30 → syntax error, unexpected '.' route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8%"enp3s0f1.30" → syntax error, unexpected TEXT, expecting CF_SYM_KNOWN or CF_SYM_UNDEFINED route 2a00:5884:105::/48 via "fe80::ae1f:6bff:fead:2ed8%enp3s0f1.30" → no error but no route route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8 interface "enp3s0f1.30" → syntax error, unexpected INTERFACE route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8 "enp3s0f1.30" → syntax error, unexpected TEXT And https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.14 only shows examples about IPv4. What is the correct syntax? Thanks, -- Alarig Le Lay
On Fri, May 01, 2020 at 07:46:54PM +0200, Alarig Le Lay wrote:
Hi,
It’s the first time I try to do such a configuration, but I can’t find the right syntax.
route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8%enp3s0f1.30 → syntax error, unexpected '.' route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8%"enp3s0f1.30" → syntax error, unexpected TEXT, expecting CF_SYM_KNOWN or CF_SYM_UNDEFINED
Hi It is a bit tricky. Expression fe80::ae1f:6bff:fead:2ed8%eth0 would work, but because you have a dot in name, you need to write it as fe80::ae1f:6bff:fead:2ed8%'enp3s0f1.30' The syntax here abuses symbol syntax (like is used for e.g. protocol names). -- 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 Fri 01 May 2020 21:12:10 GMT, Ondrej Zajicek wrote:
On Fri, May 01, 2020 at 07:46:54PM +0200, Alarig Le Lay wrote:
Hi,
It’s the first time I try to do such a configuration, but I can’t find the right syntax.
route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8%enp3s0f1.30 → syntax error, unexpected '.' route 2a00:5884:105::/48 via fe80::ae1f:6bff:fead:2ed8%"enp3s0f1.30" → syntax error, unexpected TEXT, expecting CF_SYM_KNOWN or CF_SYM_UNDEFINED
Hi
It is a bit tricky. Expression fe80::ae1f:6bff:fead:2ed8%eth0 would work, but because you have a dot in name, you need to write it as fe80::ae1f:6bff:fead:2ed8%'enp3s0f1.30'
The syntax here abuses symbol syntax (like is used for e.g. protocol names).
Indeed, with simple quotes instead of double quotes it works. Thanks a lot! It’s not very obvious though ;) -- Alarig
participants (2)
-
Alarig Le Lay -
Ondrej Zajicek