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

WDS with HyperWRT v2.1b1

Discussion in 'HyperWRT Firmware' started by Toxic, Feb 22, 2005.

  1. Toxic

    Toxic Administrator Staff Member

    This document has been compiled by Celeron (linksysinfo user) who has stumbled upon a great feature for HyperWRT


    How to configure HyperWRT 2.1b1 with WDS

    Like many, I was running Sveasoft's Satori firmware. Unfortunately, the Satori firmware cotains a lot of features that I didn't need, nor want. Also, the addition of said features into the Linksys web based GUI was not exactly what I would call attractive or user friendly. Lastly, I wanted to be running on the latest Linksys codebase, not code from many months ago.

    Enter HyperWRT 2.1b1. This firmware adds only a few, very helpful features and it is based off the most current Linksys codebase. Check out HyperWRT for more information. Configuring WDS on HyperWRT is fairly straight forward and only requires a few steps.

    **Note, this document assumes you are starting with a factory default configuration**

    [hr:f355f3e563]
    To install HyperWRT I followed the following procedure:

    1. I pressed the reset button, located on the back of the router, until the power LED started flashing.
    2. After the router rebooted I went to the GUI at 192.168.1.1. From here I selected Administration --> Firmware Upgrade, browsed to the HyperWRT image and flashed the router.
    3. Next, I pressed the reset button on the back of the router until the power LED started flashing.
    4. Once the router rebooted the router was ready to be configured.

    Here's my topology:

    Cable Modem---WRT54G(A) (((--WDS+WEP--))) WRT54G(B)

    On both routers the following needs to be configured:
    1. Under the Wireless --> Basic Wireless Settings configuration be sure to set the following items to the same on both routers:
    a. Wireless Network Mode (I selected G-Only as I have no B devices)
    b. Wireless Network Name (SSID)
    c. Wireless Channel

    2. Under the Wireless --> Wireless Security configuration be sure to set the following items to the same on both routers:
    a. Security Mode **Note, I could only get WEP to work with WDS, not WPA**
    b. Default transmit key
    c. WEP Encryption
    d. Passphrase (Then press generate)

    3. Next, you need to determine the wireless MAC address of each router. To do this goto Status --> Wireless. The MAC address will be the first item listed. Write these down for future reference.

    On WRT54G(A) the following needs to be configured:
    1. Under Administration --> Management --> Startup enter the following (where BB:BB:BB:BB:BB:BB is the MAC address of the wireless on WRT54G(B):
    a. wl lazywds 0
    b. wl wds BB:BB:BB:BB:BB:BB
    Click Save and close.

    On WRT54G(B) the following needs to be configured:
    1. On the Setup --> Basic Configuration page be sure to set the following:
    a. Configured the LAN IP address to something different than the address on WRT54G(A) such as 192.168.1.2
    b. Turn off the DHCP server
    2. Under Administration --> Management --> Startup enter the following (where AA:AA:AA:AA:AA:AA is the MAC address of the wireless on WRT54G(A):
    a. wl lazywds 0
    b. wl wds AA:AA:AA:AA:AA:AA
    Click Save and close.

    Now, just reboot each router. You can use the "Reboot" button on the Administration page. That's it. Simple isn't it?

    If this works for you, please let me know at agensler@gmail.com.

    [hr:f355f3e563]
     
  2. eheh

    eheh Network Guru Member

    Thanks for your instruction!
    I have 2 WRT54GS, I will try it.
    I have just one question about the speed you get between 2 computers for example, one on the first 54G, and the other PC on the second 54G, on a file transfer?
    Thx!
     
  3. sylikc

    sylikc Network Guru Member

    eheh,

    I read somewhere that the speed of a WDS link is effectively half of whatever you had before. So assuming you have the GS with 108Mbps, the raw transfer rate would be 54Mbps. Add in some overhead of collision detection on a multiple-access wireless link, and I'd say you get about 60~70% of that for real throughput. I don't have a GS device myself, only the normal WRT54G.


    --

    Toxic,

    That's a nice and easy setup instruction for HyperWRT. Now, I think I might drop the bloat on my sveasoft firmware for HyperWRT cuz all I'm using is WDS :eek:

    Anyhow, I read somewhere that WPA does not work with ANY WDS implementation as of yet (including Belkin's F5D723x, which didn't say it in its documentation). I killed all my initial attempts at WDS cuz I thought it'd work with the more robust security of WPA 8O



    /sylikc
     
  4. Toxic

    Toxic Administrator Staff Member

    WDS does cut the bandwidth in half but the WRT54GS is not 108Mb router

    it is only a 54g with aprox 30% extra if it connects to other Linksys GS devices.

    I dont know however if Speedbooster works over WDS :)

    All thanks goes to Celeron.
     
  5. sylikc

    sylikc Network Guru Member

    Ooops, that's right. I often mistaken the GS as the 108Mbps router. :oops:

    Anyhow, I read somewhere about WDS setups trying to use speedbooster. I have it set to ON in my sveasoft setup and I haven't noticed any improvement or loss, so to the very least, it won't kill your setup. :wink:


    /sylikc
     
  6. jinjimbob

    jinjimbob Network Guru Member

    Nice, but any idea why you couldn't get WPA to work?
     
  7. tap0utt

    tap0utt Network Guru Member

    is it me or does this method of wds not work for gs?

    i can wds via other methods with hyperwrt, but not through startup command.
     
  8. eponymous

    eponymous Network Guru Member

    For what it's worth I used a similar approach to set up WDS with WEP between my WRT54GS and my wife's AirPort Express. The main difference in my method was that I started the telnet daemon and telnetted in to use wl instead of using the startup command facility. My changes via telnet do persist through router reboots, power outages, etc. so it seems that changes made through the wl command are stored in the non-volatile portion of the router's memory. Believe it or not the lazywds setting was restored to 1 (on) when I recently restored factory defaults during my HyperWRT upgrade but the MAC address I had entered for regular wds persisted. Strange.
     
  9. eheh

    eheh Network Guru Member

    Thank you!
    So the WDS mode cut off half the 54Mbs BW, and it's a little too slow for me :?
    Would the "client" mode be better ? (found in sveasoft release for the moment, hope in the hyperwrt later?)
     
  10. Celeron

    Celeron Network Guru Member

    I wasn't sure if HyperWRT saves settings entered into a telnet session after the router is reset. By doing it in the startup script it is turned on everytime and thereby ensures that LazyWDS (allows ANY AP to create a WDS link to your network, not a good idea) is turned off. Also, using the startup script removes the necessity of turning on the telnet daemon and entering the configuration. This approach is just easier over all.

    For what its worth, you shouldn't even need HyperWRT to create a WDS link to your Airport Express. If I'm not mistaken LazyWDS is turned on by default in the latest Linksys firmware and thereby allows the AE to connect to the WRT54G without and special firmware.
     
  11. Celeron

    Celeron Network Guru Member

    No, not really. It didn't work when I tried it so I didn't expend much effort into getting it to go. I already had WEP working and I was satisfied with that.
     
  12. Celeron

    Celeron Network Guru Member

    I can't see any reason why this wouldn't work with a GS router. The commands are the same. Entering in the start up script simply executes the command everytime the router boots up. What does your startup script look like?
     
  13. eponymous

    eponymous Network Guru Member

    Agreed. Just pointing out that wl settings are written to nvram. You could enter them through the command prompt facility in the HyperWRT web interface instead of telnet or startup and they should still work and persist.

    Also true, however I have the same feeling about LazyWDS that you do. I don't think it is a good idea for numerous reasons. And I use HyperWRT instead of the Linksys firmware for other reasons as well. I do intend to play around with WDS and WPA since I know the AX supports it (it's documented). Is the Linksys firmware (and therefore HyperWRT) supposed to do WDS with WPA?
     
  14. eponymous

    eponymous Network Guru Member

    RECANT! WL COMMANDS DO NOT PERSIST!

    I'm hereby recanting my previous statements and urging everyone to follow Celeron's instructions regarding putting the wl commands in the startup script!

    My settings certainly seemed to have persisted previously but after several reboot tests tonight I found that lazywds was being set back to 1 (on) after a reboot. I have since added my wl commands to the startup script as Celeron recommends!
     
  15. hyerstay

    hyerstay Network Guru Member

    I couldn't get this to work with a pair of GS units unless one was running Alchemy. I think I might need a way to disable SpeedBooster/Afterburner in HyperWRT to get this working on the GS units. I would prefer to use HyperWRT over Alchemy since I don't need extra features besides power control and WDS.

    Any tips?

    Thanks,

    jason
     
  16. Celeron

    Celeron Network Guru Member

    The "wl" command has an option to set the "gmode". One of those options is Afterburner. You can try setting it to "GOnly" and seeing if that works.

    You shouldn't have to run Alchemy to get this going. Heck, I got it running with one router running HyperWRT and the other running the stock Linksys firmware. Try entering this command:

    "wl gmode GOnly"

    I don't have a GS router so I can't test it. Let me know if it works for you.
     
  17. hyerstay

    hyerstay Network Guru Member

    This is what happens:

    # wl wds 00:17:12:05:AB:BC
    eth1: Invalid argument
    wds Set or get the list of WDS member MAC addresses.
    Set using a space separated list of MAC addresses.
    wl wds xx:xx:xx:xx:xx:xx [xx:xx:xx:xx:xx:xx ...]


    Any explanation? I've tried typing the mac address in lowercase and it makes no difference.

    Thanks,

    jason
     
  18. eponymous

    eponymous Network Guru Member

    This can reportedly be caused by the router being set to use afterburner. WDS does not work with afterburner enabled. Try the following...

    # wl gmode

    Make sure it is not set to afterburner (6). If it is...

    # wl gmode 1

    A subsequent wl gmode should now tell you you are set to auto (1)

    In theory you should now be able to use your wl wds command now. I say in theory because I tried several permutations on the above and things still wouldn't work for me. I finally did...

    # nvram show | grep gmode

    ...and found that wl_gmode and wl0_gmode were still set to 6 (I believe only the wl0_xxx settings are really in use).

    I ended up using nvram set to set wl0_gmode=1, wl0_wds=<MAC ADDRESS>, and wl0_lazywds=0 followed by nvram commit and a reboot.
     
  19. commanderberti

    commanderberti Network Guru Member

    hi i have 2 wrt54gs V1.1 and its running... (without switching of SpeedBoster)...
    what HW revision do you have ? is it running now with switch off speed booster ?
    regards..


     
  20. JackHambabo

    JackHambabo Network Guru Member

    WDS with Siemens Repeater

    Hello,

    I consider buying a WRT54G. I could get a Siemens Gigaset Repeater for cheap money.
    Is it possible to get the Siemens Gigaset Repeater which should support WDS to work with the HyperWRT WDS?
    Is there no WDS support on the standard WRT54G firmware?

    Very many thanks,
    yours Jack
     
  21. Avenger20

    Avenger20 Network Guru Member

    Re: WDS with Siemens Repeater

    No, and I actually doubt they will add it.

    If they would put WDS in the WRT54G (like repeater, bridge, ...), nobody would buy their WAP54G, WET54G(S), WRE54G, which are more expensive then the WRT54G
     
  22. rickyd

    rickyd Network Guru Member

    Works great, but, shell question

    I followed the instructions, and works great - 2 WRT54Gs talking to each other; great coverage throughout the house now

    But, a simple, and I'll preface that I'm am not familiar with router commands, or with unix.

    I entered the wl commands into the startup script as instructed, and apparently they are working. But, I tried to enter some simple wl commands into the command shell. They all fail with a not found. So, how do I know that the wl wds commands are actually working as they should?
     
  23. Toxic

    Toxic Administrator Staff Member

    what commands are you trying to send. linux usally works like this,

    if it works is says nothing, if a command is wrong then it reports an error.
     
  24. rickyd

    rickyd Network Guru Member

    I tried the wl commands in the script, i.e. --> wl lazywds 0

    Not sure this is even a valid test.
     
  25. dellsweig

    dellsweig Network Guru Member

    The reason they fail with a not found is that the wl command must not be in the PATH for the shell. You can type the full pathname /usr/sbin/wl

    This forces the shell to execute the wl command in the /usr/sbin directory
     
  26. hellstrom

    hellstrom Network Guru Member

    I have set up one of my clients with hyperwrt and wds. All other clients and the master AP are using sveasoft Alchemy.

    The reason I did this was becuase that client uses the v2.2 hardware which seems to be unstable with Alchemy.

    With Alchemy the real time is set automatically with an NTP server.

    How does it work with hyperwrt? I have set the time zone but under status the time is not available.

    thanks for any answer

    Micke
     
  27. rickyd

    rickyd Network Guru Member

    Kinda figured that, so, I just added the path info in front of the commands.
     
  28. Avenger20

    Avenger20 Network Guru Member

    WPA over WDS should normally work. You just got to let the 'nas' driver (that's broadcom's driver that handles WPA) know.
     
  29. kubark42

    kubark42 Network Guru Member

    I get the exact same error on a WRT54GSv1, also. However, before you think too much of this, I warn you that I have NOT reset the router as detailed in the instructions. (It's on the building's rooftop and I haven't got a key.)

    I'll go get a key tomorrow and tell you guys how it works out. In any case, I've got a spare WRT54G sitting around, so I should definitely be able to do some interesting tests.
     
  30. badboyndsu

    badboyndsu Network Guru Member

    I got this working with a v1.0 WRT54G as the base and a v2.2 WRT54G as the extension following the instructions exactly except for the WEP part. It's running open right now. I want to try use MAC address filtering first, and then play with WEP and WPA.
     
  31. rickyd

    rickyd Network Guru Member

    Works fine with 2, version 2 54g's and WEP and MAC filtering ( using the same MAC filters on both routers) . Haven't tried WPA yet, but will soon.
     
  32. badboyndsu

    badboyndsu Network Guru Member

    Update: Running with MAC address Filtering and WPA TKIP, wired and wireless through the extension.
     
  33. Cassius

    Cassius Network Guru Member

    I get a strange problem when I enter thse commands in the Start up script.

    Mine seems to be th opposite to everyone elses.

    WRT54G will function flawlessly in WDS if i enter teh commands in the telnet daemon, however when i add these same commands to the start up script it doesnt seem to work.

    After putting it into script and pressing save, i cannot ping the other router or any machines connected to the other router, although when i check the settings ( ie type wl wds ) it says i am connected to it....

    Very strange
     
  34. xtrvd

    xtrvd Guest

    I was wondering, in the case of application port forwarding, does all of the forwarding only need to be done through Router A, or does B have to be set-up somehow also?

    Thank you,

    Xtrvd
     
  35. nvpbrown

    nvpbrown Network Guru Member

    Two suggested changes to the HOWTO

    I had Sveasoft installed on my 2 WRT54G's, but got tired of the instability. I was able to get WDS up and running according to the HOWTO. Two suggestions:

    (1) It doesn't appear to be necessary that the two routers have the same SSID (network name). I am configuring separate SSIDs in my house, with each system connecting to the nearest router.

    (2) The one problem I had getting it working was that I used the *wired* connection's MAC address, which was the first one that showed up when I clicked on the status tab. I would guess this is a common error -- it would be worth emphasizing that the *wireless* MAC address is the one you need to enter.

    HyperWRT works great so far.
     
  36. nomsspam

    nomsspam Guest

    Refuses to accept MAC addres, problems parsing

    I always get this error when I try to put in the MAC address for my 2nd AP:

    Problem parsing MAC address "0011245c8cc1".
    wds Set or get the list of WDS member MAC addresses.
    Set using a space separated list of MAC addresses.
    wl wds xx:xx:xx:xx:xx:xx [xx:xx:xx:xx:xx:xx ...]


    Previously when I typed "wl wds" it would list all the MAC addresses. But now it's just blank. And when I tried to re-enter the MAC addresses it just gives me the above error.

    I tried resetting the router, setting back to factory defaults, and I even reflashed the firmware. Nothing seems to resolve that error.

    Need help. :(
     
  37. Nick666

    Nick666 Network Guru Member

    WDS Problem

    I got one strange problem:

    I'm working with two WRT-Routers (WRT54G V2, WRT54GS V1). Both with HyperWRT 2.1b.
    I installed the script as described and it works fine with WEP enabled.
    But as soon as I change a parameter in the WRT54GS (e.g. enable/disable QoS/DHCP or change whatever parameter) I can't get the wds-connection back (menas: I cant get a connection to the GS-router or to the internet)!
    I tried several reboots and re-entered the startup script with no effect.
    Only when I connect with my W-LAN card direct to the GS and change the transmit power (and so far it only works with this parameter!!) to whatever value (it could even be lower) the wds-connection will be back.
    This is very strange to me. I'm not dreaming ;) and I can provoke this behavior at any time as described above.
    I can only provoke the behavior when I change a parameter in the GS. I can play around with the G-router with no effect on the wds-connectivity.
    And I can only re-establish the wds-connection when I change the transmit-power in the GS-router.

    My assembly:

    my PC --wired-- WRT54G --WDS-- WRT54GS --Internet/PCs
     
  38. Celeron

    Celeron Network Guru Member

    Re: Refuses to accept MAC addres, problems parsing

    Are you entering the MAC address with the colon? You need to have that in there. For example, using the address you listed above, you need to enter:

    wl wds 00:11:24:5c:8c:c1

    Is that what you are entering?
     
  39. Celeron

    Celeron Network Guru Member

    Re: WDS Problem

    Have you tried setting the GS router to G mode only, thereby turning off Afterburner? Try entering this command and see if it helps:

    "wl gmode GOnly"
     
  40. Celeron

    Celeron Network Guru Member

    You only need to enter the port forwarding on the router connecting to the internet. Because Router B doesn't have anything connected to its WAN port configuring the port forwarding here wouldn't do anything.
     
  41. imageroc

    imageroc Network Guru Member

    WDS accepts clients?

    When using WDS with two routers.
    Are both routers able to have wireless clients?
     
  42. dellsweig

    dellsweig Network Guru Member

    Re: WDS accepts clients?

    YES

    If you set up both routers on the same channel and give both the same SSID, you will be able to freely roam throughout the covered area. The client will associate with whichever AP has the better signal..
     
  43. imageroc

    imageroc Network Guru Member

    How?

    I was wondering how you got WPA To Work I tried but no luck. did you do something special
     
  44. Nick666

    Nick666 Network Guru Member

    Re: WDS Problem

    In both routers the "Wireless Network Mode" in the web frontend is set to "G only".
    When I entering the command "wl gmode" in the GS it says "54g Auto (1)".
    I set it to "wl gmode GOnly" but the problem persists.
     
  45. fixmacs

    fixmacs Network Guru Member

    MAC Filtering, WPA, and Repeaters

    According to Linksys KnowledgeBase doc 2088, MAC filtering does not work when using any repeater with the WRT54G or WRT54GS. According to the documentation, the clients connected to the repeater are not seen by the gateway/router, thus any computer may connect to the repeater station even if specifically blocked by the gateway access point. The main access point sees only the repeater MAC, not any MACs associated with clients connected to the repeater.

    Are you sure MAC filtering is working along with WDS using HyperWRT?

    Regarding WPA encryption, the stock Linksys firmware does not support it in "repeater" mode. Only WEP is supported. I am curious to get confirmation on WPA functionality with HyperWRT in WDS mode.

    I agree with Avenger regarding the unlikelihood that Linksys will ever support WDS in its firmware because that would lead to an immediate loss of sales of the pricey WRE54G. According to Linksys KnowleBase, the WRE54G works with the WRT54G, WRT54GS, and the WAP54G, Also, the WAP54G works as a repeater only for the WRT54G and other WAP54Gs (not the WRT53GS), according to Linksys.
     
  46. Celeron

    Celeron Network Guru Member

    Re: MAC Filtering, WPA, and Repeaters

    WRT54Gs running WDS are not in repeater mode. They are both in infrastucture AP mode which means MAC filtering works just fine.
     
  47. rickyd

    rickyd Network Guru Member

    Re: How?

    I didn't have to do anything special to get WPA running. I was using WPA with only 1 router. Installed the second, and went WDS and WEP ( because of the reported problems with WPA ). A few days later I just re-enabled WPA on both routers. Works great. Be sure to use the same WPA key on both routers.
     
  48. thoalex

    thoalex Network Guru Member

    Hey, I had some weirdness that I thought someone might be able to explain to me.

    When I logon to the web admin and I go to the status page, my MAC address for my router/s is:

    00:12:17:0E:3A:AD
    00:06:25:A2:D2:41

    but when I go to the command window and type in /usr/sbin/wl wds on each router I'll get

    00:12:17:0E:3A:AE
    00:06:25:A2:D2:42

    which is what I have to use to get this to work (it works by the way and it's fantastic).

    So, what's going on? Any ideas?

    Thanks
    Thoalex
     
  49. dellsweig

    dellsweig Network Guru Member

    The second set of MAC's are the WIRELESS radio MAC address. The first is the Hardware address of the router
     
  50. thoalex

    thoalex Network Guru Member

  51. Celeron

    Celeron Network Guru Member

    I have confirmed that HyperWRT with WDS does in fact work with WPA without any extra work. This is what I did.

    1. I have my WDS up and running per my instructions on the main page.
    2. In WRT54G(B) I configured WPA, pre-shared key. Save settings.
    3. In WRT54G(A) I configured WPA, pre-shared key to the same value. Save settings.
    4. I waited for WRT54G(A) to come back up, then I power cycled WRT54G(B).

    All is well, WDS is up and running with WPA. Life is good.
     
  52. Celeron

    Celeron Network Guru Member

    Well, on second thought, it seems the reliability of WPA when using WDS is not all that great. I had the link between my routers go down twice in that past 20 minutes. I would recommend sticking with WEP.
     
  53. thoalex

    thoalex Network Guru Member

    I had one problem with this and I'm curious as to how others have gotten around it (or if it's an issue). My default route on my internal WDS router isn't being set properly. Actually, it's not being set at all.


    My routing table on the internal WDS router is:


    192.168.0.0 * 255.255.255.0 U 0 0 0 br0
    127.0.0.0 * 255.0.0.0 U 0 0 0 lo

    I had to put the following in my startup script:

    route add default gw 192.168.0.1

    but this isn't the right way to handle this is it?

    I'm kinda working two different posts here (sorry). I didn't think this was a WDS issue until I investigated it further so there's other information here:

    http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&p=14312#14312
     
  54. thoalex

    thoalex Network Guru Member

    My problem is solved. The laptop that I was using to test was running PeerGuardian and it was giving me problems.
     
  55. Rosebud

    Rosebud Network Guru Member

    HyperWRT 2.1b1 with WDS not working with WRT54GS V1.0

    I have spent several hours meticulously following the instructions to set up two WRT54GS V1.0 units flashed with HyperWRT 2.1b1, long rebooted configured for WDS but I cannot get the two devices to talk to each other. The instructions for the startup script are so simple, and I have triple verified the proper use of the wireless mac address for each unit, but cannot ping the other unit after entering the startup script and re-booting. The first line should be "wl lazywds 0" the last parameter is zero?

    I have verified functional hardware connections and configuration in standard access point mode, so I am puzzled why the startup script does not work for me, unless it is just this hardware version that does not work?

    Is there way such as telnet to manually check the startup commands are being accepted and configured properly? Since others have found this basic setup works on the WRT54G, I don't know why the WRT54GS V1.0 unit would not work.

    Perhaps I have missed something, but I would like to try any suggestions.
     
  56. imageroc

    imageroc Network Guru Member

    Re: HyperWRT 2.1b1 with WDS not working with WRT54GS V1.0


    I had One WRT54GS 1.0 and WRT54G, I put them in WDS mode with no problems everything worked great . So I took Back my WRT54G to the Store And exchanged it For A WRT54GS v1.0.

    Now I have Two WRT54GS 1.0 And I haven't Been Able To get them to talk To each other(NO WDS), so I dont think its the startup script thats not working for you its probaly the models we got :(

    In this thread someone said to turn off Speedbooster I think they called it afterburner and that might be the problem I haven't tried it yet becasue I dont know how but if anybody knows how to turn off speedbooster please inform us

    thanks:)
     
  57. Rosebud

    Rosebud Network Guru Member

    WDS with WRT54GS V1.0

    I have explored a few more items related to attempting to get two WRT54GS V1.0 units to talk with each other via WDS.

    I started a telnet session as follows:

    BusyBox v0.60.0 (2005.02.18-17:50+0000) Built-in shell (msh)
    Enter 'help' for a list of built-in commands.

    # wl gmode
    54g Mode is 54g Auto (1)

    This seems to indicate that I am not in the afterburner mode which is option 6

    It seems to turn lazywds off OK

    #
    # wl lazywds 0
    #

    However when I try to set up the WDS link I get this message:

    # wl wds 00:0F:66:A9:3E:96
    eth1: Invalid argument
    wds Set or get the list of WDS member MAC addresses.
    Set using a space separated list of MAC addresses.
    wl wds xx:xx:xx:xx:xx:xx [xx:xx:xx:xx:xx:xx ...]


    checking an earlier post on this topic, I check the nvram variables:

    #
    # nvram show | grep gmode
    startup_script=wl gmode 1
    wl0_gmode=6
    wl_gmode=6
    command_cmd=wl gmode
    size: 18438 bytes (14330 left)
    wl_gmode_protection=off
    wl0_gmode_protection=off
    #
    #

    this seems to suggest for some reason I am still in the afterburner mode which apparently will not work with WDS

    When I attempt to change this parmeter I get the following error:

    # wl nvset wl0_gmode=1
    eth1: Invalid argument
    nvset set an nvram variable
    name=value (no spaces around '=')

    It seems that the problem may be due to these nvram parameters being set to 6 which is the afterburner mode, but I don't seem to be able to change them "1"

    If I understood the poster which had this working both wlgmode and wl0_gmode need to both be set to "1" to get this to work. Any ideas where the eth1: invalid argument is?

    I tried nvget to get the value of Wl0_gmode but this variable did not seem to be recognized.

    Willing to try further suggestions.
     
  58. Rosebud

    Rosebud Network Guru Member

    WDS on WRT54GS V 1.0

    I have made a little more progress.

    I have been able to set the parameters and save them.

    wl0_gmode=1
    wl_gmode=1

    BusyBox v0.60.0 (2005.02.18-17:50+0000) Built-in shell (msh)
    Enter 'help' for a list of built-in commands.

    # nvram show | grep gmode
    startup_script=wl gmode 1
    wl0_gmode=1
    wl_gmode=1
    wl_gmode_protection=off
    size: 12231 bytes (20537 left)
    wl0_gmode_protection=off
    #

    I know I have the afterburner turned off now however I still cannot get the wds command and mac address setting to work

    # wl0_wds=00:0F:69:A9:3E:66
    wl0_wds=00:0F:69:A9:3E:66: not found
    #

    also the following command does not appear to be accepted

    # wl0_lazywds=0
    wl0_lazywds=0: not found
    #
    #

    Any ideas? Not sure why this is not found.
     
  59. Toxic

    Toxic Administrator Staff Member

    Re: WDS on WRT54GS V 1.0

    why are you adding the _ and = to the wl command?

    wl0_wds=00:0F:69:A9:3E:66 < WRONG
    wl0_lazywds=0 < WRONG

    afaik it should be

    wl wds 00:0F:69:A9:3E:66
    wl lazywds 0

    read the initial post

    On WRT54G(A) the following needs to be configured:
    1. Under Administration --> Management --> Startup enter the following (where BB:BB:BB:BB:BB:BB is the MAC address of the wireless on WRT54G(B):
    a. wl lazywds 0
    b. wl wds BB:BB:BB:BB:BB:BB
    Click Save and close.

    On WRT54G(B) the following needs to be configured:
    1. On the Setup --> Basic Configuration page be sure to set the following:
    a. Configured the LAN IP address to something different than the address on WRT54G(A) such as 192.168.1.2
    b. Turn off the DHCP server
    2. Under Administration --> Management --> Startup enter the following (where AA:AA:AA:AA:AA:AA is the MAC address of the wireless on WRT54G(A):
    a. wl lazywds 0
    b. wl wds AA:AA:AA:AA:AA:AA
    Click Save and close.
     
  60. Rosebud

    Rosebud Network Guru Member

    The basic instructions supplied for the WRT54G just don't seem to work with the WRT54GS V 1.0 units that I have. A few other posters in this thread have reported the same behaviour, so I don't believe I am alone in my difficulty with the WRT54GS and WDS with this firmware version.

    The only hint of the problem seemed like it may be related to the afterburner mode in the GS version.

    My obeservations are identical to those posted by eponymous on Monday February 28th. I have been able to successfully turn afterburner mode off as was described, and also set the parmeters described in that post. It still does not work after trying these changes unfortunately.

    Imageroc also reported the same difficulty on March 24 with a version 1.0 units not working, and he had a version 1.0 working with WDS to a WRT54G unit earlier.

    I have the following commands in the start up script

    wl gmode 1
    wl lazywds 0
    wl wds 00:0F:66:A9:3E:96

    It does not work with this, even if you leave the first line.

    If I try the same commands via telnet I get the following:

    BusyBox v0.60.0 (2005.02.18-17:50+0000) Built-in shell (msh)
    Enter 'help' for a list of built-in commands.

    # wl lazywds 0
    #
    # wl wds 00:0F:66:A9:3E:96
    eth1: Invalid argument
    wds Set or get the list of WDS member MAC addresses.
    Set using a space separated list of MAC addresses.
    wl wds xx:xx:xx:xx:xx:xx [xx:xx:xx:xx:xx:xx ...]

    #
    #

    Whatever the cause of the difficulty is, I do not believe it is the result of not trying the basic instructions outlined at the beginning of the thread.

    I do appreciate the attempt to assist.
     
  61. Toxic

    Toxic Administrator Staff Member

    try
    wl gmode 2

    that is 54g only

    gmode 1 is auto and may by default, enable afterburner
     
  62. imageroc

    imageroc Network Guru Member

    For all the trouble



    Well I solved my problem I took a different route but I got my routers working in WDS mode.
    Once again I went to the store bought a WRT54G V 2.2 and took back one of my WRT54GS V 1.0

    So now I got a

    internet == WRT54GS V1.0 == WDS+WEP== WRT54G V2.2

    Working great !!!! w/Mac filter

    The only thing I had to do different form everybody else which I mentioned before on this forum is enable ssid maybe because there two different models I dont know, but it works great and it took minutes to setup.

    Rosebud I really would recommend getting at least one WRT54G v 2.2
    and taking one of those V1.0 's back. Compared to the trouble your having with the V1.0 I'm thinking your problem will be solved much quicker if you go the same route I did. If not Good Luck on geting those damn V1.0's working.
     
  63. dellsweig

    dellsweig Network Guru Member

    Re: WDS with Siemens Repeater

    The default WRT54G firmware does in fact do Lazy WDS so the Linky repeater will work with it. You cannot get to a command shell to issue commands in the default Linky firmware to make a WRT54G into a repeater - you need third party firmware to do this.
     
  64. imageroc

    imageroc Network Guru Member

    This is a long shot question

    This question might be alittle crazy but I was wondering???
    When in WDS mode is there any way to find out the singnal strength between the two routers like a real client program would?Another way of putting it is there a program that would survey and show ssid networks and signal strength of Networks in the area using just the hyperwrt router and not an actual client?.

    Reason I ask this question is My WDS is Very Stretch out

    First : this is my setup


    internet == WRT54GS V1.0 == WDS+WEP== WRT54G V2.2


    MY house : internet == WRT54GS V1.0 is at my house

    IN between : == WDS+WEP

    Neighbors house (two houses away):== WRT54G V2.2

    Now My neighbor can get my connection and can surf very fast and smoothly(then again I only had this setup for a few hours now it could change and begin to die out)
    But I have no idea what the singal strength is at my neighbors house,between the two routers. Now I know I could just go over with a laptop and WifI card and use netstumble to find the singnal strength but it would not be the actual signal the Router is picking up from my home router, it would only be what the laptop signal and they have bad built in anntennas compared to the router


    Extra info:

    I'm doing this with no extra DbI anntenas just he factory one that come with the router and power up to 53mW on both routers.

    Well there's probably not a program out there for this but if there is by luck, please let me know:

    thanks for viewing:)
     
  65. Rosebud

    Rosebud Network Guru Member

    WDS with WRT54GS V1.0

    Thanks for the suggestion. I gave this a try but just could not get them to talk. Reverted back to Satori and both WDS and client mode work fine, so it may be that the implementation of WDS in the current HyperWRT beta release may not be robust depending on the version of hardware. It has something to do with the current firmware and setup for sure.

    Note to Imageroc:

    Glad to hear you have your system working. After going through this little experiment, I noticed there is a telnet command called rrsi which returns the signal strength. You might want to give that a try first. Signal strength is displayed on the wireless status page in Satori, but as I have discovered, this may lead to a lot more effort that expected. Best of luck.
     
  66. jagboy

    jagboy Network Guru Member

    well if your neighbor can get internet and still surf at very fast speeds then i guess the singal is pretty good. howmany walls are between your neighbors router and yours
     
  67. Broertje

    Broertje Guest

    Ajustable transmit power in HyperWRT 2.1b1

    Hi, i have downloaded today the HyperWRT 2.1b1 and upgrade de WRT54G. It works great ! But a question;
    I have set the transmit power to 100% (84 mW)
    But you also do manual setting en set the mW higher.
    What is de maximum ? Is het possible to blow up the output transmitter when you set the power to high ?

    Bye Bye Danny
     
  68. pharma

    pharma Network Guru Member

    Re: Ajustable transmit power in HyperWRT 2.1b1

    Try a forum SEARCH on the words power transmit. You will find some informative posts on the topic -- below is one where someone asked the same question as you:

    http://www.linksysinfo.net/modules.php?name=Forums&file=viewtopic&t=2125&highlight=power+transmit

    Pharma
     
  69. bigrig

    bigrig Network Guru Member

    No success with two GS v1.1 and 2.1b1. :disgusted:
     
  70. Toxic

    Toxic Administrator Staff Member

    Re: Two suggested changes to the HOWTO

    SSID has to be the same for WPA to work in Alchemy or DDWRT firmware. however i dont know if WPA works on hyperwrt firmware.
     
  71. bigrig

    bigrig Network Guru Member

    Also, any suggestions would be appreciated! :wink:

    Apparently imageroc and rosebud had the same problems trying to use two GS's. I'm using DD-WRT right now for WDS, but it seems to lock up once a day.

    Thanks,

    Matt
     
  72. digitalamish

    digitalamish Network Guru Member

    OK, very basic question here. Has anyone had any experience getting two v3 WRT54G's connected via WDS using the 2.1b1 firmware? I followed the orginal instructions, and didn't get it to work after triple checking everything, and I wanted to make sure there were no known problems with that version before I dropped into a shell to see what is going on.

    d
     
  73. kyrules

    kyrules Guest

    I am running WDS with two v3 WRT54Gs and the 2.1b1 hyperwrt firmware.

    Did you make sure that MAC addresses are from wireless status window not from local/router status window?
     
  74. digitalamish

    digitalamish Network Guru Member

    Thanks. I can now confirm that WDS run on the v3 routers. My 'quirk' was in the timing of the reboots of the routers. Eventually I figured out that if I reboot the A router, I need to wait a few seconds and reboot the B router. For some reason the B router wouldn't reconnect if I just rebooted the A router. Even if I let them sit for a few minutes. Oh well.

    Thanks for the writeup on WDS, and thanks for the excellent work on the firmware. My challenge now is to get these two routers to work over 500yards apart, through some houses, using cantennas.
     
  75. mfer

    mfer Network Guru Member

    Well I bought a second WRT54G and configured it with the hyperwrt guide. It works perfect for what I wanted. I now have an excellent connection upstairs and my ps2 is wired to the wrt and working perfectly. Remember that WDS only cuts your lan speed in 1/2 (I actually only saw a 1/4 cut). That doesn't affect the speed of your internet connection, just transfers between lan systems. I still connect to the internet at 2.5 - 3 megs.

    http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=2946

    I used the guide above. FYI, for all you newbies like me..here's some more instuction from what I found.

    **Note, this document assumes you are starting with a factory default configuration**

    To install HyperWRT I followed the following procedure:

    1. I pressed the reset button, located on the back of the router A, until the power LED started flashing.
    2. After the router rebooted I went to the GUI at 192.168.1.1. From here I selected Administration --> Firmware Upgrade, browsed to the HyperWRT image and flashed the router.
    3. Next, I pressed the reset button on the back of the router until the power LED started flashing.
    4. Once the router rebooted the router was ready to be configured.
    5. I set the lan ip of router A to 192.168.1.4
    6. From a cmd prompt type ipconfig /release then ipconfig /renew on your workstation
    7. I plugged router B into the uplink port on router A
    8. I went to the GUI at 192.168.1.1 and reset router B to factory config and installed hyperwrt firmware
    9. Reset router B and set lan ip to 192.168.1.5
    10. Turned off DHCP Server on router B
    11. Then I followed the rest of the steps below

    I don't know if all these steps are correct or necessary, I'm going through them from memory. It worked great for me...seems like reboots help a lot throughout the process

    Here's my topology:

    Cable Modem---WRT54G(A) (((--WDS+WEP--))) WRT54G(B)

    On both routers the following needs to be configured:
    1. Under the Wireless --> Basic Wireless Settings configuration be sure to set the following items to the same on both routers:
    a. Wireless Network Mode (I selected G-Only as I have no B devices)
    b. Wireless Network Name (SSID)
    c. Wireless Channel

    2. Under the Wireless --> Wireless Security configuration be sure to set the following items to the same on both routers:
    a. Security Mode **Note, I could only get WEP to work with WDS, not WPA**
    b. Default transmit key
    c. WEP Encryption
    d. Passphrase (Then press generate)

    3. Next, you need to determine the wireless MAC address of each router. To do this goto Status --> Wireless. The MAC address will be the first item listed. Write these down for future reference.

    On WRT54G(A) the following needs to be configured:
    1. Under Administration --> Management --> Startup enter the following (where BB:BB:BB:BB:BB:BB is the MAC address of the wireless on WRT54G(B):
    a. wl lazywds 0
    b. wl wds BB:BB:BB:BB:BB:BB
    Click Save and close.

    On WRT54G(B) the following needs to be configured:

    2. Under Administration --> Management --> Startup enter the following (where AA:AA:AA:AA:AA:AA is the MAC address of the wireless on WRT54G(A):
    a. wl lazywds 0
    b. wl wds AA:AA:AA:AA:AA:AA
    Click Save and close.

    Now, just reboot each router. You can use the "Reboot" button on the Administration page. That's it. Simple isn't it?
     
  76. Avenger20

    Avenger20 Network Guru Member

    Re: Two suggested changes to the HOWTO

    Will work. You'll just have to disable speedbooster (via nvram). I'll make a speedbooster on-off button in the next 3.x release
     
  77. wayer

    wayer Guest

    WDS w/ HyperWRT. Do your remote router's ports work?

    I've got two WRT54G's hooked as outlined in this forum:

    Cable Modem---WRT54G(A) (((--WDS+WEP--))) WRT54G(B)

    Wireless connection works great connecting to both (A), and (B), and the 4 ethernet ports on the back of (A) work fine.

    However, if I connect to the ports of the remote router (B), my machine is served a DCHP address, and can connect to the internet for about 30 seconds, then the connection fails.

    If I reboot the (B) router, I get another aprox 30 seconds of connection.

    Do other folk's remote (WDS) router's ports work?

    Thanks,

    wayer
     
  78. mfer

    mfer Network Guru Member

    Did you turn off DHCP server on the second router?
     
  79. Traveller

    Traveller Network Guru Member

    Hey all,

    I just setup a WPA-PSK AES-encrypted WDS point to point-link between 2 v1.0 WRT54GS's, running HyperWRT_2.1b1_GS. It's actually pretty straightforward, if you're familiar with the inner workings of the units. BTW: WDS only halves throughput if you use an AP with 1 radio, like the WRT54G(S), on the far end of a WDS-link to connect clients which need to talk to something on the other side of that WDS-link. The radio will have to repeat all data in that case. If you only connect to the LAN-ports on both sides, WDS is about as fast as regular AP -> client. I'm currently pulling around 20 Mbit/sec over a distance of around 2 KM with this setup, using external directional antenna's.


    Here's my setup:

    LAN <---> WRT54GS 1 <----WDS----> WRT54GS 2 <---> LAN

    Start out by factory-defaulting and configuring basic IP on both units. Also configure wireless for the desired channel and SSID. Make sure you select "G-only" wireless mode. Enable WPA-PSK, choose AES for encryption and select a strong pass-phrase. I always change the "Group Key Renewal"-interval to 600 seconds. Under "Advanced Wireless", you could tweak antenna and power-settings. It's best to keep the wireless settings identical on both units. Once everything works, you can backup your settings and start playing with them. Locking the transmission-rate to the highest possible value sometimes improves throughput. Under "Administration -> Management" you could turn off UPnP, enable HTTPS and "Wireless Access Web".

    One of the first things you need to know to set up WDS, is the MAC-address of the wireless interface for all units participating. This can be found in the web-interface, under "Status -> Wireless".

    Let's assume:

    WRT54GS 1: 00:0F:66:11:11:11
    WRT54GS 2: 00:0F:66:22:22:22

    These are the settings I will use in my example below:

    SSID: Test
    WPA PSK: SuperSecret

    And now for the good stuff. Let's start by configuring WRT54GS 1:

    Under "Administration -> Management", click the "Firewall"-button and paste the following into the window, then click "Save" at the bottom:

    -----------------------------------------------------
    # Some NVRAM presets.
    nvram set wl_mode=wds
    nvram set wl0_mode=wds
    nvram set wl_lazywds=0
    nvram set wl0_lazywds=0
    nvram set wl_afterburner=off
    nvram set wl0_afterburner=off
    nvram set wl_afterburner_override=0
    nvram set wl0_afterburner_override=0
    nvram set wl_wds=00:0F:66:22:22:22
    nvram set wl0_wds=00:0F:66:22:22:22

    # No lazywds.
    wl lazywds 0
    -----------------------------------------------------

    Now close the "Firewall Script"-window and, still under "Administration -> Management", click the "Startup"-button. Paste the following into the window and click "Save" at the bottom:

    -----------------------------------------------------
    # Authenticate WPA-PSK encrypted WDS-interfaces.
    nas4not lan wds0.2 up auto aes psk 'SuperSecret' 'Test'
    -----------------------------------------------------


    That's it for WRT54GS 1. The config for WRT54GS 2 is identical, except for the MAC-address for WDS. Each unit uses the other unit's MAC-address. For clarity, here it is:

    Under "Administration -> Management", click the "Firewall"-button and paste the following into the window, then click "Save" at the bottom:

    -----------------------------------------------------
    # Some NVRAM presets.
    nvram set wl_mode=wds
    nvram set wl0_mode=wds
    nvram set wl_lazywds=0
    nvram set wl0_lazywds=0
    nvram set wl_afterburner=off
    nvram set wl0_afterburner=off
    nvram set wl_afterburner_override=0
    nvram set wl0_afterburner_override=0
    nvram set wl_wds=00:0F:66:11:11:11
    nvram set wl0_wds=00:0F:66:11:11:11

    # No lazywds.
    wl lazywds 0
    -----------------------------------------------------

    Now close the "Firewall Script"-window and, still under "Administration -> Management", click the "Startup"-button. Paste the following into the window and click "Save" at the bottom:

    -----------------------------------------------------
    # Authenticate WPA-PSK encrypted WDS-interfaces.
    nas4not lan wds0.2 up auto aes psk 'SuperSecret' 'Test'
    -----------------------------------------------------


    That's it. Reboot both units and they should start talking to eachother. Some notes about the configuration above:

    This is a WDS-only configuration. All AP-functionality is disabled. The units won't accept clients and won't even send out any beacons, as far as I can tell. It's identical to the WAP54G "bridge-mode". If you need to connect clients, change the first 2 NVRAM-parameters in the example above to:

    nvram set wl_mode=ap
    nvram set wl0_mode=ap


    The latest wireless drivers and NAS allow for some pretty neat tricks. You can setup multiple WPA-PSK encrypted WDS-links and use a different encryption, pass-phrase and SSID for any of the WDS-links and AP-mode, for example. I won't go into too much details at the moment, but if you use the above configuration in AP-mode, with clients, you should be able to change the "Wireless Security"-parameters in the web-interface to anything you want, as long as it's WPA. The clients will use those settings and the WDS-link will use the settings you pasted into to "Startup"-window as the `nas4not' command-line.

    Good luck and for anyone who tries, please post any results and questions.



    Grtz,

    Traveller
     
  80. Avenger20

    Avenger20 Network Guru Member

    Thanks Traveller.
    The multiple WPA-PSK encrypted WDS-links look pretty cool.
    I'm sure going to give that a try!
     
  81. Traveller

    Traveller Network Guru Member

    Hey Avenger20,

    Here's some more info. "notify_nas()" in "router/rc/network.c" has some useful info on how `nas4not' should be called:

    char *argv[] = {"nas4not", type, ifname, action,
    NULL, /* role */
    NULL, /* crypto */
    NULL, /* auth */
    NULL, /* passphrase */
    NULL, /* ssid */
    NULL};

    type: Not entirely sure what this does. You'll always want to use "lan" for now.

    ifname: The WDS-interface you're authenticating.

    action: "up" or "down".

    role: "authenticator", "supplicant" or "auto". Using "auto", the link-partners negogiate who's going to play which role.

    crypto: Which crypto to use. Can be "tkip" or "aes".

    auth: Authentication-method to use. Only WPA-PSK is supported on WDS-links at the moment, AFAIK, so always use "psk".

    passphrase + ssid: Obvious. Note that the SSID's are actually used in the WPA authentication-process, so they need to match on both sides of the link, just like the passphrase.


    If you look at "notify_nas()", you'll also notice that it tries to use "get_wds_wsec()" (from "router/shared/nvparse.c") to fetch the WPA-configuration for multiple WDS-links out of NVRAM, from the "wl0_wdsX"-vars, before falling back to using the system-wide configuration. This somehow only works in AP-mode and not in pure WDS-mode (wl0_mode=wds). I haven't had a closer look at why yet, but that is the reason I chose to authenticate the WDS-links from the startup-script instead of NVRAM (which would have been a bit cleaner). The reason I use the startup-script instead of the firewall-script, BTW, is because things tend to stop working if `nas4not' is called multiple times for bringing up the same WDS-link and the firewall-script is run at least 3 times in a row.

    As all of the functionality is already available in the stock-firmware and just needs some NVRAM-vars to activate, it would qualify to be implemented in HyperWRT's web-interface, right? :)

    Anyways, let me know if you have any questions.



    Grtz,

    Traveller
     
  82. Rosebud

    Rosebud Network Guru Member

    WDS Working with WRT54GS V1.0's - Thanks Traveller!

    Many thanks to Traveller for his excellent tutorial on the extra configuration steps required on the WRT54GS units for proper WDS operation with the HyperWRT firmware! I have successfully set up my V1.0 units as you described with WPA Security. Speed measures around 24 kbps using NetIQ Qcheck, and I can connect multiple wired clients to a single ethernet port using a switch. Glad to hear this is working well for you on a 2 km link. I have been running a 2.6 km link for several years using a WAP11 / BEFSR41 combination, and was very pleased to learn of your excellent results with the WRT54GS units in a similar configuration.

    Thanks for helping me, and I am sure this tutorial is going to help out many other folks as well. Well done! :p
     
  83. bigrig

    bigrig Network Guru Member

    Traveller, thanks so much for posting that info! It finally got my two GS's talking to each other.

    That would be nice! 8)

    Matt
     
  84. RHamel

    RHamel Guest

    Thank you Traveler!

    I just got 2 WRT54G ver 2's talking to each other with AES WPA encryption. I didn't follow the instructions exactly.

    WRT54G (1) is set up normally with Hyperwrt 2.1b1 no special changes other than through the http screens just like a regular access point with AES WPA encryption. This box is connected to the cable modem.

    Supersecret = the password you choose
    ssid = ssid of WRT54G(1)

    WRT54G (2) has DHCP turned off. Has the gateway pointed at WRT54G (1) and has the following in the Startup script:

    nas4not lan wds0.2 up auto aes psk 'Supersecret' 'ssid'

    and this in the firewall script where xx:xx:xx:xx:xx:xx is the MAC of the WRT54G (1):

    nvram set wl_mode=wds
    nvram set wl0_mode=wds
    nvram set wl_lazywds=0
    nvram set wl0_lazywds=0
    nvram set wl_wds=xx:xx:xx:xx:xx:xx
    nvram set wl0_wds=xx:xx:xx:xx:xx:xx
    wl lazywds 0
    iptables -t filter -A FORWARD -o wds0.2 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
     
  85. HardyMacia

    HardyMacia Network Guru Member

    internet === WRT54G === WRT54G === WRT54G

    All of the talk seems to be about

    internet === WRT54G-A === WRT54G-B

    I plug in all of the MAC addresses and have the above working, but...

    How would I add on an additional WRT54G?

    internet === WRT54G-A === WRT54G-B === WRT54G-C

    Do I put the MAC address of C into A, or do put it in B? Do I put A & B both into C?
     
  86. wrt54gs

    wrt54gs Network Guru Member

    Re: internet === WRT54G === WRT54G === WRT54G


    as my experience , even u enabled MAC filter, you don't put the Routers MAC address into any routers. All WDSed-Router could connect scussfully.


    Try it and you will get answer.
     
  87. Acquirer

    Acquirer Network Guru Member

    Please forgive my WDS ignorance, but will the setup as described at the beginning of this topic allow me to have my USR MaxG router wirelessly connected to my WRT54G router thereby extending the range and allowing for use of the hub on the WRT?

    I'm trying to expand my overall range from the original router location two floors down to the full third floor area. I've tried using the WRE54G and a DLink Range Expander with no good results.

    thanks in advance.
     
  88. jksmurf

    jksmurf Network Guru Member

    I am REALLY green at all this so please bear with me. This seems a simple way to go and very similar to Celerons' new updated details here http://www.genslernet.com/hyperwrt/index.html

    As RHamel and Celeron ONLY configure ONE router with the wl commands, rather than BOTH like Traveller, what is the reason (in simple terms!) or advantage disadvantage of doing one over both?

    Thanks

    Kristian
     
  89. jaquinn

    jaquinn Guest

    Thanks for the great post.... this works really well. After battling with Talisman 1.05 and having WDS working fine but no luck with PPPoe this was just too easy.

    Using HyperWrt 2.1b1 based on 4.70.6 and WRT54G v 3.1 hardware.
     
  90. Toxic

    Toxic Administrator Staff Member

    glad you found a firmware that works for you.
     
  91. cypro66

    cypro66 Network Guru Member

    I finally managed to get my two WRT54GS's (both v1.1) working in WDS mode.
    In my current config speedbooster is turned of. Because I read somewhere on this forum that it should be disabled.
    Is it also possible to turn on speedbooster in WDS?
     
  92. cypro66

    cypro66 Network Guru Member

    I followed Traveller's instructions for wds :clap:
    I thought I would be able to connect wireless clients. But I'm not.
    I changed the WDS to AP setting...
    But it did not work.
    Could someone tell me what I should change exactly to accept wireless clients on 1 of the 2 WRT54GS's?
     
  93. rally1

    rally1 Network Guru Member

    What if I want to add a second bridged WRT54G?
     
  94. rally1

    rally1 Network Guru Member

    For what it's worth, this is what I did to get 3 WRT54G routers going.
    A is the main router.
    B is a bridge/repeater on one side, C a repeater/bridge on the other.

    On WRT54G(A) the following needs to be configured:
    1. Under Administration --> Management --> Startup enter the following (where BB:BB:BB:BB:BB:BB is the MAC address of the wireless on WRT54G(B):
    a. wl lazywds 0
    b. wl wds BB:BB:BB:BB:BB:BB CC:CC:CC:CC:CC:CC
    Click Save and close.

    On WRT54G(B) the following needs to be configured:
    1. On the Setup --> Basic Configuration page be sure to set the following:
    a. Configured the LAN IP address to something different than the address on WRT54G(A) such as 192.168.1.2
    b. Turn off the DHCP server
    2. Under Administration --> Management --> Startup enter the following (where AA:AA:AA:AA:AA:AA is the MAC address of the wireless on WRT54G(A):
    a. wl lazywds 0
    b. wl wds AA:AA:AA:AA:AA:AA
    Click Save and close.

    On WRT54G(C) the following needs to be configured:
    1. On the Setup --> Basic Configuration page be sure to set the following:
    a. Configured the LAN IP address to something different than the address on WRT54G(A)and WRT54G(B) such as 192.168.1.3
    b. Turn off the DHCP server
    2. Under Administration --> Management --> Startup enter the following (where AA:AA:AA:AA:AA:AA is the MAC address of the wireless on WRT54G(A):
    a. wl lazywds 0
    b. wl wds AA:AA:AA:AA:AA:AA
    Click Save and close.

    I also disabled the firewall on B and C, as I ready somewhere about a loop back issue.

    It seems to work fine. I am a little confused why client that are very close to C only connect @ 5.5MBs according to the wireless status. I would have thought the connection to C would be 54MBs, even if from C to A was only 28MBs or less.

    Also I am using the "stable" 2.0 HyperWRT firmware as opposed to the newer beta version out there.
     
  95. n7uv

    n7uv Network Guru Member

    Toxic sez: This document has been compiled by Celeron (linksysinfo user) who has stumbled upon a great feature for HyperWRT

    How to configure HyperWRT 2.1b1 with WDS


    Ok, I already have two WRT54GS machines running Alchemy 1.0 in WDS mode. This is very cool. In fact, the setup has been stable for several weeks now. Today, I bought a WRT54G V3.1 and installed HyperWRT 2.1b1(Rupan) a few minutes ago. Using the most excellent instructions collected and retransmitted by Toxic (above), I was able to get WDS running three ways now.

    AP1 (WRT54GS Alchemy)
    AP2 (WRT54GS Alchemy)
    AP6 (WRT54G HyperWRT)

    AP1<>AP2
    AP1<>AP6
    Simultaneously. Works very nice.

    See the ongoing experiments at
    http://www.jonadams.com/pages/wifi/N7UV-WDS_Setup_Aug2005_files/frame.htm

    If I have enough room, maybe next weekend I try AP1<>AP2<>AP6...

    Cheers - Jon
     
  96. faiiaf

    faiiaf Network Guru Member

    Hello,

    As read the topic totally. I have got one WRT54G and one wap54g working without any problem!! Now, I want to elimiate the deadpoint by adding one exter WRT54G. What's arrange can be?

    WRT54G ==> wap54g ==> WRT54G or
    WRT54G ==> WRT54G ==> wap54g

    Can I use the method as metion as above ??

    thank you very much !! :)
     
  97. n7uv

    n7uv Network Guru Member

    Good morning, faiiaf -

    Please check out experiment 3, just added to the site at the powerpoint at the link above. There you'll see WDS used in Point to Multipoint mode, like your drawing above. Just consider

    A <--> B <--> C --- internet (like what I think you want) is very similar to

    internet
    |
    A <--> B <--> C

    which is the way I have it in the experiment.

    If you're using Rupan v2.1b2, make sure to follow Toxic's setup procedure in
    http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=2946

    Sincerely, Jon
     
  98. n7uv

    n7uv Network Guru Member

    In the above ASCII sketch, it appears that the site software doesn't appreciate leading spaces...


    .....internet
    ...........|
    A <--> B <--> C

    the internet connection should be at B, not A. Please ignore the "..." in the drawing above.

    This topology is identical to that in Experiment 3, which is just drawn a little differently, like this:


    ........internet
    ..............|
    ..............B
    ............/ \
    ..........A C

    Jon N7UV
     
  99. faiiaf

    faiiaf Network Guru Member

    thank you very much everybody !!
    I will try it today, hopefully I can made it !! :cheering:
     
  100. gerds2001

    gerds2001 Network Guru Member

    Masters of the WRT54G/GS,

    first things first: This is the best forum I have found with regard to the HyperWRT software. The HyperWRT software is the best software for my boxes, as far as I could tell, although there is a minor problem (see below). Thanks a billion for the software Avenger, Thibor, Tofu and Rupan! You guys rock! Before switching to HyperWRT I used the plain vanilla linksys software and Seasoft's Alchemy (final) but I won't switch back :)

    For the last week I tried to set up WDS+WPA-Personal/TKIP on the following configuration:

    Internet <==> WRT54GS V1.1 <==> WDS+WPA/TKIP <==> WRT54G V2.2

    The WRT54GS runs Thibor-191005 software, the WRT54G ran Tofu 6.2 and is now running Tofu 7.

    To cut a long story short: I failed miserably. I was not able to get this setup going. Each time I disconnected the WRT54G, I was unable to connect to it anymore. And believe me, I read virtually every thread regarding WDS and I tried every suggestion there was. The result stayed the same :-/

    Finally, I switched to WDS+WEP and suddenly all went smooth. The setup was finished within 2 minutes and both boxes are talking to each other and they still do. The only drawback is the flawed security of WEP but I guess I will have to live with it...

    OK, stop whinig, here is my current setup, maybe some other soul might be saved :)

    I started flashing both boxes to the right software and reset the nvram variables by pressing the reboot button for more than 30 seconds. The WRT54GS box is connected to the internet via a DSL modem using PPPoE. I set the IP address to 192.168.1.254 (Mask 255.255.255.0), enabled DHCP. The "Basic Wireless" setting is "Wireless Mode"=Access Point, "Wireless Network Mode"=G-Only, Channel=1, "SSID Broadcast"=Enable, WDS=Enable, "Bridge Restrict"=Enabled and for "Remote Bridges" I used the WIRELESS MAC adress of the WRT54G box, SES=Disabled. As stated above, I was unable to let both boxes talk to each other using WPA-Personal/TKIP (I am restricted to TKIP due to the notebook I use, I did try AES as well but it did not work either!). Right now I am using WEP 128 Bit and the Wireless MAC Filter is disabled.

    The WRT54G box is only connected to the power line. The IP is 192.168.1.1 (Mask 255.255.255.0), DHCP server is disabled. The "Basic Wireless" setting is "Wireless Mode"=WDS-AP, "Wireless Network Mode"=G-Only, Channel=1, "SSID Broadcast"=Enable, "Bridge Restrict"=Enabled and for "Remote Bridges" I used the WIRELESS MAC adress of the WRT54GS box, SES=Inactive, WEP 128 Bit encryption and the Wireless MAC Filter is disabled.

    All but one setting were left unchanged, I set lazywds off using the command line "wl lazywds 0" on both boxes.

    Things that did not work:

    I tried the setup as proposed by Celeron and posted Toxic, but I used WPA/TKIP encryption. As stated by numerous other people, I could not get it to work :-/

    I tried to set the nvram variables according to Traveller's guide but it did not work. The things I changed from Traveller's setup were:
    a) I set wl_mode=ap and wl0_mode=ap in order to use the boxes as access points
    b) I used the proposed nat4nas command which failed. I checked both boxes using the command ifconfig and did not find a "wds0.2" interface in both boxes. I found an interface named "wds0.4915" on both boxes so I used this interface as well for the nas2nat command with no success. Yes, I did change the "tkip", SSID and password parameters of the script. I even tried simple passwords since I was not sure whether the boxes will accept "$" characters.

    Traveller, thanks for the guide but I was not lucky though.

    I found another guide at http://www.genslernet.com/hyperwrt/ which is pretty close to Traveller's guide. The difference is that the startup script is used on the WRT54G box only, the WRT54GS box will not run a startup skript. Well, this did not work as well.

    Keep up the good work guys, without your help and the guides you have written I would not have made it!

    Best
    Gerds2001
     

Share This Page