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

WRT54G v1.1 and v2.2 WDS problem with hyperWRT 2.1B1

Discussion in 'Networking Issues' started by antare, Mar 23, 2005.

  1. antare

    antare Network Guru Member

    Hi,
    I am trying to setup a WDS using HyperWRT. i have 2 WRT54G.
    The main one v. 1.1 (main) and another v2.2 (repeater). I used the "Celeron" setup guide posted here but i could not get it to work

    Here is the Topology:

    Main WRT54G (v 1.1) (((WDS +WEP))) Repeater WRT54G(v 2.2)
    | | |
    internet computer A (192.168.1.101) computer B 192.168.1.103


    The main one is configured as follows:

    IP: 192.168.1.1
    Subnet 255.255.255.0
    DHCP: enabled
    DHCP IP start : 192.168.1.110
    Wireless enabled channel 6
    SSID (set and same on both router)
    WEP with same key on both WRTs
    Firewall enabled
    Block anonymous connections checked
    startup command: wl lazywds 0
    wl wds (mac address of repeater)
    Mac filter : enabled (listing all macs of the main, repeater and even NIC of all computers)
    Internet connection : PPOE (DHCP)
    Advanced Routing is left blank


    The repeater one is configured as follows:

    IP: 192.168.1.2
    Subnet 255.255.255.0
    DHCP: disabled
    Wireless enabled channel 6
    SSID (set and same on both router)
    WEP with same key on both WRTs
    Firewall disabled
    Block anonymous connections unchecked
    startup command: wl lazywds 0
    wl wds (mac address of main)
    Mac filter : enabled (listing all macs of the main, repeater and even NIC of all computers)
    Internet connection : left as DHCP
    Advanced Routing is left blank

    I have internet on computer A but not upstairs on computer B
    all IP on the computers are static

    What am I doing wrong. ? I do not want to disable the firewall on Main like some postings suggested.

    Tim
     
  2. antare

    antare Network Guru Member

    I fixed this myself. the mac address was pointed to WAN instead of RF
     

Share This Page