Print

[AMDinside]

I don't know if anyone here is familiar with dd-wrt.  It is a 3rd party firmware for the Linksys WRT54G routers.  Anyway, I snagged a WRT54GS router and loaded the dd-wrt firmware onto it with the intention of using it as a wireless network bridge for my Xbox360.  I managed to get it configured and connected to my existing wireless network(netgear WGR614).  The problem is that even though it is connected to the wireless it refuses to pass internet access through to the ports on the WRT54GS.

If anyone is familiar with dd-wrt and can lend a hand I'd appreciate it.

[GenTsoChiken]

i believe noodle has quite a bit of experience with this but hes hard to get a hold of these days.

[PsiFire]

So it won't pass internet to the PHYSICAL ports on the router? Thats odd. Sure the router works properly? Did you buy it new or used? Does the NIC connected to the router on the ether report a connection (light on the NIC itself). I use DD-WRT. It's awesome. Far favor it over the stock ROM.

[Popsikle]

hmm, I had to setup mine wierd to do so.. Ill look at my config and get back to you.

[PsiFire]

Oh wait. I just reread the OP and realized you are using it as a bridge and not a typical router/firewall combination. The configuration is DEFINITELY different. I will see about hooking my router up later today (after sleep) to see if I can find out more about the settings and play with a bridge config here.

[PsiFire]

Here's a link to review on the subject: http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge

[AMDinside]

Thing is, I followed those directions to a T.  Thats how I found out how to configure it, but I still cant get the internet to pass through.

[PsiFire]

Well, check the obvious shit. Can you ping the gateway from the machine you are using? Are you using DHCP or static IPs on the connected machine?

I just setup a WRT54GL today with DD-WRT v23 vpn as the receiving end of a wireless bridge and it worked fine. Only time I had problems was when I had set the connecting machine to the wrong IP.

[AMDinside]

I haven't tried pinging the gateway.  The WRT54 is set to use static IP, but any computers connected are set with DHCP.

[PsiFire]

Yeah, both routers should be static. The problem I had was my connected computer was also set to static, when I set it back to DHCP it worked fine. Definitely try pinging around and see what you hit. Also make sure you turn off as much as possible (firewall on the receive side of the bridge, etc) until you find the problem.

In the wireless section of "status" is it showing a decent signal coming from the originating router?

Worst case, bring it in October to LAN and we'll see if we can't figure out the issue there.

[AMDinside]

Both routers are static, with the netgear 192.168.1.1 and the WRT54 192.168.1.2.

The wireless strength shows 4/5 bars, and the connection light is solid so I know it is connected to the network.  I'll have to tinker with it when I get the chance.

[AMDinside]

I got it figured out.  For some reason or another I had to set a static IP for my 360.  Once I set the static IP it worked fine.

[PsiFire]

Thats retarded. Only reason I can think that would happen is if the 360 was setting it's IP wrong and conflicting with one of the routers.

On a side note, I wish there were a way to have the router act as BOTH a router AND bridge, but seems like you can't have the bridged router act as a second tier router making that subnet appear as a single IP instead of having the originating router dish out one IP for each system hooked up on the second side of the net. Might only be possible with a second router.