[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Advanced network configuration
From: |
Ludovic Courtès |
Subject: |
Re: Advanced network configuration |
Date: |
Mon, 10 Oct 2022 17:17:16 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) |
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’.