Hi All, Well... I thought I was networking savvy. I guess not! ... Because I've tried and read EVERYTHING! I'm down to having to ask for help! Please! I'm using a E4200 with Tomato RAF v1.28.9013 as my primary router now. It works great; everything connects and B, G, & N function well per whatever device connects. I used to have a WRT54Gv2 with the stock v1.28 Tomato as my primary. I have a media rack in the living room that relied on a wireless bridge also running the stock Tomato v1.28 on a WRT54GL v1.1 in, of course, 'Wireless Bridge' mode. The devices that were connected to it physically (DirecTV receiver and Samsun Blu-Ray Player) were able to access the primary router, get a DHCP static assignment, and hit the Internet without issue. I was using G, of course, on Channel 6, with WPA/WPA2 Personal & AES on the main router and WPA Personal & AES on the Bridge. This was the only that seemed operable. The bridge was also set to use the same channel as the primary router, same SSID, etc. Main router is at 192.168.1.1; bridge is at 192.168.1.2. Once I upgraded to the E4200 and installed Tomato RAF, I have not been able to get the WRT54GL Wireless Bridge (I switched out the WRT54Gv2 to the WRT54GL v1.1 for the bridge when I upgraded the main router) to see the Internet. It connects to the WAN/LAN, but will not allow the devices physically connected to see the Internet even though the Bridge has been set to use 126.96.36.199 as the gateway and DNS. I have flashed the WRT54GL (the bridge) to the standard Tomato v1.28 and also 'tomato.RAF-K24-1.28.8515_lite' and regardless of firmware, they both seem to connect to the WAN/LAN, but cannot get my racked media devices to see the Internet for some reason. I'm totally stumped -- there shouldn't be much to setting up a wireless bridge. <g> I've put the bridge in 'Router' mode and to not use 'Internal DNS' when using the latter firmware. I thought that just the stock Tomato v1.28 on the bridge should be compatible with Tomato RAF. But, to make things mesh all the more, I flashed to 'tomato.RAF-K24-1.28.8515_lite' on the WRT54GL bridge and set it up the same way. Same results... Both firmwares will not allow devices plugged into the bridge to access the Internet. I even tried dropping back to the WRT54Gv2, trying both firmwares again... Same results. That confirmed it wasn't a hardware issue. So, I have to suspect that I have something set up incorrectly on the main router -- the E4200 running Tomato RAF v1.28.9013. I'm not sure what, but since stock Tomato 1.28 on both, one as an AP and one as a Wireless Bridge worked fine, that it has to be something to do with the E4200's config. At present, I have the E4200 Router/AP at Tomato RAF v1.28.9013 and the WRT54GL Wireless Bridge at Tomato.RAF-K24-1.28.8515_lite. Again, I am able to see and access the bridge (via the E4200) and the devices connected to the WRT54GL bridge can access all but the Internet. Sorry for all the redundancy, but I wanted to provide as much detail as possible. Any help would be GREATLY appreciated! I love the new E4200 and having N up on the WAN/LAN, but I'd like to get a bridge back and operable as well, if only running G. Figure it's something simple I'm missing 'cuz I've been using these routers and Tomato for over 5 years now and never had an issues. Thanks much!