induna wrote:
I had the same issue with my Vortexbox. I had to edit
/usr/local/sbin/network_up.sh and add the following 'echo ethtool -s
eth0 wol g | at now + 1 minute' to set the WOL configuration after the
network had started. This is with Fedora 16, so YMMV.
nah that did not work i had
Mnyb wrote:
What surprised me was that it has no memory backup for this ?
I don't think this has much to do with memory.
I surmise either:
a - soft power off mode differs from cold power off in the network card
status
b - when the machine encounters a power failure event, somehow the bios
gets
epoch1970 wrote:
I don't think this has much to do with memory.
I surmise either:
a - soft power off mode differs from cold power off in the network card
status
b - when the machine encounters a power failure event, somehow the bios
gets zapped to a factory config that has the NIC disabled
Hi,
Wol is a complex thing.
its Hard Softwarebased.
So please describe your Network and what Versions / Os you have (with
the problems)
Basic is:
The Bios/UEFI has a Menü - WOL must be enabled.
The Switch/ Router has a Map this MAC Adress is here this Mac
Address is there and that MacAdress is
The server is HP microserver N36L with clear OS 6 beta ( redhat Linux )
WOL is enabled in bios it works for my daily and weekly use , the
problem only occurs after a long time away .
The router is an old linksys wrt54L with tomato firmware there are some
simple Netgear switches in use ( blue
Due to my erratic travel schedule I have no clue to exactly how long I
have to be away = not using the equipment
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
MeridianDSP5200 MeridianDSP5200HC 2
I'd say likely to be the router forgetting the location of the server
due to inactivity. ARP tables etc
QNAP TS419p 4Tb LMS7.6.1
Living Room - SB3 - Onkyo TS606 connected Digitally - Celestion
Ditton F20s - and connected Analogue for Zone 2 - Sony TA FE 320 -
Sennheiser HDR 130
Office - SB3 -
d6jg wrote:
I'd say likely to be the router forgetting the location of the server
due to inactivity. ARP tables etc
But is not wol supposed to work over broadcast ? if i use an utility
where i can manually spec the mac anything on the net with that mac
should wake up ?
But keep the ideas
Mnyb wrote:
Server , computer and squeezeboxes have static network adresses outside
of the routers DCHP pool .
Combined with switches that means that the desktop and the server can
comunicate even when the router is down.
That's why I suspect the NIC in the server as I use etherwake on my
The MAC will disappear from the ARP table after a while. But as you use
the broadcast address this should not be an issue.
Enters power management.
For a few years now PCs which are euro-compliant are mandated to feature
a power off mode ~ 1Wh. Many (all?) machines will reach this level only
Thank's again ! i will read this more carefully when i get home .
Why i wanted to pull the plug was to test if the root cause is that the
server looses its memory , before investigating more complex causes . It
can be that simple as everything works fine ( including wol ) when i'm
around .
One part solved for now ( I must gather more data after a long stay from
home ).
Fact I forgot to mention i use WOL to boot the server it's not ojust the
standby part .
The server NIC can't remember a thing even if remove the power just a
couple of seconds . So power cable must be in even if
Mnyb wrote:
One part solved for now ( I must gather more data after a long stay from
home ).
Fact I forgot to mention i use WOL to boot the server it's not ojust the
standby part .
The server NIC can't remember a thing even if remove the power just a
couple of seconds . So power cable
induna wrote:
I had the same issue with my Vortexbox. I had to edit
/usr/local/sbin/network_up.sh and add the following 'echo ethtool -s
eth0 wol g | at now + 1 minute' to set the WOL configuration after the
network had started. This is with Fedora 16, so YMMV.
Really ? I'll check my
Mnyb wrote:
Really ? I'll check my configuration , I have something similar already
so WOL is working but it was years since I've done that .
Do your vbox handle the total loss of power case ?
Yes, it does. I believe that the problem was a timing issue. Although
the WOL setting was correct,
induna wrote:
Yes, it does. I believe that the problem was a timing issue. Although
the WOL setting was correct, it was being applied before the network
interface loaded and wasn't taking effect after cold boots, but did take
effect after warm boots. The work-around re-applies the proper
Mnyb wrote:
Interesting it could be hardware dependent too I can't remember my old
server doing this .
In fact I will check even closer it was so long ago that I migth
remember it wrong , my old server needed some script a long these lines
to even to do a varm boot ! I'll check if my
This is a strange one . I don't actually expect to solve it but
plausible explanations would be nice .
WOL works fine for me , with one exception if I've been away for some
weeks ( work usually ).
It does not work I have to manually fire up the server once then all is
fine indefinitely until
18 matches
Mail list logo
