From: Christian Ebner <c.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager docs 0/3] add optional WoL config options
Date: Tue, 5 Mar 2024 13:54:28 +0100 [thread overview]
Message-ID: <20240305125431.273796-1-c.ebner@proxmox.com> (raw)
For certain network setups the default values currently used to send
a wake on lan magic packet are not correct, e.g. it will get send via
the interface for which the default gateway is configured.
This patches add optional configuration options to set a bind
interface, over which to send the WoL packet and/or set a broadcast
address to use.
The functionality was tested by listening on all interfaces of the
sending host via `tcpdump -i any udp port 9`, and testing the
combinations of
`pvenode config set -wakeonlan-bind-interface <iface-name>` and
`pvenode config set -wakeonlan-broadcast-address <broadcast-address>`.
See also the thread in the community forum
https://forum.proxmox.com/threads/123459/
pve-manager:
Christian Ebner (2):
fix #5255: node: wol: add optional bind interface
fix #5255: node: wol: configurable broadcast address
PVE/API2/Nodes.pm | 16 ++++++++++++++--
PVE/NodeConfig.pm | 12 ++++++++++++
2 files changed, 26 insertions(+), 2 deletions(-)
pve-docs:
Christian Ebner (1):
pvenode/wake-on-lan: mention optional config options
pvenode.adoc | 14 ++++++++++++++
1 file changed, 14 insertions(+)
--
2.39.2
next reply other threads:[~2024-03-05 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 12:54 Christian Ebner [this message]
2024-03-05 12:54 ` [pve-devel] [PATCH manager 1/3] fix #5255: node: wol: add optional bind interface Christian Ebner
2024-03-21 17:27 ` Thomas Lamprecht
2024-03-22 14:37 ` Christian Ebner
2024-03-26 9:21 ` Christian Ebner
2024-03-05 12:54 ` [pve-devel] [PATCH manager 2/3] fix #5255: node: wol: configurable broadcast address Christian Ebner
2024-03-05 12:54 ` [pve-devel] [PATCH docs 3/3] pvenode/wake-on-lan: mention optional config options Christian Ebner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240305125431.273796-1-c.ebner@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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