Virtual Brain Online Logo

Bookmark: Root \ Networking \ HOWTO: Use Linksys WRT54G as a wireless ethernet bridge

HOWTO: Use Linksys WRT54G as a wireless ethernet bridge


Last Updated: 2005-12-02

Topic Title HOWTO: Use Linksys WRT54G as a wireless ethernet bridge

Date Posted: 02/07/2005 02:00 PM Posted By: user1234(Platinum Member)

This howto is intended to help people who currently use a wireless router in their house, and also have additional PCs or devices without wifi cards which cannot be connected to the wireless router using a cable because they're too far from it (like in another room).

This howto will explain how to use the wrt54g a to connect these remote PCs to the internet and your home network, without using wifi cards. This is possible using 3rd party firmware (sveasoft) which allows the wrt54g to operate in "client" mode, where it forwards packets from its connected devices to the main wireless router, using a wireless link.

I got my wrt54g running in client mode - that is, it serves as a bridge between a PC attached to it and the main wireless router. Here's my complete setup, starting with the wired connections (markeded by "<===>"):

Room 1: Cable Modem <===> D-Link DI-624 Wireless Router <===> PC-1
Room 2: WRT54G <===> PC-2

The DI-624 and the WRT54G connect to each other wirelessly. I also have a mobile laptop which connects wirelessly to the DI-624.
So in this case, the WRT54G let me use PC-2 without having a wifi card in that PC. In fact, I could connect up to 4 PCs to the wrt54g, and save the price of 4 wifi-54g pci cards, plus I don't have to install drivers for wifi cards (a pain in Linux). The wrt54g acts like a "wireless ethernet bridge", which in fact is another product sold by linksys (WET54G) for around $150. This is also useful when you have devices (in a room which doesn't have ethernet connections) which can only connect using a ethernet cable, but cannot connect wirelessly - like XBOX !

So how do you do it ? Here's the list of steps - you should be doing these steps (except step 1) from a PC attached to the wrt54g (e.g. PC-2 in my setup). Physically attaching a PC to the wrt54g is required only for this initial set up phase, because we need to login and set up the various options. Note that this doesn't require any changes to your main router's configuration, so it's quite safe with regard to not messing up your current networks' setup.

1. Download the "wrt54g alchemy firmware" (google this, or go here) version 6rc5 from the internet (it is the only one compatible with the new models wrt54g V2.2 & wrt54gs V1.1).
2. Upload the firmware to the wrt54g via the "Administration->Firmware Upgrade" option in the router's web interface.
3. Reset the device (press reset button until power led flashes - this could take 20 seconds or more). In the following steps, leave all settings which are not mentioned in the description at their default (only change the ones specifically mentioned in the step).

Note: We will use addresses that end in 128-255 for the wrt54g router and it's attached PCs. To make sure there is no overlap in the addresses assigned by the two routers, we have to make sure that your main router only assign addresses below 128 to its own clients. For example, if your main router address is 192.168.0.1, its DHCP address range could be 192.168.0.50 - 192.168.0.120. Another important note regarding the main router: some routers allow you to disable the broadcast of the SSID, but for this setup to work properly the SSID broadcast MUST BE ENABLED (which is usually the default behavior).

4a. In "Setup::Basic setup" screen, set Internet Connection Type to "Auotomatic Configuration - DHCP".
4b. Set the local IP to 192.168.0.129, assuming your main router is 192.168.0.x (in general, if your main router is a.b.c.d set the wrt54g to a.b.c.129).
4c. Set the Subnet Mask to 255.255.255.128.
4d. Set the "Gateway" to the IP address of your main router (e.g. 192.168.0.1).
4e. Set the DHCP Server to Enabled, and starting IP Address to something above 129 (e.g. 140).
4f. Save the settings on this page. You should reboot the attached PC, since the subnet mask has changed. Note: from now on you have to use the new local IP you set in step 4b (e.g. http:// 192.168.0.129) to connect to the router from your PC.

5. In "Setup::Advanced Routing" screen, make sure operating mode is "Gateway".

6. In "Wireless::Basic Settings" screen, set Wireless mode to "Client", wireless network mode to "mixed", and SSID to your main wireless router's SSID.

7. In "Wireless::Security" screen, set yor WEP/WPA settings which match the main wireless router. You should now be connected to the main wireless router. Note: if you have MAC filtering set up on the main router (which allows only specific clients to connect), then obviously you have to add the client router to the list of allowed clients.
To verify that you've established a connection to the main router, you can check the "Status::Router" screen, which should show an IP Address assigned by the main router (which would end with a number below 128), and the "Status::Wireless" page should show the AP Signal strength together with the mac address of the main router. Also you should now be able to ping the main router and even log in to it (using h ttp://192.168.0.1) from the PC attached to the client router (the wrt54g).

8. In "Security::Firewall" screen, disable firewall protection, as this subnet is already behind your main router's firewall. Also make sure that "Block Anonymous Internet Requests" is unchecked.

9. In "Administration::Management" screen, you can leave all settings at their default. You may want to enable remote management and Telnet or SSHD, especially if you want to be able to log in to the wrt54g from a computer which is not directly attached to it.

10. To enable PCs attached to the main router to be able connect to PCs attached to the wrt54g: Login into the wrt54g using telnel or ssh by running the command "telnet 192.168.0.129" and use same root/passwd as for the web interface. Then type this command (copy it exactly):

# echo 1 > /proc/sys/net/ipv4/conf/`route | grep default | awk '{print $NF}'`/proxy_arp

Now you should be able to ping/telnet to any PC attached to the wrt54g from any PC attached to the main router. Btw, this assumes that the subnet mask of the main router is the default 255.255.255.0.

Important note about the last step : The last step (which is an optional step) allows PCs attached to the main router to be able to connect to PCs attached to the client router, by specyfing the IP of the destination PC, for example "telnet 192.168.0.150". But they are still on two different subnets which do not share their broadcast messages, therefore when browsing PCs on the local network you will not automatically see the PCs attached to the other router. But you can always connect to them by explicitly specyfing the IP. Btw, this step was added after the initial posting of this HOWTO and solves a lot of the issues people discussed later in this thread, so don't worry if you read posts in this thread about problems with communicating between PCs attached to different routers. Also note that this proxy_arp setting is not saved in the WRT54G non-volatile memory like all the other settings, so when the router is rebooted (like after a power outage), it will be cleared and you will need to repeat step 10 to set the proxy_arp back on.


Done !!! That's it !!!!

So in summary, you don't need two wrt54g routers, nor do you need WDS capable routers. A single wrt54g (with the right firmware) can operate as a "client" of any other wireless router, and create a bridge so any device connected to it will be able to access your network and the internet. The above works great for me, even with 3-4 PCs attached to the wrt54g (verified that it works).


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/27/2005 at 10:30 PM by user1234

Date Posted: 02/07/2005 02:57 PM Posted By: Oakenfold(Diamond Member)

I'll have to give this a shot, not that I need it but it sounds pretty interesting.
I'm currently using the sveasoft fw and can't remember if these options were in it or not.

-------------------------
Paul Van Dyk is teh Uber! VANDIT FOREVER! Heatware Linkage

Current CCNA in training Flunky



Edited: 02/07/2005 at 02:58 PM by Oakenfold

Date Posted: 02/07/2005 04:11 PM Posted By: user1234(Platinum Member)

The setup I explained above creates two networks in a hierarchy. The first one is created by the main router, which uses NAT to translate betwen the local addresses and the main address it gets from the ISP. The second network is created by the client router (the wrt54g) which translates the address in its client network to the address it gets assigned by your main wireless router. So it's a double NATed configuration, with packets originating in the client network doing one extra hop.

This setup has some a small limitation when a PC connected to the main router needs to connect to a PC on the client router's subnet. This will not work, since the main router will just forward it to the WAN (internet) because it's not really aware of the client router's subnet (the devices attached to the wrt54g). On my D-Link DI-624 there is no way to teach the router that it has a client router with its own separate subnet, which all datagrams addressed to 192.168.1.xxx should go to, because the DI-624 is not programmable like the wrt-624 is, so you can't change its routing tables. So to enable computers attached to the main router to connect to computers attached to the client router, I have to add a rouing table entry to each of the computers on the main subnet.

For example, in my case the main router (DI-624) is 192.168.0.1 and PC-1 attached to it is 192.168.0.101. The wrt54g is 192.168.1.1 and its attached PC-2 is 192.168.1.100. Also the wrt54g gets a dynamic IP from the DI-624 which is 192.168.0.112 (DI-624 allows static DHCP, so I can make sure it always gives the same IP to each physical device). So I can always access the wrt54g using this address (e.g. http: //192.168.0.112), from any PC attached to the main router (e.g. PC-1), assuming remote administration is enabled on the wrt54g, like I suggested in the steps above. But to get PC-1 to access PC-2, I have to instruct it to route requests addressed to 192.168.1.xxx thru the wrt54g, like this:

# route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.0.112

I have to do the above on every PC attached to the main router, if I want it to be able to talk to PCs on the client network. If your main router is also a wrt54g, you could try adding this entry on the main router, and it should then route request to connect to the client subnet correctly, for all its attached PCs.




-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/08/2005 12:51 AM Posted By: VirtualLarry(Diamond Member)

Sorry, I replied to the other thread, without seeing this one first. A couple of questions:
1) I would be very interesting to know if it works to connect multiple PCs to the wired ports of the WRT54G while operating in Client AP mode, and whether/how this works with NAT disabled. Last I knew this wasn't currently possible, but was being worked on.
2) From what I understand, there is a limited set of other routers that will interoperate wirelessly (Client AP mode and/or WDS) with the WRT64G running Sveasoft firmware. The D-Link is one of them. You might not be so lucky with other brands/models.
3) I was under the impression that doing Client AP mode, or perhaps just WDS, was limited to only using WEP, not WPA. Has this changed? WEP is easily crackable.
4) Why use "Gateway" mode on the WRT54G when in Client AP mode? Why not use "Router" mode, and set up the subnets and routes?

It's really cool that you got that all working, I admit. I had similar plans, with a LinkSys 'b' router (Realtek 8181 OEM platform), and a WRT54G (running Sveasoft), but when I found out how dodgy Sveasoft was, and that I couldn't find an easy way to get updated Realtek firmware onto the other box, I decided against my original plan, and picked up a WUSB54Gv1 for my main PC to use as a client NIC, and use a switch and run ICS on my main PC to allow my laptop access to the net via WiFi as well.



Date Posted: 02/08/2005 01:16 AM Posted By: user1234(Platinum Member)

1) Yes, I just connected another PC to the wrt54g and writing this from it, while the other one is playing ut2004 online !
2) Who told you that ? there is nothing special about what the main router has to do. In fact the main router (d-link di-624 in my case) treats the client router as just another wireless client with an address on it network (usually assigned via dhcp). The client router (wrt54g) translates between that address and the computer attached to it on its own client network (this is NAT, you know). So using this NAT, the wireless link between the main router and the client router is shared by all the PCs attached to the client router. As I said, the main router does not know or care about this, just like your ISP doesn't know how many computers share the address it assigns to your home.
3) Since the client router (wrt54g) acts just like any wireless client of the main router, it can connect in any way which is supported for wireless clients, including WPA, etc (haven't tried it though).
4) Gateway mose is the standard mode where the router performs NAT and forwards packets to its gateway router, which is the case in this configuration. I'm not sure what router mode does, maybe it doesn't do NAT ? Theoretically, I guess it could be possible to set this up as a single network, that is the PCs attached to the main router and and PCs attached to the wrt54g to be in the same netwrok, and possibly even use only one DHCP server. In that case, the second router (wrt54g) will not have to perform NAT. But I'm not sure that there's any addvantage to doing it this way (single network) compared to my client network solution. And it's not clear if this could actually be done using any available firmware. I do know that some people got WDS mode to work, but this requires two programmable routers like the wrt54g. My solution should work with any other router.

Maybe other configurations could also work, but I think my solution works quite well.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/08/2005 at 01:43 AM by user1234

Date Posted: 02/08/2005 05:19 PM Posted By: user1234(Platinum Member)

bump

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/08/2005 08:04 PM Posted By: skyking(Diamond Member)

quote:
I would be very interesting to know if it works to connect multiple PCs to the wired ports of the WRT54G while operating in Client AP mode, and whether/how this works with NAT disabled. Last I knew this wasn't currently possible, but was being worked on.


Larry,
user1234 has it working with nat enabled.

-------------------------
Heat



Date Posted: 02/08/2005 08:40 PM Posted By: VirtualLarry(Diamond Member)

Thanks for the reply user1234. (Hope I got the caps right this time. )

