You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a standalone (non-LTSP) client boots, it's possible that epoptes-client will be started before networking.
And if SERVER=some-ip or some entry from /etc/hosts, then the epoptes-client.wait_for_dns function won't wait until DNS is up.
In that case, the current epoptes-client.apply_wol function can't detect the interface that will be used to contact the epoptes server, so it doesn't enable WoL for any interface.
One solution could be to transform wait_for_dns into wait_for_server_ip_reachable (using ip r get ...).
Another solution could be to enable WoL in all interfaces anyway; I can't think of any reason we'd prefer to enable WoL only in a specific interface.
The text was updated successfully, but these errors were encountered:
eltoukos
added a commit
to eltoukos/epoptes
that referenced
this issue
Jul 28, 2023
When a standalone (non-LTSP) client boots, it's possible that epoptes-client will be started before networking.
And if SERVER=some-ip or some entry from /etc/hosts, then the epoptes-client.wait_for_dns function won't wait until DNS is up.
In that case, the current epoptes-client.apply_wol function can't detect the interface that will be used to contact the epoptes server, so it doesn't enable WoL for any interface.
One solution could be to transform
wait_for_dns
intowait_for_server_ip_reachable
(usingip r get ...
).Another solution could be to enable WoL in all interfaces anyway; I can't think of any reason we'd prefer to enable WoL only in a specific interface.
The text was updated successfully, but these errors were encountered: