Solved Trouble with WakeOnLan (WoL) using XBMCbuntu
#1
I recently migrated to XBMCbuntu from Mythbuntu.

I appear to be having problem with WoL. WoL itself works great. If the machine is off, I can wake it up.
However, it appears that by having WoL enabled (ethtool), when I shutdown the system, the system immediately restarts! It's as if a magic packet is constantly being sent to the thing.

If I unplug the ethernet cable, shutdown works fine.
If I manually disable the WoL using ethtool after boot, and then shut down, it works fine.

Additionally, I can't seem to force disable WoL upon boot. I tried by adding the following into /etc/network/interfaces under eth0:
Quote:up ethtool -s eth0 wol d
(d = disable)
But after reboot, "g" (enabled) still appears in ethtool.

So the only way I can disable is manually through BIOS. (Ideally I WANT WoL, but not if this auto-reboot stuff keeps happening)

Any idea what would cause WoL to force a reboot upon shutdown?
And any idea what would force it WoL "g" after reboot?
Reply
#2
I may have answered my own question for WHY it's happening. But currently working on debugging how to fix.

It appears I recently switched to a new router, the Asus RT-N56U, with custom firmware. I did a packet sniff on my network and got the following:

% sudo tcpdump -i eth0 udp portrange 9 -n
Code:
...
20:45:30.648896 IP 192.168.1.1.2563 > 192.168.1.255.9: UDP, length 102
20:45:30.662685 IP 192.168.1.1.64030 > 192.168.1.255.9: UDP, length 102
20:45:30.676404 IP 192.168.1.1.12160 > 192.168.1.255.9: UDP, length 102
20:45:30.690081 IP 192.168.1.1.32776 > 192.168.1.255.9: UDP, length 102
20:45:30.703620 IP 192.168.1.1.37256 > 192.168.1.255.9: UDP, length 102
...

Now I need to figure out why it's blasting wake-on-lan packets nonstop. Smile
Reply
#3
May be a longshot, but when your PC is shutdown, try unplugging the power cord from the wall socket, waiting a few minutes, and then plugging it back in. Turn on your PC and retry shutdown (with WOL enabled in BIOS and Ethernet cable attached) to see if it now powers off or if it still reboots.
Reply
#4
Think I got it.
I had a terrible port-forwarding rule in my router:

The rule was: "anything on port 9 ... send to 192.168.1.1 (router) at local port 9."

So if I send ONE magic packet, the router was not only blasting that to 192.168.1.255:9 as shown above, but it must've been looping it back to itself. I removed the rule to forward appropriately (directly to my xbmc box), and restarted the router.

All is good now.
Reply
#5
Cool, glad you got it sorted!
Reply

Logout Mark Read Team Forum Stats Members Help
Trouble with WakeOnLan (WoL) using XBMCbuntu0