> > I got a bit ahead of myself -- I'm correct that to do this right, you > need policy match. But you should be able to get it to work if we can > determine why your ruleset drops most traffic to/from 192.168.241.65. > Please send me a tar-ball of your /etc/shorewall/ directory. >
>Ah -- I see. eth0:192.168.241.65 is a zone called 'obo'. And there is no >net->obo policy; neither are there any net2obo rules. >Consequently all net->obo traffic is being dropped under the net->all DROP policy. Tom, this last one hit the nail on the head. Added the following rule: ACCEPT net:192.168.10.0/24 obo all And now things work. Thank you for all your help, you solved a problem that I struggled with for weeks. Regards Jan van der Vyver ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
