wrong network interface / wol

B

ber56

New Member
Feb 27, 2023
2
0
1
Hello,

I have a proxmox cluster (7.3), with private cluster network.
cluster network : 192.168.19.x

Only 1 node (frontal) has 2 interfaces:
vmbr0: on my network, accessible via web gui https://172.25.34.10:8806
vmbr1: on private cluster network (192.168.19.1)


if I do :

pvenode wakeonlan cluster02

does not work, because the command is sent to the wrong interface (vmbr0)
Same thing with graphical interface.

wakeonlan xx:xx:xx:xx:xx:xx either

etherwake -b -i eth1 xx:xx:xx:xx:xx:xx is ok.


Is it possible to specify on which interface we want to send the magic packet with proxmox ?

Sincerely
 
Last edited:
Hi,
no unfortunately this is not implemented, the interface on which the magic packet is send out is determined by the routing table.

Could you open feature request for this at https://bugzilla.proxmox.com/, it should be possible to include the interface to send the packet to in the config, and set it via setsockopt by specifying SO_BINDTODEVICE.
 
Chris said:
Could you open feature request for this at https://bugzilla.proxmox.com/, it should be possible to include the interface to send the packet to in the config, and set it via setsockopt by specifying SO_BINDTODEVICE.
Click to expand...
I have the same issue (in 8.1.3) and looked for that feature/enhancement request in bugzilla but found nothing so I'll probably open it myself.
Looking at the code it should be easy to replace the hardcoded local broadcast (255.255.255.255) with a new configuration option (e.g. "Broadcast address for Wake on LAN") that defaults to 255.255.255.255. That way it would be possible to direct the broadcast (e.g. 192.0.2.255) to a specific subnet interface if needed.
 
Stefan Radman said:
I have the same issue (in 8.1.3) and looked for that feature/enhancement request in bugzilla but found nothing so I'll probably open it myself.
Looking at the code it should be easy to replace the hardcoded local broadcast (255.255.255.255) with a new configuration option (e.g. "Broadcast address for Wake on LAN") that defaults to 255.255.255.255. That way it would be possible to direct the broadcast (e.g. 192.0.2.255) to a specific subnet interface if needed.
Click to expand...
Hi,
yes do please open an issue in our bugtracker for this, I will have a look at this when time allows. Thanks!
 
You must log in or register to reply here.
Top Bottom