I also had the same problem with my XBOX 360 when I power cycled my Linksys WRTG54 v8(Client Bridge) router.
A work-around to this problem is to setup the Administration\Keep Alive settings. There is WDS/Connection Watchdog setting that will automatically reboot your client bridge if it fails to detect an IP address.
I set the interval time to 60 seconds and the IP address to the IP address on my primary DLINK router. When you power cycle the Linksys(Client Bridge) the connection watchdog runs after 60 seconds. The watchdog will then fail because the client bridge is not available after a power cycle. The watchdog will then do a warm reboot which in turn fixes the Client Bridge, DHCP…etc)
With respect to the transparency of the bridge, it's worth mentioning that the Windows XP bridge thing also acts in the same way; you only see its wifi MAC at the router end too for all the clients connected to it.
Posted: Wed Jan 30, 2008 21:52 Post subject: WAP54Gv3 - can't get bridge fully functional
I have a bridge between two Linksys WAPs that's been running for a couple of years. However, on one end the link is flaky; there's some kind of interference or something that causes the thing to keep changing its encryption key to something random. Swapping boxes didn't help but switching to DD-WRT did; it's rock stable now.
However, the bridge is not running quite right. Here's the setup:
I have the WAP11B set in AP mode with WEP encryption.
I have the WAP54G set in Client Bridge mode.
It links, and I can ping. I can set up PCs on the second segment with static IPs and DNS and such and they work, but the PCs on the 2nd network will not DHCP successfully. It SHOULD get its DHCP requests satisfied by the Netgear. This USED to work when both Linksys boxes were set with factory firmware in "bridge" mode.
I can haul a laptop up to the other building, select the network that the WAP11B is hosting, enter the WEP key, and it connects and DHCPs correctly.
So that's my problem; DHCP isn't working.
Somewhere around here I have another WAP54G; if I can find it I'm going to trash that old WAP11B, it's ancient, but it's what I have on hand right now. If I find the 54G I'll flash that to dd-wrt as well and see if it helps, but since DHCP works with regular clients on the 11B now, I'm not sure it will help.
Joined: 17 Jun 2006 Posts: 184 Location: Essex, England
Posted: Thu Jan 31, 2008 9:14 Post subject:
I wrote a whole big essay on this but my browser lost it. So here is the simple version.
Clients on the bridged lan lose their real MAC address when their traffic passes through the bridge. They end up 'coloured' with the MAC address of the bridge wrt.
Obviously with everyone bridge side offering the same MAC address, DHCP cannot individually assign IP addresses.
The problem does not end here. Even if you assign static IP's you are going to have problems when two bridge side clients try to access the Internet or PC's lan side.
Check the above using arp -a on a lan side PC you have been pinging from PCs on the bridge side. The problem would look something like this;
Code:
C:\Documents and Settings\...>arp -a
Interface: 192.168.1.123 --- 0x3
Internet Address Physical Address
192.168.1.1 00-16-b6-ea-39-e3 'router
192.168.1.2 00-16-b6-bc-62-08 'bridge
192.168.1.96 00-30-6e-fa-1b-0b 'lan side
192.168.1.97 00-0e-2e-84-bb-e6 'lan side
192.168.1.201 00-16-b6-bc-62-08 'bridge side
192.168.1.202 00-16-b6-bc-62-08 'bridge side
Obviously with everyone bridge side offering the same MAC address, DHCP cannot individually assign IP addresses.
Wow. In that case, dd-wrt doesn't really have what you could really call a working bridge mode then, does it?
Is it possible for this to work? It worked with the stock firmware but that was with the other end in bridge mode, not AP mode. It seems like the thing could masquerade the sender's MAC, but I don't know much about how TCP/IP works inside.
I might try setting up the second end as a router with its own subnet then; can the single port on a WAP54G be plugged into a switch with client PCs, and the wireless end be used as a WAN port?
Joined: 17 Jun 2006 Posts: 184 Location: Essex, England
Posted: Fri Feb 01, 2008 9:20 Post subject:
traalfaz wrote:
Wow. In that case, dd-wrt doesn't really have what you could really call a working bridge mode then, does it?
Yes the fact that dd-wrt does not have a working bridge mode is rather shocking, but then nether do any of the other firmwares on this hardware. I assume it's a hardware thing since the MAC address is a hardware address. It may be a different situation with GL version hardware since this is able to spoof different ESSIDs using V24 RC6.2
A company I know how sell a product based on the WRT54G tried to actually use these to bridge some buildings together. Their results were terrible and they gave up using the WRT54G based units on that job.
For me the most useful part of dd-wrt is wireless client mode. This works fine. I believe there are only two circumstances where bridge mode can be used. First where you only have one PC and second where you use an external router. Both pretty pointless uses.
I don't have experience of WAP54G but if it runs dd-wrt then it should do client mode the same as wrt54g. On the client turn off the firewall and NAT and set up a static route in the main router to reach your client subnet. Traffic will flow freely between the two.
Good luck,
Wayland _________________ Buffalo
WRT54G
Posted: Sun Feb 03, 2008 0:05 Post subject: BEFW11S4 main router FON router DD-WRT as wireles bridge
I have a BEFW11S4 router as my main router in the house. It has the standard linksys firmware on it. I have a FON router flashed with DD_WRT v24 RC-5 setup as a wireless bridge. If I plug the sling directly into the linsys router everything works perfect. As soon as I put it on the wireless bridge sling player can't find it. I can ping 192.168.1.237 when it's on the wireless bridge and get responses. I have the firewall turned off on the bridge also. I can telnet 192.168.1.237 5100 and get a hanging blang screen which tells me the port is open. I also can get the sling to work if I use the IP instead of the finder service. I can connect the FON to my laptop and get internet to work fine. Any suggestions would greatly be appreciated.
Thanks
I am looking for some way to improve the transparency of my wireless bridge. I have a buffalo WHR-G54S flashed with DD-WRT v23.SP2 bridged via "client bridge mode" to another buffalo with the original firmware running WPA security. My neighbor has his XBox connected to the host router, mine is connected to the client router.
Almost everything works fine. I can share media between PC's anywhere on the network and either XBox, and both XBoxes can connect to XBox Live with Open NAT. I even have an HP network printer behind the client and it works perfectly. The only thing that doesn't work is a System Link between the two xboxes.
Some background info from my attempts so far:
-Pinging a computer behind the client from a computer connected to the host does not work.
-Many forums have suggested Cloning the XBox MAC to the Router. When I do this, the XBox cannot acquire an IP from the host. Same deal when I enter the router's MAC address into the XBox network settings
-I have tried every manner of static IP, DMZ, port forwarding - no go.
-I have tried two telnet scripts
# echo 1 > /proc/sys/net/ipv4/conf/`route | grep default | awk '{print $NF}'`/proxy_arp
# echo 1 > /proc/sys/net/ipv4/conf/br0/proxy_arp
Both of these were intended to fix this exact problem, but neither have executed in my case.
Any help would be highly appreciated.
Nevermind, I got it figured out. I had it set to TKIP and my existing network was using AES. Still doesn't work for WPA2 but that's documented so I can't complain.
Hi all,
I just bought a WRT54GL with the intent to use it as a client bridge to connect my Xbox 360. I got it flashed to DD-WRT okay but now I'm having trouble with the bridge setup. I first tried the setup with my existing WPA2 security but saw a few things online that said V23 SP2 didn't support that so I moved to WPA. I tried several times to make the bridge work to no avail. I decided to try disabling the security on my wireless and then tried the bridge again. That worked like a champ. I was able to get to the internet on my laptop, connected to the bridge router with no problem.
I then tried going back to WPA and now I can't get to the internet again. It appears that I'm able to connect to my wireless network with no problem - even when using WPA2, this step worked fine. The problem comes in right after that when I take the static IP out and try to get an IP through the DHCP of my primary router. It gives me an IP but it never says anything for the default gateway and I can't get to the internet.
I've looked around trying to find out what's going on but I haven't had any luck yet. Any help or ideas would be greatly appreciated. Thanks![/b]
Last edited by Supermercado on Thu Feb 21, 2008 18:39; edited 1 time in total
Posted: Thu Feb 21, 2008 16:50 Post subject: Network
I've recently added 2 (Cisco) Linksys WRT-54GL (flashed to dd-wrt v23sp2) and a WAP54G (v24 rc6 micro) that is acting.
This is replacing some Planet WMRT-414 AP's damaged by power disruptions/spikes.
All of this sits on top of my IPCop 1.4.18 firewall/gateway/DHCP/DNS/etc, newly setup on new hardware.
Prior to replacing the old AP's, everything worked fine. IPCop's a system I've used with great sucsess for several years, without much trouble.
Now I can only get HTTP & HTTPS traffic up to my IPCop box (192.168.2.1/255.255.255.0), but nothing else.
I've followed instructions in this forums, and all 3 AP's are set up as Gateway, Client Bridge. This was the only combination I could use to establish connections. Added MAC's of other AP's in WDS LAN's
Please help me troubleshoot my network.
What am I missing? I feel it could a simple setting somewhere, but find it frustrating to find