On Wed, Dec 2, 2020 at 18:23 Vieri <rentor...@yahoo.com.invalid> wrote:
> Hi, > > My Guacamole-Client/Tomcat installation is running on a gateway, and the > target machines (RDP, VNC, etc.) are in a subnet behind a firewall. This > firewall "forwards" the wake-on-lan packets to that LAN through the use of > socat. I run it like this on the firewall because I have different netmasks > there: > > socat -u -T1 UDP-LISTEN:7,fork UDP-DATAGRAM:10.215.145.255:9,broadcast > socat -u -T1 UDP-LISTEN:8,fork UDP-DATAGRAM:10.215.247.255:9,broadcast > socat -u -T1 UDP-LISTEN:9,fork UDP-DATAGRAM:10.215.248.255:9,broadcast > socat -u -T1 UDP-LISTEN:10,fork UDP-DATAGRAM:10.215.111.255:9,broadcast > > Before the wake-on-lan feature was added to Guacamole-Client I used to run > a custom script which would in turn use a popular program called > 'wakeonlan' from http://gsd.di.uminho.pt/jpo/software/wakeonlan/. This > command has a -port parameter which allows to specify where to send the > magic packet. So I run things like: > > wakeonlan -p $port -i $broadcast $mac > > where $port is any of 7,8,9,10 in my case. > > Now, I'd like to use Guacamole's built-in support for WOL instead. > However, according to > https://guacamole.apache.org/doc/gug/configuring-guacamole.html there > doesn't seem to be a way to specify this port. I guess it always uses the > default port 9. > > Would it be possible to add this feature? > Yes, definitely possible to add this feature. When I was implementing the WoL support and researching things it didn't seem like the port was ever beyond just complying with best practices, so it didn't seem worthwhile to be able to change it. I see that you've found a use for it. You can put in a feature request in JIRA for it and someone can tackle it. It should be a pretty trivial change. -Nick
