From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 52511@debbugs.gnu.org
Subject: bug#52511: service networking provided more than once
Date: Wed, 15 Dec 2021 14:50:35 +0100 [thread overview]
Message-ID: <875yrqj7tg.fsf@gnu.org> (raw)
In-Reply-To: <87ee6evvy3.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 15 Dec 2021 14:28:36 +0100")
Hey,
> In this particular case, you could/should have a single
> ‘static-networking’ with multiple addresses:
>
> (static-networking
> (addresses
> (list (network-address …)
> (network-address …)))
> (routes …))
Oh, I see. There's still something problematic:
--8<---------------cut here---------------start------------->8---
;; Connection to the DMZ for public access
;; This is a 10G port.
(static-networking-service "eno2"
"141.80.181.40"
#:netmask "255.255.255.0"
#:gateway "141.80.181.1")
;; Connection to build nodes
(static-networking-service "eno1"
"141.80.167.131"
#:netmask "255.255.255.192")
--8<---------------cut here---------------end--------------->8---
The above configuration used to create two distinct shepherd services:
networking-eno1 and networking-eno2.
We now have the aforementioned error because those two interfaces are
now provisioning 'networking, breaking compatibility.
Browsing the code, I also found:
--8<---------------cut here---------------start------------->8---
(service static-networking-service-type
(list %loopback-static-networking
;; QEMU user-mode networking. To get "eth0", you need
;; QEMU to emulate a device for which Mach has an
;; in-kernel driver, for instance with:
;; --device rtl8139,netdev=net0 --netdev user,id=net0
%qemu-static-networking))
--8<---------------cut here---------------end--------------->8---
which made me think that creating a distinct static-networking record
per interface was the way to go.
Thanks,
Mathieu
prev parent reply other threads:[~2021-12-15 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 13:04 bug#52511: service networking provided more than once Mathieu Othacehe
2021-12-15 13:28 ` Ludovic Courtès
2021-12-15 13:50 ` Mathieu Othacehe [this message]
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=875yrqj7tg.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=52511@debbugs.gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).