HOWTO: Use Linksys WRT54G as a wireless ethernet bridge

[bazookajoe]

Hi,

Thanks user1234 for the info. on how to setup a bridge. I have been wanting for an opportunity like this one for some time. A little history first. My desktop is in one corner of the room. The wireless signal is strongest in the opposite corner. So untill now I used a usb adaptor with usb extension cables to pick up the strongest signal. The problem, however, is that my pc becomes sluggish when I xfer large files. This solution is ideal. Since I can use cat5 instead of usb 2. Anyways.

Here is the network setup.

Cable Modem<--->Dlink 524 ~ ~ ~ ~ ~ WRT54G<--->Desktop

I followed your instructions to the the letter with one exception. In line number nine you mention "DNS Netmaq". Do you mean "DNS Masq"? If so, I followed your directions exactly. Otherwise I could not find "DNS Netmaq".

My problem is that I can login to both routers. Meaning the bridge is functioning. But I cannot access the internet using the wrt54g. What might solve this problem? I'm running zone alarm. Before using the wrt, I was using a "G" usb adaptor. Any ideas?

 

[bazookajoe]

Also, the Dlink is forwarding a static IP to the WRT:

Cable Modem<--->Dlink 524(192.168.0.1) ~ ~ ~ ~ ~ WRT54G(192.168.0.101)<--->Desktop

 

[skyking]

sounds like you need to specify the 524 router as the gateway. Maybe your computer has something other than 192.168.01 for a gateway.
Try opening the command prompt and doing
ipconfig /all
If you get a gateway of 192.168.0.101, then you won't get to the internet.

 

[bazookajoe]

Skyking,

I followed your instructions. Here is what I get after using cmd:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8D-A5-11-91
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.0.105

Now when I go ahead and plug in my usb adpator the following appears:

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . : san.rr.com
Description . . . . . . . . . . . : Linksys Wireless-G USB Network Adapter #2
Physical Address. . . . . . . . . : 00-0F-66-73-4C-40
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.150
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

I went ahead and made changes to "gateway" under setup->basic setup on the WRT but no go. Was that the right place to change the gateway value? Do I need to configure "Local Area Connection Properties" under windows manually? Specifically the TCP/IP properties tab, where values for IP address, subnet mask and default gateway can be entered. I am not sure with what to do next. Thank you.

 

[bazookajoe]

Oh wait I think I've solved my own problem... For some reason the WRT had 192.168.0.105 as DNS. After changing the value to 192.168.0.1 it appears to be working. Thanks Skyking, and thanks once again to user1234.

Finally, is there anyway to find out what kind of signal strength the WRT is receiving? Similar, or not, to the 5 bar graphic on the wireless network status.

 

[user1234]

Originally posted by: bazookajoe
Oh wait I think I've solved my own problem... For some reason the WRT had 192.168.0.105 as DNS. After changing the value to 192.168.0.1 it appears to be working. Thanks Skyking, and thanks once again to user1234.

Finally, is there anyway to find out what kind of signal strength the WRT is receiving? Similar, or not, to the 5 bar graphic on the wireless network status.

glad you got it working..... I guess you mean that the DNS setting was wrong on the Desktop attached to the wrt54g, right ?



You can get some info about the signal in the "Status->Wireless" screen - it shows rssi and noise values (in dBm), but I'm not sure how to translate that to 0-100 scale. Mine's showing 54/93 (rssi/noise) and I'm getting about 20 Mbps between the routers (measured when doing file transfers between 2 PCs attached to each router) which is as good or better than what I get with other wireless clients.

btw, I also used a USB wifi adapter before getting the wrt54g. For linux, using the wrt54g works much muchs better, as I don't need to set up driver configurations for the usb-wifi adapter in Linux....

 

[bazookajoe]

user1234,

The DNS entry in the wrt54g, under setup->basic setup-> Static DNS 1, was incorrectly entered. It was probably an error on my part, when nothing worked initially. Forcing me to tinker with numbers and settings. So far, so good. The xfer rates are just as good as before, perhaps even better. I do not have another pc to test intranet performance. My pc is definitely less sluggish than before. I am not sure if the usb 2.0 bus is supposed to burden the cpu or not. But, for my pc, the effect was very noticaeable.

