WOL over internet help

[Engineer]

Originally posted by: JackMDS
At this point it is starting to turn into Video type of argument (nVidea - ATI. etc.).

Nah, I have no real preference. I used HyperWRT for 3 years and loved it. Using Tomato right now and love it. I would say that DD-WRT is great too....just has more features than I "think" I need, lol! :laugh:

As long as it works, doesn't matter one bit to me.

Oh, and I own both ATI and nVidia...as well as AMD and Intel...and they all work great to me. Give me the cheapest that does what I need and I'll bite!

 

[Gillbot]

Originally posted by: Engineer

Originally posted by: JackMDS
At this point it is starting to turn into Video type of argument (nVidea - ATI. etc.).

Nah, I have no real preference. I used HyperWRT for 3 years and loved it. Using Tomato right now and love it. I would say that DD-WRT is great too....just has more features than I "think" I need, lol! :laugh:

As long as it works, doesn't matter one bit to me.

Oh, and I own both ATI and nVidia...as well as AMD and Intel...and they all work great to me. Give me the cheapest that does what I need and I'll bite!

Same here, I'm not overly brand loyal. I am VERY cheap, LOL! I may try tomato or DD-WRT and see what happens though after two bad flash attempts with DD-WRT, i'm hesitant.

 

[Gillbot]

Well, Tomato it is. I had one successful test on one machine, the others will not work yet. DD-Wrt bricked it again so the hell with DD-Wrt. It took me an hour to get it back to life so I tried Tomato and it flashed fine.

Hopefully I'll figure out why it's only working on one machine and get it sorted out.

 

[Gillbot]

Tomato installed, added IP's with MAC into the table, Forwarded ports to the appropriate system and still a no go. Worked once, never to work again.

 

[Gillbot]

No other thoughts?

On a side note, I got a VP6 running XP using an intel network card. WOL header is hooked to mobo but WOL won't work. All settings in OS and BIOS are set up for WOL but nothing. GAH, WOL is wearing me thin.

 

[JackMDS]

I am not actively familiar with Tomato thus I do not know its roll in this issue.

However the whole thing is strange, at this Point I would try another Router.

 

[Gillbot]

I've updated my WTB thread already, this is just frustrating because all the online "fixes" do nothing or only work intermittantly.

 

[JackMDS]

Originally posted by: Gillbot
I've updated my WTB thread already, this is just frustrating because all the online "fixes" do nothing or only work intermittantly.

This is a better device than the Linksys as is.

Takes well DD-WRT if needed.

Right now $34.99 after rebate free ship.

http://www.newegg.com/Product/...x?Item=N82E16833320023

 

[Engineer]

Originally posted by: JackMDS

Originally posted by: Gillbot
I've updated my WTB thread already, this is just frustrating because all the online "fixes" do nothing or only work intermittantly.

This is a better device than the Linksys as is.

Takes well DD-WRT if needed.

Right now $34.99 after rebate free ship.

http://www.newegg.com/Product/...x?Item=N82E16833320023

I can vouch for that router too. It's been very good (I'm running one of these as well as a version 2.0 WRT54G). I'll try to set up a WOW situation (using one of the websites to send the magic packet) and see what happens.

Edit: I just set up two of my PC's for WOL and used your website (located in OP) to wake up each with no issues.

Steps (for each PC):

1. Enable WOL in the "Advanced Settings" tab of the Network card in Device Manager. Right click on the network card, select properties, select "Advanced" and then set WOL to allowed and type (Magic Packet in this case).


2. Enable the network card to wake the PC from the "Power Management" tab for the network card in Device Manager. Right click on network card, select properties, select "Power Management" and select "Allow this device to wake the computer".

3. Reboot the PC and enter BIOS. Select <Enable> for WOL for each. Save BIOS.

4. Reboot each PC and then set to "suspend". Edit: I turned off each PC and then attempted a WOL (WOW), and all worked well. Each PC proceeded to turn on and boot after the magic packet (information below).

5. Entered router (Asus router running Tomato 1.23) from another PC and set each of the other two PC's (already asleep) to a static IP using the MAC address of the network card of the respective PC (set under STATIC DHCP). Note, using STATIC DHCP, the PC still has automatic IP enabled and received a fixed IP as well as DNS, etc. information from the router. No need to set the IP/DNS/etc. to fixed in each individual PC.

6. Proceeded to forward port 7 to one of the PC's and Port 1 to the other PC. Set both port 1 and 7 to UDP forwarding in the respective PC forwards.

Note: Make sure that you select "SAVE" at the bottom of each tomato page before leaving the respective page. I have made the mistake of leaving the page after "Add" (ing) the static IP's, etc. without "SAVING" to the routers memory.

7. Proceeded to the magic packet webpage. Entered IP (of cable modem - found in router status) and used IP Subnet of 255.255.255.255 (to force exact match of PC to send to and not send to "range" of PC's on the cable company's network) and then entered port 7 or port 1. Tested each individually and both woke fine.

