Comment # 16 on bug 1175455 from Lukas Ocilka

(In reply to Lukas Ocilka from comment #15)
> (In reply to Petr Mikul���k from comment #7)
> > 3. What about adding a check box into the "Allow WOL" into the "Network
> > setup"? Or would this conflict with Network Manager, wick, ...?
> 
> According to
> https://apuntesderootblog.wordpress.com/2015/12/02/enable-wake-on-lan-with-
> networkmanager/ it's possible to configure NM to allow for WOL too.
> 
> ... YaST exists to make hard tasks simple(r), but we can't target all
> use-cases. Ideally the majority only, and special cases should be covered by
> a good documentation and commandline tools.

I've discussed this topic with Knut today and there is a problem that would be
hard to overcome: There are simply too many ways to enable WOL and even to
"keep it enabled". At the end all of them probably call ethtool. But most of
them do not care about disabling WOL.

So, let's imagine that we have a checkbox that would allow for enabling WOL and
it would also show the current state (enabled/disabled) once you run YaST.
Ethtool can provide that info. The problem is when you decide to disable WOL,
in such case YaST has simply too many options what it could try: check for
service that maybe calls ethtool and remove it there, remove the udev-rule
package, check other startup scripts, any other or even unknown way :-/

And when we are at it, there are several types of WOL, so YaST should offer the
type too.

I'm afraid that it's far beyond the scope of YaST and we should really have the
wol-udev-rules package fixed or have another simple way. And especially, we
need to provide a proper documentation. Maybe wicked-maintainers could share
their view, please?