how-to block ads
|
prestonlewis
Premium,MVM
join:2003-04-13
Sacramento, CA
 ·VoiceStick
| Re: using WRT54G as a bridge to another WRT54G said by montee4  :
2 questions..
1) Will you be able to use all 4 ports on the router when it is acting as a bridge?
2) Can you use the WRT54G as a bridge to a non linksys router using the Alchemy firmware?
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. | |
|  willmaier
join:2004-07-29
| Re: using WRT54G as a bridge to another WRT54G I apologize for opening this thread up again, but I've had a rather rough go of things...
I'm using a WRT54G (revision 2, I believe) with the latest stable Sveasoft Satori firmware. I successfully installed the firmware and began configuring the router, as per the topic starter's instructions. I would like to bridge my house 802.11b connection to a PC running Debian Linux (testing, w/2.6.6 kernel). Our wireless AP is a Homeportal 1000SW -- I've set the Network Name/SSID and IP to the best of my ability (our SSID is Phoenix Coop and the IP appears to be static, 64.109.XXX.XXX. I've used the default WEP pass phrase (printed in brackets on the Homeportal's underside), as well.
Despite what seems to me to be a good configuration, I cannot get an IP lease from the Homeportal. I have DHCP turned off on the WRT54G, and when I do:
# dhclient
on my computer, I get several error messages "network down" etc. (dhclient essentially requests a new IP, similar to winipconfig /RENEW, IIRC) Simply, I cannot establish a connection.
It is possible that the wireless network is not functioning well, as the day has been rather wet, but I doubt the functionality has been impaired to such a degree as to render my set up useless.
Thank you for your clear directions, and thanks in advance for any help you can provide. | |
| | smellyirish
join:2004-07-20
| Re: using WRT54G as a bridge to another WRT54G I am trying this today as well, and what I would like to know is, is it possible to not put ANYTHING in the WAN (internet) port and just create a LAN between the two APs?
So it goes
PC---WRT54G----(LAN)----WRT54G---PC
and this can be used for file-sharing and gaming etc and not sharing Broadband?
is that possible | |
| | |
prestonlewis
Premium,MVM
join:2003-04-13
Sacramento, CA
·VoiceStick
| Re: using WRT54G as a bridge to another WRT54G said by smellyirish :
I am trying this today as well, and what I would like to know is, is it possible to not put ANYTHING in the WAN (internet) port and just create a LAN between the two APs?
So it goes
PC---WRT54G----(LAN)----WRT54G---PC
and this can be used for file-sharing and gaming etc and not sharing Broadband?
is that possible
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. | |
| | | | pzero
join:2004-10-11
Italy
| Re: using WRT54G as a bridge to another WRT54G 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. | |
| 
grcore
New and Improved
join:2003-12-06
usa
| 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 | |
| | pzero
join:2004-10-11
Italy
| Re: using WRT54G as a bridge to another WRT54G 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
| Re: using WRT54G as a bridge to another WRT54G 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. | |
| | | | digixmax
join:2004-02-11
usa
| Re: using WRT54G as a bridge to another WRT54G 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. | |
| | | |
|