Hope this somehow helps. I know that I tested this "locally" but it should not matter as the webpage that you list is not local in transmitting the magic packet to my network. Should be the same as if you were remotely transmitting the magic packet yourself.

 

[mxnerd]

To OP and Jack:

I try to understand whether the WOL over internet sholud be configured like this.


on router (192.168.100.254)

UDP 1111 fowarded to 192.168.100.101 UDP port 7, mac address (11:22:33:44:55:66)
UDP 2222 fowarded to 192.168.100.100 UDP port 7, mac address (11:22:33:44:55:77)
UDP 3333 fowarded to 192.168.100.169 UDP port 7, mac address (11:22:33:44:55:88)

And at http://www.depicus.com/wake-on-lan/woli.aspx

you should enter info like

Your Network Cards Mac Address (one of the above mac addresses)

Any Computers Ip Number or FQDN subdomain.dyndns.org

Your Subnet Mask 255.255.255.0

Any Port Number 1111/2222/3333

 

[spidey07]

Even on that site it instructs you that you need to enable directed broadcasts on the router.

That's what 192.168.1.255 means - it's an IP broadcast which is turned also into a LAN broadcast on that subnet.

 

[Engineer]

Originally posted by: spidey07
Even on that site it instructs you that you need to enable directed broadcasts on the router.

That's what 192.168.1.255 means - it's an IP broadcast which is turned also into a LAN broadcast on that subnet.

The router doesn't allow the xxx.xxx.xxx.255 (broadcast all on lan) ip. The only work around for that (that I've seen) is setting subnet to 255.255.255.128 and then send to xxx.xxx.xxx.127 (IP) which will then broadcast to all on the lan.

 

[mxnerd]

Originally posted by: spidey07
Even on that site it instructs you that you need to enable directed broadcasts on the router.

That's what 192.168.1.255 means - it's an IP broadcast which is turned also into a LAN broadcast on that subnet.

I have ASUS 500gp running DD-WRT v24. But I don't see an option like that.

 

[Engineer]

Originally posted by: mxnerd

Originally posted by: spidey07
Even on that site it instructs you that you need to enable directed broadcasts on the router.

That's what 192.168.1.255 means - it's an IP broadcast which is turned also into a LAN broadcast on that subnet.

I have ASUS 500gp running DD-WRT v24. But I don't see an option like that.

I don't think you get to select it. From what I can understand, if you enter a broadcast IP ending in 255, it will send the packet to every PC in the IP range (i.e. if you enter 192.168.0.255, it will send the packet to every PC from 192.168.0.1 to 192.168.0.254). However, the routers that I have played with will not let you enter a forwarded port to xxx.xxx.xxx.255....they cut off at 254. Maybe I'm missing something.

 

[mxnerd]

Well. After reading all of this, I think WOL over internet is not really that easy.

Maybe turn on DD-WRT remote management, then log into the DD-WRT, and use the DD-WRT built-in WOL function to wake up one of the machines is the easier way.

 

[JackMDS]

WOL entails Computer that is totally Off and its Network Card is capable to stay on the Network and start the computer when it geta a Magic Packet.

Option 1. Using a Router hat has a Magic Packet programed in.

In such case the Router (or the firmware) has to provide info about how to trigger the WOL from the outside (Internet).

Option 2. The Router has No Magic Packet Capacity.

In such this case the solution is to use this, http://www.depicus.com/wake-on-lan/wake-on-lan-gui.aspx

This util send the packet over the Internet and the Router needs to broadcast it into the Network.

Th MAC address in this util. has to be the MAC address of the Network card in the computer that need to be wake up.

P.S. Currently there is No wy to do WOL with Wireless Client Card, the computer must be connected with wire.

 

[Engineer]

Originally posted by: JackMDS
WOL entails Computer that is totally Off and its Network Card is capable to stay on the Network and start the computer when it geta a Magic Packet.

I did not realize that the PC had to be "totally off" (I had only ran the test earlier with it in suspend mode) so I turned on port forwarding again and turned off one of the PC's that I had did a WOL (actually WOW) on earlier and tried it again. Sure enough, it turned on and booted. Really cool stuff!

 

[spidey07]

Originally posted by: mxnerd
Well. After reading all of this, I think WOL over internet is not really that easy.

Maybe turn on DD-WRT remote management, then log into the DD-WRT, and use the DD-WRT built-in WOL function to wake up one of the machines is the easier way.

It is easy. You just have to understand the concepts and I honestly don't know much about WOL, just the 30 seconds scanning your link.

You need to allow subnet directed broadcasts on your router. The "magic packet" must reach it's destination and that destination is a broadcast. The internet doesn't do broadcasts and a router stops broadcasts and most all do not allow a directed broadcast, you have to specifically tell it to allow/forward it.

 

[mxnerd]

