Got it working. I have nothing diagnostic to report, though. I must have factory reset the router 5 times, All the steps were the same. This time it didn't error out on the ARP table stuff.
-Ryan On 10/14/07, Ryan | Speed <[EMAIL PROTECTED]> wrote: > > It's just a one way transmission over layer 2 (mac level) > that incapsulates a small string with the mac address of > the target device. It doesn't use TCP and cannot be directed > to a machine specifically. It's broadcast to every port attached > to the router and all subsequent routers/switches/hubs. > Every active port/pc/device on the network "hears" the packet > and discards it if the mac doesn't match their own. > > Wake on WAN works by sending a UDP packet from the internet, > to a predefined open port pointed towards your internal subnet's broadcast > address, where it is then transformed and broadcasted at the mac level > to the entire network. > > The problem with that is most consumer level routers doing NAT > discard the packet either because they simply cannot handle it, > or the gui does not allow you to forward ports to x.x.x.255 for security > reasons. That's Netgear's excuse anyway. > > The WRT45G I'm working with now running DD-WRT v23 SP2 (09/15/06) std - > build 3932 > is discarding the packet... I believe.. > > Creating the static ARP table which is run on boot is supposed to fix > that problem, but from that error I was getting the settings aren't > taking. > > This is my understanding of how it works, if I'm wrong, someone correct > me. > > -Ryan > > > On 10/14/07, 0x0000 < [EMAIL PROTECTED]> wrote: > > > > > > > > --- Ryan | Speed < [EMAIL PROTECTED]> wrote: > > > > > Has anyone successfully been able to wake up > > > a PC from the internet using DDWRT? > > > > > > I can wake up locally, and I've followed the > > > > > wiki<http://www.dd-wrt.com/wiki/index.php/Wake-on-LAN_%2528tutorial%2529 > > > > > > backwards and forwards. Tried several different web based scripts, > > > but the problem is really with the router configuration. > > > > > > The port forward is setup as follows: > > > Name: WOL | Port Start: 9 | Port End: 9 | UDP only | 192.168.1.250 | > > > enabled > > > > > > It says to not use the x.x.x.255 broadcast address, but to use an ip > > > not in > > > use > > > on the network, hence .250. > > > > > > From there we have the following commands being run at startup by the > > > router: > > > ip neigh change 192.168.1.250 lladdr ff:ff:ff:ff:ff:ff nud permanent > > > dev br0 > > > ip neigh add 192.168.1.250 lladdr ff:ff:ff:ff:ff:ff nud permanent dev > > > br0 > > > > > > Which did nothing, so I changed the ff:ff:ff: mac above to the actual > > > mac > > > of the PC I'm trying to boot, which also did nothing. > > > > > > Running the commands manually yields this as a result: > > > "RTNETLINK answers: No such file or directory" > > > > > > If anyone has any suggestions, please save me from ripping out my > > > hair. > > > > What sort of packet wakes the PC from the local net? You should be > > able to log into the router and ping the PC NIC - would that wake it up > > if the packets originated with the LAN interface side of the router? > > > > > > > > -Ryan > > > > > > > > > > > > > > > > 0x0000 > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CHAOS706.ORG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chaos706?hl=en -~----------~----~----~----~------~----~------~--~---
