[Bug 1781597] Re: [SRU] WoWLAN settings are not supported

[Alfonso Sanchez-Beato]

** Summary changed:

- WoWLAN settings are not supported
+ [SRU] WoWLAN settings are not supported

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packages over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect <ssid> password <password>
  $ sudo nmcli c modify <ssid> 802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down <ssid>
  $ sudo nmcli c up <ssid>

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i <wifi_iface> <destination_MAC_address>

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions