NASLite Network Attached Storage

Ok .. could someone smarter than I explain the following output. I have been pontificating about WOL features for months now ... however, now it's my turn to (for the first time) having found a mobo that does not wake with a magic packet, even though a specific option in BIOS is enabled. My sepcific question is: What does "pumbg" (bold-faced red-line is my doing) and "d" mean ? (This output is from "T - Tools and Utilities" / "9 - Show Network Configuration".)

[ Test32 ] - Administration Utility - NASLite-2 USB v2.04 02-2007

NETWORK CONFIGURATION ( 1 of 2 )

Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes

ENTER to continue: >

Thanks,
Georg

Ok ... I've done some research and found my own answers. Maybe this will also help someone else, and the "d" explains why this mobo will not wake !

Here's some info: http://ralien.nytka.org/index.php/2007/02/20/wake_on_lan_in_fedora_core (The strange phenomenon several forum members have experienced with the NIC behaving unexpectedly to WOL.)

And some more: http://www.squarebox.co.uk/cgi-squarebox/manServer/usr/share/man/man8/ethtool.8 (Option "wol" explained way at the end and what the "pumbg" means.)

I also just discovered that v2.05 is now out ... (THANKS ! ... but ...) too bad ... I was going to ask that the following be included (haven't had time to verify that it wasn't ):

Tony / Ralph: please add an option under "Tools & Utilities" via which the user can change the NIC's behaviour by allowing setting of any one or more of the following characters (options): "pumbgd", then upon boot and shutdown reset the NIC to that ethtool setting.

Thanks,
Georg

That's on the list but it didn't make it in 2.05 purely based on oversight. Please accept my apologies for that. The intent is to set WOL at shutdown no matter what. There is no harm in doing so regardless if WOL is being used or not. That way everything should work fine without user intervention. Version 2.06 will include that for sure.

Tony: Thanks ... looking forward to it.
Georg