The reason that I was asking about running multiple wired PCs behind a WRT54G running in Client AP mode or WDS mode, without NAT, was because of how the other wireless router would see things in terms of MAC addresses. (It will only see the MAC address of the Client WRT54G's wireless NIC, not the MACs of the machines connected to it via the wired ports, at least not without running in wireless bridge mode or WDS mode) NAT obviously solves that problem, at the IP level, but that would prohibit running things like Windows' file-sharing over the wireless-to-wireless link between machines connected to the two wireless routers. (Something that I would want to do, if I could get it working.) So perhaps leaving NAT enabled, is key to getting multiple wired PCs working, at the cost of a double-blind NAT setup. I wish WiFi just simply worked, like Fast Ethernet does and has for years.

However, you wrote:

quote:
So to enable computers attached to the main router to connect to computers attached to the client router, I have to add a rouing table entry to each of the computers on the main subnet.


How is that possible to implement, if the wireless router in Client AP mode is running NAT? There's no way to route to a machine behind a NAT, their addresses simply aren't visible on the "public" side of the NAT, period. (The side facing the "main" router.)

Did you actually test that that works? Can you ping the PCs connected to the wired ports behind the client AP-mode router, from PCs attached to the wired ports on the "main" router? If so, then I suggest that either NAT is not operational, somehow (perhaps it doesn't apply to the wireless link, only to the wired "WAN" port on the client router), or the two wireless routers are actually talking to each other in WDS mode, which as I mentioned before only works between a limited subset of devices, since WDS-mode protocol is not fully standardized, but your D-Link is one that I've read mentioned that will operate in WDS mode with a WRT54G running Sveasoft firmware. So I'm wondering how much of this is replicable with other-brand routers, or if you sort of happened to "get lucky" with your choice of hardware, and it turned out to be compatible.

I really do appreciate your posts and info though, I'm trying to learn as much about this as possible, and your experience is valuable.



Date Posted: 02/08/2005 10:09 PM Posted By: user1234(Platinum Member)

Well, first of all NAT is enabled in the client network, since the machines in that network have a different network address (the prefix) then the network address of the main router. And second, it is working, as I can ping, ssh, sftp, VNC, http, and even use freeNX (remote X-windows) between the machines in the two networks in both directions.

I agree that normally it's not possible for outside packets to be directed to PCs behind a NAT router, but I guess it doesn't apply for this special "client" mode. I think that allows requests for the NATted addresses to be forwarded by the wrt54g to the PCs in its network without doing any translation.

So to route a packet from the a computer (e.g. PC-1) in the main network (attached to the D-link di-624), to a computer (e.g. PC-2) in the client network (attached to the wrt546), all I have to do is tell the PC-1 to send the packet to the wrt54g, using the wrt54g address on the main network.

My complete network setup is like this:

Main network: PC-1 192.168.0.101 <=wired=> DI-624 192.168.0.1 <--wifi--> wrt54g 192.168.0.112

Client network: wrt54g 192.168.1.1 <=wired=> PC-2 192.168.1.100

As you can see the wrt54g has an address on both networks (thanks to NAT), but it forwards requests addressed directly to computers in its network without doing any translation. This is probably the idea behind sveasoft's client mode, which is a different mode then AP/WDS, so I don't think any of the routers are operating in WDS in my setup.


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/08/2005 at 11:08 PM by user1234

Date Posted: 02/09/2005 12:54 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: VirtualLarry
Thanks for the reply user1234. (Hope I got the caps right this time. )



This is not a laughing matter. My user name is case sensitive. Tell me, how many times you arrive at your computer in the morning, half asleep probably, and type in your password, only to get "access denied, please try again" response ? and after trying it a couple more times, banging on the keyboard and ready to smash it into bits, or call IT and vent your anger on them... only to find out that the caps lock key is on ?



-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/09/2005 at 12:55 AM by user1234

Date Posted: 02/09/2005 01:42 AM Posted By: VirtualLarry(Diamond Member)

quote:
Originally posted by: user1234
Well, first of all NAT is enabled in the client network, since the machines in that network have a different network address (the prefix) then the network address of the main router. And second, it is working, as I can ping, ssh, sftp, VNC, http, and even use freeNX (remote X-windows) between the machines in the two networks in both directions.

I agree that normally it's not possible for outside packets to be directed to PCs behind a NAT router, but I guess it doesn't apply for this special "client" mode. I think that allows requests for the NATted addresses to be forwarded by the wrt54g to the PCs in its network without doing any translation.

So to route a packet from the a computer (e.g. PC-1) in the main network (attached to the D-link di-624), to a computer (e.g. PC-2) in the client network (attached to the wrt546), all I have to do is tell the PC-1 to send the packet to the wrt54g, using the wrt54g address on the main network.


But that means that the IP addresses of the PCs on the wired side of the client wireless AP are routable over the LAN - therefore NAT isn't being used there. It may be enabled, but it's likely not being actively used for those connections.

quote:
Originally posted by: user1234
As you can see the wrt54g has an address on both networks (thanks to NAT), but it forwards requests addressed directly to computers in its network without doing any translation.


Well, NAT doesn't give out IP addresses nor configure them, if the router has an IP address on both interfaces (one connected to each network), then either you've configured them manually, or it's getting them (or one of them) from a DHCP server (which you've mentioned that the front-facing wireless interface does get one from the main router), or the firmware auto-sets one. Nor is NAT actively being used if there is no address-translation going on.

quote:
Originally posted by: user1234
This is probably the idea behind sveasoft's client mode, which is a different mode then AP/WDS, so I don't think any of the routers are operating in WDS in my setup.


Well, I'm just trying to point out that with only Client AP mode and NAT being used, what you claim is possible with your current setup (bi-directional pinging), should not be possible. So there must be some hidden magic going on here, and I'm suggesting that that "hidden magic" is what is really allowing this all to work, so it would be useful to find out what that is.

Can you do us all a favor, and set the client AP wireless's IP to a static IP in the same subnet as the "main" AP, and then configure the PCs connected to the wired ports on the client AP to use DHCP, and see if they are able to request and obtain an IP from the "main" router's DHCP server? That would be proof-positive that layer-2 broadcast frames are sucessfully negotiating the wireless link in both direction between the APs, which would likely indicate that either "wireless bridge" or WDS is active, whether you've explicitly configured them to be or not.

Another possibility, would be to assigned static IPs on the same subnet to every machine, disable NAT, and see if you can still connect bi-directionally and ping between wired PCs attached to each wireless AP.

I suppose that it's possible, that what Sveasoft's Alchemy firmware calls "Client AP mode", may not actually be that at all.

From what I understand, the way that WDS and wireless bridging mode works, is by having *two* source and destination MAC addresses in the wireless frames. Essentially, it works almost like addressing letters with a "C/O" ("care of") name on them. There is the immediate source/destination MAC address, and then a sort of sub-address. So in that way, an ordinary wired ethernet frame, coming from a PC on a wired port on the client AP, would have a source MAC from its ethernet card, and a destination MAC.. well, assume a broadcast frame (DHCP request) for now, so all 0xFF's. All of the PCs on the local wired ethernet switch fabric would recieve the frame and discard it, as well as the AP, which wouldn't discard it, and would either answer with a DHCP reply if it was running a DHCP server, or forward the broadcast frame over the wireless link if so configured. It would likely "wrap" the frame, containing the wired PC's source address, and send it over the wireless link with a source MAC of the AP's wireless interface, with a destination MAC of the other AP's wireless, or a broadcast, I'm not sure which. The "main" AP would recieve the frame over it's wireless interface, and if it was running a DHCP server, then it would send a reply back, with a primary destination MAC of the client AP's wireless interface, source MAC being the main AP's wireless interface, and a sub-destination MAC of the original wired PC that initiated the broadcast DHCP request frame. Whew.



Date Posted: 02/09/2005 03:48 AM Posted By: user1234(Platinum Member)

Hmm... ok, I think you're confusing things, and I'm getting a little confused as welll.... no wait, I do understand how my setup works, maybe I need to explain it again. But first, let me clarify again that it works 100% right now, and I'm pretty sure it would work with any router as the main one, and the wrt54g as the client. Second, wrt54g is operating in a special "client mode" which is not AP mode - these are two different modes you can choose between with this firmware. Lastly, DHCP is completely optional - you could set up the same configuration by specyfing static addresses for each computer.

Ok, now for the clear and simple explanation. The main router is the default gateway for all the devices attached to it, wether wired or wireless. That means that any packet addressed outside the local network (192.168.0.xxx in this case) is sent to the main router, which then performs address translation on it, and forwards it over the WAN connection to the internet, . All the devices attached to the main router have addresses in this private local network, including the client router (wrt54g - its address is 192.168.0.112) which connects to the main router wirelessly.

Things work pretty much the same way in the client's router private network (the wrt54g and its attached devices - all have addresses 192.168.1.xxx). The client router is the gateway for all its attached devices, which means that all packets addressed outside the client private network are sent to the client router, which performs NAT and forwards them to the main router. So the main router doesn't know about all the devices in the client network, it only sees the client router with the address 192.168.0.112.

So with this setup the computers in the client network can contact any computer in the main network or the internet, because all externally addressed packets are forwarded by the client router to the main router (192.168.0.1). Now the tricky part is how to route packets originating in the main network to computers in the client network. This is tricky because the main router doesn't know about these computers and their addresses. In fact, it doesn't even know that the 192.168.1.xxx network exists (except maybe somewhere on the internet). That's why I need to manually add a routing table entry which says - "send all packets addressed to 192.168.1.xxx over to local device 192.168.0.112 (the wrt54g), instead of sending it over to the WAN interface". Now, normally the wrt54g should not accept packets addressed directly to its local private network, because all the packets it sends are NATed, so all replies should come addressed to its external address. But the special magic of "client mode" is that the wrt54g accepts packets addressed to its own private network, and forwards them to the appropriate attached PC. I hope you understand it now.

If you want to understand better, here's the routing tables of PC-1, PC-2 and wrt54g. Unfortunately, I can't dump the routing table of di-624, but it's quite obvious what it would be):

Routing table of PC-1:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 192.168.0.112 255.255.255.0 UG 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

Here's the routing table of the wrt54g:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 br0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth1

Here's the routing table of PC-2:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

Study the above and you will get it how it works.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/09/2005 at 03:59 AM by user1234

Date Posted: 02/09/2005 05:00 AM Posted By: VirtualLarry(Diamond Member)

quote:
Originally posted by: user1234
Second, wrt54g is operating in a special "client mode" which is not AP mode - these are two different modes you can choose between with this firmware.


Hmm, that seems a bit unclear then. I have no idea what Sveasoft's "client mode" is or does then, if it is not the same thing as what is commonly referred to as "Client AP mode", which is when a wireless access-point that negotiates/communicates with another wireless access-point running in infrastructure AP mode, as if it (the first wireless AP) was a simple wireless client NIC instead of an AP. (Which is what I thought your original description was about.)

Generally, "wireless bridging mode", operates point-to-point between two wireless APs, and requires manually configuring both APs with each other's MAC addresses as the two endpoints of the "bridge". However, I've heard reports of LinkSys WRT54 devices (running stock firmware), being able to operate in "bridge mode" in conjunction with a LinkSys WET54 wireless bridge device, without requiring manual configuration. (But not between two WRT54G's.) I'm not sure how that works.

The third is WDS mode, which allows multiple wireless APs to talk to one another, and also bridge ethernet frames from any connected wired devices. I don't know a lot about it, but as I understand it, it is not a standardized part of the 802.11 spec, and different mfgs implement it differently, so interoperability is rather hit-or-miss with WDS. Supposedly.

Client AP mode is not bridging, and the remote wireless AP in infrastructure mode will only see the MAC of the wireless interface of the client AP operating in client AP mode, AFAIK.

Maybe I'm missing something here, and perhaps the Sveasoft firmware when operating in client AP mode (sorry, "client mode") will proxy-arp and MAC-translate for the other devices attached to the wired ports. I guess that would allow for IP packets to pass and get routed between each wireless AP, but it wouldn't allow things like ethernet DHCP request/reply broadcast frames to pass, I don't think.

That sort of makes sense then, and means that NAT actually isn't applicable here, since the "translation" is happening at layer-2, not layer-3.

In other words, from the point-of-view of the "main" wireless AP in your example, all of the IPs assigned to PCs attached to the wired ports behind the client AP belong to the client AP and have the same MAC as the wireless interface on the client AP. However, when IP packets arrive at that interface, the client AP bridges them individually to the proper device's wired ethernet ports, using that device's MAC address that is known only to the client AP, not to the remote "main" AP.

It then makes sense, if the PCs behind the client AP are on a different IP subnet than those PCs connected to the wired ports on the "main" AP, then by default IP packets sent out from the "main" AP would get routed to the default gateway, which is the WAN interface, and they wouldn't go anywhere, so you have to manually configure the routing to assign the gateway for the client AP's local subnet to be the IP of the client AP's wireless interface, so that the packets will reach there. (Or I might have that slightly wrong, maybe the gateway for that subnet would be the "main" AP's wireless interface.)

Now this is starting to make some sense.

In fact, it would seem that the above probably would not work at all, if all of the devices, both the ones wired to the "main" AP, as well as ones wired to the client AP, were all on the same subnet. They have to be different subnets. But NAT has nothing directly to do with anything either, since no layer-3 address-translation seems to be needed nor happening.

What would be interesting then, to test this out, would be to ping from a PC attached to a wired port on the "main" AP, to a PC attached to a wired port behind the client AP, and then dump the ARP table ("arp -a" on Windows, I think), and see if the MAC address associated with the IP of the machine behind the client AP is the same as the MAC of the client AP's wireless interface.

In fact, ping several different PCs behind the client AP, from a PC on the "main" AP, and see if all of the MACs are the same, and that that MAC is the same as the client AP's wireless interface. If so, then my theory fits. If not, and those MACs are in fact the real MACs of the ethernet interfaces of each of the PCs wired behind the client AP, then something else is going on, and it is likely that WDS mode is enabled and running.

Edit: In case it wasn't totally clear, what I'm suggesting is really going on here is slightly different than NAT. Normally, all machines behind a NAT are on a local subnet with private IPs, and from the outside, there is only a single public IP address. In this case, it's a little different, from the outside, there is only a single MAC address visible, that of the client AP's wireless interface, but it appears to have multiple IP addresses, in fact all of the IPs of the machines behind it. The client AP recieves the frames with its own wireless MAC as the destination address, containing an IP packet with a destination IP that actually belongs to another machine, but to the outside, it appears to belong to the client AP. So it re-sends the ethernet frame containing that IP packet, except over the wired interface, with a destination MAC of the correct PC that corresponds with that destination IP on the local wired ethernet segment.

This is all the same basic sort of proxy-ARPing that goes on, with a dial-in RAS server on a local office LAN, etc. From the point-of-view of the other machines on the ethernet LAN, the RAS server has multiple IP addresses, and it proxy-ARPs on the ethernet interface for all of the dialed-in clients, which obtain their IPs via PPP or similar from the server.

Now if only one could convince LinkSys to implement this in the stock firmware, everything would be totally groovy. (I'm not really sure what this would be called, perhaps "Client AP mode with proxy-ARP and bridging"? "Enhanced Client AP mode"? "Multi-client client AP mode"?)



Edited: 02/09/2005 at 05:28 AM by VirtualLarry

Date Posted: 02/09/2005 05:38 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: VirtualLarry


It then makes sense, if the PCs behind the client AP are on a different IP subnet than those PCs connected to the wired ports on the "main" AP, then by default IP packets sent out from the "main" AP would get routed to the default gateway, which is the WAN interface, and they wouldn't go anywhere, so you have to manually configure the routing to assign the gateway for the client AP's local subnet to be the IP of the client AP's wireless interface, so that the packets will reach there. (Or I might have that slightly wrong, maybe the gateway for that subnet would be the "main" AP's wireless interface.)

Now this is starting to make some sense.



Bingo !!! Houston, we have lift off !! You are finally getting it, what you said in tha paragraph is exactly right (except what you said in parenthesis at the end).

quote:

In fact, it would seem that the above probably would not work at all, if all of the devices, both the ones wired to the "main" AP, as well as ones wired to the client AP, were all on the same subnet. They have to be different subnets. But NAT has nothing directly to do with anything either, since no layer-3 address-translation seems to be needed nor happening.



Yeah, I did try a few other settings which didn't work, before setting this configuration, but maybe there is a way to make it work as a single network. Maybe I'll try fiddling with it later.

I still think NAT is being done by the client AP, as the PCs in the client network are on a different (private) subnet, which the main router doesn't know about. So I think the client router is translating between those private network addresses (e.g.192.168.1.xxx) and its external address (192.168.0.112) which is the one it uses to talk to the main network and its AP. This is called NAT (n-to-1 mode which linux kernel performs natively).

quote:


What would be interesting then, to test this out, would be to ping from a PC attached to a wired port on the "main" AP, to a PC attached to a wired port behind the client AP, and then dump the ARP table ("arp -a" on Windows, I think), and see if the MAC address associated with the IP of the machine behind the client AP is the same as the MAC of the client AP's wireless interface.

In fact, ping several different PCs behind the client AP, from a PC on the "main" AP, and see if all of the MACs are the same, and that that MAC is the same as the client AP's wireless interface. If so, then my theory fits. If not, and those MACs are in fact the real MACs of the ethernet interfaces of each of the PCs wired behind the client AP, then something else is going on, and it is likely that WDS mode is enabled and running.



Not sure how to do this on linux, but I can check the logs on the main router (yep, the DI-624 is quite a nice router, for sure) which show all the connected wired and wireless clients by MAC address, and the only wireless client listed as currently connected is the client AP (wrt54g) mac address. Actually, I also have mac filtering set up on the main router, and I never needed to allow the MACs of PCs in the client network, I only allowed the (wireless) MAC address of the client router. Does that answer your question ?

quote:

Edit: In case it wasn't totally clear, what I'm suggesting is really going on here is slightly different than NAT. Normally, all machines behind a NAT are on a local subnet with private IPs, and from the outside, there is only a single public IP address. In this case, it's a little different, from the outside, there is only a single MAC address visible, that of the client AP's wireless interface, but it appears to have multiple IP addresses, in fact all of the IPs of the machines behind it. The client AP recieves the frames with its own wireless MAC as the destination address, containing an IP packet with a destination IP that actually belongs to another machine, but to the outside, it appears to belong to the client AP. So it re-sends the ethernet frame containing that IP packet, except over the wired interface, with a destination MAC of the correct PC that corresponds with that destination IP on the local wired ethernet segment.

This is all the same basic sort of proxy-ARPing that goes on, with a dial-in RAS server on a local office LAN, etc. From the point-of-view of the other machines on the ethernet LAN, the RAS server has multiple IP addresses, and it proxy-ARPs on the ethernet interface for all of the dialed-in clients, which obtain their IPs via PPP or similar from the server.



I think you can call this a double NATed configuration, which is how skyking correctly described it all along. The only non-standard behavior, which your questions made me notice, is that the wrt54g allows pass-thru of packets addressed directly to its private network, which is why my explicit main->client routing scheme works. I would think that normally these packets should be blocked by a NAT router, but maybe it lets them thru due to disabling the firewall and unblocking of anonymous requests as I described in step 8 of my setup guide above.

I believe this is how sveasoft intended for this client/bridge mode to work (except for my main->client routing enhancenment). The links below describe essentially the same thing as what I did, but in a little less clear and concise fashion. I just wanted to give people a simple one-stop-shop guide so they don't have to chase around bits and pieces of information, or try out an endless number of configurations, which could be quite daunting to people with little networking knowledge.

The docs below also clarify that this mode is not really a client/AP mode because the wrt54g doesn't act like an AP at all, it acts like a wireless client of another AP (the main AP) :

FAQ
Documentation


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/09/2005 at 06:15 AM by user1234

Date Posted: 02/09/2005 02:06 PM Posted By: user1234(Platinum Member)

I already heard from at least two other people that got it to work, but anyone else which does it, please post your experience here. I have no doublt it will work with any existing wireless router (that is, the wrt54g will serve as a wireless bridge), but would still like to hear if it worked for you without problems.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/09/2005 07:16 PM Posted By: VirtualLarry(Diamond Member)

quote:
Originally posted by: user1234
Bingo !!! Houston, we have lift off !! You are finally getting it, what you said in tha paragraph is exactly right (except what you said in parenthesis at the end).


Yes, I understand routing fine. What didn't make sense, is that you claimed to be able to route packets to private IPs behind a NAT. Which is not ordinarily possible, so something else is going on here, exactly what is what I'm trying to understand and pin down here, with your help, since what you have managed to get working, is pretty darn useful.

quote:
Originally posted by: user1234
I still think NAT is being done by the client AP, as the PCs in the client network are on a different (private) subnet, which the main router doesn't know about. So I think the client router is translating between those private network addresses (e.g.192.168.1.xxx) and its external address (192.168.0.112) which is the one it uses to talk to the main network and its AP. This is called NAT (n-to-1 mode which linux kernel performs natively).


If that's true, then the private IPs of the machines behind the client AP should not be visible, nor routable to, from anywhere else on the network. Only the "public" IP address of the client AP should be visible to the rest of your LAN. If you've been able to ping from a machine behind the main AP to a machine behind the client AP, then this cannot be true. That's all I'm trying to point out here. NAT is not being applied to those connections.

quote:
Originally posted by: user1234
Not sure how to do this on linux, but I can check the logs on the main router (yep, the DI-624 is quite a nice router, for sure) which show all the connected wired and wireless clients by MAC address, and the only wireless client listed as currently connected is the client AP (wrt54g) mac address. Actually, I also have mac filtering set up on the main router, and I never needed to allow the MACs of PCs in the client network, I only allowed the (wireless) MAC address of the client router. Does that answer your question ?


Unfortunately, no. If WDS mode is in use, it's concievably possible that the MAC-filtering only applies to the "primary" MAC addresses, not the secondary encapsulated ones. Could you please ping from a PC behind the main AP to a PC behind the client AP, and then dump the ARP table of that same PC behind the main router? Is the MAC shown for the IP of the PC behind the client AP, the same MAC as the client AP's wireless interface? If you ping multiple PCs's IPs behind the client AP, are the MAC addresses for all of them the same? In other words, from the point-of-view of a PC behind the main AP, are all of the IPs supposedly belonging to the PCs behind the client AP, matching to the MAC of the client AP's wireless interface? Is the client AP "spoofing" (proxying) ARPs on the network, on behalf of the PCs behind it?

quote:
Originally posted by: user1234
I think you can call this a double NATed configuration, which is how skyking correctly described it all along. The only non-standard behavior, which your questions made me notice, is that the wrt54g allows pass-thru of packets addressed directly to its private network, which is why my explicit main->client routing scheme works. I would think that normally these packets should be blocked by a NAT router


Yes. So therefore, that's not NAT. What I'm suggesting may be happening, is a sort of layer-2 NAT-like behavior. NAT itself is layer-3. Or WDS mode is running already.

quote:
Originally posted by: user1234
I believe this is how sveasoft intended for this client/bridge mode to work (except for my main->client routing enhancenment). The links below describe essentially the same thing as what I did, but in a little less clear and concise fashion. I just wanted to give people a simple one-stop-shop guide so they don't have to chase around bits and pieces of information, or try out an endless number of configurations, which could be quite daunting to people with little networking knowledge.


I agree, and I thank you for this thread, but your initial description of the behavior can't be correct, there's something more actually going on here. (Not to mention, "client AP mode" is something different than "wireless bridge mode". There is no such thing as "client/bridge mode".)

quote:
Originally posted by: user1234
The docs below also clarify that this mode is not really a client/AP mode because the wrt54g doesn't act like an AP at all, it acts like a wireless client of another AP (the main AP) :


Uhm, that is what "Client AP mode" is... an AP configured not for "infrastructure mode" (acting as a "server" for other wireless clients), but as a client of another AP (with the other AP configured for "infrastructure mode"). Since normally, two APs both configured for "infrastructure mode" cannot talk between each other wirelessly - which is what WDS mode was essentially supposed to allow.

I will agree with your original premise, that if this can somehow be proven to not be running in WDS mode, then indeed it must be entirely due to some "tweaks" that Sveasoft added to their implementation of "Client AP mode" in their Alchemy firmware, and therefore should indeed work in conjunction with any other normal wireless AP, since the WRT54G is doing all of the work.

I think that there is a way to dump the state of the DI-624's NAT tables, I'm not sure if there's a way to dump whether or not it's running WDS mode or not, that might give a clue as to whether WDS mode is active or not.



Date Posted: 02/09/2005 08:45 PM Posted By: user1234(Platinum Member)

Did you catually read the first paragraph of this sveasoft documentation page ? The wireless mode list box shown has 3 options - AP, Client, and Ad-hoc. I've been using Client mode, not AP mode. And it clearly says "Client mode: This mode is used when we want the WRT54G to be connected to an AP (Access Point) like a client device (i.e. emulate a PCMCIA card or a PCI card). In this mode you cannot connect to the WRT54G that is in client mode using another wireless client device". And "AP mode: This is the default mode. It acts like a half-duplex HUB in the wired networks". I've been using client mode not AP mode !

And btw, NAT is "network address translation", which is happening here. Don't get confused by the routing entry I added. In fact, it would be simpler to understand the setup without it. In that case, the hosts in the client network are indeed unreachable from the main network, but the main network is reachable from the client network. So this is classic NAT, right ?

To work around this limitation, I had to add an entry to tell a compuer in the main network to route packets addressed to the client network addresses to the client router's address on the main network. So even though a PC on the main network can't directly send to a PC on the client network, it can send to the client gateway which I added to its routing table (I hope you understand routing tables, because that's what's used to implement all these high level policies). So obviously, the main network PC never sees the mac address of PCs in the client network. And for the last time, there is no WDS - in fact, I changed nothing in the configuration of the DI-624 when adding the wrt54g and its attached devices - that's part of the simplicity of this solution - no chance to mess up your existing configuration.

Here's the output of "arp" after pinging a PC in the client network:

Address HWtype HWaddress Flags Mask Iface1
192.168.0.112 ether 00:12:17:xx:xx:xx C eth0

As you can see it shows the mac & IP of the client router (MAC masked for security reason). Of course, this only works after I add the routing table entry:

route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.0.112






-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/10/2005 at 01:46 AM by user1234

Date Posted: 02/12/2005 03:17 PM Posted By: dildar(Junior Member)

Thanks for all the good work user1234!
I think you might be able to help me with this one.
I have limited network experience so need your help with this.
I have both of the ap and the bridge talking getting an ip from the dhcp.
here is the setup
External----192.168.1.1 dhcp Firewall Firebox-----192.168.1.20(wrtg54G)ap mode------->
<-------(192.168.1.5)Client Mode (192.168.2.5)-----(192.168.2.x)192.1PC1/PC2/PC3/PC4

I have the dhcp turned off on the (.20) ap mode and would like to have the other router also have the dhcp turned off.
If not is there a way for the computers in the two subnets to see each other? Maybe throught the different subnets?
If so would I also make the routes in the Firewall or in the router or both to connect the two differnet subnets?
This is so we can connect the computer from both sides of the network to see the windows domain and connect to it using windows xp pro.


Date Posted: 02/12/2005 05:02 PM Posted By: skyking(Diamond Member)

dildar, do you have 2 wrt54g's?

-------------------------
Heat



Date Posted: 02/12/2005 05:19 PM Posted By: Nutdotnet(Diamond Member)

user1234- I have the same setup as you.

My question is, and after reading this thread seems possible, but how exactly does one go about allowing PC1 and PC2 to speak to each other?

I have a modded Xbox that I am able to FTP into. The problem is, and why I'm currently not using the 54g in client mode, is that the DI-624 sees the WRT54g (192.168.0.112) but does not have a specific IP for the Xbox, since the Xbox's IP is being assigned by the WRT54g. So, is it possible to FTP into the Xbox with this setup? Basically the Xbox is just like any PC connected to the client. And if so, how exactly would I configure it? If you don't mind explaining, thanks!

-------------------------
HEAT


Date Posted: 02/12/2005 07:46 PM Posted By: JackMDS(Elite Member)

Let first thank you ser1234. You are the first one to put the effort to actually explain this process after hundred of posts that amount to one short phrase” Get a WRT54 and hack it.

How ever can you explain to me the advantage of the usage of the WRT54?

The Buffalo and the Belkin Routers can do WDS without all of this Hoopla.

The Belkin is Cheaper and Buffalo is better.

So what is the Story?



-------------------------
Jack.
Microsoft MVP - Networking.


Date Posted: 02/12/2005 09:01 PM Posted By: VirtualLarry(Diamond Member)

quote:
Originally posted by: user1234
Did you catually read the first paragraph of this sveasoft documentation page ? The wireless mode list box shown has 3 options - AP, Client, and Ad-hoc. I've been using Client mode, not AP mode. And it clearly says "Client mode: This mode is used when we want the WRT54G to be connected to an AP (Access Point) like a client device (i.e. emulate a PCMCIA card or a PCI card). In this mode you cannot connect to the WRT54G that is in client mode using another wireless client device". And "AP mode: This is the default mode. It acts like a half-duplex HUB in the wired networks". I've been using client mode not AP mode !


I just wanted to point out, that it seems that the reason that you don't understand what I've been saying, is that I've been using the "industry standard" terminology for these things. Now that you've pointed out what it shows in the firmware, I'm not surprised, because Sveasoft made up their own names for these things. No wonder we aren't communicating clearly here.

Here's a translation table:
(Sveasoft) - (industry standard)

"Client mode" - "Client AP mode" (or "AP client mode")

Meaning: When an AP operates in a mode as if it were a client wireless NIC, capable of associating with another AP running in infrastructure mode.

"AP mode" - "infrastructure mode"

Meaning: A wireless AP running in infrastructure mode, usually with a wired connection to the rest of the LAN. Allows wireless client NICs to associate with it, in order to wirelessly access the wired LAN.

"Ad-Hoc mode" - "Ad-Hoc mode"

Meaning: Sort of a peer-to-peer, free-for-all broadcast-packet mode. (I think.) Normally does not allow direct access to a wired network. There is no "association" that takes place. Effectively a wireless-only collision domain. (Correct me if I'm wrong there.)


You will clearly note, that there are no provisions in the above, to allow stations on the wired portion of a LAN, connected to an AP, to talk wirelessly to another AP, connected to another wired LAN segment. Thus the creation of a couple more wireless protocols.

"wireless bridge mode"

Generally, this operates between two specifically-configured APs, which will talk wirelessly to each other, and bridge ethernet frames from their attached wired ethernet segments over the wireless link to the other AP's attached wired ethernet segment. Essentially just like a normal ethernet bridge, except the frames are encapsulated and transmitted wirelessly between two APs. Depending on implementation, the APs may or may not allow other wireless clients to connect to them at the same time. (IOW, running in wireless bridge mode may disallow simultanious operation in infrastructure mode.)

"WDS mode" (Wireless Distribution System)

Generally considered to be more flexible, but also not standarized, so compatibility is implementation-dependent.

Kind of like bridge mode, but functions as a many-to-many wireless connection between APs with the same SSID. (I think.) In some implementations, it may not even require any specific configuration like "wireless bridge mode" does. (Is that what "lazy WDS mode" is? I'm not entirely certain yet how that is different from "normal WDS mode". I think that the Sveasoft firmware does implement "lazy WDS mode".)

At least, that's what I understand about 802.11 general protocols thus far. If I'm wrong, then I welcome any and all corrections.

quote:
Originally posted by: user1234
And btw, NAT is "network address translation", which is happening here. Don't get confused by the routing entry I added. In fact, it would be simpler to understand the setup without it. In that case, the hosts in the client network are indeed unreachable from the main network, but the main network is reachable from the client network. So this is classic NAT, right?


So you are saying, that there is essentially a uni-directional NAT operating, that when PCs behind the client AP want to talk to the main AP or PCs behind it, then the client AP NATs those connections, but you can also trivially bypass NAT in the other direction, by setting up a routing-table entry? That seems like kind of a wierd setup, if you can route, then why not route both ways?

quote:
Originally posted by: user1234
So obviously, the main network PC never sees the mac address of PCs in the client network. And for the last time, there is no WDS - in fact, I changed nothing in the configuration of the DI-624 when adding the wrt54g and its attached devices - that's part of the simplicity of this solution - no chance to mess up your existing configuration.


It may be that both firmware already implement a compatible form of "lazy WDS" - there may not be any configuration needed. But I'm speculating there, based on a seeming recollection that the DI-624 was one of the few routers that was WDS-compatible with the Sveasoft-modified WRT54G's.

quote:
Originally posted by: user1234
Here's the output of "arp" after pinging a PC in the client network:

Address HWtype HWaddress Flags Mask Iface1
192.168.0.112 ether 00:12:17:xx:xx:xx C eth0

As you can see it shows the mac & IP of the client router (MAC masked for security reason). Of course, this only works after I add the routing table entry:

route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.0.112


Hmm, I don't remember what I was originally trying to discern there, but.. ARP is a layer-2 broadcast protocol, is it not? So therefore, it shouldn't matter what the layer-3 routing tables say, if something responds to an ARP-request broadcast or not. So that doesn't make total sense either. Was that ping-request and ARP table dump, from the main router itself, or from a PC behind the main router?



Date Posted: 02/13/2005 05:38 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: JackMDS
Let first thank you ser1234. You are the first one to put the effort to actually explain this process after hundred of posts that amount to one short phrase” Get a WRT54 and hack it.

How ever can you explain to me the advantage of the usage of the WRT54?

The Buffalo and the Belkin Routers can do WDS without all of this Hoopla.

The Belkin is Cheaper and Buffalo is better.

So what is the Story?



The story is that you don't need two routers which can operate in WDS mode. If you already have a non-WDS router and you want to connect remote devices (which are not wifi-enabled) to your network , you need a wireless bridge, which usually costs $100 or more. With this solution you can add a wrt54g router with modified firmware, to operate as a wireless bridge, so you can place it next to your remote devices and attach it to them, and it will connect to your existing main wireless router. I guess WDS is a more comprehensive and/or general solution, but I believe it's slower and may be hard to setup due to compstibility problems. If you know exactly how to do it, and which routers are compatible, please post that information, so people can decide for themseleves which solution is more reliable, easier to set up and cost effective.


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/14/2005 at 03:27 AM by user1234

Date Posted: 02/13/2005 05:57 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: dildar
Thanks for all the good work user1234!
I think you might be able to help me with this one.
I have limited network experience so need your help with this.
I have both of the ap and the bridge talking getting an ip from the dhcp.
here is the setup
External----192.168.1.1 dhcp Firewall Firebox-----192.168.1.20(wrtg54G)ap mode------->
<-------(192.168.1.5)Client Mode (192.168.2.5)-----(192.168.2.x)192.1PC1/PC2/PC3/PC4

I have the dhcp turned off on the (.20) ap mode and would like to have the other router also have the dhcp turned off.
If not is there a way for the computers in the two subnets to see each other? Maybe throught the different subnets?
If so would I also make the routes in the Firewall or in the router or both to connect the two differnet subnets?
This is so we can connect the computer from both sides of the network to see the windows domain and connect to it using windows xp pro.



I understand you have two wrt54g with the sveasoft firmware ? if so, it would be simple to do it, since you could easily add entries to thier routing tables. Your PC1/2/3/4 should already be able to contact the main ap (192.168.1.20) and its attached devices (to verify that, try to ping the main ap from PC1, for example). Now for the other direction, to be able to connect from a PC attached to the main AP, to a PC attached to the client router. To do so, you need to tell the main AP to route packets addressed to 192.168.2.x to the client router, so telnet into the main router as root, and type this:

route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.5

Tell us if this work.....


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/13/2005 at 06:01 PM by user1234

Date Posted: 02/13/2005 06:00 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: Nutdotnet
user1234- I have the same setup as you.

My question is, and after reading this thread seems possible, but how exactly does one go about allowing PC1 and PC2 to speak to each other?

I have a modded Xbox that I am able to FTP into. The problem is, and why I'm currently not using the 54g in client mode, is that the DI-624 sees the WRT54g (192.168.0.112) but does not have a specific IP for the Xbox, since the Xbox's IP is being assigned by the WRT54g. So, is it possible to FTP into the Xbox with this setup? Basically the Xbox is just like any PC connected to the client. And if so, how exactly would I configure it? If you don't mind explaining, thanks!




You have to add a routing entry to each PC in the main network, because you can't change the routing tables of the DI-624. You can use the statement I mentioned in the thread "route add..." if the computer in the main ntwork is running linux. For windows, I'm not sure how to do a similar thing, but it should be possible.....

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/13/2005 08:18 PM Posted By: bazookajoe(Member)

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?




Edited: 02/13/2005 at 08:25 PM by bazookajoe

Date Posted: 02/13/2005 08:29 PM Posted By: bazookajoe(Member)

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


Date Posted: 02/13/2005 08:50 PM Posted By: skyking(Diamond Member)

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.

-------------------------
Heat



Date Posted: 02/13/2005 10:59 PM Posted By: bazookajoe(Member)

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.


Date Posted: 02/13/2005 11:07 PM Posted By: bazookajoe(Member)

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.



Edited: 02/13/2005 at 11:13 PM by bazookajoe

Date Posted: 02/13/2005 11:37 PM Posted By: user1234(Platinum Member)

quote:
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....

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/13/2005 at 11:49 PM by user1234

Date Posted: 02/14/2005 01:06 AM Posted By: bazookajoe(Member)

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' bugger. I will surely check back to read this thread from time to time. Take care.


Date Posted: 02/14/2005 03:16 AM Posted By: user1234(Platinum Member)

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.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/14/2005 at 03:17 AM by user1234

Date Posted: 02/15/2005 01:24 AM Posted By: bazookajoe(Member)

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.


Date Posted: 02/15/2005 02:37 AM Posted By: user1234(Platinum Member)

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.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/15/2005 06:55 AM Posted By: Jumperus(Junior Member)

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?


Date Posted: 02/15/2005 01:48 PM Posted By: user1234(Platinum Member)

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.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/15/2005 at 03:47 PM by user1234

Date Posted: 02/15/2005 04:02 PM Posted By: Jumperus(Junior Member)

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.


Date Posted: 02/15/2005 05:56 PM Posted By: user1234(Platinum Member)

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.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/15/2005 at 06:01 PM by user1234

Date Posted: 02/15/2005 09:51 PM Posted By: i2av(Junior Member)

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



Edited: 02/15/2005 at 09:55 PM by i2av

Date Posted: 02/15/2005 10:29 PM Posted By: Jumperus(Junior Member)

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?


Date Posted: 02/16/2005 02:44 AM Posted By: user1234(Platinum Member)

quote:
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 ?





-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/16/2005 at 03:33 AM by user1234

Date Posted: 02/16/2005 03:25 AM Posted By: user1234(Platinum Member)

quote:
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.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/16/2005 at 04:02 AM by user1234

Date Posted: 02/16/2005 01:14 PM Posted By: Jumperus(Junior Member)

quote:
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.



Date Posted: 02/16/2005 08:57 PM Posted By: i2av(Junior Member)

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.






Edited: 02/16/2005 at 09:48 PM by i2av

Date Posted: 02/16/2005 09:37 PM Posted By: user1234(Platinum Member)

quote:
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).


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/16/2005 10:06 PM Posted By: i2av(Junior Member)

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






Edited: 02/16/2005 at 10:47 PM by i2av

Date Posted: 02/17/2005 12:33 AM Posted By: user1234(Platinum Member)

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.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/17/2005 at 12:43 AM by user1234

Date Posted: 02/17/2005 05:28 AM Posted By: Jumperus(Junior Member)

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.


Date Posted: 02/17/2005 06:02 AM Posted By: Jumperus(Junior Member)

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. =)


Date Posted: 02/17/2005 02:21 PM Posted By: user1234(Platinum Member)

I would strongly encourage you to use encription, as without it your packets (that go to all the wireless clients) are readable by 3rd parties, even if they can't connect to your network. I have WEP working with this setup: on the d-link (home->wireless tab) I have authentication set to "Open System", WEP enabled 64-bit, key type HEX, using key #1. On the wrt54g (Wireless->Security tab) I have security mode set to WEP, transmit key #1, WEP encription is 64-bit 10 hex digits, and using the same key (obviously) as the d-link. Did you ever use encription between the dlink and other wireless clients ?

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/18/2005 04:20 AM Posted By: Jumperus(Junior Member)

Yeah, I used WPA-PSK + Mac filtering until I added the Linksys. Can't get the sonbitch to work with 128bit WEP or WPA. I'll play with it some more later and I'll try 64. I know most morons won't bother trying to crack encryptions, especially around an upper middle-class area, but still, I'd much rather use WPA. >=/


Date Posted: 02/19/2005 12:30 AM Posted By: missedtackle(Junior Member)

I just got two WRT54Gs and set them up as described in the original post. Only one of them, the "client" router, is flashed with the SVEASOFT firmware, because I was for whatever reason unable to connect the main router to the internet with SVEASOFT. With that in mind, my main computers are connected to the client router, which is 192.168.2.x as opposed to 192.168.1.x for the main router. My question is, how to I do port forwarding here? The client router's firewall is disabled, but the main router only has port forwarding options for 192.168.1.x.

It's not a problem now, but as I want to pick up WoW over the summer, I can imagine it causing complications later. I would try to set everything up in the same subnet with that WDS strategy, but as stated previously, the main router when flashed w/ SVEASOFT refuses to connect to the internet...


Date Posted: 02/19/2005 01:12 AM Posted By: user1234(Platinum Member)

I think Jumperus has two flashed wrt54g's, so maybe he can help with providing the settings you need for the main router. My main router is a dlink di-624, but I should think that setting up the main router should be simple as it should operate in the most common settings. Maybe jumperus can help with the exact settings.......

And why do you need port forwarding to play online ? you only need that if you're running a server. I play ut2004 online all the time from pc's behind the client router as well as behind the main router. And anyway, it should be simple to forward ports, you just need to do it on both routers (main forwards to client which forwards to attached pc).


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/19/2005 01:39 AM Posted By: missedtackle(Junior Member)

I definitely know of some games which give you issues if the ports are not forwarded. Starcraft was one of them I think. But even then, I'm not sure how self-explanatory it would be. So let's say my computer at 192.168.2.100 needs UDP port 4000 forwarded. So I can enter that into the client router. But what would I put for the main router, seeing as it would only allow 192.168.1.xxx entries?

If I can get a flashed WRT54G to connect to the internet, that would be the best solution...



Edited: 02/19/2005 at 01:43 AM by missedtackle

Date Posted: 02/19/2005 02:52 AM Posted By: user1234(Platinum Member)

The client router also has an address (in addition to 192.168.2.1) assigned by the main router on the 192.168.1.x network (e.g. 192.168.1.102). You can see that IP address in the status::router screen. So for port forwarding, you can forward the port from the main router to 192.168.1.102. Then the client router can forward to the attached PC. But your starcraft example is a little out of date, online gaming has progressed. I've never had to forward any ports for any online game I ever played in the last few years. So you don't need it, unless you want to start hosting games.....

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/20/2005 02:58 AM Posted By: Jumperus(Junior Member)

quote:
Originally posted by: user1234
I think Jumperus has two flashed wrt54g's, so maybe he can help with providing the settings you need for the main router. My main router is a dlink di-624, but I should think that setting up the main router should be simple as it should operate in the most common settings. Maybe jumperus can help with the exact settings.......



Actually, no, I'm essentially the same system you are. DI-624 as the gateway and WRT54G as client. Working fine, but I still haven't tried encryption. Not terribly worried right now; I'll get to it soon.

As for that port forwarding, yeah, I imagine that'd work. Especially if you're not enabling the firewall on the client router. Wouldn't the client router just use NAT to send the appropriate packets to the proper PC that's been using Port X? Of course, I'm thinking some applications send on one port and receive on another. Hmn. But yeah, either way, shouldn't dual forwarding work? Naturally, everything looks good in theory, but configurations are the devil.


Date Posted: 02/21/2005 09:22 PM Posted By: robeest(Junior Member)

Hello everyone, newbie here, I saw a deal for this router and found out about its potential so i decided to buy one. I want it to be primarily an ethernet bridge. Here is my set up....basically have di624 as main router connected to a couple of pc's and to the internet. I would like to use the wrt54g to allow my replaytv in my living room to be part of my network. I have done the suggested procedure for setting up the ethernet bridge and got it to work, in addition i also added a route entry via cmd prompt so my pc from the main router can communicate with the replay on the wrt54g router. The only downfall is that this system is not efficient enough to handle streaming video. Another system I use to do was allow my laptop to be a wireless bridge. The ethernet port from the laptop would be connected to the replay tv via crossover cable and the wireless card would receive signal from the di624. In windows, I just bridge the two connections. In this system, all components are in the same subnet ( replay, my pc, router , and laptop). Ip's all came from the di624 router. In this system, streaming was perfect. I would think there should be a way to allow the wrt54g to do this as well, but I need some guidance on how to go about doing it. If anyone has any input please feel free to comment.



Edited: 02/21/2005 at 09:26 PM by robeest

Date Posted: 02/21/2005 09:24 PM Posted By: wheeler459(Junior Member)

Is it possible to bridge together a WRT54G and WRT54GS? They both use Sveasoft firmware and have the same basic technologies.


Date Posted: 02/22/2005 02:44 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: robeest
Hello everyone, newbie here, I saw a deal for this router and found out about its potential so i decided to buy one. I want it to be primarily an ethernet bridge. Here is my set up....basically have di624 as main router connected to a couple of pc's and to the internet. I would like to use the wrt54g to allow my replaytv in my living room to be part of my network. I have done the suggested procedure for setting up the ethernet bridge and got it to work, in addition i also added a route entry via cmd prompt so my pc from the main router can communicate with the replay on the wrt54g router. The only downfall is that this system is not efficient enough to handle streaming video. Another system I use to do was allow my laptop to be a wireless bridge. The ethernet port from the laptop would be connected to the replay tv via crossover cable and the wireless card would receive signal from the di624. In windows, I just bridge the two connections. In this system, all components are in the same subnet ( replay, my pc, router , and laptop). Ip's all came from the di624 router. In this system, streaming was perfect. I would think there should be a way to allow the wrt54g to do this as well, but I need some guidance on how to go about doing it. If anyone has any input please feel free to comment.




well, I would also be interested to know if you know how to set up real bridging with a single network. But as far as the throughput, I don't think this setup is limiting it. I'm getting 20 Mbps between the routers, which is as good as I get with any other wireless client device. I did notice the wrt54g is not the fastest router in the world, even a local ping takes twice as much time as a local ping against the dlink. Maybe a faster client device could do 25-30 mbps, which is better, but don't forget this router is based on a slower microprocessor than your laptop (and cheaper by a thousand bucks). And anyway real 20 mbps is quite a reasaonable speed for a 54g connection thru 2 walls and 20 feet away (in my case).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/22/2005 at 03:41 AM by user1234

Date Posted: 02/22/2005 03:28 AM Posted By: robeest(Junior Member)

Thanks for the reply user1234. If you like to know how i made a wireless bridge with only a single network you can look at

http://www.microsoft.com/windowsxp/usin...working/expert/crawford_02april22.mspx

I used that tutorial to basically use my laptop as a wireless bridge. Well, I tried something different today to check to see what was wrong with my setup. Basically, i changed the wrt54g to default settings (not communicating with di624) and I connected my laptop wirelessly to it. I connected the replay tv to one of the four ports. I then tried streaming a show. The show played quite well. I was not suprised to see this happen, I am just now confused on what to do. I want the replay tv to connect to my di624 so it can download listings fromt he internet. But in that configuration, I am not able to stream video, I am only able to download shows from the replay at the rate of 500kB/s average. So, I guess I am asking if there is any way for the wrt54g to not create a new subnet, but yet still able to connect to di624 to get to the internet wirelessly. I am thinking that maybe packets are getting lost somewhere, but don't know really. I don't know much about routing tables.


Date Posted: 02/22/2005 04:20 AM Posted By: user1234(Platinum Member)

your download rate indicates you might have been working on 802.11b settings - so make suree both routers are on "G" (in wrt54g set the "Wireless Network Mode" in the "Wireless::Basic Settings" screen to "G-Only"). I've just checked again, and right now I'm transferring an 600 MB ISO image from a PC attached to the D-link to a PC attached to the wrt54g using SSH, at 1830 KB/sec (shown by WinSCP). The actual speed is a little higher because SSH adds some overhead.

And btw, I don't think you can use the wrt54g as both a wireless router and a bridge (with a single network), unless you use WDS mode in conjunction with another WDS compliant router. But since WDS is not fully standardized, compatibility is a problem (but you can definetely make it work with another flashed wrt54g).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/22/2005 06:53 AM Posted By: wheeler459(Junior Member)

Hi user1234.

I have almost the same setup as you. I have a Dlink 524 as my main router and I have a WRT54G that i want to locate somewere else. I understand that you can only have one computer connected to the WRT54G as it is operating in client mode. Is it possible for that computer to connect wirelessly to it. I have been reading the post and I dont think that anyone has been able to do it.


Date Posted: 02/22/2005 11:44 AM Posted By: robeest(Junior Member)

Thanks for the reply user1234. As you suggested, I already have the wrt54g on "G-only" mode. On the di624 router I have it on G mode and have used it with and without "dynamic turbo". As you noted,

I've just checked again, and right now I'm transferring an 600 MB ISO image from a PC attached to the D-link to a PC attached to the wrt54g using SSH, at 1830 KB/sec (shown by WinSCP)


I understand that you uploaded a file from pc wired to di624(main router ) to pc wired to wrt54g. I was wondering if you can do the same but send the file from the pc wired to the wrt54g as that is how i am downloading from my replaytv, which is wired to the wrt54g. Thanks again for the help.




Date Posted: 02/22/2005 11:55 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: wheeler459
Hi user1234.

I have almost the same setup as you. I have a Dlink 524 as my main router and I have a WRT54G that i want to locate somewere else. I understand that you can only have one computer connected to the WRT54G as it is operating in client mode. Is it possible for that computer to connect wirelessly to it. I have been reading the post and I dont think that anyone has been able to do it.




Actually, you can have up to 4 computers wired to the wrt54g and used simultaneously (I tried it with at least two). You're right that in client mode it's not possible to connect to the wrt54g wirelessly, according to the doc (although I haven't verified that).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/22/2005 12:06 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: robeest
Thanks for the reply user1234. As you suggested, I already have the wrt54g on "G-only" mode. On the di624 router I have it on G mode and have used it with and without "dynamic turbo". As you noted,

I've just checked again, and right now I'm transferring an 600 MB ISO image from a PC attached to the D-link to a PC attached to the wrt54g using SSH, at 1830 KB/sec (shown by WinSCP)


I understand that you uploaded a file from pc wired to di624(main router ) to pc wired to wrt54g. I was wondering if you can do the same but send the file from the pc wired to the wrt54g as that is how i am downloading from my replaytv, which is wired to the wrt54g. Thanks again for the help.




I just transfered a 89.3 MB file from a PC attached to the WRT54G to a PC attached to the DI-624 in 43 seconds. That's about 2.1 MB/sec = 16.8 Mbps. This time I used Linux on both ends (previously the remote machine was booting windows), which has a better ssh implementation. I can repeat this in both directions and get the same speed. I think 17 Mbps is quite reasonable for a wireless-G connection of 20 feet away and going thru two walls. Hopefully this will be good enough for your streaming video. What's the throughput you're getting ?

btw, thanks for the bridging information for a windows machine. I was considering a solution like this before I got the wrt54g, but I'd hate to keep a PC running just for doing bridging. Using a simple dedicated router will save you a lot of money on the electric bills.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/22/2005 at 12:59 PM by user1234

Date Posted: 02/22/2005 09:55 PM Posted By: disney1(Junior Member)





Edited: 02/23/2005 at 01:18 PM by disney1

Date Posted: 02/23/2005 01:40 AM Posted By: robeest(Junior Member)

ok...i think I narrowed down what my problem is. I think basically the software I am using, dvarchive, does not like this set up. FYI, dvarchive is an application for the replaytv in order to download shows and archive them. Anyways, i did some tests just as you did to confirm that the thoroughput was up to par. I received similar numbers as you did, the 2.1MB/s was the same I was getting. I transfered files from pc behind the di624 to a pc behind the wrt54g and vice versa. I also streamed video and it was fine. The only trouble was when I started trying to access the replaytv with the dvarchive software. This software is perfect when pc and replaytv are in the same subnet. Unfortunately, I don't know a workaround for it. I guess I will be returning this great router. Thanks for all your help user1234, I am going to try to see if someone has had a similar problem in the replaytv forums.


Date Posted: 02/23/2005 03:45 PM Posted By: user1234(Platinum Member)

Hmmm...maybe the software you are using is not compatible with NAT, which changes the IP addresses of datagrams. But some apps emded (pre-translated) IP addresses in the messages, which means means that they will not match the translated addresses that the receiver sees, which could cause problem. Normally application shouldn't do that, but maybe because this was designed to work only on a LAN it does d\something like that, which prevents it from working with this setup because we created two separate networks. Maybe there's a way to use the wrt54g as only a bridge without doing NAT, but I haven't yet figured that out. Btw, a similar problem occurs when you want to play games on your LAN - it doesn't work because of the separate networks. It only works using the general internet option (ut2004).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/24/2005 12:39 AM Posted By: robeest(Junior Member)

hello user 1234, sorry to bother you again. i managed to get the wrt54g side to have the same subnet now. I can access the internet from the wrt54g side with the subnet .0.xxx same as the di624. I basically just changed autodhcp setting to static and put in ip address in the range of the subnet. I also put in the DNS of the di624 router which i guess is given by my isp. I also enabled upnp. I basically did not know what i was doing..just fiddling around. But now my problems is that i cannot ping a machine from either side of the routers. for instance, my laptop connected to wrt54g cannot ping my pc connected to the di624 router and vice versa. my laptop connected to wrt54g cannot ping di624 router ( 192.168.0.1). it can only ping the wrt54g. I tried that route command from the pc connected to di624 as you suggested in your tutorial when there were two subnets, but in this new case there is only one subnet but for some reason not all machines can't see eachother...I would really appreciate your help on this once again.



Edited: 02/24/2005 at 12:58 AM by robeest

Date Posted: 02/24/2005 12:54 AM Posted By: JackMDS(Elite Member)

Hmm...

69 posts that were viewed 2,216 times, and still Going On.

I wonder what it means?











-------------------------
Jack.
Microsoft MVP - Networking.


Date Posted: 02/24/2005 01:04 AM Posted By: skyking(Diamond Member)

I've looked in from time to time, just to see the type of questions that get asked.

-------------------------
Heat



Date Posted: 02/24/2005 04:30 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: robeest
hello user 1234, sorry to bother you again. i managed to get the wrt54g side to have the same subnet now. I can access the internet from the wrt54g side with the subnet .0.xxx same as the di624. I basically just changed autodhcp setting to static and put in ip address in the range of the subnet. I also put in the DNS of the di624 router which i guess is given by my isp. I also enabled upnp. I basically did not know what i was doing..just fiddling around. But now my problems is that i cannot ping a machine from either side of the routers. for instance, my laptop connected to wrt54g cannot ping my pc connected to the di624 router and vice versa. my laptop connected to wrt54g cannot ping di624 router ( 192.168.0.1). it can only ping the wrt54g. I tried that route command from the pc connected to di624 as you suggested in your tutorial when there were two subnets, but in this new case there is only one subnet but for some reason not all machines can't see eachother...I would really appreciate your help on this once again.




What you've done is just make the two networks (unfortunately you still have two separate networks - using the same address range doesn't make them into a single network) use overlapping IP address ranges, which doesn't really help much, but creates more problems for the routing since the addresses are now indistguishable, so we can't create a routing table rule to to properly forward them (for example, now your client router will not forward packets addressed to 192.168.0.x to the main router). Also you turning off DHCP doesn't make any difference, just makes things more tedious (nor does Upnp matters here).

But you gave me an idea to improve upon this by making the client network to be a proper subnet of the main network. You do this by choosing a netmask of 255.255.255.128 and the IP address of 192.168.0.129 in the client router (leaving the gateway as 192.168.0.1 and automatic configuration via DHCP). Also make sure the starting IP address the client router assigns to its attached PCs starts at a number higher then 129 (for example 192.168.0.150). All these setting are in Setup::Basic Setup screen of the client router. Also make sure that the address range the main router assigns to its attached devices ends at 192.168.0.127 so it doesn't overlap the client's router subnet.

So now all the numbers will be in the 192.168.0.x range, where x is below 128 in the main network and above it in the client network. This is important because now the address are easy to tell apart and will be routed properly from the client network to the main network. To create the routing table entry for forwarding packets from the main network back to the client network you can (manually) add this rule:

route add -net 192.168.0.128 netmask 255.255.255.128 gw 192.168.0.102

(where 192.168.0.102 is the client router's address in the main network as shown in its status screen).

But I still don't think this will solve your problem, as these are still two different networks - a main network and a subnet (instead of two distinct networks previously). Try it and see. The only way we can make this into a single network if we could somehow get the client router to not perform network address (replacing the addresses in packets with its own address) translation when it forwards packets.


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 02/24/2005 at 04:50 AM by user1234

Date Posted: 02/24/2005 06:42 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: JackMDS
Hmm...

69 posts that were viewed 2,216 times, and still Going On.

I wonder what it means?












it means it helped hundreds of people set up a wireless bridge.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/24/2005 08:31 PM Posted By: robeest(Junior Member)

thanks user1234, that helped a lot. I am now able to stream content from the replay with this setting. speeds are very good. Now i just need to figure out a way to add a route entry to my xbox so it can also see my replay tv. Thanks again for everything user1234. Look forward to more informative posts you have about this router. (maybe a configuration to truly make this a single subnet)


Date Posted: 02/24/2005 09:12 PM Posted By: user1234(Platinum Member)

great.. so you're not going to return the router ?

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 02/24/2005 09:34 PM Posted By: robeest(Junior Member)

no...gonna keep it.....will try to research some more to see if single subnet is possible. Maybe if someone can shed light how microsoft does bridging in winxp pro, it combines 2 segments into a single segment.


Date Posted: 03/06/2005 05:06 PM Posted By: bfc123(Junior Member)

I tried to make a small network for testing purposes with 2pcs and 2 wrt54g.
The first pc has ip 192.168.1.151 and the wrt54g 192.168.1.31. They are on subnet 192.168.1.x and the wrt54g is AP mode.

The second pc has 192.168.2.155 and the wrt54g 192.168.2.1 in client mode and they are on subnet 192.168.2.x. Also the client wrt54g gets ip from the AP DHCP 192.168.1.200.

in the AP wrt54g I added this route: # route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.200

in the pc1: route add 192.168.2.0 netmask 255.255.255.0 192.168.1.200

in the pc2: route add 192.168.1.0 netmask 255.255.255.0 192.168.2.1

Although I can ping from pc1 to pc2 and and form pc2 to pc1 and form any pc to any wrt54g I can not find the pcs in the workgroup. I can only find the pc1 or pc2 for instance if I search from pc1 the ip of the pc2 but I can not find If I search it with its name. (They are in the same workgroup). Does anybody have an idea?


Date Posted: 03/07/2005 07:00 PM Posted By: chud(Junior Member)

I have the same setup (as robeest mentioned) with laptop acting as a wireless bridge (winXP) allowing everything on the same subnet. I just got a WRT54G assuming it would do this instead of the laptop, but after reading this forum and numerous other things it seems not

This is the routing table from the laptop

c:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x30004 ...02 30 bd 9c d1 83 ...... MAC Bridge Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.254 192.168.2.12 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.2.0 255.255.255.0 192.168.2.12 192.168.2.12 25
192.168.2.12 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.2.255 255.255.255.255 192.168.2.12 192.168.2.12 25
224.0.0.0 240.0.0.0 192.168.2.12 192.168.2.12 25
255.255.255.255 255.255.255.255 192.168.2.12 192.168.2.12 1
Default Gateway: 192.168.2.254
===========================================================================
Persistent Routes:
None

A little background, I have a DG834G connected to inet, running dhcp and this pc upstairs wired to it.
Downstairs I have laptop with wireless card and xbox with x-over cable to laptop ethenet port. The wifi card and ethernet port on laptop are bridged with XP bridging function.
When launch Avalaunch (xbox dashboard) with DHCP, it gets assigned an IP from the DG834G (192.168.2.254) upstairs and is immediately online. They are all on same 192.168.2.x subnet and can all interact with each other. In fact when xbox has smb server running (courtesy of xenium ICE) I can browse it on windows network from pc up here.

The only interesting thing about this is that it shows in my DG834G connection table as having the same MAC address as the laptop. This causes laptop to show an IP conflict when xbox requests DHCP as my DG834G gives out same IP allready assigned to laptop,however after a few seconds something somewhere is intelligent enough to give it another IP, so laptop is say 192.168.2.12 and xbox 192.168.2.13.

I hope this is of some use to someone who understands routing tables enough to work out how to make a WRT54g have this functionality, it cannot be that complicated as winXP manages to work it all out automatically.


Date Posted: 03/08/2005 07:53 AM Posted By: chud(Junior Member)

As a follow up to my previous post, I had to put the wireless card in laptop to compatibility mode (as it doesnt do promiscuous mode in winxp), which from what I have read makes it act as a Layer 3 Bridge, using a forwarding table, not a routing table (which layer 2 does).

So what the WRT54g ideally needs to perform is Layer 2 bridging, that is called transparent bridging, which also implements Spanning Tree Algorithm (STA).
(more about it here http://www.microsoft.com/technet/prodtechnol/winxppro/plan/xpbrdgnt.mspx

I did read somewhere that the new Sveasoft Talisman firmware would support this? I cannot remember where I read it, does anyone have any info?

So in a nutshell from what I understand, to run everything on the same subnet the firmware must have the ability to support transparent bridging.



Edited: 03/08/2005 at 04:28 PM by chud

Date Posted: 03/09/2005 02:43 PM Posted By: user1234(Platinum Member)

what you describe with the laptop replying to ARP messages for the XBOX (thus making the DG834G think they have the same MAC address) reminds me of proxy-arp feature (ARP is used to find a MAC address of a recepienet by [the sender] broadcasting a message containing the recepient's IP address, and waiting for the recepient to reply with its MAC address). I believe the key to set up bridging is related to this feature, so you may want to read this page and try to set up bridging using proxy-arp. Please post if you get it to work.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 03/09/2005 at 02:44 PM by user1234

Date Posted: 03/12/2005 11:57 PM Posted By: newParadigm(Platinum Member)

YAY

I finally figured out how to get a computer on the main network to see 1 computer on the client network. Its actually quite simple. Just set up a pc on the cleint side as a dmz host.

The wireless client interface is technically a "WAN" connection. (i.e. if you connected the two routers the same way with wires it would be [main, lanport]--------[client, wan port].

So, since the alchemy firmware allows for the re-assignment of lan ports to the wan segment, wold it be possible to simply assign all the ports to the WAN, and have a transparent bridge?

thanks

~new

-------------------------
Official member of the ATOT Night Crew

Hey, this is the police. Move your busted-ass vehicle. Move, move, move, move. This is the LAPD. We'll pop one in your ass. We got guns and shit.


Date Posted: 03/13/2005 12:05 AM Posted By: user1234(Platinum Member)

well yeah, you can do port forwarding or DMZ but it's only good for one machine or a few ports and it's not really a solution to join the two networks together. Please can someone try the proxy_arp solution from sveasoft documentation (it's described in the link in my previous post) ?

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/13/2005 08:34 AM Posted By: newParadigm(Platinum Member)

ima try the prxy-arp latter today, say around 5:00 PM eastern


if it works ill let all y'all noe.


~new

-------------------------
Official member of the ATOT Night Crew

Hey, this is the police. Move your busted-ass vehicle. Move, move, move, move. This is the LAPD. We'll pop one in your ass. We got guns and shit.



Edited: 03/13/2005 at 08:38 AM by newParadigm

Date Posted: 03/13/2005 11:22 PM Posted By: newParadigm(Platinum Member)

havin some trouble, but it ended up being my memory---i typed in the wrong dns addy and couldnt get teh web working.

Still having some trouble though, more tomorrow, for now its bed


-------------------------
Official member of the ATOT Night Crew

Hey, this is the police. Move your busted-ass vehicle. Move, move, move, move. This is the LAPD. We'll pop one in your ass. We got guns and shit.


Date Posted: 03/14/2005 04:38 AM Posted By: user1234(Platinum Member)

I have figured out how to set up bridging in the WRT54G using proxy arp. This allows everything to operate on a single network, so no routing is required in any of the computers to communicate properly between the two segments. All you have to do is log in to the WRT54G as root, and give this command:

# echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp

That's it. Note that you need to setup everything on the same network now (e.g. 192.168.0.x) rather than use two distinct networks. I will update the main tutorial with all the details on ow to do this, but you can just follow my explanation a few pages back on setting up a 255.255.255.128 subnet mask, and then give the proxy_arp command above.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/14/2005 11:49 AM Posted By: semsoid(Junior Member)

I have DI-624 as my main router/AP and I got a Linksys WRT54g rev 2.2 that I am trying to use as a wireless bridge.

I installed 6.0rc5 firmware and followed instructions on the first page and no dice. The Linksys would not get an ip from DI-624, it is not listed under Wireless status page either.

My main IP class is 192.168.1.x, so I used 192.168.2.x for Linksys. I have tried setting the Basic setup using DHCP or a static IP (192.168.1.224) - static IP was suggested by a thread in sveasoft forums. Did not make any difference. I originally had MAC filtering on DI-624, I added all 3 mac addresses (router, wan, wireless), since it didn't work I even tried disabling it. The other thread on sveasoft was refering to use 64 bit wep, I have 128bit, but that shouldn't make any difference.

Any suggestions?

TIA


Date Posted: 03/14/2005 03:42 PM Posted By: user1234(Platinum Member)

Yes, some other people also had problems with the 128-bit WEP. Please try 64-bit WEP which works for me (or no WEP). After you get them to connect (hopefully) you only need to add one MAC to the filters on the DI-624 (the MAC will show up on the DI-624 in the status screen).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/14/2005 04:05 PM Posted By: semsoid(Junior Member)

I was trying to avoid using 64 bit wep, as I use the same WEP key at work and home, it saves a lot of hassle with my notebook and PDA. Also there are many other devices on the network (like my wife's notebook, couple of WET11, etc). I didn't want to reconfigure all

I'll give it a shot, thx


Date Posted: 03/14/2005 06:48 PM Posted By: user1234(Platinum Member)

I think it should work with 128-bit WEP, but first try to establish connection by turning off WEP. Then you can play with the settings and hopefully get the 128-bit key to work (I really don't see why it shouldn't) so you don't have to change all your other wireless clients (which would be a bummer in addition to reducing your network security).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/16/2005 10:23 AM Posted By: semsoid(Junior Member)

Nope, as soon as I enable 128bit wep, I cannot get an IP from DI-624. I don't want to decrease security, so I guess I'll look for other solutions. Has anyone posting to this thread used 128bit WEP?


Date Posted: 03/18/2005 08:10 PM Posted By: newParadigm(Platinum Member)

Hey!!

I just finally apllied the proxy arp command, and I'm having some troubles. I can access the client AP via its client or lan side address (192.168.101.129<---LAN/192.168.101.103<---WAN), but ican't access any computers behind the client AP (there's actually only one).

I'm at a loss....help would be greatly apreciated.

~new

-------------------------
Official member of the ATOT Night Crew

Hey, this is the police. Move your busted-ass vehicle. Move, move, move, move. This is the LAPD. We'll pop one in your ass. We got guns and shit.


Date Posted: 03/18/2005 09:18 PM Posted By: semsoid(Junior Member)

I ditched my DI-624, got a Pre-n belkin and voila, 128 bit WEP and all is fine....


Date Posted: 03/20/2005 05:01 PM Posted By: mlrtime(Junior Member)

quote:
Originally posted by: user1234
I have figured out how to set up bridging in the WRT54G using proxy arp. This allows everything to operate on a single network, so no routing is required in any of the computers to communicate properly between the two segments. All you have to do is log in to the WRT54G as root, and give this command:

# echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp

That's it. Note that you need to setup everything on the same network now (e.g. 192.168.0.x) rather than use two distinct networks. I will update the main tutorial with all the details on ow to do this, but you can just follow my explanation a few pages back on setting up a 255.255.255.128 subnet mask, and then give the proxy_arp command above.




Any chance you can update the original tutorial with this method? I'd like to be able to get this to work.

Thanks




Date Posted: 03/20/2005 08:43 PM Posted By: mlrtime(Junior Member)

quote:
Originally posted by: Jumperus
Yeah, I used WPA-PSK + Mac filtering until I added the Linksys. Can't get the sonbitch to work with 128bit WEP or WPA. I'll play with it some more later and I'll try 64. I know most morons won't bother trying to crack encryptions, especially around an upper middle-class area, but still, I'd much rather use WPA. >=/



Jumperus, I'm having the exact same problem. My setup is working fine now (Even with same network). But the second I turn on any type of encyption, it fails. The wrt54g refuses to talk to my wireless ap (att 6850). Anyway I turned on mac filtering on the ap and my linux firewall, and i'll write a program to parse to watch for attempts.

Anyone have any ideas why this fails with wpa/wep?

thanks



Date Posted: 03/20/2005 09:55 PM Posted By: semsoid(Junior Member)

I guess it is dependant on the AP. I had problems with 128 bit wep, I had to ditch my DI-624 and go with a Belkin. 128bit WEP works fine with it. (haven't tried wpa)


Date Posted: 03/21/2005 03:24 PM Posted By: bgbysleepy(Member)

I able to connect and use the internet with my wrt54gs to netgear 54g.
modem <--wired-->netgear
wrt54g <--wired-->pc1
I have a laptop with 54g card, but the signal is always "LOW" from the netgear's router signal. is there a way to make the linksys wrt54g to broadcast its signal so that my laptop can use, and as the same time i can connect my pc1 to it with wire.
and One more thing.
How do i share files the two computers? I can't see my pc on the workgroup



Edited: 03/21/2005 at 04:05 PM by bgbysleepy

Date Posted: 03/21/2005 06:11 PM Posted By: bgbysleepy(Member)

quote:

# route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.0.112


my computer setting like this
modem--netgear(192.168.0.1)--wifi---
linksys wrt(192.168.0.2)--pc1(192.168.1.100)
laptop(192.168.0.3)--wifi--netgear router

this is what i did on my netgear under static routes option
Route Name toLinksys
Private---unchecked
Active--I checked this box
Destination IP Address: 192.168.1.100
IP Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.2
Metric: 2

for linksys under setup--advanced routing
Gateway
Enter route name: toNetgear
desktination Lan IP: 192.168.0.3
subnet mask: 255.255.255.0
default gateway: 192.168.0.1
Interface: lan& Wireless

I can use the internet on laptop and pc1, but I can't get laptop and pc1 to recognize each other. I can't share files between them. please help



Date Posted: 03/21/2005 06:25 PM Posted By: JackMDS(Elite Member)

Hmm. This Linksys Hack must be very Good.

97 posts viewed by 5,746 and still No Solution.



-------------------------
Jack.
Microsoft MVP - Networking.


Date Posted: 03/24/2005 06:33 AM Posted By: user1234(Platinum Member)

What do you mean no solution ? the original instructions in post number #1 give a solution to the main problem : how to use the wrt54g as a wireless bridge so you can connect remote PCs to your network and the internet without installing wireless cards. This works 100%. But as with many networking setups there are some complications, such as getting all the PCs to see each other and share files, or how to get WPA to work, etc. There are partial solutions to these complications, but that doesn't change the fact that even the basic setup described in the first post is a satisfactory for most situations.

btw, I updated the instructions with the proxy arp setting which enables seemless integration of the two network segments - the PCs attache to the main router and the PCs attached to the client router (the wrt54g). I've been using this improved setup for a couple of weeks now, and it simplifes things as no additional configuration is required on the PCs to be able to see each other. Note that for proxy arp to work, the client router and its attached PCs must share part of the subnet of the main router - so step 4 has been modified and step 10 has been added to the instructions.

Post your experiences - if this works for you or if there are any problems.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 03/24/2005 at 07:12 AM by user1234

Date Posted: 03/24/2005 11:21 AM Posted By: HarshReality(Junior Member)

I am getting a bit frustrated.... BEFW11S4(primary) and WRT54G(secondary) and I have seen 2 versions of this whole tutorial going on. One I did @ a month ago and now this... the first one suggested leaving the subnet mask the same on BOTH routers. Now the first page of this says change the WRT to 128.

All I want to do is get my freaking xbox (hooked to WRT in livingroom) to go online and have it see any network shares I setup on my main terminal (Hooked to BEFW in my office) and the whole of it frustrates me to no end.

Can one of you PLEASE write a damn step by step without all the technobabble, I took my network+ classes which makes me kinda dangerous because I know a little more than the average idiot, but lay it out simple if you could so I can actually get this thing working. My current firmware is pre7a


Date Posted: 03/24/2005 01:51 PM Posted By: user1234(Platinum Member)

HarshReality, I updated the instructions last night to use the 25 bit netmask for the client router, which makes it use part of the address range which the main router uses. This makes all PCs appear to be in a single subnet, which makes some things simpler. The idea is that all addresses start with 192.168.0.x and the main router thinks that all machines in the range 0-255 are on its network, but actually the machines connected to the client router (which are in the range 128-255) use the client router as their gateway. So when a macine attached to the main router wants to connect to a machine attached to the client, it thinks it should find it in the same network and issues ARP to find its physical address. This is where proxy arp setting comes in, so that the client router (which is wirelessly connected to the main router's network) forwards the ARP request and also sends a response on behalf of its attached PC. So it appears to the main PC that the client PC is on the same subnet even though it's really on a separate subnet.

With the new instructions I think you should be able to get all PCs/XBOXes to see each other. Please tell us what is the problem you are having ? I understand you can go online now, but you can't get the XBOX to mount file shares from your main computer ? I suggest to try entering the IP address of the main computer (e.g. 192.168.0.100) , as it may not show up automatically in the network browsing folder.


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 03/27/2005 at 08:06 PM by user1234

Date Posted: 03/25/2005 11:44 AM Posted By: Damon Spector(Junior Member)

I have tried following the steps in the first post but when I try to connect to my main router I can't get a connection. When I try to ping it I get an destanation host unreachable message. I'm using static IP addresses and thought I changed everything I needed for it to work but if you could give me the changes in the steps I need it would be very welcome.

Thank you

my main router is a westell versalink 327w router/ADSL modem


Date Posted: 03/25/2005 11:50 AM Posted By: user1234(Platinum Member)

Make sure the client router (e.g. the wrt54g 192.168.0.129) is set as the gateway for all its attached computers, and the subnet mask they are using is 255.255.255.128. This is crucial.

Also you can check if the encription and MAC filtering is not the source of the problem by turing them off (temporarily) and see if that helps.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 03/25/2005 at 11:54 AM by user1234

Date Posted: 03/25/2005 02:41 PM Posted By: Damon Spector(Junior Member)

MAC and encription are off, subnet is set, the wrt54g is the gateway for the computer hooked into it but I still can't get a conection or ping to the host router


Date Posted: 03/25/2005 08:14 PM Posted By: user1234(Platinum Member)

Is your client router set to automatic configuration via DHCP (that is, it get's its external IP from the main router) ?
Also go back over the instructions and make sure your settings are correct, especially the gateway that the wrt54g uses, and the SSID.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/25/2005 10:09 PM Posted By: Geforcer(Member)

Does this firmware allow a much greater wireless range with the stock antenna's? And if it doesn't work like I want, is it possible to revert back to the linksys firmware?

-------------------------
Asus A8N-SLI Deluxe (BIOS 1004)
AMD FX-53
2*512 MB Corsair XMS CMX512-3200C2
NEC ND-3500AG
Plextor Premium CDRW
Asus Extreme AX800XT Platinum
Audigy 2 ZS
Enermax 600W EG701AX-VE


Date Posted: 03/25/2005 10:54 PM Posted By: semsoid(Junior Member)

Hey user1234,

I found my dilemma with DI-624. With Belkin pre-n, the linksys was connecting fine, and I never had success with DI-624 and 128 bit wep, if you'd recall. Well, it turns out, if you switch the DI-624 to Open, from Shared Key, it works fine with 128 Bit WEP.

I was trying to make my PSP wireless work and it failed with Belkin using 128 bit WEP. So I decided to give a shot to DI-624, and with trial and error I found out the settings. Interestingly, Belkin pre-n does not have any Open or Shared Key option (or any advanced wireless options, such CTS, RTS, Fragmentation Threshold, etc for that matter). Once the PSP was working, I cut the Linksys back on, and to my surprise it worked just fine


Date Posted: 03/26/2005 01:16 AM Posted By: user1234(Platinum Member)

Great, I'm glad you got it working. I guess I'm gonna switch to 128 bit WEP as well, or maybe even WPA. Anyway, the encription on the wireless channel is not really directly relevant to the settings required to set up the bridging function of the wrt54g. My guide is meant to show how to set up the wrt54g as a wireless bridge. The encription settings are an orthogonal issue, although an important one for sure.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/26/2005 01:34 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: Damon Spector
MAC and encription are off, subnet is set, the wrt54g is the gateway for the computer hooked into it but I still can't get a conection or ping to the host router




Actually I see you mentioned you're using static IP addresses. In that case you need to make s&#1493;re you set the external address and IP correctly in the Basic Setup screen: In the "Internet ConnectionType" section enter in "Internet IP address" your chosen address in range 2-127 (e.g. 192.168.0.100) - this is the external address of the client router (which is seen by your main router). The subnet mask line below the address should be 255.255.255.0, and the gateway set to the address of the main router (e.g. 192.168.0.1).

Now, in the "Router IP" section enter "Local IP Address" as 192.168.0.129 and subnet mask 255.255.255.128, and gateway is again the address of the main router (e.g. 192.168.0.1).

Now you should be able to establish a connection to the main router. Try to ping it from a PC attached to the client router. (Make sure the attached PC has IP address in range 130-254, has subnet mask of 255.255.255.128 and gateway set to 192.168.0.129).



-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/26/2005 10:12 AM Posted By: Martzis(Junior Member)

I have been trying to get WRT54GS working in Client mode with no success.

I have I ADSL connection with 6 static public IP addresses (.248 mask). The ADSL router is working as a DHCP server and is connected to a ethernet switch. I also have a desktop computer and HP 420 Access point, which are connected to the switch.

ADSL router IP is xxx.xxx.75.241

Desktop PC settings are:
ip xxx.xxx.75.242 (static)
mask .248
default gateway .241
(PC has also an additional IP for AP management 192.168.1.100)

HP 420 access point does has only a management IP address 192.168.1.2.

I have also a laptop with wlan card. It receives IP address from ADSL router:
ip xxx.xxx.75.243
mask .248
default gateway .241

I have also another Desktop PC which a would like to connect wirelessly to the HP access point. I have WRT54GS (Alchemy_6rc5 or pre7a) connected to this PC with an ethernet cable using LAN 1 port. I would like that PC would receive an IP address from my ADSL router similar to laptop. But I can not get this working.

Desktop PC 2 wanted settings:
ip xxx.xxx.75.244 (dhcp assigned)
mask .248
default gateway .241

How do I need to configure my WRT54GS to get this working?


Date Posted: 03/26/2005 11:03 AM Posted By: Damon Spector(Junior Member)

I set the addresses like you sugested but for some reason I still can't get my client computer to ping my main router but it will ping my wrt54g. also I can't find a ping command on the web interface of the wrt54g. and when I double checked the wireless page on step 7 it has the wrong MAC address.



Edited: 03/26/2005 at 11:16 AM by Damon Spector

Date Posted: 03/26/2005 03:33 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: Damon Spector
I set the addresses like you sugested but for some reason I still can't get my client computer to ping my main router but it will ping my wrt54g. also I can't find a ping command on the web interface of the wrt54g. and when I double checked the wireless page on step 7 it has the wrong MAC address.



can you telnet into the wrt54g (root/admin) and type the command route, and then ifconfig, and send the output ? also try to ping the main router from the command line of the wrt54g and see if that works.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/26/2005 03:43 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: mlrtime

quote:
Originally posted by: Jumperus
Yeah, I used WPA-PSK + Mac filtering until I added the Linksys. Can't get the sonbitch to work with 128bit WEP or WPA. I'll play with it some more later and I'll try 64. I know most morons won't bother trying to crack encryptions, especially around an upper middle-class area, but still, I'd much rather use WPA. >=/



Jumperus, I'm having the exact same problem. My setup is working fine now (Even with same network). But the second I turn on any type of encyption, it fails. The wrt54g refuses to talk to my wireless ap (att 6850). Anyway I turned on mac filtering on the ap and my linux firewall, and i'll write a program to parse to watch for attempts.

Anyone have any ideas why this fails with wpa/wep?

thanks




From some other people's post (thanks semsoid) it seems that you may need to try either open system or shared key in as your authentication mode in the main router. This setting is automatic on some routers, but on others (like DLink DI-624), you need to set it manually. Also it may work with 64-bit encription with one setting, but need a different setting for the 128-bit, so the bottom line is to try both modes (open and shared).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 03/27/2005 10:14 AM Posted By: daniel29(Junior Member)

quote:
Originally posted by: user1234

6. In "Wireless::Basic Settings" screen, set Wireless mode to "Client", wireless network mode to "mixed", and SSID to your main wireless router's SSID.


Hi there,

I am also trying to use the WRT54GS in "Client Mode". Running Alchemy6.0RC1.W42 there is an additional option in the "Wireless::Basic Settings" dialog:

Client Mode [ ] Routed [ ] Bridged

I thought that using "Bridged" mode would make configuration a lot easier, but then I read that

quote:
Bridged client mode broadcasts forwarding and DHCP relay will not work with this release. DHCP relay will be worked on for my Talisman builds.


Source: http://www.i-hacked.com/component/optio...rd/Itemid,93/func,view/id,10/catid,18/

That's a real pity because with bridged mode you could drop all that subnet and ip configuration that the "routed" configuration needs and instead just plug and pray.

But it does not work for me :-( If I enable "bridged" mode, I don't even have the interface eth1 that is the wireless one (if I am correct).








Edited: 03/27/2005 at 10:15 AM by daniel29

Date Posted: 03/27/2005 10:33 AM Posted By: daniel29(Junior Member)

quote:
Originally posted by: user1234
I guess I'm gonna switch to 128 bit WEP as well, or maybe even WPA. Anyway, the encription on the wireless channel is not really directly relevant to the settings required to set up the bridging function of the wrt54g.


True, encryption has nothing to to with the "client mode" setup we are talking about in this thread.

Still encryption is an important feature one has to think about when setting up a wireless connection.

I had only success using the (obsolete) WEP-128 but failed using WPA-PreSharedKey TKIP. Bummer!

Any ideas why?








Date Posted: 03/27/2005 11:39 AM Posted By: Damon Spector(Junior Member)

here is my ipconfig and route output

~ # ifconfig
br0 Link encap:Ethernet HWaddr 00:13:10:18:0C:F3
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:818 errors:0 dropped:0 overruns:0 frame:0
TX packets:703 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:47998 (46.8 KiB) TX bytes:143819 (140.4 KiB)

eth0 Link encap:Ethernet HWaddr 00:13:10:18:0C:F3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17165 errors:0 dropped:0 overruns:0 frame:0
TX packets:61176 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1558330 (1.4 MiB) TX bytes:6931807 (6.6 MiB)
Interrupt:5 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 00:13:10:18:0C:F4
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3105 errors:0 dropped:0 overruns:0 frame:20646
TX packets:9478 errors:31 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:326947 (319.2 KiB) TX bytes:872868 (852.4 KiB)
Interrupt:4 Base address:0x1000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:103 errors:0 dropped:0 overruns:0 frame:0
TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7652 (7.4 KiB) TX bytes:7652 (7.4 KiB)

vlan0 Link encap:Ethernet HWaddr 00:13:10:18:0C:F3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17165 errors:0 dropped:0 overruns:0 frame:0
TX packets:61176 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1249360 (1.1 MiB) TX bytes:6931807 (6.6 MiB)

vlan1 Link encap:Ethernet HWaddr 00:13:10:18:0C:F3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

~ #


~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.128 * 255.255.255.128 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
~ #

and I could ping the main router when I was telneted in but I first had to enable telnet. I can also now ping the main router from the computer attached to the wrt54g and even log in to it (using http://192.168.1.1). However I still cant get on to the internet with it.


Date Posted: 03/27/2005 03:35 PM Posted By: user1234(Platinum Member)

Mr Damon Spector - I see you have made progress since you can ping the main router from a computer attached to the client router. This means you established a wireless connection between the main and client router (see step 7 of the tutorial for additional way to verify you have established a connection).

Your settings look correct, and in fact you should already be able to connect to the internet : try to "ping 144.92.104.243", which is the IP address of www.wisc.edu (university of wisconsin), from the PC attached to wrt54g (and from wrt54g itself). If this works, then the only remaining issue is the DNS translation (domain name to IP address) - make sure your attached PC has the correct domain name server (DNS) address entered. The DNS server address should be same as what the main router and its PCs use - it's usually shown in the (main) router's status screen. Btw, all these manual configurations can be avoided when using DHCP.

Also to avoid other problems, I suggest that you go thru the list of step in the tutorial again and check that your settings match. For example, in step 9 I mentioned you should enable Telent access in administraion/management screen. Also make sure you perform step 10. I know that doing all the steps seems a little long and tedious, but in fact it usually saves a lot of time in troubleshooting a missing part of the setup.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 03/27/2005 at 04:03 PM by user1234

Date Posted: 03/27/2005 03:47 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: daniel29

quote:
Originally posted by: user1234

6. In "Wireless::Basic Settings" screen, set Wireless mode to "Client", wireless network mode to "mixed", and SSID to your main wireless router's SSID.


Hi there,

I am also trying to use the WRT54GS in "Client Mode". Running Alchemy6.0RC1.W42 there is an additional option in the "Wireless::Basic Settings" dialog:

Client Mode [ ] Routed [ ] Bridged

I thought that using "Bridged" mode would make configuration a lot easier, but then I read that

quote:
Bridged client mode broadcasts forwarding and DHCP relay will not work with this release. DHCP relay will be worked on for my Talisman builds.


Source: http://www.i-hacked.com/component/optio...rd/Itemid,93/func,view/id,10/catid,18/

That's a real pity because with bridged mode you could drop all that subnet and ip configuration that the "routed" configuration needs and instead just plug and pray.

But it does not work for me :-( If I enable "bridged" mode, I don't even have the interface eth1 that is the wireless one (if I am correct).







yep, you hit the nail on the head with this enlightening post. The main limitation of my setup is that there are still two subnets (even if they share the same address range), one for the main router and its attached PCs and one for the client router and its PCs.
This means that when a PC sends a broadcast packet to its local subnet it is only seen by the PCs attached to the same router, and not by PCs attached to the other router (which are on a different subnet). So all the automatic detection utilites which use broadcasting to find what other PCs are on the local network would not find PCs attached to the other router.

But you can alway enter the actual IP address of the PC you want to connect to, and this should work, as the routing between the two subnets is set up correctly in my instructions.

So full bridging would mean that broadcasts should be forwarded, including DHCP messages. I tried to experiment with this and noticed that currently they are not forwarded. Since wrt54g is running a linux kernel, it should be possible to set up the kernel's ip tables to do this kind of forwarding, but that's beyond what a normal user would want to try. So it's best to wait until it's implemented in the firmware and available via the web interface of the router.

Did you mange to get your setup working using the "Routed" client mode ?

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 03/27/2005 at 11:45 PM by user1234

Date Posted: 03/28/2005 06:48 AM Posted By: Martzis(Junior Member)

Hello,

I update my WRT54GS with Satori firmware and now it is working fine as WLAN client. All dhcp traffic goes fine trough it.


Date Posted: 03/28/2005 03:21 PM Posted By: daniel29(Junior Member)

quote:
Originally posted by: MartzisI update my WRT54GS with Satori firmware and now it is working fine as WLAN client. All dhcp traffic goes fine trough it.

And so do ARP request and other broadcast packets? And the WRT54's IP is just for administration and not for anything else (gateway address, dns proxy)? Fine! Exactly what the client mode should be: transparent.

What exactly is the Satori firmware version you are talking about? Does Satori know anything about "WPA"?

If I flash Satori, can I easily revert to Alchemy or DD-WRT (Alchemy based)? I am also interested in trying Enhanced WRT Linux distribution or OpenWRT but I am also unsure if this process is reversable.




Date Posted: 03/28/2005 03:50 PM Posted By: tishoo(Member)

I'll echo the comments regarding the Belkin routers and their WDS mode.

The Belkin F5D7230-4 is at $10 (AR - 30+30) again at (I think: Circuit Sh!tty). Up to 4 of these can be set up to bridge (Wireless Distribution Service mode). I have 3. At the deals I found, they'll cost me a net total of $35! I can ebay (or trade, right here!) my existing 802.11B network components for more

Much simpler setup, albeit you eschew WPA (new firmware should recitfy that) as also any funky 'Super' mode functionality (plain-jane 54MBPS)

I have a multitude of TiVos, PCs, Linksys Vonage PAP2, game consoles and laptops (when friends visit, I don't own any game consoles, nor wireless devices any more!) connected together and get tremendous performance in a 3-level home! Laptops happily roam from one router to the other, depending on signal strength (confirmed by checking router MACs) and overall bandwidth is better managed than it would be if multiple wireless devices were on the network (home routers don't handle that well - ideal case is one wireless device and one router!)

FYI - I don't care for the icky Belkin router interface and capabilities, so I retained my D-link router with the 802.11B radio turned off as my outside router that handles DHCP (or Static IP) and tunneling, rules, firewall, MAC filtering etc etc.

Try it, and feel free to PM me if you have issues. I'll try to write up a mini-HOWTO from the notes I've made (all gleaned from others' help over on TiVo Community Forums - credit where its due )

<edit to reiterate ...> Only one rebate per household, in their infinite stupidity. Use countermeasures I had my uncle buy one, and a friend buy another. The (rebate) system cheats us often enough to justify (doing) this with minimal guilt! FYI!

-------------------------
New member, long-time lurker!



Edited: 03/28/2005 at 03:55 PM by tishoo

Date Posted: 03/30/2005 04:04 PM Posted By: daniel29(Junior Member)

I flashed my WRT54GS to DD-WRT (Alchemy based) using the web interface. But this firmware does not provide the "bridged/routed" option in Client Mode. So it always routes. Bad luck.

Then I flashed the Enhanced WRT Linux distribution 0.2. And that worked in client mode (transparently bridging the LAN to the WLAN interface)!
Here is how I did it:

In Setup::Basic Setup:


* Select "Static IP" and give the WAN interface any IP address from a network different from your LAN, e.g. 192.168.229.2/255.255.255.0.
* Set the "Local IP address" to a value in your LAN, so you can access the WRT. This IP is only needed for administration.
* Check "Use the local gateway as the default gateway"
* Disable DHCP server.



In WIRELESS::Basic Wireless Settings:


* Set Wireless Mode to "Client".
* Enter SSID of your AP.
* Select the WLAN channel your WLAN-Router (AP) is sending on.
* Disable "wireless SSID broadcast".



This configuration works like an Ethernet-to-WLAN-adapter and is completely transparent. Works also with WEP-128! But not with WPA :-(

Why does WPA fail? Analysis so far: AP=Router STA=WRT54G in client mode.
AP sends "Beacon frames"
STA -> AP: Probe Request
AP -> STA: Probe Response
STA -> AP: Authentication
AP -> STA: Authentication
STA -> AP: Association Request
AP -> STA: Association Response
Up to this point to connection is established if one does not use encryption.

With WPA enabled, both devices are now supposed to create a Pairwise Transient Key (PTK) through an EAPOL-key exchange (EAPOL, the Extensible Authentication Protocol over LANs) called "4-way handshake". See IEEE 802.11i and wireless security or Wikipedia 802.11i or IEEE 802.11i. The Four-Way-Handshake computes the PTK from the static Pre-Shared Key (PSK), which is the passphrase one has to enter when configuring WPA.

The AP sends the first handshake message but the WRT only responds with an empty 802.11 frame.
See the ethereal transcript here!

Why is this?




Cheers
Daniel Kabs




Edited: 04/02/2005 at 04:57 AM by daniel29

Date Posted: 03/30/2005 11:12 PM Posted By: robeest(Junior Member)

hey guys..i just tried upgrading firmware to ewrt 0.2. It upgraded...but now my ethernet ports don't work. I can't get into the router through wired ethernet. I need to use wireless to connect to router. the router is set to default and gives ip to wireless but not to wired machines. I have checked the wires and my ethernet card. Both are functioning correctly with my other router. I have installed my old alchemy firmware and linksys firmware...but that didn't work. I think something is wrong physically. I have also tried manually configuring ip so it is in same range with router..but still nothing...it gets connected but router cannot ping to pc and pc cannot ping to router using wired connection.. Any suggestions will be appreciated. thanks in advance.


Date Posted: 04/04/2005 01:03 AM Posted By: bgbysleepy(Member)

hey "user1234" can you help me fix this.
first here is my setting.
main router(netgear) has
Default Gateway: 192.168.0.1
subnet mask: 255.255.255.0
linksys wrt54gs has
default gateway: 192.168.1.1
subnet mask: 255.255.255.0
PC1 connect to wrt54gs ip is: 192.168.1.2

how do i forward port 1414 so that PC1 can use that port.
I've try to login to netgear forward like this
start: 1414 and end port 1414: server ip address: 192.168.1.1(which is linksys)
and also try to forward port 1414 in the linksys router to ip: 192.168.1.2(which is PC1)
but it doesn't work. please help me.
.......
Nevermind, i figure it out, i forward it to 192.168.0.2(which is my linksys router assigns by the netgear router), and it's work



Edited: 04/04/2005 at 01:19 AM by bgbysleepy

Date Posted: 04/05/2005 05:10 AM Posted By: pascal333(Junior Member)

User1234 and others: A good description has been given of how to use a WRT54g to add a PC wirelessly to an existing LAN which already has a router similar to a WRT54g. Here, the second WRT54g can be used to support more than one device but my interest at the moment allows me to think of adding a WRT54g/laptop combo. My question is: Can another WRT54g/laptop combo be added?

I have three areas where I compute. The main connection with the DSL modem and primary WRT5rg is in the middle of the house. The other two are at the ends of the house and are too well shielded to by reached reliably by the existing WRT54g with pcmcia cards. Wire is out of the question. I have an old WRT54g that I tried as you described, and it works great at either end location with either laptop. So I am wondering if I purchase another one if it will allow both laptops to work or break the connection I now have.

Thanx
Pascal333

-------------------------
Blaise
I have but one more cat life to give...


Date Posted: 04/05/2005 07:46 PM Posted By: pascal333(Junior Member)

user1234 or other who knows the answer:

First of all: Interesting work on the WRT54, user1234!!

Easy Question: The commannd
telnet 192.168.1.129
produces requests for login and password. When I use the web interface, I fill in a password, but no login or user. If I put in an arbitrary user here on the telnet login, the login fails, as it does if I do not put in an arbitrary user. What am I supposed to use for a login for telnet? (in plain dummy terms, please!) Thanx

-------------------------
Blaise
I have but one more cat life to give...


Date Posted: 04/05/2005 09:56 PM Posted By: pascal333(Junior Member)

Got the clarification of answer to this one... you had answered it elsewhere but I did not understand your answer (too new to know the terminology). Happily I was able to make the final little step with a little google-ing and a bit of trial and error.


-------------------------
Blaise
I have but one more cat life to give...


Date Posted: 04/05/2005 11:15 PM Posted By: skyking(Diamond Member)

quote:
Originally posted by: pascal333
User1234 and others: A good description has been given of how to use a WRT54g to add a PC wirelessly to an existing LAN which already has a router similar to a WRT54g. Here, the second WRT54g can be used to support more than one device but my interest at the moment allows me to think of adding a WRT54g/laptop combo. My question is: Can another WRT54g/laptop combo be added?

I have three areas where I compute. The main connection with the DSL modem and primary WRT5rg is in the middle of the house. The other two are at the ends of the house and are too well shielded to by reached reliably by the existing WRT54g with pcmcia cards. Wire is out of the question. I have an old WRT54g that I tried as you described, and it works great at either end location with either laptop. So I am wondering if I purchase another one if it will allow both laptops to work or break the connection I now have.

Thanx
Pascal333



If you are using all wrt54g's and sveasoft firmware, there is no reason NOT to use WDS. It is built right in to that firmware, and you can daisy-chain as many routers as you like, till the channel gets saturated.

-------------------------
Heat



Date Posted: 04/06/2005 05:35 AM Posted By: user1234(Platinum Member)

pascal333, you should be able to use two or more wrt54g routers as clients of your main router at the same time with no problem. This should work since each wrt54g is just a wirelell client of the main router, so you could have as many as you want (but note that they all share the wireless channel's bandwidth). Also, like skyking said, if your main router is also a wrt54g you could probably set up WDS mode (search for a thread here about two wrt54g's) which is more flexible than the "client mode" setup I described in this HOWTO. and btw the username to log in to the wrt54g is "root" (default password is "admin" unless you changed it).

Glad to hear about another successful setup !!

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 04/06/2005 at 05:35 AM by user1234

Date Posted: 04/06/2005 05:47 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: bgbysleepy
hey "user1234" can you help me fix this.
first here is my setting.
main router(netgear) has
Default Gateway: 192.168.0.1
subnet mask: 255.255.255.0
linksys wrt54gs has
default gateway: 192.168.1.1
subnet mask: 255.255.255.0
PC1 connect to wrt54gs ip is: 192.168.1.2

how do i forward port 1414 so that PC1 can use that port.
I've try to login to netgear forward like this
start: 1414 and end port 1414: server ip address: 192.168.1.1(which is linksys)
and also try to forward port 1414 in the linksys router to ip: 192.168.1.2(which is PC1)
but it doesn't work. please help me.
.......




ok, I think the info you gave about your setup is missing some stuff, but basically what you need to do is do the forwarding twice: first from your main router to the client router (the wrt54g) and second from the client router to its attached pc (PC1). The thing to note is that when you set up the forwarding from the main router to the client router, you have to enter (as destination) the address of client router on the main router's network (so it will be something like 192.168.0.x). This is the address by which the client router is known by the main router. You can see this address in the client router's status:setup screen , in IP Address field. So you have to set the forwarding from the main router to this address. Then on the client router set up forwarding to its attached PC. I've done that and can run a UT2004 server on a PC attached to the client router, and also manage it remotely using UT2004 built in http server (i also forward the http server's port, as well as the server's game ports).


woops I see you already figured it out on your own - good job

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 04/06/2005 at 05:49 AM by user1234

Date Posted: 04/06/2005 05:55 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: daniel29

quote:
Originally posted by: MartzisI update my WRT54GS with Satori firmware and now it is working fine as WLAN client. All dhcp traffic goes fine trough it.

And so do ARP request and other broadcast packets? And the WRT54's IP is just for administration and not for anything else (gateway address, dns proxy)? Fine! Exactly what the client mode should be: transparent.

What exactly is the Satori firmware version you are talking about? Does Satori know anything about "WPA"?

If I flash Satori, can I easily revert to Alchemy or DD-WRT (Alchemy based)? I am also interested in trying Enhanced WRT Linux distribution or OpenWRT but I am also unsure if this process is reversable.




that's great news, so if you anyone can post a more detailed description (or a HowTo) I will be glad to try this enhanced client mode.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 04/06/2005 04:28 PM Posted By: daniel29(Junior Member)

quote:
that's great news, so if you anyone can post a more detailed description (or a HowTo) I will be glad to try this enhanced client mode.

It seems, bridged client mode and WPA is not possible with the binary drivers provided by linksys. I reckon, one has to use the userland tool "wpa_supplicant".

I am still investigating into this subject. More posting when events warrant.




Date Posted: 04/10/2005 12:41 PM Posted By: madtomic(Junior Member)

hi user1234,

does this works with WRT54G - Wireless-G Broadband Router v1.0?


Date Posted: 04/11/2005 08:01 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: madtomic
hi user1234,

does this works with WRT54G - Wireless-G Broadband Router v1.0?




if the alchemy firmware is compatible with it then yes it will work. Or if there is another sveasoft firmware version which is similar to alchemy. Try flashing to alchemy first, and if you can't (the flash will fail if it's not comaptible) then try the other firmwares.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 04/12/2005 01:26 PM Posted By: Davegod75(Diamond Member)

I'm wondering if this can be done with the gigafast wf711-APR i just got.. It sounded like from the description that you could but I cannot figure it out


any clue?

-------------------------
Evals | System | Email | Seti


Date Posted: 04/14/2005 09:51 PM Posted By: rangerman(Junior Member)

Anybody figure out how to save that proxy_arp setting? It is really annoying to have to set it after the router resets for whatever reason. (Echoing 1 to it in /proc does not survive reboots. I don't see an NVRAM parameter to set either. )

I am using the Sveasoft pre7a f/w.

Anybody?


Date Posted: 04/16/2005 03:05 PM Posted By: sombranox(Junior Member)

My apologies for my stupidity when it comes to networking, but I'm new to this and this has been the best thread I've seen thus far regarding this.

I have an Actiontec DSL modem/Wireless gateway which I got from Qwest. It is in another room too far to run an ethernet from it to my desktops. I bought a Linksys WRT54G yesterday and I've followed the instructions at the top of this thread. However, my Linksys isn't connecting to the Actiontec's WAN for some reason.

The WAN IP is set as 192.168.0.1 with mask of 255.255.255.0. It broadcasts mixed on channel 9 by default and uses 64 bit WEP. I have the Linksys router set to client mode, the Wireless name and WEP info set correctly as far as I can figure out, and the linksys is just never getting an IP assigned in the Status page, though in the wireless status, it shows the Actiontec on the survey and shows it having throughput of 11 Mps.

So any clue at all why my Linksys isn't getting an IP when I can plug a wireless adapter into any of the computers and have them online directly? I'm really hoping to be able to do this so I can put my three desktops online through the router rather than using adapters for each.

If you have any suggestions, please let me know


Date Posted: 04/16/2005 03:14 PM Posted By: sombranox(Junior Member)

Scratch that. I'm a dumbass. I was using my first key as my passphrase. It all works now. Thanks very greatly for this


Date Posted: 04/18/2005 02:31 AM Posted By: g4814(Junior Member)

So, I have read all the forum, I was wondering if this firmware will work with wrt54gc? I have tried flashing the firmware but i get an error that says failed due to internet traffic or something very similar. Can you tell me what the message is when the firmware fails. I want to check to see if it is this message.


Date Posted: 04/19/2005 07:15 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: rangerman
Anybody figure out how to save that proxy_arp setting? It is really annoying to have to set it after the router resets for whatever reason. (Echoing 1 to it in /proc does not survive reboots. I don't see an NVRAM parameter to set either. )

I am using the Sveasoft pre7a f/w.

Anybody?




yeah, it's annoying but I don't know of any way to save it. Anyway, how often do reboot the router ? for me, it's only after a power outage.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/07/2005 03:46 PM Posted By: datapak(Junior Member)

I thought I had hit the mother lode when I found your detailed WRT54 to wireless eithernet bridge, but I have the Talisman Basic firmware and it is not the same for item 5
No operating mode Gateway to setup.

Any idea how I reproduce this option.
Will the 6rc5 firmware work on the WRT54gV3?

Thanks for any help.

datapak


Date Posted: 05/07/2005 08:04 PM Posted By: msdmoney(Member)

I was going through your walkthrough and got to step 4f. After I saved the settings and rebooted I can no longer connect to the router typing 192.168.1.1, not sure what I did wrong. I am pretty new to this, so there might be a basic step or thing that I am missing.

-------------------------
ebay

heatware


Date Posted: 05/07/2005 08:37 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: msdmoney
I was going through your walkthrough and got to step 4f. After I saved the settings and rebooted I can no longer connect to the router typing 192.168.1.1, not sure what I did wrong. I am pretty new to this, so there might be a basic step or thing that I am missing.




Didn't you notice that in step 4b the local IP was changed from 192.168.1.1 (or whatever it used to be before) to 192.168.0.129 ?

You need to use this new IP to connect to the router from now on ! DUH !

I also put a note in the instructions for other people to whom this may not be so obvious.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/07/2005 at 08:49 PM by user1234

Date Posted: 05/07/2005 09:22 PM Posted By: msdmoney(Member)

Thanks I got it working, sorry for the dumb question, I am pretty new at the networking stuff. I actually figured it out and was trying to connect to the right IP address(192.168.0.129) for a while with no luck, so I reset the router and went throught the steps again, and everything worked perfectly. Maybe I made a mistake the first time.

-------------------------
ebay

heatware


Date Posted: 05/07/2005 11:01 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: datapak
I thought I had hit the mother lode when I found your detailed WRT54 to wireless eithernet bridge, but I have the Talisman Basic firmware and it is not the same for item 5
No operating mode Gateway to setup.

Any idea how I reproduce this option.
Will the 6rc5 firmware work on the WRT54gV3?

Thanks for any help.

datapak




You can always try to flash to the Alchemy firmware and see if that works - if it's not compatible it will not flash. It should be compatible as long as they didn't change the CPU in the new revision. Otherwise, you can try to make it work with your firmware by trying to find similar settings, but there might be some trial and error involved in that (which is what this guide is supposed to help with).

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/07/2005 11:48 PM Posted By: semsoid(Junior Member)

Following your advice user1234, I switched from separate networks to single. My main Dlink box is 192.168.1.1, 255.255.255.0, my Linksys is using 192.168.1.129, 255.255.255.128

The Linksys gets a IP via DHCP and it is currently 192.168.1.50 (as its Internet IP). I cannot ping 1.50. I have double checked the settings on Linksys and neither firewall is on, nor block anonymous requests. Similarly, one of my boxes is connected to Linksys, has an IP 192.168.1.202,255.255.255.128 and I cannot ping it either.

Also, when setting up a port forwarding, do I still need to set it as double or just point to the whatever IP (in our case 1.202) directly on Dlink?

TIA

Sems


Date Posted: 05/07/2005 11:56 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: semsoid
Following your advice user1234, I switched from separate networks to single. My main Dlink box is 192.168.1.1, 255.255.255.0, my Linksys is using 192.168.1.129, 255.255.255.128

The Linksys gets a IP via DHCP and it is currently 192.168.1.50 (as its Internet IP). I cannot ping 1.50. I have double checked the settings on Linksys and neither firewall is on, nor block anonymous requests. Similarly, one of my boxes is connected to Linksys, has an IP 192.168.1.202,255.255.255.128 and I cannot ping it either.

Also, when setting up a port forwarding, do I still need to set it as double or just point to the whatever IP (in our case 1.202) directly on Dlink?

TIA

Sems




You should be able to ping the WRT54G client router from a PC attached to it using the address 192.168.1.129. You may need to reboot the WRT54G and the PC attached to it for the all the settings to be used. If you still can't even ping it from the attached PC using this address then you must have set something wrong, and need to start again (be doing a hard reset to clear all the setting from the non-volatile ram).

After you're able to ping the WRT54G from an attached PC, the next step is to try to ping it from PC attached to the main router, using the its external address 192.168.1.50.

Btw, I believe that you would only need to do the forwarding once with this overlapping network address setup.



-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/08/2005 at 12:44 AM by user1234

Date Posted: 05/08/2005 12:00 AM Posted By: semsoid(Junior Member)

Yes. after a reboot, I can ping the Linksys, via both 1.50 and 1.129. Strange, I wonder why I cannot ping 1.202 (my Location Free TV base), I was able to ping it when I used 2.x class. Also i cannot telnet to a port on it as well, even though the base can go out, as I can browse web with its client

Weird


Date Posted: 05/08/2005 12:07 AM Posted By: semsoid(Junior Member)

Found it. Somehow, the proxy_arp was lost. After trying to setup the port forwarding, it rebooted the Linksys, which in turn helped ping work.

Then when I applied "echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp", 1.202 became pingable and telnetable

And to confirm, yes single forward suffice. So all is good


Date Posted: 05/08/2005 12:53 AM Posted By: user1234(Platinum Member)

Cool, we have two more success stories just today ! Notice that this setup still creates a separate subnet for the client router, but because of the special proxy arp setting, the main router and its attached PCs can communicate with the client router and its attached PCs as if they are on the same network (no special routing required). In fact they can't tell that these PCs are really on a separate subnet.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/10/2005 07:25 PM Posted By: facemask(Member)


**EDIT** i reread your original post and have my answers. the only real question i have is...if i use the 3rd party firmware on one of the routers, how would i go about getting the original linksys firmware back on the router?



Edited: 05/10/2005 at 10:06 PM by facemask

Date Posted: 05/10/2005 11:50 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask

**EDIT** i reread your original post and have my answers. the only real question i have is...if i use the 3rd party firmware on one of the routers, how would i go about getting the original linksys firmware back on the router?




you can always download the latest version of the linksys firmware from their website, and use it to re-flash the router

http://www.linksys.com/download/firmware.asp?fwid=201


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/10/2005 at 11:51 PM by user1234

Date Posted: 05/11/2005 09:12 AM Posted By: facemask(Member)

thanks man...i have WRT54G now, im picking up the WRT54GS today and im giving this a shot. have you used this setup for online play with the XBOX and PS2? hopefully this works as well as im expecting!


Date Posted: 05/11/2005 06:05 PM Posted By: facemask(Member)

hmm...maybe you can help me out. i dont have much info though. i follwed your instructions step by step and i cant get connected.

WRT54GS (main router):
IP: 129.168.1.1
Subnet: 255.255.255.0
IP Range: 129.168.1.100-129.168.1.124

WRT54G (client):
Firmware Version: Alchemy-6.0-RC5a v3.01.3.8sv
IP: 192.168.1.129
Subnet: 255.255.255.128
IP Range: 129.168.1.140-129.168.1.149
Gateway: 192.168.1.1
DHCP Server enabled...
it is in Gateway Mode...
wireless mode is client...
wireless network mode is mixed...
SSID is set to the main router's SSID...
WEP settings are verified and correct...


...but the client router is not getting an IP from the main router. any suggestions?

thanks in advance for any help...

im not expecting it matters, but the only thing i changed that wasnt in your steps was the router name and time zone in the basic setup.



Edited: 05/11/2005 at 08:00 PM by facemask

Date Posted: 05/11/2005 08:04 PM Posted By: mikelish(Member)

in the original post it says this only works with version 2.2 of the wrt54g. mine says it's a v2 on the bottom of the router.

also the original post says to use the firmware version: 6rc5.... there is a new version out now titled "Final" should I get this instead?


Date Posted: 05/11/2005 09:07 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
hmm...maybe you can help me out. i dont have much info though. i follwed your instructions step by step and i cant get connected.

WRT54GS (main router):
IP: 129.168.1.1
Subnet: 255.255.255.0
IP Range: 129.168.1.100-129.168.1.124

WRT54G (client):
Firmware Version: Alchemy-6.0-RC5a v3.01.3.8sv
IP: 192.168.1.129
Subnet: 255.255.255.128
IP Range: 129.168.1.140-129.168.1.149
Gateway: 192.168.1.1
DHCP Server enabled...
it is in Gateway Mode...
wireless mode is client...
wireless network mode is mixed...
SSID is set to the main router's SSID...
WEP settings are verified and correct...


...but the client router is not getting an IP from the main router. any suggestions?

thanks in advance for any help...

im not expecting it matters, but the only thing i changed that wasnt in your steps was the router name and time zone in the basic setup.



My suggestions are:

0. Make sure you did step 4a (show below) AND that the DHCP server is enabled on the main router.

>> 4a. In "Setup::Basic setup" screen, set Internet Connection Type to "Auotomatic Configuration - DHCP".

1. Turn off WEP (on both routers) to rule that out as a problem
2. Make sure you also turn off the firewall and enable remote admin (steps 8 and 9)
3. Reboot the client router
4. If you still can't get a connection, then telnet into the client router and type "ifconfig" and "route" and send the output. Also try to do ping 192.168.1.1 from the client router (while you're telneted).



-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/11/2005 at 09:13 PM by user1234

Date Posted: 05/11/2005 09:18 PM Posted By: semsoid(Junior Member)

quote:
Originally posted by: facemask
hmm...maybe you can help me out. i dont have much info though. i follwed your instructions step by step and i cant get connected.

WRT54GS (main router):
IP: 129.168.1.1
Subnet: 255.255.255.0
IP Range: 129.168.1.100-129.168.1.124

WRT54G (client):
Firmware Version: Alchemy-6.0-RC5a v3.01.3.8sv
IP: 192.168.1.129
Subnet: 255.255.255.128
IP Range: 129.168.1.140-129.168.1.149
Gateway: 192.168.1.1
DHCP Server enabled...
it is in Gateway Mode...
wireless mode is client...
wireless network mode is mixed...
SSID is set to the main router's SSID...
WEP settings are verified and correct...


...but the client router is not getting an IP from the main router. any suggestions?

thanks in advance for any help...

im not expecting it matters, but the only thing i changed that wasnt in your steps was the router name and time zone in the basic setup.



It can be a typo, but you have put 129.168.x.x in some places and 192.168.x.x in some in your settings. All needs to be an unroutable class, like 192.168.x.x


Date Posted: 05/11/2005 09:20 PM Posted By: semsoid(Junior Member)

quote:
Originally posted by: mikelish
in the original post it says this only works with version 2.2 of the wrt54g. mine says it's a v2 on the bottom of the router.

also the original post says to use the firmware version: 6rc5.... there is a new version out now titled "Final" should I get this instead?




V2 works fine, as I own a working one. 6rc5 is known to work and that's what I used. Final version should practically work, as I don't think they removed any core functionality. The most important part of the Sveasoft firmware was the Client mode and final version should have it (I didn't check it though, you can flash and see)


Date Posted: 05/12/2005 12:21 AM Posted By: facemask(Member)

quote:
Originally posted by: user1234
My suggestions are:

0. Make sure you did step 4a (show below) AND that the DHCP server is enabled on the main router.

>> 4a. In "Setup::Basic setup" screen, set Internet Connection Type to "Auotomatic Configuration - DHCP".

1. Turn off WEP (on both routers) to rule that out as a problem
2. Make sure you also turn off the firewall and enable remote admin (steps 8 and 9)
3. Reboot the client router
4. If you still can't get a connection, then telnet into the client router and type "ifconfig" and "route" and send the output. Also try to do ping 192.168.1.1 from the client router (while you're telneted).



0. Make sure you did step 4a (show below) AND that the DHCP server is enabled on the main router.
this was done...

>> 4a. In "Setup::Basic setup" screen, set Internet Connection Type to "Auotomatic Configuration - DHCP".
this was done...

looks like WEP was part of the prob for me. i couldnt ping the main router. i disabled WEP on both routers and i am able to telnet to the client router and i can ping the main router. at this point, should the client router be able to get an address from the main router? if so, it aint happening.

i then rebooted the client router. as for the router "reboot", i took that to mean you wanted me to power cycle the sucker. i did not hold down RESET. let me know if i got that part wrong. after that, i COULDNT ping the main router anymore.

ok...

EDIT -- i have the router working with WEP disabled...so im moving on from there....

no luck using WEP. both using 128 bit (26 hex) encryption. both pass phrases match....



Edited: 05/12/2005 at 12:47 AM by facemask

Date Posted: 05/12/2005 01:25 AM Posted By: user1234(Platinum Member)

The main thing is that the WEP key (not the passphrase) must be the same on the main router and all its clients. You're only supposed to use the passphrase on one of the routers as a convenient way to generate a key and then copy this key to the other router. Or you can just come up with your own key (without using a passphrase) and use it on both routers.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/12/2005 at 01:36 AM by user1234

Date Posted: 05/12/2005 09:15 AM Posted By: facemask(Member)

after i used the same pass phrase to generate the keys...i also verified that the keys were correct and they were. so not sure what the deal is. something is not right though. i had disabled WEP again and was unable to connect to the main router again.

is the version of alchemy i used correct? other than that, all the setup is correct and the WEP settings all match. sad day.



Edited: 05/12/2005 at 09:16 AM by facemask

Date Posted: 05/12/2005 09:29 AM Posted By: semsoid(Junior Member)

Can you try setting up the system to use Open, instead of Shared Key authentication for WEP. That was the problem when I used DI-624 as my main router.


Date Posted: 05/12/2005 12:04 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
after i used the same pass phrase to generate the keys...i also verified that the keys were correct and they were. so not sure what the deal is. something is not right though. i had disabled WEP again and was unable to connect to the main router again.

is the version of alchemy i used correct? other than that, all the setup is correct and the WEP settings all match. sad day.



didn't you say before that you got it working properly without WEP ? so now it doesn't work even without WEP ?

btw, when I say to reboot your router, I mean to just restart it but not reset it because this will clear all the sttings stored in the NV (non volatile) RAM. To reboot the router you can indeed just disconnect it, or telnet and issue the command "reboot".

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/12/2005 01:43 PM Posted By: facemask(Member)

quote:
Originally posted by: semsoid
Can you try setting up the system to use Open, instead of Shared Key authentication for WEP. That was the problem when I used DI-624 as my main router.



thanks, i will try that when i get home. btw, what exactly is "shared" and "open"?


Date Posted: 05/12/2005 01:45 PM Posted By: facemask(Member)

quote:
Originally posted by: user1234
didn't you say before that you got it working properly without WEP ? so now it doesn't work even without WEP ?

btw, when I say to reboot your router, I mean to just restart it but not reset it because this will clear all the sttings stored in the NV (non volatile) RAM. To reboot the router you can indeed just disconnect it, or telnet and issue the command "reboot".



didnt know you could reboot from the cmd line...thx. and yes, it was working before. thats when i figured i could go ahead with the WEP setup, tried that, but it didnt work. tried to go back to no WEP and it wouldnt work anymore. i rebooted it and still couldnt get a connection...then i had to go to work.

i will mess with this some more as soon as i get home. thanks again for the help.


Date Posted: 05/12/2005 02:17 PM Posted By: semsoid(Junior Member)

quote:
Originally posted by: facemask
thanks, i will try that when i get home. btw, what exactly is "shared" and "open"?



Take a look at http://www.dslreports.com/forum/remark,8645211~mode=flat


Date Posted: 05/12/2005 04:58 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask

quote:
Originally posted by: user1234
didn't you say before that you got it working properly without WEP ? so now it doesn't work even without WEP ?

btw, when I say to reboot your router, I mean to just restart it but not reset it because this will clear all the sttings stored in the NV (non volatile) RAM. To reboot the router you can indeed just disconnect it, or telnet and issue the command "reboot".



didnt know you could reboot from the cmd line...thx. and yes, it was working before. thats when i figured i could go ahead with the WEP setup, tried that, but it didnt work. tried to go back to no WEP and it wouldnt work anymore. i rebooted it and still couldnt get a connection...then i had to go to work.

Did you remember to disable WEP on both routers right ?

i will mess with this some more as soon as i get home. thanks again for the help.




btw, some routers like my D-Link DI-624 (that what me and semsoid have in common), allow you to reboot them using their HTML interface, which is useful sometimes when things get messed up. Not sure why Linksys doesn't have that option, but then again the DI-624 has one of the best interfaces (better than Linksys and Netgear routers)

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/12/2005 at 08:20 PM by user1234

Date Posted: 05/12/2005 06:02 PM Posted By: facemask(Member)

quote:
Originally posted by: user1234
Did you remember to disable WEP on both routers right ?


yes, if i disabled/enabled WEP on one, i'd do the same for the other. i just walked in and im going to try this again...even though i should be doing things like going through bills or refinancing my mortgae.

ill post where im at in just a bit...


Date Posted: 05/12/2005 06:33 PM Posted By: facemask(Member)

well...i went through the menus on both routers verifying all the settings and hitting save again just for the heck of it.i couldnt find the OPEN key setting, but i know i have seen it before. i found SHARED key in Wireless::Advanced Wirless...but the only options were SHARED or AUTO. i selected AUTO on both. is the OPEN option suppossed to be here? the client router is being assinged an IP and i can ping the AP and internet domains from the client router...but the laptop connect to this client can not. so thats where im at...



Edited: 05/12/2005 at 06:43 PM by facemask

Date Posted: 05/12/2005 06:43 PM Posted By: facemask(Member)

hold the phones!! its working! thanks for the help guys...im gonna move it downstairs now and test it out for real.


Date Posted: 05/12/2005 07:35 PM Posted By: semsoid(Junior Member)

Well, some routers put both Open and Shared Key and some, like Linksys, says Auto and Shared Key. In Auto, it will try Open first, then try Shared Key if I am not mistaken.


Date Posted: 05/12/2005 08:06 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
hold the phones!! its working! thanks for the help guys...im gonna move it downstairs now and test it out for real.




congrats!!! now you will finally have time for to the real fun stuff like paying bills etc........j/k

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/12/2005 10:54 PM Posted By: facemask(Member)

thanks again for the help guys. didnt have time for bills...was playing Halo and Madden all night without a 50-ft cat5 connected to my router upstairs to the consoles down stairs...awesome!


Date Posted: 05/13/2005 08:52 AM Posted By: facemask(Member)

just out of curiosity....how long has linksys had their code open source? who had the first 3rd party firmware available for this? just wondering how far behind in the times i am

is sveasoft the first and/or only 3rd party firmware for this? is using the router as a bridge/client not possible any other way?


Date Posted: 05/13/2005 11:19 AM Posted By: net(Member)

This sounds cool. But why would I want to do this? What can I do with this?

-------------------------
Selling a Canon Rebel GII camera

Heatware: net


Date Posted: 05/13/2005 12:00 PM Posted By: semsoid(Junior Member)

Many things, put one into your entertainment unit and provide connection/s to your devices, such as PS2, Xbox, Media Center, DVD player an internet connection without running wires all around the house.


Date Posted: 05/13/2005 12:52 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
just out of curiosity....how long has linksys had their code open source? who had the first 3rd party firmware available for this? just wondering how far behind in the times i am

is sveasoft the first and/or only 3rd party firmware for this? is using the router as a bridge/client not possible any other way?




no there are lots of modded firmwares around, and I think some recent ones are even better. I believe it's possible to do this bridging with many of the modded firmwares, but when I got my WRT54G I couldn't find any clear and simple step by step instructions on how to do it. So I went googling around the internet and found various bits and pieces of information and finally after a lot of trial and error I was able to get it working. So I thought I should write this guide so other people can benefit from my experience and not have to go thru the same process (which most people will probably not even want to attempt, or give up after a while).

A good start about available firmwares is this thread (especially the first post)

http://forums.anandtech.com/messageview...atid=40&threadid=1343138&enterthread=y



-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/17/2005 11:43 PM Posted By: wiltonh(Junior Member)

Over the last few weeks I have spent my spare time working with the Wrt54g and many of the different firmware versions that are available. My goal was to get a simple client mode running. I actually was trying many of the things mentioned in this thread over a month ago but could not get it to work. About a week ago, I found this thread and thought my troubles were over. NOT SO

I setup my wrt54g just as shown and the router would not get a DHCP address. I tried every thing I could think of and nothing would work. This included several versions of firmware plus starting over several times from scratch. I bricked the router a few times in the process.

I can now do this setup by memory.

My break came today when I read every article in this thread. I found another user who had some very bitter things to say about the Linksys BEFW11S4 wireless router. This router has a checkered past. Just Google it if you really want to know the history. I puchased it because my Company recommended it as the router they wanted us to use for VPN.

Tonight I decided to shut off the wireless on the BEFW11S4 and try a very old WAP11 that I had sitting around. I plugged it in and configured it as an AP. The Wrt54g associated with it and connected just fine. I am sending this post over that setup.

I have other cards that can connect to the BEFW11S4 just fine. These include Netgear MA111, WG111, and Dell Trumobile 1150. We have connected Centreno Laptops, Dell Laptops and Toshiba tablets. In general the wireless has worked okay but it will not connect to the wrt54g.

The current setup does not work on the BEFW11S4 but does work on the WAP11. The only thing that is different is the SSID. The WAP11 has a different SSID than the BEFW11S4.

If anyone else has connected with BEFW11S4 wireless router to a Wrt54g, I would like to hear from you.




Edited: 05/18/2005 at 12:15 AM by wiltonh

Date Posted: 05/18/2005 04:24 AM Posted By: user1234(Platinum Member)

wiltonh, welocme to the forums !!!!!!! yes, I remember someone complaining about the BEFW11S4 not being able to connect with the wrt54g, but since this person only posted a single time I do not know if he was able to get it to work. In theory, the wrt54g should be able to act as a client of any wireless routers (especially linksys routers), but of course in reality there might be some bugs and other snags which might prevent that. In fact, most people that experienced problems and posted about them here, were able to solve them and get a working setup.
In your case, I understand you probably tried almost everything, therefore there is a good chance it really is because of some underlying incompatiblity. But just to make sure, you can check two major sources of problems: one is WEP (i recommend to turn it off to rule it out as the source of the problem), and second is the MAC filtering feature on your main router which only allows specific clients to connect. I understand you can connect to your BEFW11S4 main router using other wireless clients, so I guess you must know how to set up the WEP and mac filtering correctly, but it's always better to double check.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/18/2005 11:45 AM Posted By: wiltonh(Junior Member)

I do understand WEP and Mac filtering.

>one is WEP (i recommend to turn it off to rule it out as the source of the problem),

Wep was shut off on both the WRT54g and the BEFW11S4.

>and second is the MAC filtering feature on your main router which only allows specific >clients to connect.

When I started, I found the WRT54G listing of MAC addresses to be really confusing. The wireless page shows a MAC address but it is not the MAC address of the wireless. I mentioned this in another forum and was told by BrainSlayer (DD-WRT coder) that it is a routed wireless so you really need to put in the MAC address for the router. I covered my bases and put in all three MAC addresses but it did no good. I then just disabled MAC address filtering all to gether and it still did not work.

I created your exact setup using fixed IP address for everything and that did not work either. The radio connected just fne but the WRT54g would not send data across the link on a consistent basis. There were a few times when a ping or two would work but it would then stop again. I did see the NMTP server update the time correctly once. So it was not a 100% failure. It was about a 99.99% failure.

There may be a later version of software for the BEFW11S4 and I will probably check into that but the software that is on the box is about 6 months old. When I got BEFW11S4 the thing would crash about every day or so, but when I went to the current version of software it now runs fine with no crashes. VPN works well and I thought things were all happy until I spent about 20+ hours trying to get client mode running.


Date Posted: 05/18/2005 11:58 AM Posted By: user1234(Platinum Member)

yep, I noticed that BEFW11S4 has a large number of frustrated user reports, so maybe it's time to get a 54g router...and don't worry about VPN, it now works with almost every router

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/18/2005 02:09 PM Posted By: hak0r 5t4tus(Junior Member)

user1234 thanks for the info. It works perfectly

Now this is the problem I am having. There are 2 printers on the network and when i try to ping the IP addresses of the priters sometimes i get the standard reply

Reply from 192.168.1.249...

And sometimes it looks like this

Reply from 192.168.1.249.....
Reply from 192.168.1.110 destinaltion host unreachable

and the damn printers arent working half the time. Now the .110 IP address is the one assigned to the Router that I set up as a wireless bridge (wrt54g #2) and its getting it from my main routher which is one of the linksys hard wired routher w/ VPN. It doesnt make any sense to me why traffic would sometimes be directed to the WRT54G thats setup as just a client

So my setup look like this

linksys hardwired--------WRT54G(ap mode with alchemy fw)~~~~~~~WRT54G(client mode)

Whats your thoughts on that?


Date Posted: 05/18/2005 03:11 PM Posted By: user1234(Platinum Member)

Did you perform step 10 (set up proxy arp) ? note that this setting is NOT saved in the non volatile memory of the client router (unlike all the other settings), so if you reboot it or disconnect it, then this setting is lost, and need to be restored manually by repeating step 10.
The "host unreachable" message seems like it's saying that the client router (.110) is not able to connect to the printer (.249) which I assume is wired to it, right ? Are you seeing this problem when you ping the printer from a PC attached to the first WRT54G or from a PC attached to the client WRT54G ?

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/19/2005 02:26 AM Posted By: hak0r 5t4tus(Junior Member)

I did perform step 10. And the printers and hard wired machines all go into a switch the goes into the BEFVP41. The first WRT54G is plugged into the BEFVP41 as well. So if i ping from wireless or hardwired clients i still get the same problem


Date Posted: 05/19/2005 02:43 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: hak0r 5t4tus
I did perform step 10. And the printers and hard wired machines all go into a switch the goes into the BEFVP41. The first WRT54G is plugged into the BEFVP41 as well. So if i ping from wireless or hardwired clients i still get the same problem



Oh, I see..... the problem is of overlapping addresses - your printer address (.249) is in the range 128-255 which is supposed to only be used by the client router and its attached PCs, so assigning this address to the printer causes ambiguity and conflicts.

Did you see the note preceding step 4 ?

"Note: We will use addresses that end in 128-255 for the wrt54g router and it's attached PCs. To make sure there is no overlap in the addresses assigned by the two routers, we have to make sure that your main router doesn't assign addresses to its own clients in that range. For example, if your main router address is 192.168.0.1, its DHCP address range could be 192.168.0.50 - 192.168.0.120."

So the solution is to change the IP assigned to your printers and any other PC attached to your main router to NOT use the range 128-255. You should be able to do it by modifying the DHCP settings on the main router (if you're using DHCP), or if you're using static addresses for the printers, you'll have to change those on each of them.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/19/2005 at 02:55 AM by user1234

Date Posted: 05/19/2005 08:48 AM Posted By: hak0r 5t4tus(Junior Member)

I never even thought of that. Ill give that a try today and post the results. Thanks for the advice


Date Posted: 05/19/2005 11:35 AM Posted By: wiltonh(Junior Member)

Last night I checked on the firmware version of my BEFW11S4 and it was not the latest version. The file that lists things fixed in the new version, showed a wireless compatibilty problem fixed, so I had high hopes. I downloaded it and updated my firmware. The existing network seems to still work correctly but it did not help my client mode problem.

I setup the wrt54g to connect as a client and I did see it partially connect. It picked up the correct DNS server but by the time I got ping running it would no longer connect.

At this point I do not believe the Wrt54g and the BEFW11S4 are compatible for wireless connections. They will associate but not communicate.

In the long run I do not plan to use this wrt54g connected to this system. It will be used as one end of a long distance link for a home that is located where there is no cable or DSL access and never will be any. Here is a link to the antenna which will be connected to one end:

http://windsurf.mediaforte.com/dish_can.jpg

The other end of the link will be another antenna and a second wrt54g. The distance will be around a mile so we could use a much smaller antenna.

The irony of this situation is that there is fiber running across the end of the property. I checked, and the telephone company would only connect me if I was willing to pay for a DS3 connection. A couple of Wrt54g routers and antenna seemed like a lot cheaper way to go.






Edited: 05/19/2005 at 11:59 AM by wiltonh

Date Posted: 05/19/2005 01:30 PM Posted By: hak0r 5t4tus(Junior Member)

Ok the IP range for inside is 192.168.1.100-192.168.1.149 and outside with the clients connected to the WRT54G the IP range is 192.168.1.150 (device IP) and the scope is 192.168.1.155-192.168.1.205. I put the printer which previously was .249 to .145 and i am still having the ping say:

reply from 192.168.1.110 destination host unreachable...

and that is from any client that is connected to the first WRT54G that is setup as the office AP


Date Posted: 05/19/2005 01:55 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: hak0r 5t4tus
Ok the IP range for inside is 192.168.1.100-192.168.1.149 and outside with the clients connected to the WRT54G the IP range is 192.168.1.150 (device IP) and the scope is 192.168.1.155-192.168.1.205. I put the printer which previously was .249 to .145 and i am still having the ping say:

reply from 192.168.1.110 destination host unreachable...

and that is from any client that is connected to the first WRT54G that is setup as the office AP



no it has to be below 128 !!!!!!! otherwise the client wrt54g will think it's meant for its own subnet, and will initiate a proxy arp reply.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/19/2005 at 02:43 PM by user1234

Date Posted: 05/20/2005 12:50 AM Posted By: Tom33(Member)

I have a WRT54G that looks to be a Version 3 (CDF8), still in the package, for now.

1. Do I need a firmware upgrade to get the unit into Client mode ?
2. If so, is there a proven safe firmware for a v3 unit ?

Thanks

-------------------------
Be Kind To Your Neighbors -- They Know Where You Live !!


Date Posted: 05/21/2005 12:48 AM Posted By: Tom33(Member)

Well to answer my own question.....Talisman Basic 1.0.3.1 Firmware will install on a V3 router. Router works as a router fine after the upgrade. I will head out tomorrow to pick up another router, to move the project further along.

-------------------------
Be Kind To Your Neighbors -- They Know Where You Live !!


Date Posted: 05/22/2005 12:13 AM Posted By: facemask(Member)

im back. so far i have had great success with this setup. got my PS2 and XBOX hooked up to a WRT54G which is the client router.

I just got my ReplayTV this week and hooked that up and was up and running with that as well without any problems.

However, now I want to try and transfer photos from my PC on the main router to my ReplayTV (RTV) box on the client router. I ran the command "echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp" on the client router, but I am unable to establish a connection with the RTV box.

After running the proxy_arp command on the client router, I could not ping the RTV and the software that looks for an RTV on the network did not find it either.

any suggestions?


Date Posted: 05/22/2005 02:56 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
im back. so far i have had great success with this setup. got my PS2 and XBOX hooked up to a WRT54G which is the client router.

I just got my ReplayTV this week and hooked that up and was up and running with that as well without any problems.

However, now I want to try and transfer photos from my PC on the main router to my ReplayTV (RTV) box on the client router. I ran the command "echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp" on the client router, but I am unable to establish a connection with the RTV box.

After running the proxy_arp command on the client router, I could not ping the RTV and the software that looks for an RTV on the network did not find it either.

any suggestions?



try: ping the RTV from the client router (after telneting into the router), then try to ping it from a PC attached to the client router, and then from PC attached to the main router. Which one fails ? if the first one fails then maybe the RTV is not responding to pings....
Do you succeed in pinging the XBOX and other devices attached to the client WRT54G from a PC attached to the main router ?

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/22/2005 09:31 PM Posted By: facemask(Member)

the ping to the RTV from the client router is successful. i dont have a PC hooked up to the client, but if you think it will help debug the prob, i can hook one up.

i typed in the cmd "echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp" in quotes exactly. if thats correct, im not sure where to go from here.

on a side note...what exactly does having proxy_arp with "1" in the file do?



Edited: 05/22/2005 at 09:43 PM by facemask

Date Posted: 05/23/2005 02:43 PM Posted By: user1234(Platinum Member)

hmmm.. so you can ping it from the client router but not from a PC attached to the main router ? is this he same for the other devices attached to the client router (e.g. can ping them from the client router but not from a PC attached to the main router) ? if so, then maybe the proxy_arp is not working. Verify the setup by typing this command and check that it prints out "1":

cat /proc/sys/net/ipv4/conf/eth1/proxy_arp

If it's only the RTV then that doesn't respond to pings from a remote PC, then try using a different physical port on the wrt54g

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/23/2005 03:18 PM Posted By: facemask(Member)

quote:
Originally posted by: user1234
hmmm.. so you can ping it from the client router but not from a PC attached to the main router ? is this he same for the other devices attached to the client router (e.g. can ping them from the client router but not from a PC attached to the main router) ? if so, then maybe the proxy_arp is not working. Verify the setup by typing this command and check that it prints out "1":

cat /proc/sys/net/ipv4/conf/eth1/proxy_arp

If it's only the RTV then that doesn't respond to pings from a remote PC, then try using a different physical port on the wrt54g



i tried that last night, and cat did display "1". i will have to turn turn on the consoles when i get home and try the pings then. thanks.


Date Posted: 05/25/2005 07:43 AM Posted By: jeremycobert(Junior Member)

user1234, many thanks for the tips.

here are some tips for replaytv users.i did get mine running with IVS and dvarchive and poopli updater all working wirelessly.

i had been using the old satori firmware just because it allowed me to easily bridge my wrt54's . so i read user1234 first post in this topic and upgraded the firmware on both routers.

i didnt get it to work right away but after about 12 hours i did finally get it up and running. now i have 4 ports on the client instead of just 1. i had trouble when i was not using the x.x.x.129 address on the client, but it became pingable and then fully working after assigning it the 129 then with echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp on the client, made it pingable to all spots within the network


my setup looks like this
cable modem-->wrt54g#1---wirelessly----wrt54g#2--->replaytv

#1s ip is 192.168.1.1 and #2 is 192.168.1.2, but the subnet on#2 starts on 192.168.1.129
the tricky part for me was getting port forwarding to the RTV, i had to forward my sharing port # from #1 into #2's ip address not the routers subnet address. so after i got RTV's sharing feature up and working i then had problems with DVarchive from my laptop(wrt#1) connecting to RTV, but i did a port forward of port 80 on wrt#2 to forward it to RTV. and now its all back and running.the only thing left is that when dvarchive (laptop)is listening for RTV on the network associated with my laptops ip, it never seems to find it, so i still have to manually tell dvarchive where it is. no big deal, i will get it!!!


Date Posted: 05/25/2005 03:32 PM Posted By: facemask(Member)

quote:
Originally posted by: jeremycobert
user1234, many thanks for the tips.

here are some tips for replaytv users.i did get mine running with IVS and dvarchive and poopli updater all working wirelessly.

i had been using the old satori firmware just because it allowed me to easily bridge my wrt54's . so i read user1234 first post in this topic and upgraded the firmware on both routers.

i didnt get it to work right away but after about 12 hours i did finally get it up and running. now i have 4 ports on the client instead of just 1. i had trouble when i was not using the x.x.x.129 address on the client, but it became pingable and then fully working after assigning it the 129 then with echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp on the client, made it pingable to all spots within the network


my setup looks like this
cable modem-->wrt54g#1---wirelessly----wrt54g#2--->replaytv

#1s ip is 192.168.1.1 and #2 is 192.168.1.2, but the subnet on#2 starts on 192.168.1.129
the tricky part for me was getting port forwarding to the RTV, i had to forward my sharing port # from #1 into #2's ip address not the routers subnet address. so after i got RTV's sharing feature up and working i then had problems with DVarchive from my laptop(wrt#1) connecting to RTV, but i did a port forward of port 80 on wrt#2 to forward it to RTV. and now its all back and running.the only thing left is that when dvarchive (laptop)is listening for RTV on the network associated with my laptops ip, it never seems to find it, so i still have to manually tell dvarchive where it is. no big deal, i will get it!!!



hey man...if you could put together a step by step procedure for each router and all the port forwarding, i would greatly appreciate it!! im still kinda a newbie with networking, so if you could break it all down, that would be awesome!

i have the setup user1234 posted and it works fine. but even with the proxy_arp, i cant ping devices on the client router. i'd like to be able to use PCs on the main router for all the ReplayTV tools you mentioned.


Date Posted: 05/26/2005 12:20 AM Posted By: user1234(Platinum Member)

facemask, I think your proxy_arp is not working. Are you using a slightly different version of the firmware then what I described in the guide ? the thing is that different versions of the firmware use different device designations for each port, so you may need to set up the proxy_arp a little differently. To find out the device name to use for proxy arp (e.g. eth0 or eth1 ir eth2, etc) telnet to the wrt54g and type the command "ifconfig". You should see a list of devices like "br0", "eth1", "vlan0" etc, and next to each one is some information. Look for the device which has an IP address that looks like 192.168.x.y where y is BELOW 128. There should only be one device with such an address. Now you just need to use this device name ito set up the proxy arp. For example, if the device is eth0, then use this command to set up proxy arp:

echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp

Now you can try to ping from the remote PC. btw, after you set up the proxy_arp (hopefully it will finally work), you can do port forwarding very easily by just setting it on the main router (designating the port to forward and the machine to forward it to). There is no need to set up the port forwarding on the client router, as the proxy arp will seamlessly forward anything that is addressed to a device attached to the client router.



-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/26/2005 at 12:31 AM by user1234

Date Posted: 05/26/2005 02:59 AM Posted By: jeremycobert(Junior Member)

hey facemask,
i used the alchemy6.0 rca v3018sv as it says on the first post. i used this firmware on both the gateway and client routers. after the main router is running i unhooked my wireless card in my laptop and started working on the client, using the wrt54(client) as the nic card. follow all the steps in post 1, here is a pic of my clients setup.

picture of my client setup

so the first network can use 192.168.1.1 through 192.168.1.28 then the second network (subnet) starts on 192.168.1.129 through 192.168.1.254.


its easy to forward the ports, i let the client router get ip 192.168.1.2 , on the main router(192.168.1.1) i forward my replaytv sharing port to the clients address x.x.x.2, then on the client i forwad the same port to my replaytv at 192.168.1.151 (you may notice that i start the IP's at x.x.x.150, thats just to keep things straight in my head.

i use grc's shield up to test my port, use the custom probe port and your port number. it will say if its open or hidden.

poopli updater seems to search over the network and its subnet, so i just let it auto add. and its working, along with poopli sharing

dvarchive will only search for RTV's on its network so it has trouble finding it on the other network (the subnet) but you can just tell it where its located and then it will open up you RTV. i runs at about 290KB/s which is close to 300, so im happy with it.

i hope i helped ya,


Date Posted: 05/26/2005 07:47 AM Posted By: pat68(Junior Member)

Hi user1234

very nice description. And I managed it to get it working sporadicly.
My configuration:
WAG54G ------- WRT54G ------ PC1

I'm living in an apartment house with 2 other WLAN environments installed. With the settings you described, the WRT will make s short connection to the WAG54G, receive a IP address, but after a short time, it will loose connection and change the channel. It then resides on the channel used by my neighbours WLAN and shows the MAC address of this AP in the wireless status. I use 128bit WEP encryption.
When it works I get ping response times from 20-30ms in average. May this be cause by the WAG54G? I've seen that there are lot of negative statements about this router. But in my opion, it is a practiable, cheap, all-in-one solution (if it works).

Thanks in advance
pat


Date Posted: 05/26/2005 12:26 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: pat68
Hi user1234

very nice description. And I managed it to get it working sporadicly.
My configuration:
WAG54G ------- WRT54G ------ PC1

I'm living in an apartment house with 2 other WLAN environments installed. With the settings you described, the WRT will make s short connection to the WAG54G, receive a IP address, but after a short time, it will loose connection and change the channel. It then resides on the channel used by my neighbours WLAN and shows the MAC address of this AP in the wireless status. I use 128bit WEP encryption.
When it works I get ping response times from 20-30ms in average. May this be cause by the WAG54G? I've seen that there are lot of negative statements about this router. But in my opion, it is a practiable, cheap, all-in-one solution (if it works).

Thanks in advance
pat



the WRT54G client router will only connect to a router/AP with the specific SSID name that you instruct it to (in step 6 of the howto). But if you have more than one router with the same SSID then it will probably associate with one of them randomly, and maybe even switch to the one with strongest signal. If that is the case, then I suggest you use a unique SSID for the WAP54G and tell the WRT54G to connect to it.


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/26/2005 06:01 PM Posted By: facemask(Member)

quote:
Originally posted by: user1234
facemask, I think your proxy_arp is not working. Are you using a slightly different version of the firmware then what I described in the guide ? the thing is that different versions of the firmware use different device designations for each port, so you may need to set up the proxy_arp a little differently. To find out the device name to use for proxy arp (e.g. eth0 or eth1 ir eth2, etc) telnet to the wrt54g and type the command "ifconfig". You should see a list of devices like "br0", "eth1", "vlan0" etc, and next to each one is some information. Look for the device which has an IP address that looks like 192.168.x.y where y is BELOW 128. There should only be one device with such an address. Now you just need to use this device name ito set up the proxy arp. For example, if the device is eth0, then use this command to set up proxy arp:

echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp

Now you can try to ping from the remote PC. btw, after you set up the proxy_arp (hopefully it will finally work), you can do port forwarding very easily by just setting it on the main router (designating the port to forward and the machine to forward it to). There is no need to set up the port forwarding on the client router, as the proxy arp will seamlessly forward anything that is addressed to a device attached to the client router.



ahhhh!!! sorry man...i know jack about proxies and and was just mindlessly following your directions. i do have the version in your original post. and i did just use eth0 in the proxy. i checked ifconfig, and needed to use eth2. changed it and i can ping from my pc on the main router. hooray!

now i just need to figure what i need to do for port fwding to get my ReplayTV tools up and running.

thanks man!


Date Posted: 05/26/2005 06:13 PM Posted By: facemask(Member)

quote:
Originally posted by: jeremycobert
hey facemask,
i used the alchemy6.0 rca v3018sv as it says on the first post. i used this firmware on both the gateway and client routers. after the main router is running i unhooked my wireless card in my laptop and started working on the client, using the wrt54(client) as the nic card. follow all the steps in post 1, here is a pic of my clients setup.

picture of my client setup

so the first network can use 192.168.1.1 through 192.168.1.28 then the second network (subnet) starts on 192.168.1.129 through 192.168.1.254.


its easy to forward the ports, i let the client router get ip 192.168.1.2 , on the main router(192.168.1.1) i forward my replaytv sharing port to the clients address x.x.x.2, then on the client i forwad the same port to my replaytv at 192.168.1.151 (you may notice that i start the IP's at x.x.x.150, thats just to keep things straight in my head.

i use grc's shield up to test my port, use the custom probe port and your port number. it will say if its open or hidden.

poopli updater seems to search over the network and its subnet, so i just let it auto add. and its working, along with poopli sharing

dvarchive will only search for RTV's on its network so it has trouble finding it on the other network (the subnet) but you can just tell it where its located and then it will open up you RTV. i runs at about 290KB/s which is close to 300, so im happy with it.

i hope i helped ya,



thanks man...i am new to ReplayTV, just got it about a week ago. ive only done a limited amount of research on dvarchive and i havent heard about grc shield up or poopli...so i have some work to do. youve helped...just need to figure out how to get started. thanks!

btw, i have it setup as user1234 described, so my client is 192.168.1.129. do you know if thats gonna be a problem? im assuming not, but just thought i'd ask.



Edited: 05/26/2005 at 06:26 PM by facemask

Date Posted: 05/26/2005 06:52 PM Posted By: facemask(Member)

quote:
Originally posted by: jeremycobert
its easy to forward the ports, i let the client router get ip 192.168.1.2 , on the main router(192.168.1.1) i forward my replaytv sharing port to the clients address x.x.x.2, then on the client i forwad the same port to my replaytv at 192.168.1.151 (you may notice that i start the IP's at x.x.x.150, thats just to keep things straight in my head.


how do you know which port to fwd to?

quote:
Originally posted by: jeremycobert
i use grc's shield up to test my port, use the custom probe port and your port number. it will say if its open or hidden.


what is the point for running this? are you checking to make sure it says it is open?

quote:
Originally posted by: jeremycobert
poopli updater seems to search over the network and its subnet, so i just let it auto add. and its working, along with poopli sharing


never heard of this...what is poopli updater for?

*EDIT* - searched for poopli...tried to follow their directions but i cant find a menu they are talking about. i have a 5508...i have no idea how to get a prompt for a port number.

quote:
4) When prompted for a port number, enter the number of an unused port on your network. This number should be higher than 1024. 29000 is generally a good choice. Remember this number, it is the "IVS PORT" that must be forwarded to your ReplayTV in your router later.




thanks again...maybe i should be sending you private msgs or start a new thread so i dont hijack this thread with ReplayTV specific questions



Edited: 05/26/2005 at 09:36 PM by facemask

Date Posted: 05/26/2005 08:23 PM Posted By: facemask(Member)

heres a question for user1234 or anyone else. how can i provide a static IP to my replaytv box on the client router? (im searchin the web for my answers as well, i figure it out i will post so i dont waste anyones time.) thanks.


Date Posted: 05/26/2005 11:01 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
heres a question for user1234 or anyone else. how can i provide a static IP to my replaytv box on the client router? (im searchin the web for my answers as well, i figure it out i will post so i dont waste anyones time.) thanks.




that's an easy one. I assume you currently use DHCP in the client router to assign addresses to its attached devices. The problem with DHCP is that it may choose any address in the range you define, and everytime it can choose a different address. Luckily, there is a way to ensure it assign the same address every time - this is called STATIC DHCP. To set it up, use the wrt54g's web interface, and go to Administration::Management screen. Locate the "Static Allocations" text box in the "Dhcpd" section. There you need to type in the desired IP address followed by the MAC address of your device and its name, for example:

192.168.0.130 11:22:33:44:55:66 SLI

Note that it's best to use an address that is not part of your dynamic DHCP address range (but it still must be above 128). In my case, my dynamic DHCP address start at .140 (this is selected on the Setpu::Basic setup scrren), so I use the static .130 address as a static address for my SLI machine. You can add all your devices to the list, thus ensuring they will always have the same address assigned to them.

btw, regarding your port forwarding....now that you got proxy arp working it is very simple to set up the port forwarding. First, let me explain that port forwarding means that an incoming connection on a specific port from the internet to your main router is forwarded to one of the machines on your home network. Normally your router will block all INCOMING connections, but if you set port forwarding then a packet coming on that port will be forwarded. For example, when I want to host an online game (such as UT2004 or Doom3) I run the game server software on one of my PCs, so it is waiting for incoming connections from online gamers who want to join the game (the game server software notifies the central UT2004 server that it is available and ready to host public games). For UT2004 the default port it listens on is 7778 UDP, but of course my main router normally blocks all incoming connections on all ports. So I set up a port forwarding rule on my main router to forward UDP port 7778 to 192.168.0.130 which is the machine running the game server. Most routers have this simple feature to set up port forwarding. You ONLY NEED TO SET UP PORT FORWARDING ON YOUR MAIN ROUTER, even if you want to forward to a device attached to the client router, because in that case the proxy arp will ensure that your main router can connect to the destination machine.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/26/2005 at 11:43 PM by user1234

Date Posted: 05/26/2005 11:11 PM Posted By: facemask(Member)

awesome!! i actually checked that screen and missed it. once again...thanks a lot!


Date Posted: 05/27/2005 07:43 AM Posted By: pat68(Junior Member)

Hi user1234.
Thanks for your advice. I already found the problem, on the WAG54G I had SSID broadcast disabled, enabled again and it works 8-)


Date Posted: 05/27/2005 10:32 AM Posted By: The Goon(Junior Member)

First off "hello" and secondly would like to thank User1234 for his excellent tut

Right here we go with my problem, my main modem/router is a Belkin F5D7632uk4 and my bridge is a WRT54G, now the only thing i'm using the WRT54G for is for a wireless connection to my modded Xbox in another part of the house. I followed the tut and i was online with the xbox through xbox media centre listening to web radio etc, so the routers are talking fine. The problem i have is i can't FTP into the xbox, the ip addy the xbox is giving me is 192.168.2.140 as my Belkin uses 192.168.2.**. I put the above ip addy into flashfxp but no go. I saw you replied to someone else about this earlier on in the thread but it went "whoosh" over my head lol. The xbox is set up as per the tut except for my main router ip addy and on the Belkin i have 2 wired PC's and 2 wireless pc's with ip addy's going from 2.2 to 2.5.
So basically in n00b terms how to i ftp from my pc on subnet mask 00 to my xbox on subnet mask 128. The PC with flashfxp is 2.2 and my O/S is XP Home.

All help very much appreciated



Edited: 05/27/2005 at 10:34 AM by The Goon

Date Posted: 05/27/2005 10:51 AM Posted By: facemask(Member)

quote:
Originally posted by: The GoonSo basically in n00b terms how to i ftp from my pc on subnet mask 00 to my xbox on subnet mask 128. The PC with flashfxp is 2.2 and my O/S is XP Home.

All help very much appreciated



user1234 helped me out with this....il just quote him in from an earlier post. you need to telnet to the wrt54g and login. you want to execute the command "echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp"
notice the bold around eth0...it could be eth1, eth2...you need to find out by first running the cmd "ifconfig" -- look for the eth# that is listed with an IP from your main router. that is the eth# you use in the proxy_arp command. once you do that, you should be able to ping, ftp to the xbox.

quote:
Originally posted by: user1234To find out the device name to use for proxy arp (e.g. eth0 or eth1 ir eth2, etc) telnet to the wrt54g and type the command "ifconfig". You should see a list of devices like "br0", "eth1", "vlan0" etc, and next to each one is some information. Look for the device which has an IP address that looks like 192.168.x.y where y is BELOW 128. There should only be one device with such an address. Now you just need to use this device name ito set up the proxy arp. For example, if the device is eth0, then use this command to set up proxy arp:

echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp

Now you can try to ping from the remote PC. btw, after you set up the proxy_arp (hopefully it will finally work), you can do port forwarding very easily by just setting it on the main router (designating the port to forward and the machine to forward it to). There is no need to set up the port forwarding on the client router, as the proxy arp will seamlessly forward anything that is addressed to a device attached to the client router.



btw, to telnet to your client router, just bring up a cmd prompt and telnet to its ip, user will be "root" and then the password you setup for it....default is admin.


Date Posted: 05/27/2005 11:47 AM Posted By: The Goon(Junior Member)

I luv this place,brilliant it worked,thank you Facemask i just ftp a skin over and it worked. Now thats done the next thing is to get KAI games network to go through. In the wireless setup it ask for the real mac addy and the virtual mac addy, the real one being the mac addy of the xbox and the virtual one being the wrt54g's which is written on the bottom of the router. I put them in and it's not detecting the xbox. Will i have to port foward this through the belkin? it says to use port 3000 tcp to port forward KAI,if this is the case what ip addy do i port foward to, the Belkin,WRT54G or the xbox ip addy?


Date Posted: 05/27/2005 12:11 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: The Goon
I luv this place,brilliant it worked,thank you Facemask i just ftp a skin over and it worked. Now thats done the next thing is to get KAI games network to go through. In the wireless setup it ask for the real mac addy and the virtual mac addy, the real one being the mac addy of the xbox and the virtual one being the wrt54g's which is written on the bottom of the router. I put them in and it's not detecting the xbox. Will i have to port foward this through the belkin? it says to use port 3000 tcp to port forward KAI,if this is the case what ip addy do i port foward to, the Belkin,WRT54G or the xbox ip addy?




To forward a port, you just need to set it up on the MAIN ROUTER ONLY. You specify the port you want to forward (e.g. 3000 tcp) and the destination machine to forward to (e.g. the XBOX 192.168.2.140). Each router has a slightly different interface to setup the port forwarding, but they all usually involve specyfing the port to forward and the destination machine.

Not sure in what context you mention the real MAC and virtual MAC addresses ? in general, you should not need to be aware of the router's MAC address, so I would say that just put in your XBOX mac address for everything.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/27/2005 12:14 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
awesome!! i actually checked that screen and missed it. once again...thanks a lot!




cool ! I think I need to update the proxy_arp step in the guide , as it seems that the WLAN device on the WRT54G could be any "ethX", and not always "eth1" like it is on my router.

newsflash: I udated step 10 of the guide to choose the correct interface when setting up the proxy_arp. So if anyone else had problems with this (especially people running a different version of the router or the firmware), you can retry step 10.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/27/2005 at 10:08 PM by user1234

Date Posted: 05/27/2005 03:34 PM Posted By: The Goon(Junior Member)

Thanks user1234 but i tried your suggestions but no go. KAI and Xconnect use a system called "tunneling" basically the software is installed onto the pc, then it logs onto the net to find the games servers,you then put a system link game in the xbox go to system link and wait at the looking for games page,KAI and xconnect then see the xbox on the lan then the servers come up on the sytem link page and you join. I don't know if "tunneling" is possible with your setup, it does everything else,but fowarding ports isn't working. I disabled both the s/w and h/w firewalls but it still can't find the xbox.

Can this be done?? seems pretty dificult to me (as most things are lol) but in essence the pc is being used to "piggyback" the connetion to the internet from the xbox.

Thanks once again


Date Posted: 05/27/2005 03:53 PM Posted By: user1234(Platinum Member)

Goon, the XBOX is not visible automatically on the lan from PCs attached to the main router. The only way to connect to the XBOX is by specifically using its IP address (e.g. 192.168.2.140). As for MAC address, from the point of view of the PC attached to the main router, the MAC address of the XBOX is actually the MAC address WRT54G wireless interface (it's not neccessarily the one printed on the bottom of the router, as the router has more than one MAC - one for each interface). To find out the WRT54G's wireless MAC address, type this command on the WRT54G:

ifconfig `route | grep default | awk '{print $NF}'`

The MAC address is shown in the first line.
As for port forwarding, I'm not sure if you intend to forward the port to the PC running the software, or to your XBOX. In any case, this should be simple to set up - you only need to do this on your main router. The proxy arp will take care of the rest. Good luck!!!


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)




Edited: 05/27/2005 at 10:51 PM by user1234

Date Posted: 05/27/2005 10:31 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: pat68
Hi user1234.
Thanks for your advice. I already found the problem, on the WAG54G I had SSID broadcast disabled, enabled again and it works 8-)




great ! btw thanks, I added a note about this to the guide, just in case other people have a problem with this.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/27/2005 11:02 PM Posted By: facemask(Member)

echo 1 > /proc/sys/net/ipv4/conf/`route | grep default | awk '{print $NF}'`/proxy_arp

nice!


Date Posted: 05/28/2005 12:21 AM Posted By: user1234(Platinum Member)

quote:
Originally posted by: facemask
echo 1 > /proc/sys/net/ipv4/conf/`route | grep default | awk '{print $NF}'`/proxy_arp

nice!




thank you sir !

This uses the fact that the wireless interface device can be seen in the routing table as the one used to access the default gateway (which is the main router):

# route

I still think it's usually eth1 (because it worked for most people), except maybe in very recent or new versions of the WRT54G.


-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/28/2005 09:44 AM Posted By: ddmcdoodle(Junior Member)

I looked around, but couldn't get a solid answer for this question: Is it possible to use this on a version 3 of the WRT54G router? If so, would I have to do something special to make it work, or just follow the instructions normally? The thing is, I just bought a WRT54G from Amazon.com, and it could be a version 3 model. If anyone could help me out with this, it would be much appreciated. Thank you.


Date Posted: 05/28/2005 03:06 PM Posted By: user1234(Platinum Member)

quote:
Originally posted by: ddmcdoodle
I looked around, but couldn't get a solid answer for this question: Is it possible to use this on a version 3 of the WRT54G router? If so, would I have to do something special to make it work, or just follow the instructions normally? The thing is, I just bought a WRT54G from Amazon.com, and it could be a version 3 model. If anyone could help me out with this, it would be much appreciated. Thank you.




Did you see this post a couple of pages back ?

quote:
Originally posted by: Tom33
Well to answer my own question.....Talisman Basic 1.0.3.1 Firmware will install on a V3 router. Router works as a router fine after the upgrade. I will head out tomorrow to pick up another router, to move the project further along.






-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/28/2005 04:25 PM Posted By: ddmcdoodle(Junior Member)

Yes, but the main reason I need the router for is to use it as a wireless bridge. Does the Talisman firmware do that?


Date Posted: 05/28/2005 07:09 PM Posted By: user1234(Platinum Member)

I am not completely sure, as my router (also got it from amazon) is V2.2, but I believe you will be able to find at least some version of the sveasoft firmware which supports "client mode" (i.e. bridging) that is compatible with your router.

-------------------------
"Stroking it doesn't make it grow..." (housecat, 2005)



Date Posted: 05/28/2005 09:05 PM Posted By: ddmcdoodle(Junior Member)

quote:
Originally posted by: user1234
I am not completely sure, as my router (also got it from amazon) is V2.2, but I believe you will be able to find at least some version of the sveasoft firmware which supports "client mode" (i.e. bridging) that is compatible with your router.


Are there any free alternatives to the Sveasoft firmware? The Talisman firmware costs $20 to get, and of course I would like to spend the least amount possible on this. Basically all I need is a firmware for the version 3 of the router that supports client mode/bridging. Thanks.


Date Posted: 05/28/2005 10:10 PM Posted By: The Goon(Junior Member)

User1234, thanks again for your prompt reply . I still can't get it to find the xbox in KAI. It tells me the network is reachable but it not detecting the xbox at all. This what i've done, put my main pc on a static ip address, port forwarded the ports for KAI to the pc in virtual servers and application gateways in the belkin. I've been to the KAI forums and they say it can be done as the xbox only need to speak to the pc not the internet, but thats all they will say. I saw this in the forum from one of the develepers of the program

"One thing you need to keep in mind is MAC address cloning - Kai will ignore any device that doesn't start with a certain MAC address, so the bridge is going to need to clone the XBox's MAC"

If you want to look at the program its here www.teamxlink.co.uk

Thanks again, please be patient with me, i'm a middle aged bloke with teenage kids and trying to learn all this new fan dangled stuff lol


Date Posted: 05/30/2005 06:10 PM Posted By: WolverineGator(Senior Member)

I'm currently using OpenWRT, but I now want to try Alchemy. Just as I powered up the router I used tftp to upload the OpenWRT firmware while boot_wait=on, but Alchemy is too big to flash this way. How can I change firmware? I tried flashing to Satori since it is less than 3MB, but I get "can't downgrade to this old firmware version." Am I stuck?

Update1: I flashed to ewrt since it was less than 3MB and then using the web interface I flashed to Alchemy. Anyone who has a dead/bricked router can follow the above directions to revive it.

Update2: Got it to work in client mode just following OP's directions and I'm using version 3 of this router. Thanks!

-------------------------
. . \|/ .____..\|/
~@./..oO..\.@~



Edited: 05/31/2005 at 03:59 PM by WolverineGator

Date Posted: 05/30/2005 11:18 PM Posted By: jeremycobert(Junior Member)

does anyone know if i could setup a cron job to run the proxy command echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp on the client ?

i need to figure a way out to keep the subnets working together. unless i could setup a routing table in the gateway router. im not quite sure how to do that.


Date Posted: 06/01/2005 08:14 AM Posted By: pat68(Junior Member)

Hi user1234.

I still had the 10-20ms ping times issue between WRT54G client and WAG54G v2. Also I had this timings with WiFi client PCs directly connected to the WAG54G v2.
I figured out, that this was definitly a firmware issue. Originally the WAG54G was equipped with 1.00.19. I switched to 1.00.47 (beta version form Linksys) and now I have ping times around 2ms! Hope there will be a final version of the firmware soon.

Bye
pat


Date Posted: 06/01/2005 06:57 PM Posted By: ddmcdoodle(Junior Member)

Alright guys, I got my router today from Amazon.com. I set up the router, connected all cables, reset it just in case, and uploaded this firmware which IS compatible with the new version 3 models of the WRT54G: http://wrt54g.thermoman.de/FreemanBasic_V1.0.4_wrt54g.zip
It is a modified version of the Sveasoft Talisman firmware, which works on v3 routers, and it is absolutely free (compared to the $20 you have to pay to get basically the exact same thing from Sveasoft). I uploaded it, and part of the way through, a error message popped up say that the upload had failed. I thought I had a $60 brick on my hands, but I was determined to make it work again, as I had read it was possible to recover from a failed upgrade. I downloaded the original Linksys firmware, used TFTP to upload it to my router, and lo and behold, it worked! I was able to go to the regular Linksys web-based configuration, and I tried uploading the Freeman firmware again. This time, it worked like a charm. I set everything up according to your guide in the first post, and now I've got my WRT54G running as a wireless bridge for my Windows PC, my Linux box, and my Playstation 2. Thank you user1234, you have changed my life!


Date Posted: 06/07/2005 01:03 PM Posted By: mikelish(Member)

how do I do port forwarding for bitorrent using this setup? i have a dlink router connected to my linksys wrt54g


Date Posted: 06/07/2005 07:07 PM Posted By: fdrgnmx(Junior Member)

Hello user1234,

Your tutorial is great, I got the setup working on two WRT54G routers with Alchemy firmware.

But I have a question.. I want to setup a sightly more complex configuration, something like this:

Main router IP: 10.0.0.1
Mask: 255.255.255.0

Router1 IP: 10.0.1.1
Mask: 255.255.255.0
Clients attached: 10.0.1.10-250

Router2 IP: 10.0.2.1
Mask: 255.255.255.0
Clients attached: 10.0.2.10-250

And so on... How I can get this setup working?

Also, I want that clients on Router2 can see clients on Router1 and the Main router in two ways.. that is difficult to implement?

Thank you very much in advance for any help.

P.S. Sorry for my bad english.


Date Posted: 06/08/2005 11:01 AM Posted By: WolverineGator(Senior Member)

quote:
Originally posted by: ddmcdoodle
Alright guys, I got my router today from Amazon.com. I set up the router, connected all cables, reset it just in case, and uploaded this firmware which IS compatible with the new version 3 models of the WRT54G: http://wrt54g.thermoman.de/FreemanBasic_V1.0.4_wrt54g.zip
It is a modified version of the Sveasoft Talisman firmware, which works on v3 routers, and it is absolutely free (compared to the $20 you have to pay to get basically the exact same thing from Sveasoft). [snip] I set everything up according to your guide in the first post, and now I've got my WRT54G running as a wireless bridge for my Windows PC, my Linux box, and my Playstation 2. Thank you user1234, you have changed my life!




There is no option for Gateway operating mode and there are 2 client modes so I couldn't complete steps 5 and 6:

5. In "Setup::Advanced Routing" screen, make sure operating mode is "Gateway".

6. In "Wireless::Basic Settings" screen, set Wireless mode to "Client".....

How did you get FreemanBasic_V1.0.4_wrt54g.zip to work?

-------------------------
. . \|/ .____..\|/
~@./..oO..\.@~


Date Posted: 06/08/2005 01:12 PM Posted By: skyking(Diamond Member)

quote:
Originally posted by: fdrgnmx
Hello user1234,

Your tutorial is great, I got the setup working on two WRT54G routers with Alchemy firmware.

But I have a question.. I want to setup a sightly more complex configuration, something like this:

Main router IP: 10.0.0.1
Mask: 255.255.255.0

Router1 IP: 10.0.1.1
Mask: 255.255.255.0
Clients attached: 10.0.1.10-250

Router2 IP: 10.0.2.1
Mask: 255.255.255.0
Clients attached: 10.0.2.10-250

And so on... How I can get this setup working?

Also, I want that clients on Router2 can see clients on Router1 and the Main router in two ways.. that is difficult to implement?

Thank you very much in advance for any help.

P.S. Sorry for my bad english.



If you are talking atout (3) WRT54G's then WDS does this for you, all on the same subnet.


-------------------------
Heat



Date Posted: 06/08/2005 05:48 PM Posted By: fdrgnmx(Junior Member)

Yes, I know. The problem is, with WDS I can only connect 10 WRT54G, but I need to connect more than 10 of them


Date Posted: 06/08/2005 06:40 PM Posted By: skyking(Diamond Member)

WooHoo!
sounds like fun

-------------------------
Heat



Date Posted: 06/13/2005 05:50 AM Posted By: ddmcdoodle(Junior Member)

quote:
Originally posted by: WolverineGator

quote:
Originally posted by: ddmcdoodle
Alright guys, I got my router today from Amazon.com. I set up the router, connected all cables, reset it just in case, and uploaded this firmware which IS compatible with the new version 3 models of the WRT54G: http://wrt54g.thermoman.de/FreemanBasic_V1.0.4_wrt54g.zip
It is a modified version of the Sveasoft Talisman firmware, which works on v3 routers, and it is absolutely free (compared to the $20 you have to pay to get basically the exact same thing from Sveasoft). [snip] I set everything up according to your guide in the first post, and now I've got my WRT54G running as a wireless bridge for my Windows PC, my Linux box, and my Playstation 2. Thank you user1234, you have changed my life!




There is no option for Gateway operating mode and there are 2 client modes so I couldn't complete steps 5 and 6:

5. In "Setup::Advanced Routing" screen, make sure operating mode is "Gateway".

6. In "Wireless::Basic Settings" screen, set Wireless mode to "Client".....

How did you get FreemanBasic_V1.0.4_wrt54g.zip to work?


Set the mode to client-routed in the wireless settings page. That is the only thing I did differently, but it works fine.


Date Posted: 06/13/2005 11:43 PM Posted By: cram(Junior Member)

quote:
Originally posted by: ddmcdoodle
Set the mode to client-routed in the wireless settings page. That is the only thing I did differently, but it works fine.



I've also done all you suggested (set wireless mode to client-routed and all the steps that i could from the first post) but it still wont work. The main router assigns me an IP address but I can't ping it or access the internet. Is there something I need to do the main router to get the client to talk to it?? I'm running Free-Man 1.04 on a wrt54g v3....

Also, my laptop connects fine to the main router...i'm very confused.

Thanks in advance for the help.



Edited: 06/14/2005 at 12:14 AM by cram

Date Posted: 06/14/2005 01:54 PM Posted By: xtc1(Junior Member)

Here`s my problem
I need to do this: LAN-WRT 54g (AP)- WRT 54g (client)- Video recording device . (Unimo 204)
Tricky part is how to make recording device accessible in lan? I need that device will be visiable in LAN and that decive could see LAN too.
Would enyone to be so kind to explain me how to do it? I hope that explanation will be very simple to understand. (Step by step) Starting with LAN router IP(192.168.1.1) and will finish to the device IP



Date Posted: 06/16/2005 06:36 AM Posted By: candlebox1369(Junior Member)

i read this entire forum and tried so many time to get this darn bridge to work.

I have a belkin pre-n router and was trying to bridge wrt54gs v2 with talisman 1.0.4
Could not get it working until a few posts back when ddmcdoodle posts:

"Set the mode to client-routed in the wireless settings page. That is the only thing I did differently, but it works fine."

....i had the darn thing on client-bridge...

I reset both and put in all the settings with that minor diference and it works!
this howto kicks ass...thanks everyone

Questions
1) I have a WDS at a different location (two linksys routers). Does anyone know if I can add a bridge to main router and have my WDS at the same time or can I only choose one or the other?
2) For a router that acts as a bridge, mac address must be entered in main router if filters are enabled. But for WDS, I have it working with MAC filters enabled but without each router's MAC in the other router. Is this because it just repeats the signal?

I can post detail steps of how i set up WDS if anybody wants to know...it's just a little late and i go to work soon...



Date Posted: 06/16/2005 06:39 AM Posted By: candlebox1369(Junior Member)

to cram,

when i had the router on client-bridge, it would not get an ip from the main router. when i set it to client-route, it got an ip but i still could not go online. i then reset both and did it over again but right this time and it worked. maybe you can try it again?


Date Posted: 06/19/2005 10:02 PM Posted By: truk(Junior Member)

I followed this "howto" exactly and was 100% sucessful in using my WTR54g v3 x router as a network bridge. The only problem is having to reenter the routing command into my WTR54g after a power loss or glitch. Since it was linux I went ahead and tried Vi and found I could create a file called myroute.sh which lets me add the
echo 1 > /proc/sys/net/ipv4/conf/`route | grep default | awk '{print $NF}'`/proxy_arp command without retyping it each time. I stored it in the /temp dir because it seemed a good place, but I am a linux newbie and am only just starting to laern about Vi and the file structure etc. Now all I have to do is type ./myroute.sh to add the command. My goal is to get this file to be automatically ran when the router is restatred. I am not sure how that is done yet and if someone would like to jump in that would be greatly appreciated.
For my home network I have 3 systems 2WXP and 1 Linux system downstairs using my main wireless router, an 811b Microsoft jobber, that was free after rebates. Upstairs is where my wife's computer , a W2K Pro box, lives along with a Dlink wired print print server that serves the whole house. Both my wife's PC and the print server are "wired" to the wrt54g which gets it's WAN connectivity from the MS router down stairs. Before having this set up I had the linksys router servicing my whole house from the upstairs and needless to say connectivity downstairs was weak with frequent outages. After finding this thread I dug my MS router out of the junk box and gave it a try with excellent results. Connectivity is strong upstairs and downstairs with my only problem being the routing info that lets my wife's downstairs laptop talk with her main PC and printer upstairs. This is bad because my wife is the toughest IT customer I have, and I work in the IT world, and if power glitches while I am away I inevtibly get the call asking why she can't reach her shares on her main PC upstairs. One last thing I had to do to get everything working was to add the hostnames for each computer to the lmhosts file on each system in order to map drives on other computers and so far everything works like a charm.

Thanks for the "how to"!!!!

-------------------------
KG Sends


Date Posted: 06/21/2005 08:44 PM Posted By: mikelish(Member)

i am trying to get SMB (samba) networking to work for my xbox using Xbox Media Center. i had it working when my computer and xbox were both hooked up the wrt54g. now I put my computer on the dlink router. I can FTP into it but I can't get SMB to work anymore. maybe I didn't setup something correctly on my xbox.


Date Posted: 06/23/2005 04:37 AM Posted By: jamesmc(Junior Member)

Hi all,

I hope I’m not repeating anyone here, but couldn't find an answer for this particular case. I know a little bit about networking and IP addresses, but am definitely nowhere close to an expert. Hopefully whoever answers this will also help someone with this particular case as well. Thanks so much in advance!

Configuration:

1) Main Router Upstairs: WRT54GS: Statically 192.168.1.1/255.255.255.0 with Linksys Firmware and connected to a cable modem via the WAN port.
1b) This main router connects to a Windows XP computer upstairs called “\\TYAN” given an IP Address via DHCP (I’d rather it not be static, but if it must be, then it must be) which is a File and Print server.

2) Secondary WRT54G Router Downstairs acting as a Wireless Bridge with Alchemy Firmware, configured step-by-step via user1234’s guide on Page 1 (ps: thanks user1234). This secondary router currently has the IP Address of 192.168.0.129/255.255.255.128. If this address needs to be changed, I am okay with this.
(I have also tried making this router 192.168.1.129/255.255.255.0, but the connected computers would not appear to connect to the Internet.) The secondary router’s DHCP server would give connected computers downstairs IP addresses above 192.168.1.140 per user1234’s directions.

The question is: I would like to give the secondary router’s connected computers access to simply type \\TYAN instead of typing whatever IP address that computer currently has, to access its shared files and printer.

Is this (hopefully) doable? If so, may I ask what steps are needed to do this? Thank you sooo much!!

[ps: ddmcdoodle- to answer your question, I was able to install this successfully on a v.3 router]

James




Edited: 06/23/2005 at 04:57 AM by jamesmc

Date Posted: 06/29/2005 03:54 AM Posted By: kkennedy070790(Junior Member)

turn WRT54G into WET54G:
You need a firmware that has telnet ( I use DD-WRT ).

Starting w/factory defaults..
On the Basic setup page, disable STP
under Router IP, set the local ip to something not on your network (admin IP)
disable the DHCP server
click Wireless setup tab - basic settings
Wireless Mode: AP, Mixed, ssid does not matter (yet), set correct channel,ssid broadcast does not matter either..
click administration tab - Telnet enable
reboot the router..
set your ethernet card to static (temporarily) give it an ip address on the network of the admin IP (see above)
telnet to the admin IP
login as root (admin password)

~ # wl ap 0 (this puts the wireless card out of Access Point mode and into 'Ad-hoc')
~ # wl wet 1 (this puts the wireless card into bridging..)
~ # wl join netWork (join your network.. SSID goes here, if you are using WEP just do wl join by itself for options..)
~ # wl status
SSID: "netWork"
Mode: Managed RSSI: -37 dBm noise: -97 dBm Channel: 7
BSSID: 00:11:95:34:E8:8B Capability: ESS ShortPre ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]


~ #

thats it - now set your local network card back to dhcp, the main routers dhcp server will give you a new address.

I have no idea how to "save" this config, if the WRT54G is rebooted, you will need to telnet in again re-do the above commands...

Kenny




Date Posted: 06/29/2005 07:15 PM Posted By: Hav0k99(Golden Member)

hmmm I'l think about it.

-------------------------
Heatware: Hav0k99
Ebay Feedback: Bargain-Hunter-X
AIM: Ice Dragon Ro
Yahoo: Hav0k2k3
MSN: Hav0k99
Email: hav0k99(at)hotmail(dot)com


Date Posted: 06/29/2005 09:46 PM Posted By: kkennedy070790(Junior Member)

HyperWRT 2.1b1 has a startup button on the administration page, if you put your commands in that window, it saves between reboots!


Date Posted: 06/30/2005 07:11 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: jamesmc
Hi all,

I hope I’m not repeating anyone here, but couldn't find an answer for this particular case. I know a little bit about networking and IP addresses, but am definitely nowhere close to an expert. Hopefully whoever answers this will also help someone with this particular case as well. Thanks so much in advance!

Configuration:

1) Main Router Upstairs: WRT54GS: Statically 192.168.1.1/255.255.255.0 with Linksys Firmware and connected to a cable modem via the WAN port.
1b) This main router connects to a Windows XP computer upstairs called “\\TYAN” given an IP Address via DHCP (I’d rather it not be static, but if it must be, then it must be) which is a File and Print server.

2) Secondary WRT54G Router Downstairs acting as a Wireless Bridge with Alchemy Firmware, configured step-by-step via user1234’s guide on Page 1 (ps: thanks user1234). This secondary router currently has the IP Address of 192.168.0.129/255.255.255.128. If this address needs to be changed, I am okay with this.
(I have also tried making this router 192.168.1.129/255.255.255.0, but the connected computers would not appear to connect to the Internet.) The secondary router’s DHCP server would give connected computers downstairs IP addresses above 192.168.1.140 per user1234’s directions.

The question is: I would like to give the secondary router’s connected computers access to simply type \\TYAN instead of typing whatever IP address that computer currently has, to access its shared files and printer.

Is this (hopefully) doable? If so, may I ask what steps are needed to do this? Thank you sooo much!!

[ps: ddmcdoodle- to answer your question, I was able to install this successfully on a v.3 router]

James



sure, you can just add it to your hosts file (usually c:\windows\system32\drivers\etc\hosts) - add a line that looks like

TYAN 192.168.1.10

The resolver alsways looks at this file before querying the dns server when trying to resolve a domain name.


-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 06/30/2005 07:52 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: fdrgnmx
Hello user1234,

Your tutorial is great, I got the setup working on two WRT54G routers with Alchemy firmware.

But I have a question.. I want to setup a sightly more complex configuration, something like this:

Main router IP: 10.0.0.1
Mask: 255.255.255.0

Router1 IP: 10.0.1.1
Mask: 255.255.255.0
Clients attached: 10.0.1.10-250

Router2 IP: 10.0.2.1
Mask: 255.255.255.0
Clients attached: 10.0.2.10-250

And so on... How I can get this setup working?

Also, I want that clients on Router2 can see clients on Router1 and the Main router in two ways.. that is difficult to implement?

Thank you very much in advance for any help.

P.S. Sorry for my bad english.




Connecting multiple client routers should be possible. For you configuration to work all you need to do is set the subnet mask of the MAIN router to 255.255.240.0 so you can have up to 15 client routers with IPs 10.0.x.1 where x is between 1 and 15. Keep the subnet mask of the clients as 255.255.255.0 as you mentioned. If you want up to 255 clients you can set the subnet of the MAIN router to 255.255.0.0.


-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/01/2005 04:19 AM Posted By: ericzwiep(Junior Member)

great work user1234. it was hard to find instructions on how to set the wrt54g as a bridge like indeed the wet54g.
One thing remaining as question for me is, the wet54g allows you to choose from severall available networks, signal strength included. You do not need to know the settings op IP addresses mac etc from this particular available router as the wet54g shows you this already and adjusts to it. So no hassle and the wet54g does the connection trick for you.

Would this be possible for the wrt54g as well??

Would be great as I bought a wrt54g wanting to do the trick the much more expensive wet54g does!!

thanks,

eric!

NOTE:

I did manage to get connect to a belkin54g router..without knowing the IP or SSID.
could have been a lucky shot but still searching for none secured networks....



Edited: 07/06/2005 at 09:10 AM by ericzwiep

Date Posted: 07/01/2005 06:13 AM Posted By: DidlySquat(Senior Member)

well, you could always change the network your client WRT54G connects to by changing the SSID value that it's trying to connect to. While the wrt54g is not a dedicated bridge like the wet54g, it is MUCH more flexible and versatile, especially with the open source firmware versions available, which theoretically allow you to customize it to do pretty much anything that you want. You could even create your own firmware version by modifying the source (warning: this is WAY beyond what most people would do). So if in the future you'd like to use the wrt54g to serve a different purpose in a different network setup, you will be able to do that. Not so with the WET54g is a bridge only - but of course its advantage is that it is easier to set up because it has only one purpose.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/08/2005 02:52 PM Posted By: smokeyhill(Junior Member)

quote:
Originally posted by: mikelish
i am trying to get SMB (samba) networking to work for my xbox using Xbox Media Center. i had it working when my computer and xbox were both hooked up the wrt54g. now I put my computer on the dlink router. I can FTP into it but I can't get SMB to work anymore. maybe I didn't setup something correctly on my xbox.



I have exactly the same problem. I cannot ftp to the xbox however, and I have typed in instruction 10. With my wireless laptop connected to the main router, I can ping a PC on the other side of the bridge, and also my xbox attached to the main router.

When on the PC on the other side of the bridge, I cannot ping the xbox at all.

On another note, I have set up port forwarding for bittorrent (forward from main router to the bridge router, then from the bridge router to the PC) but my light stays yellow and my downloads are a lot slower then I'd expect. Any other notes?

Awesome guide by the way - very helpful and made my network what it is today! ;o)


Date Posted: 07/09/2005 01:03 AM Posted By: DidlySquat(Senior Member)

smokeyhill - that is strange: you say you can't ping the xbox from a PC connected to the client router ? can you ping other computers connected to the main router from the PC connected to the client router ? can you ping/connect to internet hosts such as www.wisc.edu from that PC ?

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/10/2005 08:08 AM Posted By: smokeyhill(Junior Member)

didly squat - my setup is currently:


Study:
PC --- WRT54G **wireless ether***

Front room:
xbox -----¦
laptop ----¦----WAG54G


Now, all can access the internet.

Ignoring my previous post (I think it was actually flinging some pings wirelessly as I wired it up to the main router instead of wireless and got different results.)

But no PC, laptop, or xbox can ping each other over the bridge. They can ping each other on the same side. I did complete step 10 (pasted it in, I assume you start from the word "echo"?) but it still doesn't work...



Edited: 07/10/2005 at 08:09 AM by smokeyhill

Date Posted: 07/10/2005 11:23 PM Posted By: DidlySquat(Senior Member)

that's totally weird....
I understand that the WAG54G is connected to your cable/DSL line and is the gateway for the WRT54G, right ? can you give the address you're using for each router and the output of the "route" command on the WRT54G (after you telnet into it) ?

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/11/2005 08:15 AM Posted By: smokeyhill(Junior Member)

Okay - config is as follows;

Main Router (WAG54G): ip = 192.168.1.1
xbox: ip = 192.168.1.144
subnet: 255.255.255.0

WRT54G: ip = 192.168.1.129
PC: ip = 192.168.1.140
subnet: 255.255.255.128

When typing in the echo command, there is no output. It just brings up another prompt. Should there be some kind of message confirming the change? If so, this may mean it has not been entered (by me!) correctly. Could you confirm from which point on the lin I need to copy and paste? Is it the WHOLE line, or are some of the first characters (ie #) not needed?

I'll get the "route" output to you when i get home.



Edited: 07/11/2005 at 08:23 AM by smokeyhill

Date Posted: 07/11/2005 11:30 AM Posted By: DidlySquat(Senior Member)

smokeyhill, your mistake is that you xbox (and possibly the laptop) is using an address that ends in a number above 128. All machines connected to the main router need to have addresses below 128 as the guide says after step 3:
"To make sure there is no overlap in the addresses assigned by the two routers, we have to make sure that your main router only assign addresses below 128 to its own clients".

So if you're using DHCP on the main router, you need to change that such that it only assigns addresses in the range 1-127. After you do this and reboot the affected machines, you should be able to ping from the PC connected to the WRT54G to any device connected to the main router. Also hopefully the revese ping will work.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/11/2005 02:37 PM Posted By: smokeyhill(Junior Member)

quote:
Originally posted by: DidlySquat
smokeyhill, your mistake is that you xbox (and possibly the laptop) is using an address that ends in a number above 128. All machines connected to the main router need to have addresses below 128 as the guide says after step 3:
"To make sure there is no overlap in the addresses assigned by the two routers, we have to make sure that your main router only assign addresses below 128 to its own clients".

So if you're using DHCP on the main router, you need to change that such that it only assigns addresses in the range 1-127. After you do this and reboot the affected machines, you should be able to ping from the PC connected to the WRT54G to any device connected to the main router. Also hopefully the revese ping will work.



DidlySquat, come over here for a great big hug... I have tears of joy in my eye!! ;o)

My assumption was that "making sure there was no overlap" merely meant no chance of an ip conflict - not that they must be 128 and below and 129 and up. Wonderful! All working!!

Now - any chance of helping with my bittorrent download speeds? ;o)

Currently, 192.168.1.1 (WAG54G) router is forwarding all BT ports to 192.168.1.129 (WRT54G). 192.168.1.129 is then forwarding all BT ports to 192.168.1.140 (PC which has BT running). But the light stays yellow and downloads are nowhere near as fast as they should be. Any suggestions at all? I tried Port triggering, but didn't make any difference and thought I might just be confusing the issue.


Date Posted: 07/11/2005 02:41 PM Posted By: Thraxen(Golden Member)

Hey all,

I've got Xbox problems using this guide too. I followed the guide almost exactly, the only difference being the IP ranges. My main router (D-Link DGL-4300) assigns IPs up to 192 and the client WRT54G assigns IPs starting at 200. My XBox is the only client on the client router and drawing an IP of 192.168.0.200. Most of the features work great. XBMC (which is my dash) says the XBox is not connected to the internet, but it is. The RSS feeds, weather, internet related python scripts, etc... work just fine. I can also FTP to my XBox just fine. But I can't get the SMB shares to work. That is a major hang-up for me since I rely on the SMB shares to stream media from my PC to my entertainment system via the XBox. This feature works just fine when both my PC and XBox are attached to the same router. I have seen a couple of other people post here with the same issue. So has anyone figured out the SMB shares yet?

[edit] Nevermind, I figured it out just a few minutes after posting. I had my SMB shares set-up in the XBMC XML file using my PC's name... I forgot that I needed to change this to the IP instead (just as the instructions from the OP state). Works fine now.



Edited: 07/11/2005 at 03:00 PM by Thraxen

Date Posted: 07/11/2005 05:17 PM Posted By: DidlySquat(Senior Member)

smokyhill, glad to hear you got that working !!!!

regarding the BT issues, I'm not sure if the slowdown is caused by the client router setup. I've heard of similar BT slowdowns when a personal firewall software (e.g. windows firewall or zone alarm, etc) is used and configured improperly. So I suggest you check the firewall on the BT machine itself. Try turning it off and see if that helps.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/11/2005 05:27 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: Thraxen
Hey all,

I've got Xbox problems using this guide too. I followed the guide almost exactly, the only difference being the IP ranges. My main router (D-Link DGL-4300) assigns IPs up to 192 and the client WRT54G assigns IPs starting at 200. My XBox is the only client on the client router and drawing an IP of 192.168.0.200. Most of the features work great. XBMC (which is my dash) says the XBox is not connected to the internet, but it is. The RSS feeds, weather, internet related python scripts, etc... work just fine. I can also FTP to my XBox just fine. But I can't get the SMB shares to work. That is a major hang-up for me since I rely on the SMB shares to stream media from my PC to my entertainment system via the XBox. This feature works just fine when both my PC and XBox are attached to the same router. I have seen a couple of other people post here with the same issue. So has anyone figured out the SMB shares yet?

[edit] Nevermind, I figured it out just a few minutes after posting. I had my SMB shares set-up in the XBMC XML file using my PC's name... I forgot that I needed to change this to the IP instead (just as the instructions from the OP state). Works fine now.



Great !!! just one comment regarding the IP ranges - the clients attached to the main router NEED to have IP ending in number below 128. So you need to change your main router to assign IP up to 127 (instead of 192). If you read smokyhill's posts just before yours you'll see that devices attached to the main router which have addresses above 128 will cause mucho problemo.......

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/11/2005 06:28 PM Posted By: smokeyhill(Junior Member)

quote:
Originally posted by: DidlySquat
smokyhill, glad to hear you got that working !!!!

regarding the BT issues, I'm not sure if the slowdown is caused by the client router setup. I've heard of similar BT slowdowns when a personal firewall software (e.g. windows firewall or zone alarm, etc) is used and configured improperly. So I suggest you check the firewall on the BT machine itself. Try turning it off and see if that helps.



No firewall software running on the client PC at all currently...

I have a couple of things to try, I'll come back if I'm still stumped, but any ideas in the meantime would be welcome!

Thanks again...


Date Posted: 07/12/2005 04:08 AM Posted By: DidlySquat(Senior Member)

I see.....reading your message again about the double port forwarding I remember that it's not necessary, and in fact it may in fact be causing the slowdown. You should be able to port forward directly from your main router to the IP of your BT machine (which is connected to the client router). The proxy arp setting is what enables that, and hopefully that will perform better then the double forwarding.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/12/2005 10:38 PM Posted By: wirelessjoe(Junior Member)

Thanks for Opening my eys, user1234 your original method work well, but I had some problem with connection to some host in my network

so

I install DD-WRT pre5 firmware on both of my Linksys WRT54G-v3 routers
1-wrt configure as normal AP local_sub_net-192.168.1.0/24
2-wrt configure as client local_sub_net 192.168.2.0/24

what I did to my client wrt is remove WLAN(eth1) from the bridge - under vlan configuration

then configure both routers WPA-PSK
reboot both wrts

everything works, no need to do any proxy_arp stuff

Note: what happend is client's wrt is getting ip address of 192.168.1.0/24 via dhcp server cool ! so this is not a True Client Bridge, but it is a True-Client-Routing-Bridge and that is what I like about this, Now I can attach as many routers and client pcs behind the Client-WRT with out any proxy_arp or mac_nat

:-hope my notes will help someone out there

Thanks

WJ



Edited: 07/12/2005 at 10:46 PM by wirelessjoe

Date Posted: 07/13/2005 11:23 AM Posted By: smokeyhill(Junior Member)

DidlySquat, you've done it again.

Straight away my downloads jumped from 20k to around 180k.

Ta v muchly!!


Date Posted: 07/13/2005 01:29 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: wirelessjoe
Thanks for Opening my eys, user1234 your original method work well, but I had some problem with connection to some host in my network

so

I install DD-WRT pre5 firmware on both of my Linksys WRT54G-v3 routers
1-wrt configure as normal AP local_sub_net-192.168.1.0/24
2-wrt configure as client local_sub_net 192.168.2.0/24

what I did to my client wrt is remove WLAN(eth1) from the bridge - under vlan configuration

then configure both routers WPA-PSK
reboot both wrts

everything works, no need to do any proxy_arp stuff

Note: what happend is client's wrt is getting ip address of 192.168.1.0/24 via dhcp server cool ! so this is not a True Client Bridge, but it is a True-Client-Routing-Bridge and that is what I like about this, Now I can attach as many routers and client pcs behind the Client-WRT with out any proxy_arp or mac_nat

:-hope my notes will help someone out there

Thanks

WJ




ummm.....yeah, great but it's just that not everyone has two WRT54G routers. Most people already have some kind of wireless router, and this guide let's them connect devices, that have no wifi capability and are too far from the main router to be attached with a cable, to their network by adding a WRT54G as a client router. There is no need to change any of the settings on the main router, let alone replace it with another WRT54G. btw, if you have two or more WRT54G you can opt for WDS mode operation where wireless clients can roam between them and automatically connect to the strongest signal.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU




Edited: 07/13/2005 at 02:27 PM by DidlySquat

Date Posted: 07/20/2005 07:23 PM Posted By: majmera(Member)

Hi Guys,

I have a question:
My apt community provides wireless internet. I have desktop that is not wireless capable (so I probably need a bridge). I also need a NAT capable router to be able to connect to my company's VPN.
Can I use a WRT54G with the modded firmware to perform the bridge function and connect to my VPN without having to buy another router?

thanks
Mayank


-------------------------
MSI K8N Neo2 Platinum
AMD64 3000+
Seagate Barracuda 7200, 200GB
WD 7200, 100GB
Corsair Value Select (2x512MB)
Nec 3520A
Antec Sonata with stock PSU
WinXP Pro SP2.


Date Posted: 07/20/2005 08:58 PM Posted By: DidlySquat(Senior Member)

The short answer is YES !

The long answer is YOU BET !

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/26/2005 12:56 AM Posted By: xboxtrauma(Junior Member)

my stuff.

AP router: Netgear
client router: WRT54 GS v2.0
Either firmware: Freeman 1.04, WRT 22 Final



quote:
Originally posted by: Nutdotnet
My question is, and after reading this thread seems possible, but how exactly does one go about allowing PC1 and PC2 to speak to each other?

I have a modded Xbox that I am able to FTP into. The problem is, and why I'm currently not using the 54g in client mode, is that the DI-624 sees the WRT54g (192.168.0.112) but does not have a specific IP for the Xbox,



If you're using the Avalaunch dash on XBox with DHCP enabled you should see the IP address of your XBox in the lower left.

Currently I'm able to FTP into the xbox from a PC wirelessly connected to the AP, though I'm using my 54GS v2.0 in client mode per these instructions:

http://forum.bsr-clan.de/ftopic694.html


However this requires that your AP be able to create static routes.



-------------------------
ProtestWarrior.com -- doing it right



Edited: 07/26/2005 at 01:10 AM by xboxtrauma

Date Posted: 07/26/2005 04:11 PM Posted By: DidlySquat(Senior Member)

the instructions you linked above are almost the same as the initial version of the instructions in this thread, before the proxy_arp setup was added. The proxy_arp setting makes it a lot eaiser to allow communication between devices attached to either router. The method described in the linked thread to set up static routes is a lot less flexible and cumbersome.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 07/29/2005 06:52 PM Posted By: kkennedy070790(Junior Member)

quote:
Originally posted by: DidlySquat
the instructions you linked above are almost the same as the initial version of the instructions in this thread, before the proxy_arp setup was added. The proxy_arp setting makes it a lot eaiser to allow communication between devices attached to either router. The method described in the linked thread to set up static routes is a lot less flexible and cumbersome.




There is an easier and less confusing way:
follow these instructions on older DD-WRT, Sveasoft,Freeman firmware:

http://forum.bsr-clan.de/viewtopic.php?t=1750&highlight=bridge

Or, if you are willing to try-out Alpha software, try DD-WRT v23-Alpha:

http://www.dd-wrt.com/dd-wrtv2/sneaks/dd-wrt.v23-alpha.zip

These are true layer-2 bridging - not a "pseudo-bridge" - no routing table adjustments or proxy arp needed. Works with any type of main AP. My AP is a DLink 524.

Kenny



Edited: 07/29/2005 at 06:54 PM by kkennedy070790

Date Posted: 08/05/2005 01:08 AM Posted By: tjwenger(Senior Member)

quote:
Originally posted by: kkennedy070790
turn WRT54G into WET54G:
You need a firmware that has telnet ( I use DD-WRT ).

Starting w/factory defaults..
On the Basic setup page, disable STP
under Router IP, set the local ip to something not on your network (admin IP)
disable the DHCP server
click Wireless setup tab - basic settings
Wireless Mode: AP, Mixed, ssid does not matter (yet), set correct channel,ssid broadcast does not matter either..
click administration tab - Telnet enable
reboot the router..
set your ethernet card to static (temporarily) give it an ip address on the network of the admin IP (see above)
telnet to the admin IP
login as root (admin password)

~ # wl ap 0 (this puts the wireless card out of Access Point mode and into 'Ad-hoc')
~ # wl wet 1 (this puts the wireless card into bridging..)
~ # wl join netWork (join your network.. SSID goes here, if you are using WEP just do wl join by itself for options..)
~ # wl status
SSID: "netWork"
Mode: Managed RSSI: -37 dBm noise: -97 dBm Channel: 7
BSSID: 00:11:95:34:E8:8B Capability: ESS ShortPre ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]


~ #

thats it - now set your local network card back to dhcp, the main routers dhcp server will give you a new address.

I have no idea how to "save" this config, if the WRT54G is rebooted, you will need to telnet in again re-do the above commands...

Kenny





This worked phenominally on Freeman. Anyway we can somehow figure out to Save Telnet settings?

-------------------------
Seems to me I need some identity, seems to me I've become the oddity...When all your wishes are granted, many of your dreams will be destroyed...I wouldn't be ugly if you couldn't see me, I wouldnt regret you if you wouldn't hate me...Lets just cut our wrists like cheap coupons and say that death is on sale today. Because I'm not a slave to a god that doesn't exist and I'm not a slave to a world that doesnt give a shit


Date Posted: 08/05/2005 02:35 AM Posted By: kkennedy070790(Junior Member)

on DD-WRT you can save it to nvram like this

~ # nvram set rc_startup="wl ap 0;wl wet 1;wl join <SSID> <mykey>"
~ # nvram commit

I don't know of a way to save it in Freeman (I don't use it)

The alpha version of DD-WRT has it as a selectable option - see my post above for a link to it.

Kenny


Date Posted: 08/05/2005 03:15 AM Posted By: tjwenger(Senior Member)

nvram worked. Thanks KKennedy. You have no idea how cool this is for me! heh.

-------------------------
Seems to me I need some identity, seems to me I've become the oddity...When all your wishes are granted, many of your dreams will be destroyed...I wouldn't be ugly if you couldn't see me, I wouldnt regret you if you wouldn't hate me...Lets just cut our wrists like cheap coupons and say that death is on sale today. Because I'm not a slave to a god that doesn't exist and I'm not a slave to a world that doesnt give a shit


Date Posted: 08/09/2005 04:18 PM Posted By: MeatPoPsiclez(Junior Member)

Have you tried to see if any firewalling will work on the client wrt54g when in transparent mode?

I have a special application where I need the benefits of a subnet, without any of the traversal problems. Like others here I have xbox's on both ends that I want to use system link on. However, unlike others I do not want to share internet with the other side, and I don't much like the idea of having to enter all my ip and gateway info in statically on one side of the network. My solution is to insert a firewall blocking port 67 and 68 (dhcp/bootp) between the bridge and network b. I can then have a dhcp server on each side, as long as they don't pass out the same addresses, with 0 traversal problems. I'd really like to have the dhcp filtering on the bridge wrt54g itself. Can anybody try this out and see if my 'theory' works?

If somebody can give me a heads up on inserting firewall rules into iptables on dd-wrt I'll experiment myself.


Date Posted: 08/09/2005 04:56 PM Posted By: mikelish(Member)

I am now using this setup and it's working great. I live on a college campus and so lots of people around my have wireless and I would like to block them out of my main router's but still keep my network up and allow all computers I want to be connected to work.

My main router is a Dlink 614+. Can I set passwords?



Date Posted: 08/10/2005 02:14 PM Posted By: DidlySquat(Senior Member)

MeatPoPsiclez: the setup described in the initial guide does use separate DHCP servers - one in the main router and one in the client - with different address ranges.

mikelish: You can easily set up WEP - just use the same settings on the main and client. I use 64-bit WEP key in open system authentication mode, but others have used 128-bit and shared key mode.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 08/10/2005 04:17 PM Posted By: MeatPoPsiclez(Junior Member)

quote:
Originally posted by: DidlySquat
MeatPoPsiclez: the setup described in the initial guide does use separate DHCP servers - one in the main router and one in the client - with different address ranges.



Yes, but that has two subnets, and along with that comes traversal problems. Even with proxy_arp I don't believe Xbox system link data can migrate over the networks. More thorough testing is needed on my part, but my initial assesment says no.


Date Posted: 08/12/2005 04:55 PM Posted By: Silex(Senior Member)

I have almost the same routers as you so when I do try it out, I'm sure it will work without a hitch. The only thing I was wondering, and something I couldn't find addressed, was if the client WRT54G can still be used to "extend" the wireless network by also being wireless (does that make sense?). I couldn't find that addressed in the main post so I wasn't sure. If the answer is no, can I hook up another AP, I have an Orinoco RG-1100 as well, and use that somehow to extend the network?

It would sure be a conversation piece (the client setup will be in the living room) when one sees a wireless router with a wireless gateway attached to it. I'll do what I have to though to ensure that this setup will work. Thanks for any help.

-------------------------
Warning: The following possibly contains material not yet suitable for children |Fighters-Xtreme|



Edited: 08/12/2005 at 04:55 PM by Silex

Date Posted: 08/12/2005 09:14 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: Silex
I have almost the same routers as you so when I do try it out, I'm sure it will work without a hitch. The only thing I was wondering, and something I couldn't find addressed, was if the client WRT54G can still be used to "extend" the wireless network by also being wireless (does that make sense?). I couldn't find that addressed in the main post so I wasn't sure. If the answer is no, can I hook up another AP, I have an Orinoco RG-1100 as well, and use that somehow to extend the network?

It would sure be a conversation piece (the client setup will be in the living room) when one sees a wireless router with a wireless gateway attached to it. I'll do what I have to though to ensure that this setup will work. Thanks for any help.




No, the client WRT54G cannot have wireless devices connect to it. But I believe you could connect another wireless AP to it which clients can connect to. But there will not be seemless roaming between this AP and your main wireless router. That is, a wireless client will have to select which AP to connect to.

If you want seemless roaming you need to set up WDS mode connection between two identical wireless routers which support WDS, such as two WRT54G.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU




Edited: 08/12/2005 at 09:16 PM by DidlySquat

Date Posted: 08/25/2005 04:49 PM Posted By: GrassR00t(Senior Member)

N/M I figured it out.

Great post OP

-------------------------
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge." -- Stephen Hawking
Heat under GrassR00t



Edited: 08/26/2005 at 12:34 AM by GrassR00t

Date Posted: 08/28/2005 03:31 PM Posted By: gedikart01(Junior Member)

ello! Help me Please!

I've got two WRT54G ap-router. I want to use Client mode, but it doesn't work.

Main router (Linksys 3.03.9 firmware)
******************************
Local IP = 192.168.1.1
Subnet Mask = 255.255.255.0
DHCP server: Disable

Advenced routing:
Operated mode = Geteway
Destination LAN IP = 0.0.0.0, Subnet mask = 0.0.0.0, Default gw: 0.0.0.0, Interface = Lan & Wireless
Wireless security: Disable

Client router (Sveasoft Alchemy 1.0)
******************************
Internet Connection Type = Static IP
Internet IP Address = 192.168.1.2
Geteway = 192.168.1.1
Static DNS1 = 192.168.1.1

Local IP = 192.168.2.2
Subnet mask = 255.255.255.0
Geteway = 192.168.2.2
Local DNS = 192.168.1.1
DHCP Server = Enable

Wireless mode = Client.
SSID, Channel = (same as the main router)
Firewall: Disable
Wireless security: Disable

In administration: All settings are default. (I don't know what have to set).

I tired these settings, but I couldn't ping the main router from the client router. (My client router's WAN port isn't good: it was killed by the lightning). BUT if I use a Freeman-talisman 1.0.2 fw on it, and it's in Client-Bridged mode, I can ping the main router. But with this freeman-talisman I can connect only one PC to the client router (If I connect 2 PC the Internet stop.)

So, What I set in alchemy, it doesn't work, and the freeman is only works with one PC.


Please help me! (I try to client mode since 2 weeks)


Date Posted: 08/29/2005 05:52 AM Posted By: DidlySquat(Senior Member)

Did you follow the instructions in the first post ? obviously not, because your IP addresses are NOT what is explained in the guide. For starters, you have to set the client router to 192.168.1.129 , not 192.168.2.2. If you want to make client mode in with the alchemy firmware, just follow the instructions.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 08/30/2005 11:29 AM Posted By: padmewan(Junior Member)

Hi all, thanks for this excellent guide and discussion.

After reading (but not necessarily understanding) most of this thread, I still have some questions I'm hoping someone will be able to answer:

Situation: My landlord, one floor above, has a Netgear 802.11g router, and we were interested in connecting to that router (with his permission) and saving ourselves $70/month in phone+DSL charges.

1. Will the WRT54G work in "Client Mode" not just with WEP but with WPA-PSK?

2. I plan on wiring at least two PCs to the WRT54G. Will peer-to-peer data sharing (via my Windows workgroup) between my two PCs go directly through the WRT54G, or will it have to go all the way back to my landlord's Netgear router?

3. Will a computer connected to my landlord's Netgear router be able to see/access computers connected to my WRT54G router? Since we are 2 separate households I would prefer to have two, distinct networks in terms of my Windows workgroup, and the less access others have to my workgroup, the better.

4. Assuming the answer to 3 is "no" (that is, my landlord cannot access my Windows workgroup), can a laptop in my apartment connect to the Windows workgroup via the WRT54G operating in client mode, or does it have to connect to the landlord's Netgear router? Put another way, can I connect to a WRT54G running in client mode?

5. Finally, any thoughts on Sveasoft in terms of support, etc.? Do I want "Alchemy" or this newfangled "Talisman" product? Is there a definitive list of which firmware versions work with which hardware versions?

I have not yet bought the WRT54G in anticipation of getting these answers before making the plunge. Thanks in advance for your help!


Date Posted: 08/30/2005 12:19 PM Posted By: DidlySquat(Senior Member)

1. No, only WEP encription seems to work in client mode
2. Not completely sure, but I don't think packets exchanged between two wired clients are transmitted.
3. Yes, the landlord's netgear router and other devices attached to it can see you WRT54G and its subnet, but only if you set up the proxy_arp in step 10. If you skip that, they will not be able to access your sub-network. But even otherwise, you can easily block them from accessing your workgroup and PCs.
4. No, WRT54G in client mode can't operate as a wireless access point. Your wireless device(s) need to connect directly to the landlord's router. Another option is to connect another wireless AP to the WRT54G, so your wireless devices can connect to it.
5. Don't know, once you set it up it should just work.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU




Edited: 08/30/2005 at 12:22 PM by DidlySquat

Date Posted: 08/30/2005 04:08 PM Posted By: padmewan(Junior Member)

Thanks, Didly - I'm afraid your answer to #1 scuttles the project I'm not going to ask my landlord to compromise network security so we can use his network. So, I guess I will get individual PCI cards for our desktops.


Date Posted: 08/31/2005 03:23 PM Posted By: atrophic(Junior Member)

I still need to play around a bit more I think, but I got stuck last night trying to follow this guide and thought somebody might help me head in the right direction when I try again tonight. Here's the current set up:

Internet<--->Cable Modem<--->US Robitics Router (USR8054)<--->PC1
Two other PCs connected to this router via Wireless cards
WRT54G<--->two PCs

The two computers connected to the wrt54g are in the basement and can't get the signal from the USR router, though a laptop can. The WRT54G also can. I've followed the steps in the guide and the wrt receives an IP from the USR, and also assigns IPs to the two computers connected to it. However, neither of those computers can access the internet, and the WRT can't ping anything either.

It's probably something quite simple and I just don't know enough about networking to find it. The USR's ip is 192.168.123.254 (default ip) and its subnet is 255.255.255.0. The wrt is 192.168.123.129 with 255.255.255.128 subnet. I've configured the dhcp settings so they don't overlap assignable ips. Am I missing something simple or is there something more complicated going on?



Date Posted: 09/01/2005 03:31 AM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: atrophic
I still need to play around a bit more I think, but I got stuck last night trying to follow this guide and thought somebody might help me head in the right direction when I try again tonight. Here's the current set up:

Internet<--->Cable Modem<--->US Robitics Router (USR8054)<--->PC1
Two other PCs connected to this router via Wireless cards
WRT54G<--->two PCs

The two computers connected to the wrt54g are in the basement and can't get the signal from the USR router, though a laptop can. The WRT54G also can. I've followed the steps in the guide and the wrt receives an IP from the USR, and also assigns IPs to the two computers connected to it. However, neither of those computers can access the internet, and the WRT can't ping anything either.

It's probably something quite simple and I just don't know enough about networking to find it. The USR's ip is 192.168.123.254 (default ip) and its subnet is 255.255.255.0. The wrt is 192.168.123.129 with 255.255.255.128 subnet. I've configured the dhcp settings so they don't overlap assignable ips. Am I missing something simple or is there something more complicated going on?



Yes, you have to change IP of the main router (USRobotics) and its attached devices to end with numbers between 1 and 127. For example, change your USR IP to 192.168.123.1 and make sure it assigns DHCP addresses in the range below 127. So the address it assigns to the WRT54G ishould also be below 127 (note that the local IP address of the WRT54G is still 192.168.123.129).

Your problem is a result of overlapping ranges which confuses the routing logic.


-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU




Edited: 09/01/2005 at 03:34 AM by DidlySquat

Date Posted: 09/01/2005 11:24 AM Posted By: atrophic(Junior Member)

I thought that might be the case, but didn't get around to trying it yet. Switching the routers worked, apparently the wrt has a stronger signal than the USR router. I might try to play with it tonight though and see if putting them on different ip ranges helps. What I don't understand is why it would cause a problem configured as it was before so long as I made sure the IPs assigned by the routers didn't fall within the same range. I'm sure it makes perfect sense to somebody who knows what they're doing though Anybody care to explain it?



Edited: 09/01/2005 at 11:28 AM by atrophic

Date Posted: 09/01/2005 12:01 PM Posted By: DidlySquat(Senior Member)

The reason, if you want the technical explanation, is that the WRT54G in client mode acts as a router for its attached devices and decides which packets need to be forwarded to its gateway, and which ones are local. The way the guide sets it up, all local addresses end in a number above 128 - for example 192.168.123.140 is a local address and will not be forwareded, but 192.168.123.100 (and any address which doesn't start with 192.168.123) will be forwared to the gateway . But in your case the gateway address itself is above 128 so it never really gets forwarded corretly. Bottom line the routing rules in your WRT54G are inconsistent.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 09/02/2005 12:30 PM Posted By: Torro(Member)

Thanks for this guide. I was looking for something like this and I actually found it 5 minutes after I emailed Linksys about the possibility (they said it could not be done btw )
My question:
Everything works fine, I get a signal on the 2nd router and it assigns IP addresses to my PC and XBOX. However, every couple of hours (I think ~3) the connection on my PC dies. It says that it is connected but I am unable to do anything with it (surf the web, ping IPs, messenger clients etc) However, I am still able to play XBOX Live. So I know the connection is still there, my PC just doesn't honor it. I usually end up doing ipconfig /renew or even ipconfig /release then ipconfig /renew. Is there some setting that I've inadvertantly turned on or is there something I can set so that it always refreshes its own connection?
PS the router status says that the IP expires in 24 hours. The network connection status tab also says the lease expires in 24 hrs.

Thanks again for this great post


Date Posted: 09/05/2005 11:02 PM Posted By: Silex(Senior Member)

quote:
Originally posted by: DidlySquat

quote:
Originally posted by: Silex
I have almost the same routers as you so when I do try it out, I'm sure it will work without a hitch. The only thing I was wondering, and something I couldn't find addressed, was if the client WRT54G can still be used to "extend" the wireless network by also being wireless (does that make sense?). I couldn't find that addressed in the main post so I wasn't sure. If the answer is no, can I hook up another AP, I have an Orinoco RG-1100 as well, and use that somehow to extend the network?

It would sure be a conversation piece (the client setup will be in the living room) when one sees a wireless router with a wireless gateway attached to it. I'll do what I have to though to ensure that this setup will work. Thanks for any help.




No, the client WRT54G cannot have wireless devices connect to it. But I believe you could connect another wireless AP to it which clients can connect to. But there will not be seemless roaming between this AP and your main wireless router. That is, a wireless client will have to select which AP to connect to.

If you want seemless roaming you need to set up WDS mode connection between two identical wireless routers which support WDS, such as two WRT54G.


Makes sense. Since seemless integration is pretty important, I guess that I will try my Homeplug setup again first (always been a pita to setup) and if I truely can't get that working, I'll probably set this type of network up.


-------------------------
Warning: The following possibly contains material not yet suitable for children |Fighters-Xtreme|


Date Posted: 09/07/2005 06:41 PM Posted By: usrlocalfox(Junior Member)

I got this setup to work except for accessing computers on the client router. I was hoping I could use the Port Forward feature so I can reach a webserver port on the computer I have setup on the client WRT54G.. No Dice. I tried understanding how your Echo command worked to see if I could modify my own for the one WebServer port with no luck. Here is what I got.


Primary Network (sub 255.255.255.0) <WRT54G linksys Firmware 192.168.1.2 WAN connected to cable modem> ---------(Lan Connection)-----<dlink router 192.168.1.3> (Wireless) ***

* * *

**(Wirelessconnection to dlink)** <WRT54G Firmware Alchemy-V1.0 v3.37.6.8sv> Wan Side IP 192.168.1.69 Lan Side 192.168.0.199 subnet 255.255.255.128
+---- (Wired connection port 1)--- <Axis Web Camera ip 192.168.0.200 sub 255.255.255.128 running Webserver on port 8000>

On the 255.255.255.128 network I can access the internet and PCs on the 255.255.255.0 wired network.. I just cannot setup any computer on the Primary Network to access the webserver. I configured the Alchemy to forward port 8000 to 192.168.0.200 ip and tried connect to 192.168.1.69 (The WRT54G ip on the Primary Network Side) no dice.. I can use that IP address to connect to telnet and remote management but nothing is fowarded to the axis camera.

Any ideas?

-------------------------
/usr/local/fox



Edited: 09/07/2005 at 06:48 PM by usrlocalfox

Date Posted: 09/07/2005 06:48 PM Posted By: usrlocalfox(Junior Member)

BTW, I know it's not EXACTLY like the how too.. I been hacking different ideas all day to try and get this to work..


-------------------------
/usr/local/fox


Date Posted: 09/09/2005 12:00 PM Posted By: kkennedy070790(Junior Member)

quote:
Originally posted by: usrlocalfox
BTW, I know it's not EXACTLY like the how too.. I been hacking different ideas all day to try and get this to work..




You really need a true wireless bridge, see my instructions earlier in this thread..


Date Posted: 09/09/2005 04:22 PM Posted By: 51mmz0rz(Junior Member)

How about this one....I have 2 xbox's and I want to play system link between the two. The crossover cable works, but is invasive. Here is my current setup:

--------------------------------------------------------------------------------------------------------
||Campus Jack||====Internet===|WRT54G #1 (Main)| > > > Wireless > > >
.............................................................. ||............||
.........................................................|Xbox #1| |PC #1|

< < < Recieving Wireless < < < |WRT54G #2 (Client)|====|Xbox #2|
..............................................................||
.........................................................|PC #2|
--------------------------------------------------------------------------------------------------------

WRT54G #1 is running stock firmware. I tried to flash it with Alchemy, but it failed. It became corrupted, and I had to tftp with precise timing to get it back to normal. I don't want to mess with it if it don't have to, as it's not even mine...

WRT54G #2 has Alchemy 1.0 installed, and is working in client mode fine. I can acess the internet from PC #2 which is hard wired into WRT54G #2. I can also FTP (and ping) xbox #2 from PC #1. Xbox #1 gets a DHCP IP from WRT54#1 (under 128), and Xbox #2 gets DHCP IP from WRT54G #2 (over 130). All IPs are 192.168.0.XXX.

The problem is the two xboxs are not communicating with each other. I believe it has something to do with the fact that you can't browse the network across routers, and I was wondering if there was a solution to this.

Is there another firmware that supports WDS? The alchemy install fails on WRT54G #1, but another firmware might work. I think WDS might be the only solution.



Edited: 09/09/2005 at 04:23 PM by 51mmz0rz

Date Posted: 09/09/2005 10:25 PM Posted By: kkennedy070790(Junior Member)

quote:
Originally posted by: 51mmz0rz
How about this one....I have 2 xbox's and I want to play system link between the two. The crossover cable works, but is invasive. Here is my current setup:

--------------------------------------------------------------------------------------------------------
||Campus Jack||====Internet===|WRT54G #1 (Main)| > > > Wireless > > >
.............................................................. ||............||
.........................................................|Xbox #1| |PC #1|

< < < Recieving Wireless < < < |WRT54G #2 (Client)|====|Xbox #2|
..............................................................||
.........................................................|PC #2|
--------------------------------------------------------------------------------------------------------

WRT54G #1 is running stock firmware. I tried to flash it with Alchemy, but it failed. It became corrupted, and I had to tftp with precise timing to get it back to normal. I don't want to mess with it if it don't have to, as it's not even mine...

WRT54G #2 has Alchemy 1.0 installed, and is working in client mode fine. I can acess the internet from PC #2 which is hard wired into WRT54G #2. I can also FTP (and ping) xbox #2 from PC #1. Xbox #1 gets a DHCP IP from WRT54#1 (under 128), and Xbox #2 gets DHCP IP from WRT54G #2 (over 130). All IPs are 192.168.0.XXX.

The problem is the two xboxs are not communicating with each other. I believe it has something to do with the fact that you can't browse the network across routers, and I was wondering if there was a solution to this.

Is there another firmware that supports WDS? The alchemy install fails on WRT54G #1, but another firmware might work. I think WDS might be the only solution.




WDS will work, and so will true bridging - see my post earlier in this thread! You only need one WRT to run in bridge mode - since you already have alchemy on #2 - just run #2 as a bridge.


Date Posted: 09/10/2005 03:37 PM Posted By: 51mmz0rz(Junior Member)

Thanks, that worked nicely, however, there is still a problem. I cannot ping xbox #2 or WRT54G#2 from PC #1. I have gotten a response once or twice, but the response is >100ms. Would echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp help in this case? I have disabled loopback and it is still this slow. Being on the same network, shouldn't I be able to ping across the routers at reasonable speeds?


Date Posted: 09/10/2005 10:15 PM Posted By: clarkkent333(Senior Member)

Does this guide work for the new DD-WRT firmware as well?

-------------------------
HEATWARE


Date Posted: 09/11/2005 07:33 PM Posted By: cashel(Junior Member)

I followed this guide using a DI-624 as my main router and a WRT54G as my secondary router. Everything works fine except for one thing. While I can surf the web fine through the second router, I can't access my server on the second router through protocols such as telnet or SSH. What I noticed was that the external IP's for computers hooked up to the secondary router are the same, and that when I enter in the address for my server (I have an account on DynDNS), it displays the external IP in the title bar, but nothing appears on the main screen and the connection times out. Any idea on what's going on here? The server is running Ubuntu Linux and is physically connected to the WRT54G.

-------------------------
My Gaming/MP3 Rig


Date Posted: 09/14/2005 04:49 PM Posted By: vanillatoast(Junior Member)

I've read this thread about as well as I expect to be able to. I'm really close to having this working but it doesn't - the client router recieves an IP but can't communicate with the main router. I'm pretty sure I understand why, too.

My problem is that I am setting this up in an apartment that I haven't even moved into yet. The main router is in my landlord's section of the house--it's his internet connection and his router. I can http it but don't have a password for making changes.

Now. I think the problem is that there is IP address overlap:
1. I have no idea what the main router's DHCP address range is. There are only 2 or 3 other computers on the wireless network. One was given 192.168.1.10, mine was given .100, another was given something else ... the point is that I don't see any discernable pattern. I have no reason to believe that it will stop at 127 like we want, but I haven't seen it assign any addresses above 127 yet.
2. The IP address for the main router is 192.168.1.254. I'm sure this is what's causing the problem, it's just that i can't do anything about it.

Am I just SOL? I'm hesitant to ask my landlord for access to his router, since I've only talked to him 2 or 3 times. He is not technically literate and won't understand why I should have to access his router, at least in technical terms. Because of that, I'm pretty sure that if I ask him, he will either a) not want to give me the password, or b) not even know what the password is. And in the event that I get access to the router, I'm not even sure if it is advanced enough to customize those settings.

My last resort would probably be to buy him a new router. But is there anything else I can do, strictly with my WRT54G? And if I do get access to the router, is this what I should change the settings to:

subnet mask: 255.255.255.0
router ip: 192.168.1.1
dhcp range: 192.168.1.2 - 127
?


Date Posted: 09/15/2005 11:06 PM Posted By: designgirl(Senior Member)

just so people know or maybe it's just me.

I tried using the final release version of the firmware and could not get this to work.

make sure to USE the Alchemy_6rc5. I did that and magically it works. (following the instructions posted by OP of course).

great stuff.




Date Posted: 09/17/2005 09:52 AM Posted By: ba990300(Junior Member)

Hi,
first of all I would like to thank you for the manual. Now everything works just fine.

The only thing I just cannot get to work is FTP.
Internet Explorer tells me that it cannot find the DNS or the Server. When I use a ftp-client, the client tells me that the Server closed the connection.

Do I have to forward/open any Ports in my Linksys Router or any Ports in my Netgear MR814V2, which is connected to the DSL-Modem.

Thank you very much for any help.

ba990300

Nevermind, it was the XP Firewall!!



Edited: 09/22/2005 at 02:38 PM by ba990300

Date Posted: 09/22/2005 02:31 PM Posted By: CrazySmurfs(Junior Member)

Thanx user1234. Your steps worked great! Well, all except for the last one, but I'm very happy nonetheless.

-------------------------
Gargamel? Where!?


Date Posted: 09/23/2005 07:29 AM Posted By: ucenec(Junior Member)

Hello!

I have two of questions for user1234 or other users who know my situation.

1.question

I connected mine 2 WRT54gs and work perfectly. But I have another WRT54gs and I would like to connect to the client router (WRT54gs)

My situation:

Internet ------- Main router (WRT54gs)---------1st Client Router (WRT54gs)------------2nd Client Router (WRT54gs)

Second router must use the first client router because it is to away from the main router.
How can I solve this problem?

2.question

How to share files.....because I don`t see a files of client computer?


Thank`s to answer....... sorry for my not fluent english . I`m from Slovenia...








-------------------------
Nevio



Edited: 09/23/2005 at 07:50 AM by ucenec

Date Posted: 09/23/2005 07:31 AM Posted By: ucenec(Junior Member)

Hello!

I have two of questions for user1234 or other users who know my situation.

1.question
I connected mine 2 WRT54gs and works perfectly. But I have another WRT54gs and I would like to connect to the client router (WRT54gs)

My situation:

Internet ------- Main router (WRT54gs)---------Client Router (WRT54gs)------------2nd Client Router (WRT54gs)

Second router must use the first client router because it is to away from main router.
How can I solve this problem?

2.question

How to share files.....because I don`t see a files of client computer?


Thank`s to answer....... sorry for my not fluent english . I`m from Slovenia...








-------------------------
Nevio


Date Posted: 09/23/2005 09:43 AM Posted By: ucenec(Junior Member)

Hello!

I have problem to login via telnet because I don`t have login name (username), and you can not leave login field empty in telnet.

One topic describe how to connect via telnet. It said that you can login the same way as the web interface. But when you login to the web interface you don`t use any username....where can I find this username?


Thanks..... sory for my not very fluent english !



-------------------------
Nevio


Date Posted: 09/27/2005 09:24 PM Posted By: clarkkent333(Senior Member)

Can someone help me out with this: I've got 2 WRT-54G's - 1 hardwired to my DSL modem and the second that I want to connect to wirelessly. I don't need access to the computer on the second router since it's only down the hallway but I'd like to use WPA for the most secure connection. Is this possible?

-------------------------
HEATWARE


Date Posted: 09/27/2005 09:32 PM Posted By: Charon(Junior Member)

quote:
Originally posted by: ucenec
Hello!

I have two of questions for user1234 or other users who know my situation.

1.question
I connected mine 2 WRT54gs and works perfectly. But I have another WRT54gs and I would like to connect to the client router (WRT54gs)

My situation:

Internet ------- Main router (WRT54gs)---------Client Router (WRT54gs)------------2nd Client Router (WRT54gs)

Second router must use the first client router because it is to away from main router.
How can I solve this problem?

2.question

How to share files.....because I don`t see a files of client computer?


Thank`s to answer....... sorry for my not fluent english . I`m from Slovenia...








OK basically as you have 3 WRT54G's you wish to connect, the easiest way is using WDS mode. With this you'll be able to view shared files between them all, it's easy to setup, and the client computer should roam seamlessly between them all depending on signal strength -> IDEAL SITUATION. (correct me someone if i'm wrong ).

To do WDS, you just need to install a compatible firmware on them all, as far as i know, the alchemy builds from the first post should work fine.

Only catch may be how WDS works when the third router is too far away to communicate with the first router, i assume this is not a problem, but i'm honestly not sure. Anyway just a quick answer for you.



Edited: 09/27/2005 at 09:36 PM by Charon

Date Posted: 09/29/2005 04:29 AM Posted By: ThroatPunch(Member)

I've been having the problem that after I have set everything up, including the telnet command, I cannot see other computers on the network(or other computers sharing iTunes libraries in particular). I apologize if this has been answered already. Thanks for your help.

-------------------------
--ThroatPunch



Edited: 09/29/2005 at 04:29 AM by ThroatPunch

Date Posted: 09/29/2005 08:20 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: ThroatPunch
I've been having the problem that after I have set everything up, including the telnet command, I cannot see other computers on the network(or other computers sharing iTunes libraries in particular). I apologize if this has been answered already. Thanks for your help.




You will not be able to automatically see other computers which are connected to the other router because this guide sets up two subnets which do not share their broadcast messages. But if you performed step 10, you will be able to ftp,telnet,ssh or use http to connect to any computer on your private network by EXPLICITLY SPECYFING THE IP ADDRESS OF THAT PC. For example, suppose PC-1 is connected to the main router and has IP of 192.168.0.50, and PC-2 is connected to the client router and has IP 192.168.0.150. PC-1 can ftp to PC-2 by doing "ftp 192.168.0.150" or to browse PC-2's shared folder go to "my network places" and add a network place "\\192.168.0.150\share". Note you may need to set up the sharing permissions accordingly.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU




Edited: 09/29/2005 at 08:24 PM by DidlySquat

Date Posted: 09/29/2005 08:22 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: ucenec
Hello!

I have two of questions for user1234 or other users who know my situation.

1.question
I connected mine 2 WRT54gs and works perfectly. But I have another WRT54gs and I would like to connect to the client router (WRT54gs)

My situation:

Internet ------- Main router (WRT54gs)---------Client Router (WRT54gs)------------2nd Client Router (WRT54gs)

Second router must use the first client router because it is to away from main router.
How can I solve this problem?

2.question

How to share files.....because I don`t see a files of client computer?


Thank`s to answer....... sorry for my not fluent english . I`m from Slovenia...









Q1: not possible using this setup. The client router cannot have wireless clients. You need to use WDS mode.

Q2: see my previous post one above

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 09/29/2005 08:26 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: ucenec
Hello!

I have problem to login via telnet because I don`t have login name (username), and you can not leave login field empty in telnet.

One topic describe how to connect via telnet. It said that you can login the same way as the web interface. But when you login to the web interface you don`t use any username....where can I find this username?


Thanks..... sory for my not very fluent english !




username = root
password = admin



-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 09/30/2005 12:40 AM Posted By: antsct(Member)

I don't suppose with will work for a D-Link DI-524?


Date Posted: 09/30/2005 11:03 AM Posted By: DidlySquat(Senior Member)

yes it does

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 09/30/2005 11:58 PM Posted By: pascal333(Junior Member)

Kenny. You have really taken off with this stuff!!
Prof Pascal333

-------------------------
Blaise
I have but one more cat life to give...


Date Posted: 10/03/2005 09:09 PM Posted By: ogonzo(Junior Member)

Hate to ask such a dumb question but will this work having a WRT54G as my primary router and a WRT54GC as my secondary. I'm trying to connect the GC to a Slingshot media box so that I don't have to run an ethernet cable....

Thanks


Date Posted: 10/04/2005 02:30 PM Posted By: The Green Bean(Platinum Member)

I want to the opposite. I want to connect my non wireless "DSL" router to my WRT54G Cable router so that the internet would be accessible wirelessly.

-------------------------
Please donate to the Earthquake relief fund


Date Posted: 10/04/2005 06:02 PM Posted By: DidlySquat(Senior Member)

ogonzo, I think you sdhould be able to do that if WRT54GC can run the same firmware which supports client mode. So first try to download and install the firmware, and if it works you can continue with the rest of the setup.

hatim, that should be no problem, in fact that's a trivial setup that has nothing to do with setting up a wireless bridge.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU




Edited: 10/04/2005 at 06:02 PM by DidlySquat

Date Posted: 10/06/2005 02:14 PM Posted By: VirtualLarry(Diamond Member)

quote:
Originally posted by: 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.



I just recently did this, actually, with a Motorola WR850Gv2 flashed with the beta 6.14 firmware, and a Linksys with official 3.03.06 firmware. (No warranty-voiding Sveasoft firmware needed!)

The good part is, it's all true layer-2 wireless bridging, or WDS mode - I can connect to either AP via a wireless NIC and access all of the wired machines connected to either AP, so perhaps it is using WDS mode. So apparently there is support for WDS mode/bridge inside the official Linksys WRT54G firmware, only it isn't exposed via the UI.

quote:
Originally posted by: user1234
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....



quote:
Originally posted by: bazookajoe
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.



I noticed that too, after I had this all set up and disconnected my Linksys WUSB54Gv1 NIC. Suddenly, my PC seemed quick again, and in viewing Task Manager, my CPU times rarely hit 100%, with the kernel-mode CPU time returning to a negligible amount, instead of 25-40%. I was also planning on moving to Linux as my primary OS eventually, and this will make it much easier, as I can use the Internet over a wired connection to set things up.

I've also tested it with my laptop plugged in to a wired port at the same time, and both machines can access the internet just fine, so this setup has none of the single-machine AP client mode limitations that the Sveasoft firmware has.

I apologize for some of my past comments in this thread too. In hindsight, I may well have been wrong, and your setup may have been using a unidirectional NAT, combined with routing in the other direction. However, given what I was able to accomplish with stock Linksys firmware, it appears that I was also partially right in my belief that there is hidden support for WDS mode in their firmware, as my current setup seems to prove that.

Getting all of the settings right on the Moto was a PITA, but once I got it working - "it just works". No manual route-table entries, no NAT, just layer-2 all the way through.

I do have to say, though, thanks for all of the blood, sweat, and tears, doing the experimentation trying to get this sort of thing to work in the first place. Sorry if I antagonized you a bit. With my recent additional discovery, it would seem an inexpensive solution to find a Moto router ($20 on clearance in many places), download the 6.14 beta firmware, and just set things up that way. (I also discovered that D-Link antennas fit onto the Moto router.)

Oh, and one more important point - this setup is actually using WPA-PSK/AES in WDS mode! (At least, that's how both of the routers are configured, and it appears to be true from testing using a wireless NIC.) So no compromise is needed on security in order to run in WDS/bridging mode.




Edited: 10/06/2005 at 04:02 PM by VirtualLarry

Date Posted: 10/06/2005 02:48 PM Posted By: VirtualLarry(Diamond Member)

quote:
Originally posted by: tishoo
I'll echo the comments regarding the Belkin routers and their WDS mode.
The Belkin F5D7230-4 is at $10 (AR - 30+30) again at (I think: Circuit Sh!tty). Up to 4 of these can be set up to bridge (Wireless Distribution Service mode).


Interesting. See this link. Scroll down to near the bottom, the Q & A section. There are a couple of interesting things there.

quote:
Follow-Up: These routers will act as routers, bridges and AP's. For bridging, enter the peer MAC address in the configuration for BOTH routers. With the 4.05.03 firmware, bridging does not work with WPA if you have additional wireless clients. It does seem to work if the only wireless traffic is between the two routers. I have successfully bridged three of the 4.05.03 version 2000 routers. Make sure to only enter the master MAC address on the remote AP's and all AP MAC's on the router/gatweway. Entering every MAC's on both AP's and the router seems to confuse them. BTW, I get better bandwidth running ethernet through the bridged AP's than using a Belkin F5D7000? 802.11g PCI card, go figure.


quote:
You should be able to bridge between all Broadcom firmware that allows bridging. I have a link WDS link between a Linksys wrt54g and a f5d7230 which I flashed the f5d7231 firmware.


Interesting, no? Search for "wl0_lazywds" too. Perhaps all that needs to be set on WRT54s is that NVRAM variable, assuming that the proper support is already in the Broadcom firmware code already somewhere. The settings I used on the Moto were essentially the same ones shown in this Belkin WDS setup guide.



Edited: 10/06/2005 at 04:06 PM by VirtualLarry

Date Posted: 10/06/2005 11:49 PM Posted By: mdcrab(Golden Member)

Thanks user1234. Your steps worked great in setting up my WRT54G as a client.

I have a LinkSys RT31P2 that I am using for a Vonage connection, but no way to get a wired connection from my main router NetGear WPN824 in basement to a cordless phone base station in kitchen. I set the WRT54G up per your instructions and connected to RT31P2. Worked first time. Thanks for providing such detailed instuctions. Plan to place units on top of kitchen cabinets, high up and out of site. Soon Verizon will be out of here.

mdcrab

-------------------------
VTVTVTVTVTVTVTVTVTVTVTVTVTVTVTVTVTVTVTVTVT
"Only Irish coffee provides in a single glass all four essential food groups: alcohol, caffeine, sugar, and fat. " ~ Alex Levine





Edited: 10/06/2005 at 11:51 PM by mdcrab

Date Posted: 10/13/2005 03:39 AM Posted By: gsr415(Junior Member)

Hello user1234 i followed your instructions to allow WRT54G to run in bridge mode and everything works perfectly except.....my videoconferencing hardware!

Hoping you can help, i'm positive its a problem somewhere with the double NAT scenario however i'm not 100% sure.

Basically i have the VC H/W device connected via ethernet to WRT54G with WAG54G as main DSL modem/router. I have opened the TCP/UDP port ranges on both routers and port forwarded these ranges to the VC system's IP address.

In its current configuration the VC device establishes a connection outbound on TCP 1720 however i receive no video or audio from the remote end videoconferencing system.
The VC system shows that its connected (so i believe i'm able to send audio and video out the network) just not receive inbound.

If i connect the VC device directly into the WAG54G and do the same procedure with opening ports/port forwarding, videoconferencing works fine!

I've tried putting the VC unit in the DMZ of both routers at different points, tried statically assigning the VC system with an IP, tried turning off all firewalls, tried turning NAT on the VC device off, however i'm not having much luck.

Ideally i would like to make and receive H.323 and SIP based video calls from the VC hardware directly connected to the WRT54G (not direct connect to WAG54G)

Hoping you can shed some light i'm not sure if you're familiar with H.323 video but would appreciate any assistance in getting this going.

Thanking you






Date Posted: 10/13/2005 03:12 PM Posted By: DidlySquat(Senior Member)

gsr415, if you're trying to allow connection from some external internet address, you only need to set up port forwarding on the main router AND NOT ON THE CLIENT ROUTER. Just set up the forwarding on the main router to the IP of your device connected to the client router (e.g. 192.168.0.150), and the proxy_arp (step 10) will take care of the rest.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 10/13/2005 05:34 PM Posted By: CiaBpi(Junior Member)

Hi,

I just acquired a WRT54G v.5. I have tried to upgrade the firmware, with several versions, but none of them are loaded, I only get upgrade failed. Any sugestions, since I need to use this one in combination with the DI-624+ as base, and the WRT54G as bridge. I have read thru the entire tread, and googled for a few hours, but I can't find any solution.



Edited: 10/13/2005 at 05:35 PM by CiaBpi

Date Posted: 10/13/2005 05:56 PM Posted By: DidlySquat(Senior Member)

The firmware mentioned in the guide is compatible with WRT54G v2.2, but maybe not with newer versions. But I'm sure you can find a newer version of the sveasoft firmware which is compatible with your new v5 wrt54g. I have a v2.2 wrt54g working as a client to d-link di-624+ and the setup is working great. Other people mentioned they got v3 wrt54g to work, but I haven't yet heard of people using v5 wrt54g. But again, I'm sure there are firmware versions compatible with this new model.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 10/13/2005 06:11 PM Posted By: CiaBpi(Junior Member)

hmm .... I found something .... that isn't encouraging :

Link : http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=9209
Date : oct 12, 2005

quote:
NO 3rd Party Firmware exists for this model. the problem is the amount of RAM and the OS is VxWorks and not Linux.

if you want to use 3rd Party Firmwares, DO NOT BUY A WRT54G v5



I guess I am sc##d.



Date Posted: 10/13/2005 07:08 PM Posted By: DidlySquat(Senior Member)

maybe you could exchange your newly acuired v5 wrt54g for a v2.2 or v3 ?

The reason there are 3rd party firmwares is that these versions are based on linux and their original linksys firmware is open source. But I guess the new v5 is not linux based and is not open source, so it's basically a blackbox just like any other router on the market.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 10/16/2005 06:05 AM Posted By: mandylion(Junior Member)

Hi ! What I needed from my wrt54 was that to act like a complete transparent bridge , but connected to a AP .
In V23 Firmware (alpha) I have that acomplished with one big inconvenience :
It does something with the MAC addresses from computers conected to the WRT directly by cable . So, from wireless , I can see only one MAC address for all the computers conected to the LAN ports of the WRT .
It does a kind of MAC proxy (or MAC-NAT ) I guess ...
Does anyone knows if it's possible to get my WRT running exactly like a switch does on the ethernet ?
Stuff like D-Link DWL-2000 and others , does this by default running in Client mode.



Date Posted: 10/16/2005 07:17 AM Posted By: gsr415(Junior Member)

Didly squat, my main router is a WAG54G V2 and doesn't support CLI through Telnet only web-based GUI.
How to complete step 10?



Date Posted: 10/16/2005 09:58 PM Posted By: DidlySquat(Senior Member)

quote:
Originally posted by: gsr415
Didly squat, my main router is a WAG54G V2 and doesn't support CLI through Telnet only web-based GUI.
How to complete step 10?




step 10 is done on the client router - the wrt54g with the alchemy firmware. So first complete this step.

Then, To set up port forwarding to any machine on your local network, you only need to use your main router's web interface and specifiy the port and IP address of the machine you want to forward to. This should work for any of your machines machines, wether they are attached to the main router or the client router.

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 10/21/2005 05:10 PM Posted By: Trikkie(Junior Member)



Great router
Great firmware
Great application

I had been searching for this solution for a long time.
Installing the firmware took me 2 hours, the rest only 5 minutes.

Thanks !



Date Posted: 10/21/2005 08:55 PM Posted By: ipontific8(Junior Member)

I followed all the steps 1-9 and sucessfully connected my WRT54 G V2.0. The only thing that does not work is logging in via Telnet or SSH. The router password does not work. Any ideas?

Ipontific8 -- sure need to have this working:-(


Date Posted: 10/23/2005 08:42 AM Posted By: DidlySquat(Senior Member)

make sure that telnet and SSHD are enabled in Administration->Management screen. Log in username is "root", password is "admin" or whatever you changed it to (same as the web interface)

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 10/23/2005 05:54 PM Posted By: ipontific8(Junior Member)

awesome! i didin't type the username root - was using the router username. duh! Thanks for helping me through this spot!

ipontific8


Date Posted: 11/10/2005 07:08 PM Posted By: stmok(Junior Member)

quote:
Originally posted by: CiaBpi
Hi,

I just acquired a WRT54G v.5. I have tried to upgrade the firmware, with several versions, but none of them are loaded, I only get upgrade failed. Any sugestions, since I need to use this one in combination with the DI-624+ as base, and the WRT54G as bridge. I have read thru the entire tread, and googled for a few hours, but I can't find any solution.




Return it. Ask for Version 4 or older.
Version 5 uses VxWorks Operating System, NOT LINUX! (like the older models)
This is why you cannot update the firmware.

Its the same for WRT54GS model, DO NOT BUY THE LATEST ONE!
(If you want to use third-party firmware!)

Linksys is well aware of enthusiasts wanting to install custom firmware with their Linux
based routers, so to cater for that market, Linksys will introduce WRT54GL
=> The L = Linux

It will have large RAM and Flash RAM storage.



Date Posted: 11/10/2005 09:29 PM Posted By: DidlySquat(Senior Member)

^^^ oh man , I tohught my V2.2 will become a collectors item so I could sell it on ebay for $200......

-------------------------
CPU: Athlon 64 3000+ Venice @9x275=2475 mhz
Mobo: Asus A8N-SLI Deluxe
RAM: 2GB (4x512MB) Kingston HyperX PC3200 @2x175=DDR350 2-3-2-6
Video: XFX 7800 GTX OC (490/1300)
Sound: Creative Audigy2 ZS
HD: Maxtor 250GB ATA/133 7200 rpm
Monitor: Dell 2405fpw 24" LCD
Case: X-Alien metallic green aluminum tower w/Thermaltake 480W PSU



Date Posted: 11/10/2005 11:39 PM Posted By: iliopsoas(Golden Member)

i tried upgrading firmware on my WRT54G v4 and it keeps telling me that upgrade failed



-------------------------
Heatware

IBM PC XT 4.77 Mhz @ 6.00 Mhz using Orchid Technology Turbo card
256Kb RAM, expanded to 640Kb with Orchid Technology RAM card
2x 10 Mb MFM HDD
300 baud modem
13" CGA monitor


Date Posted: 11/19/2005 02:05 PM Posted By: lederhosen(Member)

Will this work on a WRK54G or just the WRT?

-------------------------
My Rig


Date Posted: 11/28/2005 12:25 AM Posted By: pooq(Junior Member)

I bought my second belkin(F5D7230-4) 5 months ago but never succeeded to make the 2 belkin working in this way. (tried to configure wireless bridge and worked but PCs connected to 2nd belkin can't go online. I must missed something) so this 2nd belking has been sitting there in the dust all these days.

After google and found this thread today, i tried again. worked immediately! no any change about subnet mask or gateway in the wireless bridge belkin. so i don't need to worry about the PC communication between 2 different subnet.

and yes! one of the best thing
the belkin(F5D7230-4) is $10-20 each after rebate.

I am so happy now. finally i fixed this long-existing problem and i am watching video from my livinging room computer and LCD TV.

quote:
Originally posted by: tishoo
I'll echo the comments regarding the Belkin routers and their WDS mode.
The Belkin F5D7230-4 is at $10 (AR - 30+30) again at (I think: Circuit Sh!tty). Up to 4 of these can be set up to bridge (Wireless Distribution Service mode).
Last update by Skylinux @ 2005-12-1 22:41:58

 

No Comments yet .....

 

Add Your Comment:

Note: All posts require administrator approval. Please allow 24 hours for message approval.

Name:
E-Mail:
Title
Plain text only, less then 65 000 characters.

Do you have a dog?

Please answer the question above and type the answer into the text box below.