The wireless tab is good to look at compare from time to time for diagnostic purposes. But I hope that in your travels you come accross a utility or something similar to the system tray icon. I have become spoiled with that lil' ah heck. I will surely check back to read this thread from time to time. Take care.

 

[user1234]

I see, actually, all my DNS settings are zeroes, I think it's all set automatically via DHCP, so I never had to enter any DNS settings. Anyway, just wanted to let people know that the original instructions should work for setting up the wrt54g as a wireless bridge to any other wireless router. Don't let the lengthy discussions in this thread, from people that don't understand how it works, scare you away. Just follow the instructions carefully, I tried to edit some of the steps to make them as clear as possible.

 

[bazookajoe]

Cool. I went back and changed all my DNSs to 0 and my DMZ/port forwarding issues have been fixed. Ditto to the simplicity of this procedure. What a fine alternative to any usb/console/bridge adaptor.

 

[user1234]

great......and don't forget you can connect up to four PCs or other devices (e.g. XBOX) to the wrt54g. So it's very cost effective as it would definetely cost less than four wireless-g adapters, and is much easier to set up (no driver installations are required). The performance when connecting to the internet is almost identical to what I'm getting using a PC attached to the main router. This allows me even to play UT2004 flawlessly online from behind the client router.

 

[Jumperus]

Oy. I've spent the last 5 hours attempting to get this to work, suffering through a bad firmware (used an older Sveasoft and had useless wired ports until redoing it with the one you suggested). Now, I swear I have everything set up properly, but it's as if the two routers just don't see each other or won't talk.
Main: DI-624
Client: WRT54G 2.2
Using WPA-PSK, they're both Channel 11, both on the same SSID, CTS and everything else matches, my DHCP and filtering is set up just fine on the DI-624, WRT54G's transmit power is on full....no idea what the problem could be. >=/ I don't suppose there's any way I could yoink a very detailed configuration out of you?
The Linksys will survey and find my D-Link's SSID just fine, but it's as if the D-Link is being a snob. No log entries at all in either one for anything. Perhaps my copy of the firmware was 'altered'. Any ideas?

 

[user1234]

The symptoms you describe are usually indicative of mis-configuration of the security/encription which prevents the wireless connection from being established. I haven't tried WPA, so it might not be supported for client mode, or that you simply have some setting missing in the WPA setup. Try disabling WPA and see if that works. I use WEP encription which works fine.

 

[Jumperus]

Just reconfigured with WEP. Still nothing. I don't know what the devil's wrong with this setup. It's almost as if instead of the wired being broken now, wireless is. Heh. Unfortunately I have to go to class, otherwise I'd spend another three hours troubleshooting this thing. Hmn. Did you have to do anything special to the DI-624 to get it to work? I have the 624 set up as a DHCP server using static addressing for all devices and MAC filtering. I do have the MAC address correct for the WRT54G. Blah.

 

[user1234]

I suggest to disable MAC filtering (on the di-624) and WEP/WPA (on both routers) and see if that works first. Seeing that you haven't got any connection yet, I understand you set up the mac filtering manually, which is prone to errors. The usual method I use to allow new clients is to first disable mac filtering, then let the new cilent connect, and then its info whould be shown in the mac filtering screen of the di-624 , so you can just add it to the list of allowed clients by clicking on it, so you don't need to manually enter the mac address.

 

[i2av]

i have my two linksys WRT54g's (a v2.2 with alch on it and a v2 with stock firmware)
i followed the guide and i can login to the v2 wirelessly and remotely so i know it works

the problem is getting the computers behind each to communicate...
the stock (v2) is 192.168.1.1
the flashed (2.2) is 192.168.2.1

do i need to telnet into both and use the telnet command (this is changed to reflect my ips) how do i m$ telnet in with no username? i am so nub sometimes.

on the stock
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.1
and
on the flashed
route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.2.1

