1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Unable to forward to a broadcast IP

Discussion in 'Tomato Firmware' started by Omego2K, Jan 27, 2011.

  1. Omego2K

    Omego2K Networkin' Nut Member

    Hello,

    I am using Tomato v 1.28 and WRT54GL. From what I understand Tomato prevents forwarding to the broadcast address, in my case 192.168.1.255. I am trying to get wake on lan working from tools other than the routers web admin. Such as a phone application. In order to do this I need to broadcast the magic packet. I have found online that adding the following to the Init Script would make the broadcast IP 192.168.1.254:

    ip neigh change 192.168.1.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br0
    ip neigh add 192.168.1.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br0

    However, after I added it to the Init script, forwarded port 9 UDP to 192.168.1.254, and rebooted the router. WOL still doesn't work from the internet, but it does work using the tomato web administation. Does anybody have any suggestions on what I might be missing?
     
  2. Engineer

    Engineer Network Guru Member

  3. Omego2K

    Omego2K Networkin' Nut Member

  4. Engineer

    Engineer Network Guru Member

    Yea, not sure. The only difference is the sleep 5 that I have at the top of the script but I don't recall if I really needed that or not. Will think about it and see if I can come up with anything.

    Have you tried to keep the PC awake and sniffed with a packet sniffer to see if you are getting anything from the router when sending a magic packet?
     
  5. Omego2K

    Omego2K Networkin' Nut Member

    So I got it working. I am not sure which of the following things I did differently made it work but the changes were:

    I added the "sleep 5" to the first line of the script and then I shutdown the router instead of just rebooting. After that it just worked. I think either the sleep 5 was needed to block the script for a little bit while the router was doing some other things or rebooting the router doesn't execute the Init.
     
  6. Engineer

    Engineer Network Guru Member

    Great. Like I said above, I don't specifically recall why I added it but if you read through the entire thread that I posted, it wasn't always there. Happy WOLing, LOL.
     

Share This Page