wireless bridge

CU

Platinum Member
Aug 14, 2000
2,415
51
91
I have two Trendnet TEW-652BRP's. The main router is still running the default fireware and is sitting on 192.168.10.1. I flashed the other one with dd-wrt and followed http://www.dd-wrt.com/wiki/index.php/Client_Bridged replacing the third octet with 10 to match my network. After the last step of setting my computer back to auto ip, I can no longer get to the DD-WRT router. Shouldn't I be able to get to by going to 192.168.10.6 (the ip I gave it) even if it doesn't connect wirelessly to my main router? I guess I can hard reset and try again, but I was pretty through in following those directions. I expected to at least be able to get to the router again.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
Well I did a hard reset and did all the steps again. Same outcome though. Right after "Go to setup/advanced routing and change the operating mode from "gateway" to router. Hit Apply.", I can no longer access the router. It doesn't matter if I set windows to a static ip of 192.168.10.6 or auto. I am using Windows 7 and I haven't done alot of networking with it, so maybe I am missing something. Any suggestions?
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
My LAN connection always says Unidentified network with the router plugged in. Not sure what means. Windows trouble shooting says it doesn't have a valid IP configuration. What needs to be configured?
 

ch33zw1z

Lifer
Nov 4, 2004
39,040
19,732
146
Just save the picture and follow the steps in the lower right hand corner, substituting your settings for theirs. I just fire up that picture when I have to redo the settings. Once you get it setup right, there's no much else you need to do. Maybe unplug it and plug it back in once in a while depending on your setup.

Don't forget the 30-30-30 rule for the hard reset, that seems to be important IMXP
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
I will try that out in a few days when I can get back to it. But if that works and their wiki says don't do that do something else that doesn't work, it doesn't give me much confidence in the rest of their wiki.
 

ch33zw1z

Lifer
Nov 4, 2004
39,040
19,732
146
Confidence should be placed in what you know works, trial and error my friend.
 

JackMDS

Elite Member
Super Moderator
Oct 25, 1999
29,529
416
126
My LAN connection always says Unidentified network with the router plugged in. N

Some thing is wrong with the network toplogy.

Connect a computer with a wire to the bridge. Set the computer wit a static IP that it is of the subnet of the Bridge's core IP. Connect to the firmware and make sure that every thing is Ok.

While you are connected this way associate the Bridge's Wireless with the Main Wireless.

Make sure that the SSID and Security are correct.

On the main Wireless make sure that if the MAC filter is On it accommodates the Bridge MAC and any computer that connects to the bridge.



:cool:
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
Some thing is wrong with the network toplogy.

Connect a computer with a wire to the bridge. Set the computer wit a static IP that it is of the subnet of the Bridge's core IP. Connect to the firmware and make sure that every thing is Ok.

While you are connected this way associate the Bridge's Wireless with the Main Wireless.

Make sure that the SSID and Security are correct.

On the main Wireless make sure that if the MAC filter is On it accommodates the Bridge MAC and any computer that connects to the bridge.



:cool:

That error appears when I have it connected with a wire to the bridge and it doesn't matter if I set it to an ip in the subnet of the bridge or set it to auto. So, I cannot get back to the firmware after do the last step I listed above. That step is what causes the problem, but I don't know why.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
I followed the steps in the picture. And while it doesn't cause me to have to do a hard reset it still doesn't work. When I click join after doing the site survey it says I successfully joined, but I don't see it connect on my main router's webpage. When I set my computer back to obtain an ip, I cannot go anywhere on my network. I have to set it back to 192.168.10.9 to reach dd-wrt again.
 

ch33zw1z

Lifer
Nov 4, 2004
39,040
19,732
146
I followed the steps in the picture. And while it doesn't cause me to have to do a hard reset it still doesn't work. When I click join after doing the site survey it says I successfully joined, but I don't see it connect on my main router's webpage. When I set my computer back to obtain an ip, I cannot go anywhere on my network. I have to set it back to 192.168.10.9 to reach dd-wrt again.

Do the hard reset before you configure. I had to set one of these up for a buddy this week, and wouldn't you know it....that damn device fought me to the bitter end to work right. In the end, the 30-30-30 hard reset and one more time configuring and all was well.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
I had to do a hard reset because when I do it the other way it locks me out of the router. A hard reset is the only way I can recover after I set the operating mode from gateway to router, when following the updated instructions. So, I followed the instruction in the picture after a hard reset. It asked me to set a new password and all. I found some post on the dd-wrt forums where others have had the same problem, but no fix. Some have said client mode works, but that splits the network into two subnets, which I didn't want. Thus the reason to use client bridge.

Did you configure the same router as a client bridge? What version of dd-wrt did you use? Can I just download the newest and try it since I already have dd-wrt on it? Or do I need a special version for my router.

P.S. I have gotten more help here than the dd-wrt form. All I got from there was Sash telling me to put dd-wrt on my main router and wiki wds. But I don't need wds and I want to get it working as a cilent before I start playing with my main router to make sure dd-wrt is stable. The stock firmware is very stable for me. If it only supported client bridge mode.
 
Last edited:

aylafan

