TomatoUSB

Hi all.
I have the following config:
Router: Asus RT-N16 With latest Toastman's at this date. (1.28.7496)
I have some computers, both wired and wireless, most with static DHCP.
I have 2 DLINK DAP-2553: One connects by ethernet to the RT-N16 and acts as an AP; other connects to that DAP-2553 as a wireless client.
Both os them have static DHCP also.
One computer P5, connects to that wireless client.

Everything is good so far.

The problem:
If P5 has dynamic DHCP on the RT-N16, everything is good.
If P5 has Static DHCP set on the RT-N16, this happens: On P5 I can browse all computers via Windows 7 explorer (ex.: \\computer_name), but i have no internet access. If i use Dynamic DHCP on the RT-N16, then P5 behaves normally, thus, having internet access again.

As soon as i change the settings in the RT-n16 to static dhcp for that computer (P5), i loose internet access.

Any ideas?… could this be a bug in Toastman's firmware, or something wrong in my configuration?

Note: Static DHCP works good on all other computers that do not go through the wireless client.

Thanks in advance.

Ricardo Santos.

No one has any insight on this?… Maybe one of the developpers?

Thanks.

Hey ricardjs - I can confirm I have the same issue on a very similar configuration — I have two routers:

E4200 running Tomato Firmware v1.28.0500 MIPSR2Toastman-RT-N K26 Std
WRT54G v4 running Tomato Firmware v1.28.7821 MIPSR1-Toastman-ND K26 Mini

The WRT is set up as a wireless Ethernet bridge connecting back to the E4200. I have numerous devices connected to the WRT, including a Raspberry Pi. When I enable static DHCP for the Raspi on the E4200, it gets the correct static address, but loses Internet connectivity. Local network connectivity still works. Reverting to dynamic DHCP restores Internet connectivity.

I can't tell you what to do to resolve it, though. The problem isn't apparent when plugging the same device into the E4200 w/ static DHCP enabled, so it seems to be an issue w/ the wireless client/bridge configuration in combination w/ static DHCP.

have you changed the mode of the ethernet bridge from 'gateway' to 'router' on the advanced/routing tab?
have you set the ethernet bridge up so that gateway and dns are both pointing to your main router (e4200)?

i'm not claiming this will fix th eproblem - i'm only trying to delineate some possible variables. i have a number fo ethernet bridges that seem to work without difficulty (or at least with out the difficulty that you are describing) with the above settings.

thanks

(forgot I had previously created this account… I'm leifm)

I had high hopes for your suggestion ghoffman, since I had done neither of those things actually. At your suggestion, I did make those changes, but unfortunately the behavior is still the same.

I'm not exactly a network engineer so frequently I'm not 100% sure what I'm doing. I also tried disabling "DHCP Routes" under Advanced/Routing, since nobody on the Internet seems to know what it actually does, but that didn't seem to have an effect :)

As I said though, everything seems to work fine, *provided* that I don't use static DHCP for anything connected to the bridge. Static DHCP doesn't cause any probs for devices connected directly to the router/gateway.

What are your devices & what firmware do you use for them?

(Also, despite my previous post where I say that both of my devices are using toastman builds, this is only *because* I noticed this particular issue & updated the firmware on both devices. Previously I had been using an older non-N toastman build on my E4200 and the most current vanilla tomatoUSB on my WRT. Had the same problem in that configuration.)

Good morning (here at least)!

Just to give some more information to this thread: i still haven't found any way to circumvent this, unless keeping the other side of the bridgen (dlink bridge) with a static ip.

Regards,

Ricardo.

As I understand you have this:
Internet <-> RT-N16 <->DAP-2553 (wireless) DAP-2553

Try RT-N16 (wireless) DAP-2553 and see if the problem still exists.
Make sure your RT-N16 IP is listed in one of your static DNS slots on the DAP-2553. Maybe also put the other DAP-2553 IP in there as well. I also throw in 8.8.8.8 on my AP.

I want to say I had similar problems when I first set up my AP but I can't remember.