1.9.0 - WDR3600 - wol

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

Post Reply
Swimmer
Posts: 48
Joined: Tue Mar 05, 2013 10:36 am

1.9.0 - WDR3600 - wol

Post by Swimmer »

Hey there,

I'm testing my TP-link wdr 3600 (N600) with Gargoyle 1.9.0 and I found a glitch in the matrix.

WOL isn't wotking (and I really need it).

Can I assist you with correcting this bug? if so, how?
Proud owner of Gargoyle in
  • Tp-Link TL-WR1043N
  • Tp-Link TL-WDR3600
  • Linksys WRT1900ACS

ispyisail
Moderator
Posts: 5180
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: 1.9.0 - WDR3600 - wol

Post by ispyisail »

I had problems as well

If you want to help, install Openwrt and try WOL

if that works then the problem is with gargoyle

my 2 cents worth

mates
Posts: 128
Joined: Mon Nov 14, 2011 7:53 am

Re: 1.9.0 - WDR3600 - wol

Post by mates »

Do you have windows 10 or windows 8.1 ?

if yes than turn off FAST BOOT and try different drivers from station-driver ... because drivers from windows not working with wol properly, also latest realtek drivers is not OK. I am using i v10.4.814.2015 this one it is working for me.

but maybe you have another problem

Swimmer
Posts: 48
Joined: Tue Mar 05, 2013 10:36 am

Re: 1.9.0 - WDR3600 - wol

Post by Swimmer »

No. I'm using Linux...
Proud owner of Gargoyle in
  • Tp-Link TL-WR1043N
  • Tp-Link TL-WDR3600
  • Linksys WRT1900ACS

CarpeNoctem
Posts: 51
Joined: Fri Mar 06, 2015 11:15 am

Re: 1.9.0 - WDR3600 - wol

Post by CarpeNoctem »

For what it's worth, WoL ain't working for me either. Running it on WNDR3800CH

ispyisail
Moderator
Posts: 5180
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: 1.9.0 - WDR3600 - wol

Post by ispyisail »

I've had problems with this feature in the past.

But yesterday I confirmed it to be working with 1.9.x

It appears that the problem is with the client setup

https://en.wikipedia.org/wiki/Wake-on-L ... _operation
Troubleshooting magic packets[edit]
Wake-on-LAN can be a frustrating technology to implement. This is because it requires appropriate BIOS, network card and, sometimes, operating system and router support to function reliably. In some cases, hardware may wake from one low power state but not from others. This means that due to hardware issues the computer may be waking up from the "fully off state" (S5) but doesn't wake from sleep or hibernation or vice versa. Also, it is not always clear what kind of magic packet a NIC expects to see.
In that case, software tools like a packet analyzer can help with Wake-on-LAN troubleshooting as they allow confirming (while the PC is still on) that the magic packet is indeed visible to a particular computer's NIC. The same magic packet can then be used to find out if the computer powers up from an offline state. This allows networking issues to be isolated from other hardware issues. In some cases they also confirm that the packet was destined for a specific PC or sent to a broadcast address and they can additionally show the packet's internals.
In Windows Vista and higher, one can also determine how the OS was powered up. Running the powercfg.exe /lastwake command in a CMD prompt will list the "Wake Source". The Wake-on-LAN event should also be logged in the System event log.[11]

Post Reply