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

this wol script does it work with Thibor 12 ?

Discussion in 'HyperWRT Firmware' started by Kamui1407, Jan 17, 2006.

  1. Kamui1407

    Kamui1407 Network Guru Member

    http://www.dslreports.com/forum/remark,13287946
    If I add this to my start up script ?
    Code:
    ip neigh change 192.168.0.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br0
    ip neigh add 192.168.0.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br0
    
    Thx , I try it put it's doesnt work , pc didn't wake :(
     
  2. Thibor

    Thibor Super Moderator Staff Member Member

    ip --help
    BusyBox v1.01 (2006.01.08-17:10+0000) multi-call binary

    Usage: ip [ OPTIONS ] { address | link | route | tunnel } { COMMAND | help }

    ip [ OPTIONS ] OBJECT { COMMAND | help }
    where OBJECT := { link | addr | route | tunnel }
    OPTIONS := { -f[amily] { inet | inet6 | link } | -o[neline] }

    the ip neigh command that you are referring to is compiled in iproute2, ip is compiled in busybox in Hyperwrt
     
  3. Kamui1407

    Kamui1407 Network Guru Member

    Oki thanks ;) then can you convert that script in order to take effect with busybox in HyperWrt ?

    In cisco router for WOL , you must add that
    Code:
    ip nat inside source static udp 192.168.0.255 7 interface ethernet 1 7 
    There is an equivalent command for your firmware Thibor ?
    :)
     
  4. Thibor

    Thibor Super Moderator Staff Member Member

    my next release will have "ip neigh", i removed busybox's ip and use iproute2's instead
     
  5. rljo

    rljo Network Guru Member

    This would be great. I could really use it. Right now, it's the only thing keeping me in dd-wrt.

    Thanks,
    Bob
     
  6. Kamui1407

    Kamui1407 Network Guru Member

    It would be great :thumbup:
     
  7. prowler1968

    prowler1968 Network Guru Member

    I agree, it would be great to have implemented the Wake on Lan or the script for IP NEIGH.

    The lack of a Wake on Lan function is what led me to third party firmwares. I have a WRT54GS Version 4 and the only firmware that I found to work with this version was DD-WRT until I just recently found the Thibor build of the Linksys official source.

    DD-WRT worked well for me during the BETA stages but the final has proven to be very unstable, especially compared to the stock firmware. The HyperWrt Thibor seems stock-stable as well.

    Thanks for your great work, Thibor. When will we see the new build with the Wake On Lan functions integrated?

    ---Wishlist - I have had to use a script to redirect external ports to DIFFERENT internal ports (ie - Forward External port 8000 to internal port 80, etc.). Any way to integrate that into the GUI - DD-WRT has a great implementation of this very function.
     
  8. Thibor

    Thibor Super Moderator Staff Member Member

    the wol build will be done when qwerty's done developing it. with regard to port forwarding to different ports, i have no plans to implement it, but you are welcome to do it, i would add it to the firmware. also, you could look into using fwbuilder(spoiler!!!) as that will simplify the process of iptables greatly
     
  9. iamqwerty

    iamqwerty Network Guru Member

    Agreed - the port forward would be very useful.

    Just one question: What's the difference between Port Forwarding and UPnP Forward in DD-WRT?

    BTW: The WOL code should be ready now - I only need feedback from one user now.
     
  10. Thibor

    Thibor Super Moderator Staff Member Member

    Port forwarding forwards the same port from outside to inside, eg port 2345 external to port 2345 internal. UPnP forwarding does port 2345 external to port 5432 internal
     
  11. prowler1968

    prowler1968 Network Guru Member

    The way the UPNP is implemented in DD-WRT is different than the Thibor build in that you can define UPNP forwards in the GUI in DD-WRT even with UPNP disabled. This way, I can manually define port redirection, ie forward external port 8000 to internal port 80, or whatever other forwards needed.

    My need for doing this in the GUI is to simplify the process. I have multiple machines that need to be configured for Remote Desktop, which by default listens on port 3389. With port forwarding, I could only have 1 machine to listed on the default port. With a configurable port redirection, I could set up many machines (ie forward port 5000 to 3389, 5001 to 3389, etc.) and each forwarded port would be directed to a different internal ip, although on the same port 3389 for Remote Desktop.

    In Hyper-WRT, you cannot define the UPNP settings, you can simply enable or disable the UPNP, and Windows XP must communicate the settings to the router.

    Thibor - could you make the UPNP definable?
     
  12. iamqwerty

    iamqwerty Network Guru Member

    I have the exact same need as prowler1968

     
  13. Thibor

    Thibor Super Moderator Staff Member Member

    you're right qwerty, they are exactly the same thing in dd-wrt. i haven't used it(dd-wrt) in quite some time. but, in Hyperwrt, there is only port range forward and Port Triggering
     
  14. prowler1968

    prowler1968 Network Guru Member

    Thibor - As in Qwerty's post with the DD-WRT screen-shot - could you not modify the port forward to require not only a from but also a to address? This way, if you want to forward FTP port 21 to port 21, you would fill that in, or another program like Remote Desktop, forward port 5000 to 3389? I don't have knowledge of modding the stock firmware, but logically, it would not seem to be a big change as the GUI is only modifying the parameters that are available in text mode which I have done with a firewall script
     
  15. Thibor

    Thibor Super Moderator Staff Member Member

    it's a big change, to the webpages, and to the firewall. Seriously guys, i'm doing this in my spare time as a hobby. so far, the only person to pick up a typewriter here is qwerty. if you really really want these features, do it and i'll include it, or do your own Hyperwrt fork. In the meantime, i'll LOOK into adding it, no promises though
     
  16. prowler1968

    prowler1968 Network Guru Member

    Thibor - Thanks for your comments and open mind to LOOK at this. I did not mean to make light of the work that you do - I have had a very positive experience with your build. I have used DD-WRT for about 2 months but the final build of V23 has been unstable for me - at least compared to my experiences with the BETA versions - for me, the BETAs proved to be more stable.

    I found HyperWRT Thibor only about a week ago - and my experience with it has been very positive so far. HyperWrt to me is as stable as stock firmware, and is flexible. DD-WRT is more flexible than HyperWrt, but at the price of stability. In a perfect world, I would have STABLE DD-WRT --or-- FLEXIBLE HyperWrt, and be extremely happy.

    Thibor - Thank you for your work. Every change you make or incorporate from other's work is appreciated. As for my WISH LIST, thanks for your consideration. Either way, HyperWrt will be my firmware of choice.
     
  17. Kamui1407

    Kamui1407 Network Guru Member

    thx thibor , with Thibo 13C the script and the WOL over Internet works perfectly :thumb:

    great bro :clap: :cheering: :cheer:
     
  18. Thibor

    Thibor Super Moderator Staff Member Member

    glad you approve matey :)
     

Share This Page