desktop-packages team mailing list archive

[Doug Morse <dm@xxxxxxxxxxxxx>]

Hi,

OK, I feel stupid...

In trying again to get WOL working, I was able to set my NIC's HW / MAC
address back to what it was, 50:e5:49:36:1d:d3, by using Win7's driver
settings for it in Win7's device manager.  The upgrade to Oneiric
somehow and oddly changed it to aa:00:04:00:0a:04.

Once I changed the HW / MAC address back to the original address and
rebooted into Oneiric, WOL started working again.

Then I checked my WOL client -- an iPhone app called iNet Pro -- and I
realized that I had never changed it to wake aa:00:04:00:0a:04 and it
was still set to wake 50:e5:49:36:1d:d3.

SO... probably a false alarm here. :)  I'll close this bug if I am able;
otherwise I leave it for the proper admin to do so.

Thanks,
Doug


** Changed in: network-manager (Ubuntu)
     Assignee: (unassigned) => Doug Morse (dm-dougmorse)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/874320

Title:
  Wake on Lan (WOL) not working after upgrade from natty to oneiric

Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  Hi Fellow Ubuntu-ers,

  Wake on lan (WOL) was working fine on my system before upgrading to
  Oneiric.  Now, nothing I do makes WOL work again.  I have tried
  uninstalling network-manager and simply configuring
  /etc/network/interfaces as such:

  ----- contents of /etc/network/interfaces -----
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp
      post-up /sbin/ethtool -s $IFACE wol g
      post-down /sbin/ethtool -s $IFACE wol g
  ----- end of contents -----

  which configures eth0 correctly and works, and network-manager reports
  eth0 as unmanaged (and it says that no networks connections are
  configured and as such none of my VPN connections will work, but
  that's another matter...).  However, WOL does not work.  I also have a
  init script, /etc/init.d/wake-on-lan, that ensures that WOL is set
  during boot:

  ----- contents of /etc/init.d/wake-on-lan -----
  #!/bin/bash
  #
  ### BEGIN INIT INFO
  # Provides:             wake-on-lan
  # Required-Start:       $local_fs
  # Required-Stop:        $local_fs
  # Default-Start:        2 3 4 5
  # Default-Stop:         0 6
  # Short-Description:    Enable Wake-On-Lan 
  ### END INIT INFO
  #
  . /lib/lsb/init-functions
   
  do_start() {
      ethtool -s eth0 wol g
      exit
  } 
   
  do_stop() {
      ethtool -s eth0 wol d
      exit
  }
   
  case "$1" in
    start )
          do_start
          ;;
    restart|reload|force-reload )
          echo "Error: argument '$1' not supported" >&2
          exit 3
          ;;
    stop )
          do_stop
          ;;
    * )
          echo "Usage: $0 start|stop" >&2
          exit 3
          ;;
  esac
  ----- end of contents -----

  Moreover, /var/log/pm-powersave.log always shows:

  
      /usr/lib/pm-utils/power.d/anacron false: success.
      Running hook /usr/lib/pm-utils/power.d/disable_wol false:
      Setting Wake On Lan for eth0 to enable...Done.

  indicating that WOL is set.  Manually checking with 'ethtool eth0'
  always shows:

  	Supports Wake-on: pumbg
  	Wake-on: g

  but WOL simply does not work, whereas it was working perfectly with
  Natty (11.04).  I have not made any changes to the BIOS or another
  hardware changes in any way.

  If I comment out all of the lines in /etc/network/interfaces and allow
  network-manager to configure eth0 and lo, the network is properly
  configured (and I can use my VPN connections, BTW).  However, sending
  the WOL magic packet to the machine still has no effect -- the machine
  does not wake from sleep / suspend mode (I am not trying to wake from
  shutdown or hibernate -- always from suspend / sleep mode).

  Finally, I should, one of the oddest things that occurred as part of
  the upgrade is that eth0's MAC address changed ?!?  It had been
  something that started with "D3:..." and now it is
  'AA:00:04:00:0A:04'.  I found this rather surprising, as I thought MAC
  addresses were hardcoded into the chipset, but apparently not.  I
  doubt this is relevant, but I figured I should mention it.

  Thanks in advance for any and all help -- I really need to get WOL
  working again, especially given that linux kernel 3.0 is presently
  known to consume on average 30% more power.

  Cheers,
  Doug

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.9.1.90-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Fri Oct 14 09:52:41 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   24.159.73.182 via 192.168.0.1 dev eth0  src 192.168.0.20 
   75.148.63.113 via 192.168.0.1 dev eth0  src 192.168.0.20 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.20  metric 1
  IwConfig:
   lo        no wireless extensions.
   
   eth0      no wireless extensions.
  Keyfiles: Error: [Errno 2] No such file or directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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