Wake On Lan

Sorry for the extremely late reply, as I've only just upgraded one of my NAS to OS6, but I do have a similar configuration to CharlesR so I thought I'd put in my 2p.

In my experience, It's necessary to create/add your sources to XBMC/Kodi (Not scraping, just defining the media sources) with the bond/teaming in place. WOL in XBMC/Kodi is done via MAC address as you'd expect, but it also binds that MAC to the IP/path of the source and will only attempt to wake that particular MAC even if others exist for other sources on the same server. If you want/need to check the configuration, you can check the wakeonlan.xml file in Kodi/XBMC's userdata folder. Also, the "Wake Remote Servers On Access" setting in Kodi/XBMC must be enabled. I was going to post a sample, but as as I sit here typing this, it turns out the desktop (used for Kodi/XBMC add-on testing) hasn't created the file, and all my other machines are off. Will edit this post when I can post a sample.

To put this to bed I installed the OpenELEC Beta on my Chromebox and now WoL works great (using bond on the NAS).

With XBMC you create a SMB share via the IP address and tell it to use WOL... simply a selection. I'm not sure what my app uses but it works when both are listed as the same IP address and I click on either one to wake up.

I do know it has worked with most if not all in the past including the RN series, Ultra 2, 4, Pro 2, etc.

UPDATE: I got the Windows version to work!! I deleted the SMB share and recreated it. Perhaps it had old values from a previous configuration. I'll try the same with the OpenELEC version. OpenELEC version still isn't working... hopefully when the next version is ported to OpenELEC it will. The Windows version is a newer Beta version and I don't want to update the OpenELEC install until it's out of Beta.

Can you specify ethernet broadcast with your WoL app, or do you have to specify the IP address? Normally WoL uses ethernet broadcast. That ensures that the packet will reach the NAS even if the mac address isn't the mac address tables in the switches.

Per the first post... Adaptive Load Balancing

I just tried removing the bond and rebooting the NAS. Didn't make any different... no luck. However the WOL app still works. I'm not sure but I think perhaps I tried when I first installed it (before trying the bond) and it didn't work... perhaps it's just not compatible hardware/software with XBMC. I have been trying via OpenELEC (Linux). I'll try the Windows version of XBMC and see if it behaves the same way.

The Windows Kodi/XBMC Beta version doesn't work either... the WOL app does work with one or two lines so obviously it's possible just not something Kodi/XBMC can handle for some reason...

CharlesR wrote:
...Per the docs (I don't believe) based on the bond method the switch doesn't have to be configure uniquely.

Which bonding method are you using?

Marto73 wrote:
A test. Can you use one Ethernet cable only. I'm wondering whether you have enabled teaming/ bonding on the mating switch?

I'm going to test with just one line and I'll post the results. Per the docs (I don't believe) based on the bond method the switch doesn't have to be configure uniquely. Here's how my Wake On Lan app see it...

192.168.1.102 Ultra6Plus.wp.comcast.net xx-1F-33-EA-F5-34 Netgear Inc. Unknown
192.168.1.102 Ultra6Plus.wp.comcast.net xx-1F-33-EA-F5-35 Netgear Inc. Unknown

Normally you won't see any performance gain with only one user. Teaming generally needs to ensure in-order packet delivery end-to-end, so each data flow usually ends up on a single ethernet cable.

Charles,
A test. Can you use one Ethernet cable only.
I'm wondering whether you have enabled teaming/ bonding on the mating switch?

Regards, Marto