52 replies to this topic

[braunbär]

Hi. ;-)

 

I'm sorry for this crossposting, but I'm really looking for the information, if the actual openPLi 4 is supporting the WOL-feature of the Duo2.

 

I couldn't find any information about that.

 

Thanks in advance. ;-)

Edited by braunbär, 29 August 2014 - 08:09.

[Erik Slagter]

WOL is something that needs to be implemented in hardware, it's not image-dependent.

[Rob van der Does]

I haven't found an option to activate WOL. So unless I looked wrong or need a plugin, I think the answer is 'No'.
All other images have a dedicated option for this, either on 'deep sleep' (with or without WOL) or in the adapter setup.

[Rob van der Does]

WOL is something that needs to be implemented in hardware, it's not image-dependent.

Actually both. The DUO2 hardware supports WOL, but the image must support it as well.

[littlesat]

What proc does the duo2 uses for wol.... Then I suggest it just needs to be added in system.py or so...

[Rob van der Does]

I really can't help you there.
I only know that in all images I use apart from PLi it works fine.

[Pedro_Newbie]

Maybe this can help?

https://github.com/o...thwol/ethwol.sh

#! /bin/sh
2 #
3 # Set eth0 WOL
4 #
5 # Version: @(#)ethwol 1.00 18-Jul-2013
6 #
7
8 PATH=/sbin:/bin:/usr/sbin:/usr/bin
9
10 #activate WakeOnLAN
11 grep -q 'enable' /proc/stb/fp/wol
12 if [ $? -eq 0 ]
13 then
14 echo [WOL] activate WakeOnLAN at device eth0
15 ethtool -s eth0 wol g
16 else
17 echo [WOL] WakeOnLAN is not enabled
18 fi
19
20 : exit 0

[littlesat]

Bad.... Xtrend is writing there on/off and vu 0, 1 ???

I do not own a vu with wol.... So I cannot verify if it is working.....
.
In xtrend he wol proc is in ./power/wol.... Using on/off inline with other procs...

Is the location correct above.... Does it indeed write 0/1 for Vu?

In fact this is very easy to make... Because the proc is on a different place the differences in the required output could also be managed...but still it is not nice for general coding...

Edited by littlesat, 29 August 2014 - 14:22.

[Rob van der Does]

Yeah, a shame Xtrend didn't follow VU .....
But as the 10k doesn't support WOL anyway (hardware issue), there's no need to code for Xtrend. So it is 'general coding' indeed, as it is only required for the DUO2

[betacentauri]

et7500 supports WOL and it works

Ah, yes I know et7500 is not yet supported by OpenPli.

[littlesat]

Et et10k does support wol.... Only the beta hardware doesn't....
And indeed xtrend did not follow vu here this time....
And indeed pli does not support xtrend 7x00 (yet)

Edited by littlesat, 29 August 2014 - 14:52.

[littlesat]

Ik zie net hier https://github.com/O...9800998ecf8427e
Dat iemand het heeft oogelost op vix... Ik zie dus dat men bij de vu die hier toch wel de uitzondering is enabled en disabled naar de procs schrijft en niet 0 of 1, Dus het zal nog aangepast moeten worden....

Edited by littlesat, 29 August 2014 - 18:57.

[braunbär]

Ok, so the good news seems to me, that my device isn't broken or misconfigured. ;-)

[Rob van der Does]

....Ik zie dus dat men bij de vu die hier toch wel de uitzondering is ....

Ah, OK, now I understand: Xtrend followed VU's example to support WOL, but as they use different parameters makes VU the exception.
Sorry it took me some time to grasp this

[littlesat]

SatKiekerd,

 

Your discussion is endless.... But now my 2 cents..

 

XTrend put a proc under power... VU under stb... One call it on/off the other calls it enable/disable...

 

Both are in fact wrong as the structural place should be somewhere at the hardware interface itself that should support this feature....

 

When you analyse this VIX code

 

 

	
		
			
				- open(SystemInfo["WakeOnLAN"], "w").write(configElement.value and "enable" or "disable")
		
		
			
				+ if getBoxType() in ('et10000', 'gbquadplus', 'gbquad', 'gb800ueplus', 'gb800seplus', 'gbipbox'):
		
		
			
				+ open(SystemInfo["WakeOnLAN"], "w").write(configElement.value and "on" or "off")
		
		
			
				+ else:
		
		
			
				+ open(SystemInfo["WakeOnLAN"], "w").write(configElement.value and "enable" or "disable")
		
	

 

Then only Xtrend and GigaBlue are the exceptions....

 

What other boxes are using the stb proc with enable/disable and have a WOL feature?

 

At least OpenPLi seems to be now compatible with both "incorrect" methods... before VIX was only VU en OpenPLi only Xtrend...

Edited by littlesat, 30 August 2014 - 09:47.

[Rob van der Does]

The GigaBlue Quad, the LX3 and the Atemio Nemesis also have WOL-support. But none of the other PLi-supported boxes have.

[braunbär]

At least OpenPLi seems to be now compatible with both "incorrect" methods... before VIX was only VU en OpenPLi only Xtrend...

Unfortunately, WOL is still not working for me with the actual nightly (31.08.). No chance to wake my Duo2 up with WOL from "Deep Standby".

Edited by braunbär, 31 August 2014 - 15:09.

[littlesat]

IT should work now

Edited by littlesat, 31 August 2014 - 18:55.

[Rob van der Does]

'eotl' = End of TimeLine?

[braunbär]

IT should work now

Is this validated / confirmed?

 

Even with the (now) latest nightly from 01.09. 22:28h it is not working for me.

Tried it with Aquila-WOL (from Sourceforge) and via the webinterface of my AVM Fritz!Box-router.

I also reinstalled OpenPLi and switched WOL under the network-configuration on and off.

Nothing.