So are you firewalling the WAP or just using a separate IP range?
Worse comes to worse, assuming you are double NAT'd with the WAP doing DHCP for it's
subnet. I'd setup the WAP as Gateway, DNS & DHCP server and it's DNS client pointing
to gateway router. This should properly forward DNS requests to the main router
rather than relying on the WAP subnet clients being able to talk to main router by
NAT. If the WAP has it's firewall enabled, disable it long enough to establish if
it's blocking anything.
On that path, setting up Syslog setup for full logging (high+deny/accept) output from
from all routers to a central syslog server (kiwi freeware version, capture events to
file) running on a LAN PC would be a a good way to diagnose what's up. If you go this
route I'd say install latest supported DD-WRT on all routers capable of running it if
you have not already done so.
On 4/24/2010 3:35 PM, Winterlight wrote:
At this point (w/o doing the actual troubleshooting session) I'd say
that you just collapse your networks into one flat 192.168.1.x (you
don't need multiple networks anyway-not like you're firewalling and
enforcing security policies b/w them anyway, are you?)
I do need them, because I have employees, friends and family using my
WAP that I don't want to even see my LAN. The TV and the BRD I can solve
most of the problem just by plugging the media devices switch into the
WAN, because they don't need to access my LAN, but the WD live does.
For the time being I have done this, although I am going to try and
forward the TV devices IP number to the WAN as a gateway and see what
happens.