Originally posted by: spidey07

Originally posted by: mxnerd
Well. After reading all of this, I think WOL over internet is not really that easy.

Maybe turn on DD-WRT remote management, then log into the DD-WRT, and use the DD-WRT built-in WOL function to wake up one of the machines is the easier way.

It is easy. You just have to understand the concepts and I honestly don't know much about WOL, just the 30 seconds scanning your link.

You need to allow subnet directed broadcasts on your router. The "magic packet" must reach it's destination and that destination is a broadcast. The internet doesn't do broadcasts and a router stops broadcasts and most all do not allow a directed broadcast, you have to specifically tell it to allow/forward it.

OK. So let's say DD-WRT has the following settings. can you fill last line for me?

Forwards

APPS From Protocol IP Address to
------------------------------------------------------------------
UVNC 5500 TCP 192.168.1.20 5500
SMTP 25 TCP 192.168.1.20 25
POP3 110 TCP 192.168.1.20 110


WOL1 1111 UDP 192.168.1.111 7
WOL2 2222 UDP 192.168.1.112 7
WOL3 3333 UDP 192.168.1.113 7
WOLBroadcast

P.S. I really hope anand can change the forum software to phpBB or vBulletin ASAP. This FuseTalk really sucks.

 

[Gillbot]

4. Reboot each PC and then set to "suspend".

This step shouldn't be needed. The WOL should awaken the PC from a completely off state. Everything works 100% fine locally for all machines (except the VP6, I haven't sorted it out locally yet). The problem is the packets aren't "getting through" the router.

Well. After reading all of this, I think WOL over internet is not really that easy.

Maybe turn on DD-WRT remote management, then log into the DD-WRT, and use the DD-WRT built-in WOL function to wake up one of the machines is the easier way.

This works 100% also, but do you really want to leave your router and thus, entire network open for everyone?

I have tried the 255.255.255.128 trick to no avail, and upgraded to Tomato firmware. Neither have allowed success, other than it working sporatically. If you use the packet monitor utility, you can see the packat arriving because the IP is active. When the machine is off, with the MAC forwarded to the IP, the machine will not wake.

 

[Engineer]

Originally posted by: Gillbot

4. Reboot each PC and then set to "suspend".

This step shouldn't be needed. The WOL should awaken the PC from a completely off state.

Yes, see my updated statement after reading JackMDS's post (a few posts back). I didn't realize that it would "wake" from OFF, and just tried suspend. It did work with OFF also. Both PC's have worked fine so far.

 

[mxnerd]

Originally posted by: Gillbot

Well. After reading all of this, I think WOL over internet is not really that easy.

Maybe turn on DD-WRT remote management, then log into the DD-WRT, and use the DD-WRT built-in WOL function to wake up one of the machines is the easier way.

This works 100% also, but do you really want to leave your router and thus, entire network open for everyone?

Turn on HTTPS for management, use a different port than 80, then setup DD-WRT so the info site needs password to view. And use a strong password. Then no one can easily hack into our DD-WRT router.

Still waiting spidey07's answer.

 

[Gillbot]

Originally posted by: mxnerd

Originally posted by: Gillbot

Well. After reading all of this, I think WOL over internet is not really that easy.

Maybe turn on DD-WRT remote management, then log into the DD-WRT, and use the DD-WRT built-in WOL function to wake up one of the machines is the easier way.

This works 100% also, but do you really want to leave your router and thus, entire network open for everyone?

Turn on HTTPS for management, use a different port than 80, then setup DD-WRT so the info site needs password to view. And use a strong password. Then no one can easily hack into our DD-WRT router.

Still waiting spidey07's answer.

I have in the past, I'd still prefer not to though. It makes no sense as to why it wont work though.

Engineer,
did you de-delect the option to allow the card to be turned off to save power?

 

[Engineer]

Originally posted by: Gillbot

Engineer,
did you de-delect the option to allow the card to be turned off to save power?

Gillbot,

I just checked and it was still "checked" on the Vista PC. Will check on the XP machine shortly.

From your previous post, if you leave the PC on with a packet sniffer, you can see the magic packet arrive at that particular PC every time? If so, this just doesn't make sense...especially since it works locally per your post.

Are you letting your PC's get the IP/DNS/etc (through DHCP) from the router or have you set them locally in each PC?

Do you (by chance) have the "Only allow management stations to bring the computer out of standby" checked? I do not and don't think that WOW will work if it is checked (well, not unless you're the network admin and are sending the magic packet directly, from what I can get out of it).

 

[Gillbot]

All machines I want to use WOL on have a manually set IP address.

With the machines on, I can see the magic packet arriving if it is sent locally or through the depicus site.

I'll need to double check the other setting but on mine, I was told to unckeck the "allow this decide to be turned off" portion. Maybe I need to re-enable that, though I fail to see how that would make a difference. It has to be something in the router not allowing it through properly when the machine is powered off.