Your message dated Sat, 11 Nov 2023 22:52:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#1054051: openvpn: Please provide native NetworkManager
hook scripts
has caused the Debian Bug report #1054051,
regarding openvpn: Please provide native NetworkManager hook scripts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1054051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054051
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openvpn
Version: 2.6.3-2
Severity: normal
User: [email protected]
Usertags: nm-hook-scripts
Hi,
NetworkManager provides a service named NetworkManager-dispatcher
[1], which executes scripts in
/{etc,usr/lib}/NetworkManager/dispatcher.d upon (network) state
changes.
This is in spirit similar to ifupdown's /etc/network/if-*.d/ scripts.
Previously, NetworkManager tried to call those ifupdown hook scripts
via NetworkManager-dispatcher by faking an ifupdown environment.
This caused a variety of problems though. While the concepts are
similar, the actual implementations differ significantly, e.g. when
certain events are triggered. So the mapping was never really correct
and complete. Also, some ifupdown hook scripts are meant to extend
the functionality of ifupdown. The bridge-utils and wpasupplicant
package are examples here, that provide hook scripts that should not
be run under NetworkManager, as it has builtin implementations for
this kind of functionality.
As a result, NetworkManager in trixie will remove support for running
ifupdown hook scripts.
Your package openvpn installs one or more ifupdown hook scripts.
Please evaluate, whether your package would benefit from shipping a
native hook script for NetworkManager. If not, please just close this
bug report with a corresponding comment.
Such package provided hook scripts should be placed in
/usr/lib/NetworkManager/dispatcher.d/. If your hook script needs
additional configuration, please place this configuration in /etc and
source that in your hooks script. It is discouraged to place package
provided hook scripts directly in /etc/NetworkManager/dispatcher.d/.
This directory is meant for local modifications.
You can read more about the NetworkManager-dispatcher interface at
[1].
If you have further questions, you can contact me directly or
preferably the pkg-utopia mailing list at
<[email protected]>.
Kind regards,
Michael
[1]
https://manpages.debian.org/bookworm/network-manager/NetworkManager-d
ispatcher.8.en.html [2]
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix
On 16/10/23 07:03 PM, [email protected] wrote:
> Please evaluate, whether your package would benefit from shipping a
> native hook script for NetworkManager. If not, please just close this
> bug report with a corresponding comment.
The hook is to start a VPN tunnel after an underlying network interface
comes up, see README.Debian
---
/etc/network/interfaces can be configured to start and stop openvpn when the
underlying network interface is brought up and down. To do so add a line such
as "openvpn vpn1" to the stanza for the underlying network interface, where
"vpn1" is the name of the vpn to start and stop.
---
I don't think this is portable to NetworkManager hooks (IIRC
NetworkManager has another mechanism to start VPN tunnels as early as
possible when a physical connection comes up)
Bernhard
--- End Message ---
