mjtq
join:2004-07-30
Fort Lauderdale, FL
|  reply to prestonlewis
Re: using WRT54G as a bridge to another WRT54G
Hi,
I followed the steps to upgrade the firmware and it seems succesfull. However, I haven't been able
to access internet through the wired ports. I haven't
even tried accessing through wireless. However, it
seems like it is connected to the AP as it displays
link rate and AP information in the status window.
This is my setup: I have a US Robotics 8054 wireless
AP/Router downstairs and wan't to use a Linsys WRT54GS
as a bridge and to it I'm going to hook an xbox, vonage(motorola) VoIP, and desktop all wired. I downloaded the Satori version for the
GS and have upgraded it already. The wireless settings
I have already input and seems to be working fine. I'm
concerned about the settings in the basic setup
section and on the wired PCs. What sould I put in the
following sections for the router?
INTERNET SETUP
Internet Connection Type ? Static IP and if so what
gateway and what IP and what mask? or should I put
automatic configuration DHCP?
DNS?
NETWORK SETUP
Local IP address?
Gateway?
Mask?
In the wired PCs:
TCP/ IP settings should be dynamic or static and if
static what should they be?
to further help you answer my questions, this is what
the US Robotics Status page shows:
WAN
MAC Address 00-c0-49-e5-26-73
Connection DHCP Client Connected
IP 192.168.102.100
Subnet Mask 255.255.255.0
Default Gateway 192.168.102.1
DNS 24.233.175.145 12.38.60.20
AP ONLY
LAN
MAC Address 00-c0-49-e5-26-72
IP Address 192.168.123.254
Subnet Mask 255.255.255.0
DHCP Server Enabled DHCP Table
Wireless
MAC Address 00-c0-49-e4-19-a9
ESSID USR8054
Channel 2
WEP 128 bits
PS Is it possible to use a vonage(motorola) device for VoIP connected to one of the wired ports of the wrt54gs immediately or do I have to do any mods to the setup? |
|
prestonlewis
Premium,MVM
join:2003-04-13
Sacramento, CA
 ·VoiceStick
| said by mjtq  :
1. 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.
2. The WRT54G in bridge mode only needs the wireless settings changed. Don't worry about the "basic setup" section since they control the WAN port which should be left unused. You only need to make sure the IP address of the bridge is different from any other device in your network. WRT54Gs usually come preconfigured as 192.168.1.1 and that usually needs to be changed to something else like 192.168.1.2 depending on what router/ap you're using (some routers use 192.168.0.1 for example).
In bridge mode, the WRT54G is only using it's wireless functions and it's switch function and nothing else. DHCP can be turned off if you want or just ignored. DNS doesn't need to be setup. Your wireless client devices should have their gateway setting set to your router, not the bridge, so DHCP requests and DNS requests will go to the router and the bridge will not get those requests. So in each client device, setup the gateway and DNS settings using the router's IP address. DNS/DHCP should work automatically if the gateway (router) is known by the client. If the clients are setup properly, the bridge won't need DNS settings.
For wired PC's connected to the bridge, most people use DHCP (dynamic) and that allows your router (not the bridge) to give it a IP address. If you do use static addresses, make sure you know what address' your router will assign and use something else. For example, my router will assign 192.168.1.100 - 150 so my server has a static address of 192.168.1.90 which the router would never assign and possibly cause conflicts. If you use static address', you may need to know your DNS settings to enter them into the client computer manually or you can use the router's address as the DNS address.
In your wireless settings, I see you're using WEP 128 bit encryption. Make sure all your wireless devices, including the bridge, have the same 26 digit password as the AP. If you use keys (Key 1 for example), they have to be hexadecimal (0-9 and/or A-F only, never G-Z). An example of a 26 digit hexadecimal password for Key 1 might be two phone numbers and 6 letters like:
91655512128036252081ABCDEF
The first 10 numbers is information in the 916 area code, then another 10 numbers that used to be a family phone number in SC followed by the 6 letters allowed in hexadecimal equalling 26 digits. WEP 64 bit encryption requires 10 digits but is less secure.
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. Good luck. Aren't computers fun? |
|
mjtq
join:2004-07-30
Fort Lauderdale, FL | Thanks for your post. It helped clear things up a lot. |
|
smellyirish
join:2004-07-20 | Yes, since my post, iv been working hard to get it to work and got it working within the day.
Great guys for helping me and I am very thankful |
|
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. |
|
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. |
|
