acorderob
join:2004-08-15
Spain
| reply to prestonlewis
Re: using WRT54G as a bridge to another WRT54G
said by prestonlewis  :
When using MAC filtering for wireless, every authorized device that get a data packet has to be included in the MAC filter list. So the bridge's MAC address, all client devices, anything that is part of your home wireless network has to be in the MAC filter table (except for the device that is doing the filtering).
My wireless devices are only the router and the bridge. My test was setting MAC filtering in the router, adding the bridge MAC address to the list of authorized addresses. With this filtering activated, after the first transmission (just a ping) the wireless connection between router and bridge is closed, and the transmission fails.
quote:
If you're worried about unauthorized use of your wireless network, why not try WEP 64bit encryption?
I'm currently using WEP-128bit but i have read that it is somewhat insecure (i'm not sure at this point if WPA works correctly with this firmware).
Anyway, even with WEP, some other MAC addresses appear in the wireless status tab, so i suppose others are connecting to my router (even if i don't broadcast my non-default SSID). |
|
grcore
New and Improved
join:2003-12-06
usa
| reply to prestonlewis
said by prestonlewis :
Yes, all 4 LAN ports work fine in bridge (client) mode. You can add a switch to one of the ports to have even more ports available. I've done that without problems. As for your 2nd question, a WRT54G in client (bridge) mode doesn't care what access point it is using. It just needs to have ssid, channel, encryption, etc. set to match. I don't think it matters which version of firmware you are using. As far as I know, Samahdi, Satori, and Alchemy all work the same when it comes to bridging and the brand of access point used isn't an issue.
with Satori in client mode, only 1 device is allowed to be connected that unit. If you add more it won't work properly.
The client mode of Samahdi and Satori are pretty much the same, Alchemy does thing differently. With Alchemy, the wireless interface becomes the WAN interface of the router. This allows multiple clients to be connected to the client mode WRT (on their own subnet).
When you set a WRT to client mode it loses its ability to be an AP, so devices cannot connect to it via wireless (all devices must be wired to it).
G |
|
juztinp
join:2004-11-06
Victoria, BC
| reply to doug12
This topic rocks. I know I'm a few months behind everybody but using the information in this forum I was able to get my WRT54GS bridging with my WRT54G.
One problem that wasn't corrected in this forum that I found on another one
»www.netstumbler.org/showthread.php?t=12027
is had to do with intermachine communication on the network. I set everything up and machines cabled to either WRT could access the internet but even though they were on the same internal network they had dificulties pinging each other for some reason.
If machine A cabled to the gateway WRT tried to ping machine B cabled to the bridge WRT it would almost never work. After a fresh release/renew one packet in 4 might get through. Very odd behaviour for sure.
The solution was to go to the Administration/Management page and disable 'loopback'. After that pings went through and I was able to setup windows shares which previously had not been possible.
Cheers,
Justin |
|
Yauh
@65.73.x.x
| reply to doug12
I too am having issues with bridging two WRT54G Aps. I rumming Mandrake Linux on my server to an AP which has a omni antenna, which is then sent to a panel antenna 100 yards away, which is connected to another AP and from there to a Windows machine. I have tried Alchemy as well as Satori, but cannot get either to work properly. I am able to get Satori to work, but not with a pre-shared key. When I disable wireless security this all seems to work. I have also tried different vendors for firmware, meaning the client ap is using the SAtori firmware and the AP is using WiFi-box.net release Version 2.00.8.1h firmware. I originally tried both APs with alchemy and it seemed to be the best option except I could not seem to browse the internet in either PSK or disabled mode.
What am I doing wrong. The DHCP is coming from my linux box, and I am not using any of the other added functionality of the firmware. I simply want to be able to send my DSL signal wirelessly 100 yards away. Any ideas? |
|
pzero
join:2004-10-11
Italy
| reply to prestonlewis
said by prestonlewis :I think you mean a wireless LAN between the two WRT54Gs without using any WAN ports, right? If so, then yes you can do this but one WRT would have to be in access point mode and the other WRT would have to be in client mode. Both WRTs would have to have different IP addresses. The SSID, channel number, and encryption scheme would have to be the same between both WRTs. Also, the WRT set as the access point would need to have DHCP on if any client gaming/file sharing client needed it and any gateway settings would have to use the APs IP address. I'd turn DHCP to off on the client WRT. DNS settings would be for the access point WRT's IP address if needed for setup on a client. This is what I want to do too.
I have two LinkSys WRT54GS wireless routers.
I would like to use them to setup a wifi bridge between two buildings.
Then I'll attach the computers of each building to the LAN ports of the WRT54GS (wired, not via radio).
I want the computers of both building to be on the same network (e.g. 192.168.0.1/255.255.255.0).
The I also want to share the broadband connection, since one of the building has a high speed connection to the Internet using a Cisco router.
What is the best way to realize such wifi bridge?
Set one WRT54GS in AP mode and the other one in client mode?
Or maybe using WDS?
Any other way?
What firmware should I use? The official one, the Sveasoft one, HyperWRT or any other?
Thanks. |
|
pzero
join:2004-10-11
Italy
| reply to prestonlewis
said by prestonlewis :I had problems with the Satori and ended up using HyperWRT which I now use without problems. If all else fails, try HyperWRT version 1.3 and see if things work. So HyperWRT also has the functionaly to set up a WRT54G/WRT54GS in client or AP mode?
I thought only the Sveasoft firmware had this functionality ...
What about the official firmware?
Thanks. |
|
pzero
join:2004-10-11
Italy
| reply to grcore
said by grcore :with Satori in client mode, only 1 device is allowed to be connected that unit. If you add more it won't work properly. This is a big limitation IMHO, any workaround for it?
The client mode of Samahdi and Satori are pretty much the same, Alchemy does thing differently. With Alchemy, the wireless interface becomes the WAN interface of the router. This allows multiple clients to be connected to the client mode WRT (on their own subnet). This sounds interesting. Will I still be able to use two WRT54G/WRT54GS boxes to create an ethernet (wifi) bridge between two LANs using the same network (e.g. 192.168.0.1/255.255.255.0) on both sides of the bridge.
Any ETA about the Alchemy public release?
Thanks a lot. |
|
digixmax
join:2004-02-11
usa
| I'm been trying to get my new WRT54G running Satori-4.0 to be a client to my old BEFW11S4 without much success. I was able to ping the BEFW11S4 from a PC which is wired to the WRT54G for just a short period of a minute or so during the course of hours of fiddling.
Can someone who has succedeed in using a WRT54G client with another non-WRT54G wireless router post the client setup configuration and procedure?
Thanks. |
|
claudeo
join:2000-02-23
Redmond, WA
| reply to prestonlewis
said by prestonlewis : said by mjtq :
I don't think you can set up encryption in the Vonage SIP device. That may be a problem for you. If encryption isn't allowed in your SIP device, you may have to turn encryption off and use MAC filtering or plug your SIP device into the router using a wired LAN port and use cordless phones. That should not matter. The encryption only applies to the wireless communication between the wireless devices. Things connected by cable to those devices do not participate in that. |
|
digixmax
join:2004-02-11
usa
| reply to digixmax
I just want to report that I am finally able to get my WRT54G in client mode to work with my BEFW11S4. The client WRT is setup based on the guide »homepage.ntlworld.com/linksysinf···UIDE.pdf. The problem I had appears to be due to the use of wireless MAC filtering on the BEFW11S4. For some reason, even adding the MAC addresses of the client WRT and the attached PC to the filter list did not work, but disabling the wireless MAC filtering entirely and then power-cycling the BEFW11S4 did it. |
|
hfam95
join:2003-06-20
Woodbridge, VA
| reply to prestonlewis
said by prestonlewis : said by acorderob :
Hi. I have a problem with the bridge.
It works perfectly except when i set up MAC address filtering in the first router. When i do that the second router connects to the first wirelessly (appears in the wireless status tab), but after the first transmission of actual data (for example, a simple ping to the first router) the connection is broken and i have to reset the second router to get it again.
When using MAC filtering for wireless, every authorized device that get a data packet has to be included in the MAC filter list. So the bridge's MAC address, all client devices, anything that is part of your home wireless network has to be in the MAC filter table (except for the device that is doing the filtering). Remember, MAC address' are hexadecimal. They only use numbers 0-9 and letters from A-F so if you have any letter from G-Z in your MAC client table, you've made a mistake somewhere. If you're worried about unauthorized use of your wireless network, why not try WEP 64bit encryption? It only requires a 10 digit password key (hexadecimal again) and I usually use the phone number of an out of state relative which is 10 digits long. The bridge and all client devices will have to be set to match it but it's probably better protection than MAC filtering. not true. I got a dwl-g820 and it works for my xbox. i have the xbox in mac filtering, but not the 820, and it works. |
|
