I've successfully loaded the latest WhiteRussian build on my WRT54G and have set it up in bridged client mode as per the ClientModeHowTo.  Everything is working, in so far as devices plugged into the lan ports can connect to the internet router and pull an IP address via DHCP, etc.  BUT, the communication only seems to be uni-directional.  I cannot connect back to any devices on the bridge side from clients of my main access point.  My intended use for this is to connect an ethernet capable laser printer to my wifi network.  The printer pulls an IP and I can see it as a client of my primary access point, but printing doesn't work and I can't access the printer's web status page.  I thought it might be a firewall issue, so I disabled the firewall script in /etc/init.d but still no dice.  Unfortunately, I am not a network engineer so I need some help.  Any ideas on what else I might need to do?  Or, if you need more info, what do you need?

I had another thought, which I haven't tried yet...  I remember from hacking my TiVo that I had to disable iptables before I could connect to it, perhaps I need to disable iptables in OpenWrt as well?

Thanks a bunch, in advance, for any advice.

if it pulls an IP address from DHCP, can you ping it?

not being able to access the web admin console for your printer is not a good sign... i would expect it is something to do with your firewall.user file or perhaps your iptables settings.  disabling your firewall is a no-no in most cases, but if you are behind another router with a firewall than it should be fine.

to kill your firewall you may want to type 'ps' to see which programs are running, and then issue a 'kill -9 (pid)' to disable it.  i've found that the init.d folder is extremely unhelpful (in my experience)

Yes, this will be connecting to another access point which is behind a firewall, so I'm not too worried about killing it.  How do I permanently disable the firewall?  Killing it with a ps / kill is all well and good, but if the router gets rebooted...  As to answer the ping question, no, I cannot ping it.  I get "no route to host" and "host is down" messages.

Thanks!

I thought I might have it.  I disabled the firewall again, by replacing both iptables and firewall.user with a simple shell script that does an exit 0 (a little trick I learned in my tivo hacking).  I was able to ping the printer and access its web page after that, but actually printing didn't work.  I rebooted the printer (but not the router), just for fun, and although it once again pulled an IP from DHCP, I could no longer ping it or hit the web page.  I guess I still need help...

OK, I give up.  I think I may have something wrong with the printer now, though it was working before I started messing with this stuff.  Go figure.  I tried a commercial wifi bridge, and I can access it's config menu and anything else attached to it, but not the printer.