bridging 2 wireless routers?

[Evander]

there are 2 wireless routers in my home, the one that is currently setup to the main computer is a Netgear WGT624 v2

My old laptop in another room has a pcmcia Wireless card which is how I currently access the internet, I would prefer to use the single pcmcia slot for a firewire/usb2.0 card and not have to swap cards. I know of one way is to use power adapter converters for the wall socket with a lan cable, but instead of buying these I was hoping to use a spare router which is not currently being used, a Belkin F5D7231-4.

I have no experience with bridging routers and I'm not sure if it's even possible, but if it is I would somehow show me how to do it? I only care about internet access, and don't need to share printers or files and such with the others computer. Would there be any problems in that these 2 routers are made by different manufacturers?

 

[JackMDS]

This Netgear is not capable to be configured as a client.

Some versions of the Belkin can as is and if Flashed with 3rd party firmware.

See here, http://www.dd-wrt.com/wiki/index.php/WDS_Linked_router_network

Setup instructions here, http://www.dd-wrt.com/wiki/index.php/Client_Mode_Wireless

 

[yuppiejr]

First thing I suggest is to log on to the website for the manufacturer of each router and apply any available firmware updates. Download the manual for both and start reading - generally the process for bridging will be outlined there IF it's possible.

I run a wireless bridge with two identical Netgear AP's that added the feature in a recent firmware, here's the process I used to connect them:

-Jot down the wireless MAC for each device.
-Each device should have a STATIC LAN IP address in the same subnet. The "base" router (connected to the internet) should probably be 192.168.1.1 and the other node of the bridge can be 192.168.1.2.
-One of the two devices needs to be configured as a DHCP server, I suggest using the IP range 192.168.1.100 to 192.168.1.200 for clients. The other should have the DHCP server disabled.
-On the "base" router, configure it for bridge mode and input the MAC address for the "remote" router. <this step may not be required as long as the client lets you input the base router's MAC>
-Configure 128 bit WEP security (WPA/WPA2 doesn't seem to be supported on any devices I've bridged thus far) - note the paraphrase.
-On the "remote" router, configure bridge mode and input the MAC address for the "base" router.
-Configure WEP security with the same paraphrase that you used on the other router.

On my netgear routers, I was able to see in realtime when one was connected to the other so it was easy to tell if it was working or not. Not sure how it will work with your setup.

It's a crapshoot that your devices will or will not support bridging, and another that they will talk to one another even if they do support bridge mode. If they do, the third variable is how careful you are when you configure everything but if you use the steps above and the hardware supports it this should take care of the bridge you're looking to create.

 

[JackMDS]

Originally posted by: yuppiejr

I run a wireless bridge with two identical Netgear AP's that added the feature in a recent firmware.

Being able to run as a client is a common feature in Most Access Points.

However it is a feature that as is exists in very few Wireless Routers.

Few Belkin, SMC, and most BuffaloTech. models have the capacity as is.

Linsys WRT54xx line, and few others can do it with 3rd party firmware.

Firmware is Not Magic, it can add this capacity only if the chipset was initially designed for it.

 

[yuppiejr]

Originally posted by: JackMDS

Originally posted by: yuppiejr

I run a wireless bridge with two identical Netgear AP's that added the feature in a recent firmware.

Being able to run as a client is a common feature in Most Access Points.

However it is a feature that as is exists in very few Wireless Routers.

Few Belkin, SMC, and most BuffaloTech. models have the capacity as is.

Linsys WRT54xx line, and few others can do it with 3rd party firmware.

Firmware is Not Magic, it can add this capacity only if the chipset was initially designed for it.

Good point, I realized after the fact that my logic was flawed in terms of the router's capability to act as a client. It does look like his Belkin, assuming it's a newer hardware version, can act as a client so he might be able to associate it with the Netgear after a firmware upgrade. If it doesn't work with the stock firmware the DD-WRT option is a great suggestion.