unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Alexey Abramov <levenson@mmer.org>
Cc: guix-devel@gnu.org,  Julien Lepiller <julien@lepiller.eu>
Subject: Re: Advanced network configuration
Date: Mon, 10 Oct 2022 17:17:16 +0200	[thread overview]
Message-ID: <875ygr1zer.fsf@gnu.org> (raw)
In-Reply-To: <87zge9m70d.fsf@delta.lan> (Alexey Abramov's message of "Thu, 06 Oct 2022 15:11:30 +0200")

Hi!

Alexey Abramov <levenson@mmer.org> skribis:

[...]

>> I’m not sure.  IIUC, a “networking target” here could translate to a
>> Shepherd service that depends on all the relevant DHCP and static
>> networking services.  The question the becomes how to express that
>> grouping conveniently.
>
> Yes, I also would like to point out that their must be a way to
> establish a firewall, for example, *before* any network interface is up
> (After=network-pre.target in systemd [1]). And the same thing during the
> shutdown procedure (Before=network-pre.target in systemd).

I would do that by having ‘networking’ depend on ‘firewall’ (say).

Does that make sense?

It’d be interesting to see whether we need something beyond this.

> Applications have to be able to gracefully shutdown their network
> connections.  Is it the case right now, I don't know?

What do you mean?

> I am checking (shepherd services) where `shutdown-services' defined, and
> seems like it just walks across %services hash table. Am I missing
> something?

Correct, there’s nothing fancy going on there.

Thanks,
Ludo’.


  parent reply	other threads:[~2022-10-10 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 18:23 Advanced network configuration Alexey Abramov
2022-10-03 19:28 ` Ryan Sundberg
2022-10-04  8:21   ` Alexey Abramov
2022-10-05 10:34 ` Ludovic Courtès
2022-10-06 13:11   ` Alexey Abramov
2022-10-06 14:07     ` Julien Lepiller
2022-10-08 17:01       ` Alexey Abramov
2022-10-10 15:17     ` Ludovic Courtès [this message]
2022-10-10 16:03       ` Julien Lepiller
2022-10-11  7:57       ` Alexey Abramov
2022-10-13 14:49         ` Ludovic Courtès

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=875ygr1zer.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=levenson@mmer.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).