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

Shibby v116 on E3000 WDS behaviour?

Discussion in 'Tomato Firmware' started by illiac4, Feb 1, 2014.

  1. illiac4

    illiac4 Reformed Router Member

    On a primary router i have 116 shibby installed. The second is fonera with Gargoyle firmware and configured as Wireless Bridge (diasabled repeater so only one wired client).

    If i connect client on a fonera that has on primary router defined static ip lease the network on a client connected to fonera is not working. If i untick static lease for this client on primary router it will start working normally again.

    Is this normal behavior that client connected to wireless bridge can not use static ip lease?
     
  2. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    Are you using WDS or WET (wireless bridge.)

    WDS passes the MAC addresses of the wired and wireless devices attached to the AP and easily allows static or dynamic DHCP lease assignment of Ip addresses.
    WET makes all the traffic coming from wired devices attached to the AP look like it's coming from the AP itself. MAC addresses are not passed, and you can't set Ip addresses for individual devices the way you would like.
    WET is faster and can reestablish links more reliably. WDS has more flexibility.
     
  3. ghoffman

    ghoffman Addicted to LI Member

    marcel -
    this is a very clear concise explanation of WDS vs WET,. thank you.

    i have a related question about static leases to access the web interface (gui) on the client wireless bridge routers. this works fine in WET mode - but in WDS mode, i cannot access the web interface of the client.

    to be explicit:
    i've got a e4200v2 set up as access point + wds. i have two routers that connect wirelessly (a wrt150n and an fd7301.) all routers are running tomatousb, shibby v116. connections are fine in WET mode. i set static IP's bound to the wireless MAC addresses for both wireless routers and connect to them fine in WET mode. if they connect in WDS, then i can't access their web interfaces. of course, the MAC used for the static/bound to IP is the same as the MAC used for the WDS connection (the wireless MAC). as i'm writing this - should i bind the lan MAC on the wirelessly-connected routers to the static IP?
    (answer - no - this does not fix the problem)

    thank you in advance for this issue which i know has been addressed before. i' ve searched for the answers on this forum and dd-wrt but it's escaping me now.
     
    Last edited: Feb 1, 2014
  4. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    The usual practice is to manually set the IP address of the AP from the AP itself, using an address in the same subnet but outside the DHCP range of the gateway router. It sounds like you have been assigning a static DHCP lease from your gateway device (the E4200, if I understand correctly.)

    For example, if your E4200 is 192.168.1.1 and it gives out ip addresses in the 192.168.1.100-149 range, you could go to the AP's Web interface and set it's ip address to 192.168.1.20 and the other AP to 192.168.1.40. Make sure the subnet mask is the same and the default gateway on the AP's point to the E4200. Get rid of any static DHCP entries for the AP's on the E4200.
     
  5. ghoffman

    ghoffman Addicted to LI Member

    marcel - i've set the ip on the remote routers (they are not access points but WET or WDS clients) outside of the DHCP range on the E4200. they appear as devices in the device list on the E4200. i can access their web interfaces at their IP's in WET mode, but not in WDS mode.
     

Share This Page