WiFi Client Bridge won't hold IP [DD-WRT]

So I have this router, reflashed with DD-WRT, acting as a bridge between ath0 (rest of network) and eth0 (Xbox 360).

DHCP is handled by the primary router (connected to WAN, the WiFi AP and other switches), but most devices on my network (exception being guests' computers, PSPs, DSs, etc.) including my 360 have static IPs, subnets and primary gateways/DNS records entered.

Anyway, if I power on the client bridge and the 360, after about a minute (boot time for bridge), I can connect to Live, but even if network usage remains low (i.e. not playing with the 360, just playing single player/leaving it at dashboard/whatever) I will eventually get signed out of Live and disconnected from the rest of the network. Other PCs can no longer connect to the bridge's web interface either. Powercyling the bridge solves the problem.

Logging on my network can't be done for beans and due to security settings, subnets and the randomness factor, packet sniffing is going to have to probably be a last resort. Therefore I'm asking for help identifying where the problem is. I can lo longer ping the bridge, but it still claims to be connected, so I reckon it's probably something to do with the router , rather than bridge settings as it starts off working OK, but WHAT!?

QoS is disabled by the way.

Any ideas?
This plan to avoid paying for a wireless adapter has backfired like a baked bean vindaloo.

Thanks in advance!

 

OK...

Left it running since before I went to a LAN, plugged my Xbox back in and played an hour of Halo 3.

Therefore, I have this one down. First I reset the router to (DD-WRT) 'factory' defaults. Then 'upgraded' the firmware to 070516B (was on 071010).
Disabled STP in Setup -> Basic Setup
Increased TX Power to 18 in Wireless -> Basic Setup
Changed Operating Mode to RIP2 in Setup - Advanced Routing.

Also, these are the required ports that need to be allowed through your firewall (or forwarded, if NAT isn't working):
UDP 88, UDP 3074 and TCP 3074.

Hope this works now. If so, I've saved £60 (got the router for free. )

 

I'm having a similar problem with my OpenWRT which provides WAN to another subnet. In the configuration:

Code:

WAN → modem → router (dd-wrt) → 2nd router (openwrt) → client

It works whilst something is accessing WAN, but after some downtime it decides to bugger off the network (emphasis mine):

Code:

root@OpenWrt:~# iwconfig wl0
wl0       IEEE 802.11-DS  ESSID:"dd-wrt"  
          Mode:Repeater  Frequency:2.437 GHz  [b]Access Point: Not-Associated   [/b]
          Tx-Power:19 dBm   
          RTS thr:2347 B   Fragment thr:2346 B   
          Encryption key:<too big>
          Link Signal level:-82 dBm  Noise level:-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:3513  Invalid misc:0   Missed beacon:0

Which is slightly worrying. I'm going to set up a logging script to see what happens, I'll report back when I have some results.

You should probably ssh/telnet into the router and have a look at iwconfig and see if you are having the same problem as me.

EDIT:

I've written the script, just ssh/telnet in and run it

Code:

#!/bin/sh
LOGFILE=/var/log/iwconfig.log
INTERFACE=wl0

# I wouldn't recommend editing past here

RES=1

while [ $RES -gt 0 ]; do
      iwconfig ${INTERFACE} | grep "Not-Associated"
      RES=$?
      sleep 1
done

echo "Network lost on `date`" >> ${LOGFILE}

 

Code:

~ # iwconfig ath0
ath0      IEEE 802.11g  ESSID:"Markus"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:C0:49:ED:11:94
          Bit Rate:36 Mb/s   Tx-Power=14 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:<snip>
          Power Management:off
          Link Quality=31/98  Signal level=-64 dBm  Noise level=-95 dBm
          Rx invalid nwid:18  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

~ #

I'm starting to believe it's now fixed.
I'd say try changing it from a repeater to a client-bridge and make sure RIP2 is enabled. Worked much better for me after I got a firmware which worked (it's a Fonera - quite picky about which version of DD-WRT I use)