From: Marco van Hulten <marco@hulten.org>
To: help-guix@gnu.org
Subject: networking service problem with static address
Date: Wed, 2 Aug 2023 21:08:14 +0200 [thread overview]
Message-ID: <20230802210814.26701d5f@hulten.org> (raw)
Hi all,
Sometimes my ethernet interface was not configured at boot. I do not
know where the problem lies, but I decided to try a static address:
(service static-networking-service-type
(list (static-networking
(addresses
(list (network-address
(device "enp0s25")
(value "192.168.0.7/16"))))
(routes
(list (network-route
(destination "default")
(gateway "192.168.0.11"))))
(name-servers '("192.168.0.11")))))
Before this, I used dynamic:
(service dhcp-client-service-type)
With a static address the interface always comes up configured, at least
so far. (So, at some time, I should check cabling, the DHCP daemon &c.)
But now cups does not always start at boot, so I try to restart:
root@graviton ~# herd start cups
Exception caught while starting networking: (%exception #<&netlink-response-error errno: 17>)
Service cups depends on networking.
herd: error: failed to start service cups
root@graviton ~# herd start networking
herd: error: exception caught while executing 'start' on service 'networking':
Throw to key `%exception' with args `("#<&netlink-response-error errno: 17>")'.
Should 'networking' not be running when using a static IP?
As another work-around, could I tell the system that cups does not need
the 'networking' dependency?
Here is my cups service config; this is unchanged.
(service cups-service-type
(cups-configuration
(web-interface? #t)
(extensions
(list cups-filters foomatic-filters hplip-minimal))))
—Marco
reply other threads:[~2023-08-02 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230802210814.26701d5f@hulten.org \
--to=marco@hulten.org \
--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).