On 7/24/06, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>
> On Mon, 24 Jul 2006, Bruno Buys wrote:
>
> > This is odd: I can ether-wake my desktop from another computer on my
home
> > lan, but I can´t ether-wake it while ssh´ing to my gateway from an
outside
> > computer (win pc at work). However, I can ether-wake another sarge
machine
> > running in a abit+athlon with via-rhine eth card. Why is that?
> > The system is a sarge machine, the eth card is an onboard via
gigabit
> > (via-velocity module), in a abit/sempron desktop. The gateway is a
coyote
> > linux p1, if it matters.
> > Thanks for any inputs!
> >
> > bruno
> >
>
> etherwake uses ARP/raw ethernet packets, you need to be on the
local LAN
> and sometimes same switch to wake up your box
But am I not on the same local lan when I am logged via ssh to my
gateway
192.168.0.1? The desktop that doesn´t wake is 192.168.0.3 . The one that
does wake correctly is 192.168.0.5.
> if you're on the network + same switch, make sure your BIOS is setup
> correctly.
The computer wakes up correctly when I ether-wake it inside the lan,
so, I
guess this eliminates this possibilty?
This is a home lan, very small, there´s only one 8-port switch:
internet --- > cable-modem ---> coyote linux gateway ---> desktop1
---> desktop2
> Justin.
>