TomatoUSB

i have been a habitual upgrader on my e3000 through all the recent shibby and toastman builds. i appreciate all the work that has gone into these buids and to tomatousb in general.
sometime, over the past month, my home network has lost the ability to ping from one network device to another. it'snot a very complciaed stup and i'll try to describe it here:
cable modem at 192.168.100.1

e3000 running shibby k26usb 083V vpn build (but i'mnot using vpn) as main gateway for home network at 192.168.1.1, getting wan IP using dhcp, and handing out lan addresses in the range 192.168.1.101-199.

1 wired computer to this gateway getting ip by dhcp (current .110)
1 long ethernet cable from this gateway to a wireless access point on the third floor (wrt120n, stock firmware, routing off, firewall off)
many wireless clients connecting to the AP at using G or N protocols, wpa2 personal/aes security.

all clients get dhcp addressed from e3000, and can get out to the internet fine.

but: clients cannot ping eachother:
if i'm on a wireless notebook (192.168.1.120) i can't ping another wireless notebook (192.168.1.151) and vice-versa.
but: if i telnet into the e3000, i can ping either notebook from the router, and then FOR JUST A FEW MINUTES the wireless notebooks can ping eachother.

i am nearly certain that i used to be able to ping any device (that was set up to respond to ping) on the network at any time. i think this new behavior started sometime over thepast month.

any hints?
thanks in advance
george hoffman

Has AP Isolation been enabled in Advanced/Wireless by any chance?

toastman:
your intuition was correct - but the ap isolation was set on the wireless AP (stock wrt120n). i had checked and rechecked, rest and reconfigured, flashed and reflash tomato on the e3000 to no avail.

duh.

i must have been fooling around witht he AP at som epojnt and gotten distracted.

thank you for you excellent software development.
george

Just wanted to say thanks for the push in the right direction, E3000 here as well, none of my wireless computers would communicate with each other. I had ruled out AP Isolation after verifying it was "off" in the web interface, and figured that there must be some other security setting. Based on the message I gave it a try to enable AP Isolation, then disable it, which resolved the problem.

I also didn't remember seeing this behavior before either, but as we both have E3000 routers, perhaps it's a quirk of the model.