Wake On Lan: what am I doing wrong?

Discussion in 'Tomato Firmware' started by Yuval, Sep 3, 2012.

  1. Yuval

    Yuval Serious Server Member

    Hello! First time poster here, kindly tell me if I am doing something wrong and how can I do it better, thank you for your patience.

    I was a DD-WRT user. Bought a new router (E4200v1) and decided to give Tomato a try. Flashing was easy and the basics work. I am running Tomato Firmware v1.28.9011 MIPSR2-RAF-NCC-VLAN K26 USB VPN-NOCAT

    The one thing I could not get to work is WOL.

    When I enter the following two lines in the SSH command line, it works, but when I enter them in the web interface Administration -> Scripts -> Firewall, it does not:

    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

    querying the status in the shell, `ip neigh show` yields

    192.168.1.254 dev br0 FAILED

    instead of what it should yeild:

    192.168.13.254 dev br0 lladdr ff:ff:ff:ff:ff:ff PERMANENT

    What am I doing wrong and how can I fix it?

    Thanks
     
  2. Rehan

    Rehan Serious Server Member

    I am having the same issue myself. I am running Tomato v1.28.7498 MIPSR2-Toastman-RT K26 USB Ext.

    If inside a SSH terminal I manually type in:

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

    I get:
    RTNETLINK answers: No such file or directory

    and when I type in:
    ip neigh add 192.168.1.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br0

    that works. Do I only need that second command in my init scripts or do I still need both? Thank you.
     
  3. Rehan

    Rehan Serious Server Member

    Ok, I figured it out,

    I had it set to sleep 5 seconds before starting this script. I've now changed it to sleep 15 before doing it. Also OP, I'm adding my lines to Administration -> Scripts -> Init

    Here is what I'm using now:
    sleep 15
    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

    and it is once again working.
     
  4. Yuval

    Yuval Serious Server Member

    Thank you Rehan. sleep 15 solved my problem. It's in Administration -> Scripts -> Firewall on my router.

    To the experts / developers: Is it so that the scripts are run too early / before the interfaces are up and running? If so, shouldn't the firmware take care of this automatically?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice