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

WRTGS1.0/TinyPeap ->WDS-> WRTGS1.1/DDwrt or Alchemy =

Discussion in 'TinyPEAP Firmware' started by iote, Apr 18, 2005.

  1. iote

    iote Network Guru Member

    Hi there! since its my first post i'll try not to get too dense, but here it goes...

    I'm trying to run WRTGS1.0/TinyPeap ->WDS-> WRTGS1.1
    The second router must not use Tinypeap cause its not compatible w version 1.1.

    The 1st router is working flawlessly, and i've enabled WDS on it and on the second router. Filled the apropriate MAC adresses and even tried LazyWDS.

    The problem is, the TinyPeap WRT sees the 2nd router MAC as a WDS link w/ a RSSI = X, but the 2nd router, no mater what DDWRT or Alchemy is loaded, displays the 1st router MAC as a WDS link but w/ RSSI = 0 (the survey shows the MAC, other info and a rssi = x).
    Result, there's no comunication.

    Questions:
    Is there any WDS incompatibilities between Tinypeap and DDWRT or Alchemy?

    Is there a way through the shell to check if the WDS is loaded and working, so I can identify the culprit?

    Is rssi info gathered after a successful auth? (dont think so cause the Tinypeap sees the other router.)

    May it be a problem that i'm running both wrt on the same subnets as the clients?

    Well, thats it for now...
     
  2. Toxic

    Toxic Administrator Staff Member

    make sure the 2nd one has DHCP turned off. DHCP is handled by the first router.

    I am using at present DDWRT on 2 routers with WDS-WPA PSK AES and it works fine.


    check out our user guide...
    WDS User Setup Guide
     
  3. tinyPEAP

    tinyPEAP Network Guru Member

    thanks for the follow up, Toxic.

    There may be a chance that the WDS on Satori release is not quite compatible with the one on Alchemy.
    I could be wrong, but I think Alchemy release also included some updates on WDS.

    Other than that, is your configuration working without tinyPEAP?

    -tak
    tinyPEAP Development Team
     
  4. iote

    iote Network Guru Member

    Thanks very much for helping out...

    Here is the config for both the DDWRT and the TinyPeap(Open)

    Yes, the DHCP is turnet off on the 2nd.
    It works when i turn Auth to Open on the TinyPeap. (both show link on the Wireless status page, authough I canot ping one another trhough their shell).
    I've been trough the manuals, and it seems WDS is pretty straigtforward...
    With this setup below I should be able to ping between them but I cannot, despite its working. (I am able to ping both from the client on the DDWrt)
    Well, seems its the Auth stuff... any help?

    ---------------TinyPeap-----------------------

    Router

    Firmware Version: Satori-4.0 v2.07.1.7sv
    Current Time: Tue, 19 Apr 2005 08:32:34
    MAC Address: 00:20:ED:77:3A:34
    Router Name: MANU
    Host Name: MANU
    Domain Name:
    Uptime: 08:32:34 up 17:21, load average: 0.05, 0.02, 0.00

    Internet

    Configuration Type
    Login Type: Automatic Configuration - DHCP
    IP Address: 200.XXX.XXX.XXX
    Subnet Mask: 255.255.240.0
    Default Gateway: 200.XXX.XXX.1
    DNS 1: 200.150.4.5
    DNS 2: 200.150.4.4
    DNS 3: 200.XXX.XXX.244

    Wireless

    MAC Address: 00:0F:66:B2:AB:AE
    Mode: AP
    Network: G-Only
    SSID: WWWW
    DHCP Server: Enabled
    Channel: 1
    Rate: 48 mbps
    Encryption: Disabled
    Clients: 00:0E:9B:55:A3:6B rssi -81
    WDS Signal: 00:12:17:BB:7E:86 rssi -38

    Local

    MAC Address: 00:0F:66:B2:AB:AC
    IP Address: 192.168.1.1
    Subnet Mask: 255.255.255.0
    DHCP Server: Enabled
    Start IP Address: 192.168.1.100
    End IP Address: 192.168.1.149


    --------------------DDWRT-----------------------------

    Router

    Firmware Version: DD-WRT #22 (prefinal3.2)
    Current Time: Not Available
    MAC Address: 00:12:17:BB:7E:85
    Router Name: ANNA
    Host Name: ANNA
    Domain Name:
    Uptime: 00:02:39 up 2 min, load average: 0.09, 0.12, 0.05

    Internet

    Configuration Type
    Login Type: Static
    IP Address: 192.168.1.2
    Subnet Mask: 255.255.255.0
    Default Gateway: 192.168.1.1
    DNS 1: 192.168.1.1
    DNS 2:
    DNS 3:

    Wireless

    MAC Address: 00:12:17:BB:7E:86
    Mode: AP
    Network: G-Only
    SSID: WWWW
    DHCP Server: Disabled
    Channel: 1
    Rate: 54 mbps
    WDS Signal: 00:0F:66:B2:AB:AE rssi -41
    Encryption: Enabled

    Local

    MAC Address: 00:12:17:BB:7E:84
    IP Address: 192.168.1.2
    Subnet Mask: 255.255.255.0
    DHCP Server: Disabled
    Start IP Address: 192.168.1.100
    End IP Address: 192.168.1.149
     
  5. iote

    iote Network Guru Member

    Internet -> Tiny OPEN -> WDS -> DDWRT OPEN = Happy clients
    Internet -> Tiny AUTH -> WDS -> DDWRT RAD pointing to Tiny = Sad clients

    It seems that the WDS link itself must be authenticated, is it true? If it is, how do I do it?

    thanks
     
  6. tinyPEAP

    tinyPEAP Network Guru Member

    duh.... not sure what I was thinking last night, but
    the problem was something really obvious.

    The encryption for WDS in WRT54G, as far as I know, is done through the static WEP key.
    Well... under tinyPEAP... the WEP key is dynamically derived through
    the successful authentication. So they are two different encryption schemes
    that cannot co-exist and this explains why you have unhappy WDS connection between them...

    hope this helps,
    -tak
     
  7. iote

    iote Network Guru Member

    humm... seems I got a problem here...

    I do need authentication to be contained within the WRT firmware as I do not want to leave a machine running Radius to handle 2 or 3 auth requests a day...

    but one of my hardware is still not compatible w/ Tinypeap...

    Questions:

    Will tinyPeap be compatible w/ WRTGS1.1? if so, when?

    Is it very hard to make DDwrt to authenticate itself(wds) and its clients to TinyPeap?

    Can you point out some other firmware that offers Enterprise WPA, authentication and Radius server all contained in the firmware, and capable of running on v1.0 and v1.1 hardware?

    Is it possible to assing a static wep only for the wds (witch solves the WDS issue) and authenticate users on the Tinypeat trough DDwrt?

    thanks again...
     
  8. tinyPEAP

    tinyPEAP Network Guru Member

    Hi,

    Because of the high demand for tinyPEAP port for the latest version of routers, I am working on it at the moment.
    Hopefully it'll be out sometime very soon, however I am personally in this
    'toward the end of the semester' problem, so there's no 'promised date/time' at this point.

    Other three questions are really beyond the scope of what tinyPEAP intends to offer.
    As far as WDS is concerned, authentication and communication protocols are two different things and I will need to look at the implementation first.

    -tak
    tinyPEAP Development Team
     
  9. iote

    iote Network Guru Member

    Thank you very much for taking your time to help me out.
    TinyPeap is very powerfull app and I'm looking forward for the next release, wich will hopefully be compatible w/ v1.1.
    Congratulations for the making of such a usefull app.
    If you need a beta tester, feel free to contact me at iote at terra dot com dot br. I'll be glad to help.

    cheers,
    Caio.
     

Share This Page