unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Lars Rustand <rustand.lars@gmail.com>
To: help-guix@gnu.org
Subject: Setting up multiple NICs
Date: Thu, 23 Nov 2023 10:11:01 +0100	[thread overview]
Message-ID: <tyhwfpk5fgjaeeopqge2w4mbwlxorhf4gh3lytt7srasodfwkk@4j2wtrun7jrc> (raw)

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

Hello!

I'm trying to set up Guix on my "router", but I'm not able to get my networking
setup to work. What I need is one upstream NIC, and one downstream NIC which is
split into multiple VLANs.

I've tried to different approaches:

1. Have everything inside of one `static-networking` form.
2. Have one `static-networking` form for each VLAN.

If I specify multiple `static-networking` forms I get the error "guix system:
error: service 'networking' provided more than once".

If I instead put them all in the same `static-networking` form, at least the
system happily reconfigures, but I instead get failures of the networking
service.

I found one example of a more advanced networking config in the devel version of
the manual, but this one does not show multiple VLANs, but it does show multiple
links in the same `static-networking` to build a bond interface.

So, what is the correct way to setup a multi NIC networking with multiple VLANs?

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

             reply	other threads:[~2023-11-23 17:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  9:11 Lars Rustand [this message]
2023-11-24  3:08 ` Setting up multiple NICs Oleg Pykhalov
2023-11-29 17:33 ` Felix Lechner via
  -- strict thread matches above, loose matches on Subject: below --
2023-11-29  6:26 Lars Rustand
2023-11-29  7:39 ` Oleg Pykhalov
2023-11-29  8:38   ` Lars Rustand
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

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=tyhwfpk5fgjaeeopqge2w4mbwlxorhf4gh3lytt7srasodfwkk@4j2wtrun7jrc \
    --to=rustand.lars@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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).