Hi Everybody, This ones got my hair falling out. A very simple task, which I've done before.
1 Bering box, 2 NICs (3c905C and rtl8139) This box has no external connection (yet, still no ADSL), just needs to route between the two eth adaptors A D-Link WAP (192.168.51.2) is plugged straight into eth1 (192.168.51.1) A WinXP (192.168.50.30) box is crossed over into eth0 (192.168.50.1) Hosts.allow contains ALL: 192.168.50.0/255.255.255.0 ALL: 192.168.51.0/255.255.255.0 Two zones in shorewall, dave and alex (+fw). Dave is bound to eth1, alex to eth0. Policy is: Dave alex ACCEPT Alex dave ACCEPT Fw all ACCEPT All fw ACCEPT The routes are correctly set, all ping requests flash a light on a NIC somewhere. Fw can ping it's interfaces, the WAP and the XP box. The XP box can ping both interfaces of the FW box. A wireless client can ping the WAP and the FW box. But that's it. The XP box cannot see the WAP or any wireless clients. I could've sworn this worked on Sunday... I'm not doing any NAT, maybe I have to turn NAT off in shorewall config? Somebody please help, this is driving me nuts... Thanks again, James. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