heres a pic being as im a retard and cant type
link = [ http://i2av.djcrackman.net/pix0rz/wireless.PNG ]

i hope someone knows how to save me here

 

[Jumperus]

Success! At least, for the major problem. Yeah, disabling all filtering and security resulted in a near-instantaneous connection and DHCP assignment to the Linksys. And at first I could ping out into the WAN on a client connected to the Linksys. Just need to do a bit of DNS troubleshooting and get security back up and I should be good. =)
When the Linksys is in client mode is it allowing no client connections to it wirelessly? That is, if I set up security on the D-Link and Linksys (WEP, WPA, whatever), would I have to worry about wardrivers or residential skript kiddies getting onto the Linksys? I've considered more than once the idea of leaving encryption off but going straight off MAC filtering. Any thoughts?

 

[user1234]

Originally posted by: i2av
i have my two linksys WRT54g's (a v2.2 with alch on it and a v2 with stock firmware)
i followed the guide and i can login to the v2 wirelessly and remotely so i know it works

the problem is getting the computers behind each to communicate...
the stock (v2) is 192.168.1.1
the flashed (2.2) is 192.168.2.1

do i need to telnet into both and use the telnet command (this is changed to reflect my ips) how do i m$ telnet in with no username? i am so nub sometimes.

on the stock
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.1
and
on the flashed
route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.2.1