Member
Jun 30, 2010
55
0
66
Another option you can try is Repeater Bridge Mode in DD-WRT. I believe it is better than Client Bridge Mode because it works with both wired and wireless connections. The main drawback is bandwidth will be cut in half, but it should not affect performance that much as long you are not streaming uncompressed HD videos.
http://www.dd-wrt.com/wiki/index.php/Repeater_Bridge

Both routers will require the latest DD-WRT firmware for Repeater Bridge Mode to work.

Repeater Bridge Mode works fine for me on 2 Linksys wireless routers at home.
 
Last edited:

ch33zw1z

Lifer
Nov 4, 2004
39,040
19,732
146
I understand. I'm never had to set the gateway/router setting when I set it up.

1. 30-30-30 hard reset
2. set your IP static to 192.168.1.2 (the DDWRT router is now 192.168.1.1 due to hard reset)
3. plug in your network cable and connect to the ddwrt router, change password to whatever you want.
4. Start with basic setup, using the instructions I pointed you to. Keep in mind the bridge needs it's own IP that won't conflict with your main router. You may have to click "save" more than once on this page for the settings to keep. Double check them. Do not apply though.
5. Now set up the wireless settings in the ddwrt gui, again...don't click apply until all the settings are all set.
6. Once you have confirmed the settings look good, click the "Apply" button. This will reboot the router and it will be operating in client bridge mode. After the apply is good and the lights on the front settle down, unplug the router and plug it back in after 10 seconds.
7. either set you IP staticly to something on the same subnet that doesn't conflict with either the bridge or the main router, or enable DHCP again.
8. Open a command prompt and start by issuing the ipconfig command and see what you got
9. start pinging the bridge and main router to see if you get replies.
10. profit.

I wouldn't change the main routers firmware unless it's giving you problems. no need for ddwrt unless you want it/ need it.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
That sounds like what I did last night. Except I clicked apply every time I was done with changing a section. Not just once at the end. Not sure how that makes a difference. That and the 10sec power off thing (which I also tried) are the only differences I see from the instruction you pointed me to. Am I missing something.

After I click join shouldn't it show up on my main router? Also if I set my nic to DHCP and the client bridge doesn't connect to my main router would I still get an ip? I assume no as I didn't get one, and the main router should be the one handling DHCP.

You didn't tell me what router you set up client bridge mode for. Was it one like mine?
 

ch33zw1z

Lifer
Nov 4, 2004
39,040
19,732
146
That sounds like what I did last night. Except I clicked apply every time I was done with changing a section. Not just once at the end. Not sure how that makes a difference. That and the 10sec power off thing (which I also tried) are the only differences I see from the instruction you pointed me to. Am I missing something.

After I click join shouldn't it show up on my main router? Also if I set my nic to DHCP and the client bridge doesn't connect to my main router would I still get an ip? I assume no as I didn't get one, and the main router should be the one handling DHCP.

You didn't tell me what router you set up client bridge mode for. Was it one like mine?

If you click "apply" after you configure the first page, then you only did half the setup. You won't receive a DHCP address because the wireless part was never configured. You will have to change your IP to something that can access the DDWRT device, reconnect to the GUI using the bridges NEW IP that you just configured, and then continue with the setup procedure. Click Apply one time and save yourself the extra steps.

I setup the Client Bridge the other day on a Linksys WRT54GL, I use a GS (v5? i think) at home. All my successful client bridge setups have been on the Linksys devices or the Asus devices.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
I clicked "apply" after every page. I did all the steps/pages. And yes I had to reconnect to the bridges NEW IP, just like you said.

This may be a bug with dd-wrt and the Atheros chipset. There alot of old and newer post on the dd-wrt forum about it and the dlink 615 having this problem. Although Sash says it works, but want say how to make it work. It seems dd-wrt has went down hill in the past year or so based on the post in the dd-wrt Atheros hardware forum. Still hoping I can get it to work though. I may try client mode tonight.
 

ch33zw1z

Lifer
Nov 4, 2004
39,040
19,732
146
I clicked "apply" after every page. I did all the steps/pages. And yes I had to reconnect to the bridges NEW IP, just like you said.

This may be a bug with dd-wrt and the Atheros chipset. There alot of old and newer post on the dd-wrt forum about it and the dlink 615 having this problem. Although Sash says it works, but want say how to make it work. It seems dd-wrt has went down hill in the past year or so based on the post in the dd-wrt Atheros hardware forum. Still hoping I can get it to work though. I may try client mode tonight.

Don't click apply until all the settings are correct and saved...

If you setup the first page, and click apply, and subsequently do NOT have to change your IP, then something isn't right...
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
I did have to change my IP, but I will try it again tonight and only hit apply after everything is done.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
It didn't make a difference. I still get the same results. dd-wrt doesn't connect to my main router. I also noticed under Status/Wireless the Channel is cycling 1 through 11.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
Well I flashed to the greatest and latest v17201. Following the instruction in my first post I no longer lose the router after changing the operating mode from gateway to router. However it still doesn't connect to my main router wirelessly. But hey it is an improvement.
 

CU

Platinum Member
Aug 14, 2000
2,415
51
91
Disabling my weak web security (old b client in use) fixed it. I will work on that later.