Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[nickCR]

Hello All,

I have been working for hours now trying to get the WRT54G to wirelessly bridge to my DIR-825 so that I could put it in the room where my xbox is which needs access to my network.

I am having a problem though. I followed these intructions:

http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge

The wrt54g (secondary) sort of works. I set it up for Client Bridge and get to the point where I do site survey and select the network i'm trying to connect to. It shows up on the bottom of the wireless page as access point. I cannot ping the main router though. The wireless on the DIR-825 shows that it's a connected client.

The weird thing is that when my computer is directly connected to the WRT54G I get a 192.168.1.2 gateway when it should be 192.168.1.1.

Any help?

Thanks in advance,

Nick

[nickCR]

Here are some more details on my setup and versions i've tried:

DD-WRT v24-sp2 mini - build 11296M NEWD Eko
DD-WRT v24-sp2 mini - build 12548M NEWD Eko
DD-WRT v23-sp2 standard

I disabled security completely on my DIR-825 (AP).

I reset to factory defaults, then did the hard reset 30/30/30. Following that I followed the Client Bridged instructions to a t...

http://www.dd-wrt.com/wiki/index.php/Client_Bridged

I can see the AP in the Site Survey. I click JOIN and I see it on the status WIRELESS page under Access Points.

The problem I see though is that it's Tx Rate & Rx Rate are both N/A.

With my PC connected to the WRT54G (CB) I can connect to it without any problems. I even get the IP i've reserved for my PC.

When I try to ping the AP I don't get any results.

Scratching head.. Is there something I need to setup in the DLINK side to make it work? I can validate that the DLINK wireless works because I connected to it and got internet no problem.

I'm running on the DIR-825 Firmware Version 2.02NA and I have Hardware Version B1

Going to install the new EKO NEWD ver 12548 and see if it helps at all. I'll report back. Updated to new version and no change. Still not bridging to AP

Update: Tried an old v23 SP2 build since there was a notice that there could be a problem with v24. This still hasn't solved my problem. With this setup I also get the ip i'm expecting to get which is reserved for my pc at the ap. (if I were to take out my cable and connect it to the DIR-825 then I would get the same IP I was provided).

I cannot access the (CB) via it's IP when wire connected to the (AP).

I cannot access the (AP) via it's IP when wire connected to the (CB)

Thanks in advance!

Nick

[iMek]

Hey Nick,

  Was wondering if you ever got your dd-wrt to work with your dir-825. I currently have the same setup as you do. I have At&t modem plugged into D-Link dir-825 with WPA security. My Linksys router (with dd-wrt firmware v.24) is connected to dir-825 via Wireless. Then a desktop and a printer are plugged in to the linksys router. Currently, everything is working fine, except with occasion lost signal when my laptops are connected wireless, (still trying to figure out why).   

  I actually have another linksys router with the original linksys firmware. What I would want to do is actually connect that linkysys router to the modem, and use my dlink dir-825 router at my other house, which is one house down. But i'm not sure if that is possible because i don't know if dlink dir-825 can work as a wireless bridge mode? And the reason why i want to use dir-825 as a bridge is because it has a usb port in the back, this way i can connect a usb printer. Do you think that is possible?

Mike

[nickCR]

Just saw your reply.

Actually no I never go it to work as a bridge. If I could get it to work I would be very happy but nothing at all.

I only got it to work as a ap connected via Ethernet Cable to the DIR-825.

I am actually going to try again though since I found a bug with the IP service and that might be causing the problem I had when I was trying to setup the WRT54G as a Client Bridge.

The bug wasn't associated with this problem. Still can't get Client Bridge mode to work.

Nick

[nickCR]

Some interesting facts to add.

In client bridged mode, once I reconnect to my main router I can access the dd-wrt page via 192.168.0.2 as that is the IP I entered for the WRT54G (DD-WRT).

When i'm directly connected to the WRT54G I cannot ping the main router. When i'm connected to the DIR-825 I can ping both the main router and secondary router

When I go to the DLink admin under status -> wireless I see two items connected. The first one is the second router. But it has IP address 0.0.0.0 which I don't understand since it should be 192.168.0.2.

The second problem i've noticed in the DLink is that under statstics I have a ton of dropped packets.

I have the DLink Firewall turned off since I though that would be the problem but no resolve.

If I connect via wire to the WRT54G I do get an IP. I even get the IP that I have assigned to my MAC. But I simply cannot connect to the DLink nor can I connect to other computers on the network.

Is there something I can execute to make this work correctly? Any suggestions? Techs / Engineers?

iMek can you post your settings here?

Thanks in advance,

Nick

[nickCR]

I finally figured it out and the problem was on the DIR-825 side.

I did one and only thing. I turned off the 5 ghz adapter.

This is a problem with the DIR-825 firmware since it is not routing the packets correctly. This is obvious on the status -> statistics screen where you will see TX Drops increase on the 5 ghz adapter when the WRT54G is set to client bridge mode.

Something interesting. I tried re-enabling the 5 ghz network to see if maybe it was only a problem with the network mode and I couldn't even connect to the DIR-825 directly. So there is something really funky with the wiring (figure of speech).

I hope this will eventually help someone else who has problems bridging these two devices.

Regards,

Nick