all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Rustand <rustand.lars@gmail.com>
To: Oleg Pykhalov <go.qigust@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Setting up multiple NICs
Date: Wed, 29 Nov 2023 09:38:17 +0100	[thread overview]
Message-ID: <6shzdzqgez5zr45mx3pljqqcyeizxwbne5jeni5nbyzjlihhrc@nnlrvtkoxj22> (raw)
In-Reply-To: <87v89lt3dy.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4812 bytes --]

On 23/11/29 10:39AM, Oleg Pykhalov wrote:
> I think this "management@enp4s0f1" syntax is not what is expected by the
> configuration.

I think this is the normal naming convention used for VLAN interfaces, at least
in normal distros. It is also what the interface gets named in the output of
`ip link` when I create a `network-link` called "management".

> You mentioned that you tried a development version manual.  Did you try
> configuration similar to the example in that manual?
> 
>     https://guix.gnu.org/en/manual/devel/pt-br/html_node/Networking-Setup.html
> 
> --8<---------------cut here---------------start------------->8---
> (static-networking
>  (links (list (network-link
>                (name "bond0")
>                (type 'bond)
>                (arguments '((mode . "802.3ad")
>                             (miimon . 100)
>                             (lacp-active . "on")
>                             (lacp-rate . "fast"))))
> 
>               (network-link
>                (mac-address "98:11:22:33:44:55")
>                (arguments '((master . "bond0"))))
> 
>               (network-link
>                (mac-address "98:11:22:33:44:56")
>                (arguments '((master . "bond0"))))
> 
>               (network-link
>                (name "bond0.1055")
>                (type 'vlan)
>                (arguments '((id . 1055)
>                             (link . "bond0"))))))
>  (addresses (list (network-address
>                    (value "192.168.1.4/24")
>                    (device "bond0.1055")))))
> --8<---------------cut here---------------end--------------->8---

Yes, that is the example I have based my config on.

> So your configuration would be like:
> --8<---------------cut here---------------start------------->8---
> (service static-networking-service-type
>          (list (static-networking
>                 (links
>                  (list (network-link
>                         (name "enp4s0f1.3")
>                         (type 'vlan)
>                         (arguments '((id . 3)
>                                      (link . "enp4s0f1"))))
>                        (network-link
>                         (name "enp4s0f1.4")
>                         (type 'vlan)
>                         (arguments '((id . 4)
>                                      (link . "enp4s0f1"))))
>                        (network-link
>                         (name "enp4s0f1.5")
>                         (type 'vlan)
>                         (arguments '((id . 5)
>                                      (link . "enp4s0f1"))))
>                        (network-link
>                         (name "enp4s0f1.6")
>                         (type 'vlan)
>                         (arguments '((id . 6)
>                                      (link . "enp4s0f1"))))
>                        (network-link
>                         (name "enp4s0f1.2")
>                         (type 'vlan)
>                         (arguments '((id . 2)
>                                      (link . "enp4s0f1"))))))
>                 (addresses
>                  (list (network-address
>                         (device "enp2s0")
>                         (value "192.168.10.2/24"))
>                        (network-address
>                         (device "enp4s0f1.3")
>                         (value "10.0.3.1/24"))
>                        (network-address
>                         (device "enp4s0f1.4")
>                         (value "10.0.4.1/24"))
>                        (network-address
>                         (device "enp4s0f1.5")
>                         (value "10.0.5.1/24"))
>                        (network-address
>                         (device "enp4s0f1.6")
>                         (value "10.0.6.1/24"))
>                        (network-address
>                         (device "enp4s0f1.2")
>                         (value "192.168.0.2/24")))))))
> --8<---------------cut here---------------end--------------->8---

Thanks, I tried that but it gave the same type of error. When trying to start
the networking service I get an error "#<&netlink-response-error errno: 17>",
which, from what I can tell, means file exists.

I think it might have problems creating multiple VLAN interfaces on the same NIC
for some reason.

Also, when using your config above, only one of the VLAN interfaces are created,
and it is named "enp4s0f1.3@enp4s0f1" in the output of `ip link`.

> Also, may try without ‘(network-address (device "enp2s0") (value
> "192.168.10.2/24"))’ block.

I can't do that, since this is the interface I use to log in to the machine.
And, this part is actually working, so there should be no reason to remove it.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-11-29  8:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  6:26 Setting up multiple NICs Lars Rustand
2023-11-29  7:39 ` Oleg Pykhalov
2023-11-29  8:38   ` Lars Rustand [this message]
2023-12-02 23:34     ` rustand.lars
2023-12-03  2:49       ` Felix Lechner via
2023-12-03  4:43         ` Wojtek Kosior via
2023-12-07  7:50           ` rustand.lars
2023-12-07 16:56             ` Felix Lechner via
2023-12-07 20:22 ` Lars Rustand
  -- strict thread matches above, loose matches on Subject: below --
2023-11-23  9:11 Lars Rustand
2023-11-24  3:08 ` Oleg Pykhalov
2023-11-29 17:33 ` Felix Lechner via

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6shzdzqgez5zr45mx3pljqqcyeizxwbne5jeni5nbyzjlihhrc@nnlrvtkoxj22 \
    --to=rustand.lars@gmail.com \
    --cc=go.qigust@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.