Help building a wireless connection

Discussion in 'Tomato Firmware' started by Zaka, Dec 22, 2006.

  1. Zaka

    Zaka LI Guru Member

    Ok. The title may not be clear, but I am trying to connect my 75yr old neighbor to my internet connection.

    My neighbor lives across the street, approx 50 yards (150ft) away.

    I have done a wireless survey using a WRT54G v2.2 w/Tomato 1.01 transmitting at 67mW on channel 1 and recieve ~12% signal on a PSP in the room where the computer will be located.

    I can increase the signal strength to ~30% if I hold the WRT to the window my front bedroom.

    Using 2 WRT54GLs with Tomato I should be able to bridge the gap and provide a workstation to my neighbor so he can learn to use a computer and surf the web. (some fancy antenna work may be required here but for now that is not the problem.)

    What settings should I use on the routers AP, WDS, WET ??
    And how should I address them?
    What ports (WAN or LAN) should I connect my local network, to the remote workstation?
    Will I create a seperate subnet or will the remote workstation be another host on the local subnet?
    I have 2 Win2K servers and provide DHCP from them. Will DHCP packets cross the wireless bridge?

    Thank you for your help.
  2. digitalgeek

    digitalgeek Network Guru Member

    set the router at your house to AP and plug your modem into the wan connection and setup the router for regular use, and confirm that you can surf. set the wireless to ap

    if your neighbors computer is beside the router, use wet and plug the computer into a lan connection. (otherwise you may have to use AP+WDS on both routers.)

    make sure you set the wireles encription on both routers. (you may want to optional set mac filter as well to discourage you other neighbors from trying to use the connection as well)

    everything else should work the same.
  3. digitalgeek

    digitalgeek Network Guru Member

    you may want to consider the optional 7dbi antennas as well to boost the signal a bit
  4. Zaka

    Zaka LI Guru Member

    Thank you, digitalgeek.

    Remote WRT = computer into lan port, set to WET

    I guess that I was unclear (well reading my post I was unclear)!!!

    My normal access point is a WRT54G v.2.2 in the basement office/computer room.

    I will be installing an additional WRT54GL in the upstairs front bedroom to be the local end of the bridge.

    So the set will end up looking something like:

    RemotePC <--> 54GL(1) <)))(((> 54GL(2) <--> 54G <--> CableModem
    . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
    LocalNetwork <--> 8PortSwitch <---------------

    Thus my question on I.P. addressing and which ports to use.

    54GL(1) is computer to lanport, RF to WET, I.P. address = ??
    54GL(2) is ??? (only to be the bridge end point)
    54G is Gateway at
    LocalNetwork is

    DHCP server exists on the LocalNetwork, I am not using DHCP on the 54G.
    DNS servers exist on the LocalNetwork, I have the Gateway set to use local DNS.

    Will DHCP packets travel across the 54GL(1) <)))(((> 54GL(2) bridge??
    Is it necessary to subnet or can we all be one big happy family??
  5. digitalgeek

    digitalgeek Network Guru Member

    -do not enable DHCP on the second and third routers,
    -set your gateway and dns to the first router (or the ip of the gateway)

    as long as you don't need to "vlan" it (I don't think you want to many computers in this little family) all is easy. --- [subnetting is not necessary]

    I am assume the second router will be wired to the first..
    which means you won't need WDS for the first to the second router.

    my current setup is WDS from router a to router b, DHCP is hanled by router A and the gateway and dns is set to router a.
  6. digitalgeek

    digitalgeek Network Guru Member

    make sure you disable the internet connection on the second and third router.
  7. digitalgeek

    digitalgeek Network Guru Member

    Another thing to remember is that because these are routers and tring to do a router job we need to use the spanning tree protocol (found on the advanced / routing page)
  8. Zaka

    Zaka LI Guru Member

    Thank you for your help.

    I have finally got everthing to talk to each other and can surf the internet from the remote machine.

    The set-up:

    RemotePC <--> 54GL(1) <)))(((> 54GL(2) <--> 54G <--> CableModem

    54G (gateway) Mode:AP, Channel:11, Wan:DHCP, DHCP:disabled, RouterIP:1.1, DNS:1.11,1.12(local), SSID:gateway
    54GL(2) (local bridge end) Mode:AP, Channel:14, WAN:disabled, DHCP:disabled, RouterIP:1.2, DNS:1.11,1.12(local), SSID:bridge
    54GL(1) (remote bridge end) Mode:WEB, Channel:14, WAN:diabled, DHCP:disabled, RouterIP:1.3, DNS:1.11,1.12(local), SSID:bridge

    No RIP enabled on the routers. No Spanning-Tree protocol.

    The big trick to this is to set the SSID of the bridge ends the same.

    PROBLEM: :angry:

    54GL(1) on the remote end (Mode:WEB) can not resolve DNS addresses.
    It will ping, but it can not resolve, thus it can not get the time unless the IP address of the time server is entered.
  9. digitalgeek

    digitalgeek Network Guru Member

    On the gateway router... on the ADVANCED / DHCP DNS page


    on the other routers set the gateway and dns to the ip of the first.

    Your clients will still get the dns from the DHCP server, but the routers will take the ISP's dns
    and have dns access.
  10. Zaka

    Zaka LI Guru Member

    Done. No difference.

    I believe that the problem has something to do with trying to do DNS though the eth1 port. (both ends of the bridge are wired to their respective LAN ports, the WAN is disabled).

    I can do a trace route to from 54GL(1) with no problem, but if I try to traceroute (or ping) a name ( I do not get the spinning time thing or any other response.
  11. digitalgeek

    digitalgeek Network Guru Member

    I had that problem when I first setup my wds... it was with the dns setup on the second router? what dns are you trying to use? try enabling the RIP.

    (spanning tree protocol will prevent a broadcast storm from all three routers)
  12. Zaka

    Zaka LI Guru Member

    I always hate threads that offer no solution to the problem.
    Thus I am posting an e-mail that I sent to Jon and his reply.

    Thank you all for your help and of course thank you Jon.
    The problem is now solved.

    From : Jon
    Sent : Thursday, December 28, 2006 2:50 PM
    To : "John S"
    Subject : Re: Tomato 1.01 bug or set-up issue?


    Hmm, I'm going to guess it's because dnsmasq doesn't normally run in wet mode. You may be able to get around it by adding the following to the startup script:

    rm /etc/resolv.conf
    ln -sf /etc/dmresolv.conf /etc/resolv.conf

    Reboot afterwards or try it in telnet.

    On 12/27/06, John S wrote:

    First let me say thank you for excellent firmware. I appreciate the time and
    effort that you put into the project.

    I have set up a wireless bridge between 2 54GL's.

    Please see thread:

    The remote computer functions correctly, DHCP, DNS, etc., but the remote
    54GL cannot use DNS to determine the address of the time server. I must
    enter an IP address in order for it to get the time.

    Using various routing schemes, and router DNS settings does not help.

    Any insight that you can provide into this issue would be apprecated.

    Thank you,

    John S
  13. digitalgeek

    digitalgeek Network Guru Member

    Sorry I could not help you with the DNS issue... Jon is very good at this stuff and I'm glad he was able to help you out.
  14. srouquette

    srouquette Network Guru Member

    I'm trying the WET mode, and I wanted to know if it's still mandatory to do the little trick with resolv.conf ?
    I don't really understand what these commands do (well... I know rm and ln, but what is dmresolv.conf, it doesn't even exist in v1.14...)
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice