Hi Ludovic,
My apologies for the delayed response.
The problem was present after reboot and I didn't interact with the
interfaces manually.
Eventually I was able to resolve this by adding an explicit "up"
statement for the primary interface:
(network-link
(name "enp191s0")
(type #f)
(arguments '((up . #t))))
I believe it has to do with the order of how the alias interface gets
created. The primary should be in an up state, before the alias is
defined, otherwise the networking script fails.
Cheers,
Mate
On 14/10/26 22:55, Ludovic Courtès wrote:
Hi Mate,
Mate Gabri <[email protected]> skribis:
(service static-networking-service-type
(list (static-networking
(links
(list (network-link
(name "enp191s0.50")
(type 'vlan)
(arguments '((id . 50)
(link . "enp191s0"))))))
[...]
However the networking service (set-up-network) fails with the
following error (from /var/log/messages) during boot:
Backtrace:
1 (primitive-load "/gnu/store/37dvbf5a6zvfn64v4pfiwqisyxr?")
In ice-9/eval.scm:
619:8 0 (_ #f)
ice-9/eval.scm:619:8: ERROR:
1. &netlink-response-error: 17
I don’t know how tagged VLAN interfaces are supposed to work. Number 17
here is an errno value corresponding to EEXIST (“File exists”), which in
turn suggests that the ‘networking’ service is trying to create an
interface, link, or route that already exists.
Could it be that you first created that config manually, for instance
using the ‘ip’ command? That would explain why ‘networking’ fails to
set it up by itself.
Also, is the problem present after reboot?
Thanks,
Ludo’