heres a pic being as im a retard and cant type
link = [ http://i2av.djcrackman.net/pix0rz/wireless.PNG ]

i hope someone knows how to save me here

PCs behind the client router (the one flashed to alchemy firmware) should already by able to connect to PCs behind the main router (with the stock firmware). You can verify that by doing "ping 192.168.1.100" (in windows, use the "run...." in start menu) from the PC 192.168.2.100.

Now for the opposite direction you need to add a routing table entry either in the .1.100 PC itself or in the main router (stock). For this you need to know the IP assigned to the client router (flashed) by the main router (stock), which would be something like 192.168.1.101 (for example). This is shown in the "Status:Router" screen on the client router in "IP Address" line.

Now you need to tell PC 1.100 to use the flashed router 1.101 (which is the flashed router's address on the main network so the PC 1.100 can connect to it directly) as the gateway to get to 192.168.2.100. So, you'll have to "telnet 192.168.1.1" from the PC 1.100 with your regular username and password (e.g. root/admin), and then give this instruction:

# route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.101

The problem is that I'm not sure if the stock router will allow you to telnet into it and give the above command. So you may need to flash it as well. Alternatively, you could add this entry directly to PC 1.100 routing tables, which is what I do since my main router is a d-link which is not hackable like the linksys. Since I'm using Linux, this is easy as typing the command above in a terminal, or adding it to one of the configuration scrips (/etc/network/interfaces to be exact). For windows, it should be possible to do the same thing, but I'm not sure exactly how to do it. Basically, you have to find the dialog box which defines your gateways, and add the address 192.168.1.101 as the gateway to subnet 192.168.2.x, which is what the above command is doing. Isn't unix simpler ?

 

[user1234]

Originally posted by: Jumperus
Success! At least, for the major problem. Yeah, disabling all filtering and security resulted in a near-instantaneous connection and DHCP assignment to the Linksys. And at first I could ping out into the WAN on a client connected to the Linksys. Just need to do a bit of DNS troubleshooting and get security back up and I should be good. =)
When the Linksys is in client mode is it allowing no client connections to it wirelessly? That is, if I set up security on the D-Link and Linksys (WEP, WPA, whatever), would I have to worry about wardrivers or residential skript kiddies getting onto the Linksys? I've considered more than once the idea of leaving encryption off but going straight off MAC filtering. Any thoughts?

I'm not sure if the wrt54g allows wireless connections to itself when it's operating in client mode. According to this doc page it does not, although you should try it out for yourself (I haven't tried connecting to it wirelessly yet).

As for the DNS server address, it should all be relayed automatically by the DHCP protocol, but you could always set it manually (it is ususally shown in the status screens of both routers). Notice how DHCP works "recursively" - your main router is a DHCP client of your ISP, the client router is a DHCP client of the main router, and your PC (attached to the wrt54g) is a DHCP client of the wrt54g. DHCP is used to automate networking configuration by providing all the required settings to the clients, such as the default gateway, DNS server, and even the client's IP address.

 

[Jumperus]

Originally posted by: user1234
I'm not sure if the wrt54g allows wireless connections to itself when it's operating in client mode. According to this doc page it does not, although you should try it out for yourself (I haven't tried connecting to it wirelessly yet).

As for the DNS server address, it should all be relayed automatically by the DHCP protocol, but you could always set it manually (it is ususally shown in the status screens of both routers). Notice how DHCP works "recursively" - your main router is a DHCP client of your ISP, the client router is a DHCP client of the main router, and your PC (attached to the wrt54g) is a DHCP client of the wrt54g. DHCP is used to automate networking configuration by providing all the required settings to the clients, such as the default gateway, DNS server, and even the client's IP address.

Yeah, I've done some playing with DHCP on commercial routers, but nothing heavy. One thing I can't remember is if I should just completely automate everything, point to the WRT for DHCP, or point through it at the D-Link for it. I shall experiment.

I've been waiting and looking for about a month for this exact line of advice and questions, and bam, out of nowhere I find it. This is great of you; thanks a lot.

 

[i2av]

ok when i telnet to each of the routers (now both flashed to alch)

192.168.2.1
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 br0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1


route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.102
is what i type in the telnet console of .1 to get the top entry below.
(before it was everything minus the top line)

192.168.1.1
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 192.168.1.102 255.255.255.0 UG 0 0 0 br0
192.168.1.0 * 255.255.255.0 U 0 0 0 br0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

192.168.1.102 is the IP that [.1.1] assigned to [.2.1]
so far, my computer on .2 (the client mode) can access the computer behind .1
but not the other way (gets access denied), the computer behind .1 can ping my
computer behind .2 so i dont see why windows just wont work

i can also telnet into .1 and webadmin into .1 from my computer behind .2
its ip is 192.168.2.100


i was thinking the route add line is setting it for the wrong thing maybe?
being as the .2 sets the route to .1 using eth1 ... im not sure what to add to the
telnet command to change that any help? :s


IF ANY OF THAT WAS CONFUSING i'll clarify....
its just my brain is breaking right now.

IM JUST SOOO CLOSE I KNOW IT >_<


right now (picture)

WINDOWS--------------------AP---------------------CLIENT---------------WINDOWS
------------------wired-------------------wireless-----------------wired
192.168.1.100 <===> 192.168.1.1 <- - - - -> 192.168.2.1 <===> 192.168.2.100

the .2.100 can ping/access 1.100's shared folders/webadmin BOTH routers/telnet BOTH routers/etc.)
the .1.100 can ping .2.100 and web admin its router.


:|

 

[user1234]

Originally posted by: i2av

192.168.1.102 is the IP that [.1.1] assigned to [.2.1]
so far, my computer on .2 (the client mode) can access the computer behind .1
but not the other way (gets access denied), the computer behind .1 can ping my
computer behind .2 so i dont see why windows just wont work

If you can do "ping 192.168.2.100" from 192.168.1.100 then it means the routing is working fine. But you're saying that you get accessed denied when trying to "access" the machine, so it means some firewall is blocking the request. What kind of access is it ? Please check the firewall settings on machine 192.168.2.100 as well as on the client router (it should be turned off).

 

[i2av]

EDIT-------

IT NOW WORKS

it turns out it was my pc not working.

hooked up a laptop and sisters pc and they work fine... looks like i get a reformat now
thanks for all the help

2 windows comps and 2 WRT54g's (both with alch)

i am going to try adding a WAP54g in the middle....
wish me luck

 

[user1234]

Actually, if you have two wrt54g's you could even set up WDS mode, in which all PCs are on the same local network (so there is no need to add special routing entries to get them to "see" each other), and each router is also an access point, so you could roam between them with wireless clients. This mode offers more flexibility than my client mode setup, but it does require two flashed wrt54g routers, or at least two routers which support WDS and are compatible with each other (and it's not easy to find out which ones are compatible), so it's defintely not applicable to everyone. If you're interested, you can check out this thread for information on how to set it up.

 

[Jumperus]

Sigh.
It was working fine with no encryption. DNS and everything. Now I cannot get them to work with each other with WEP or WPA. This is getting really old.

 

[Jumperus]

Well, it's working fine now without encryption but with MAC filtering set on the D-Link. That'll do for now as long as no one can access the Linksys (hopefully in client mode it really doesn't allow clients to connect to it.) Not showing up in my site surveys from 4 feet away, so I think all is well. =)