search for: p2pwall

The version of the ''firewall'' script in CVS (/Shorewall project) is capable of integration with p2pwall (http://p2pwall.sourceforge.net). The ''rules'' file in CVS contains updated help information. The ''releasenotes.txt'' file in CVS gives the simple instructions for setting up Shorewall to work with p2pwall. Note: I have confirmed that Shorewall passes connection...

Still in beta testing, but it works: http://www.lowth.com/p2pwall/ftwall/ Thought you would like to know... gypsy _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

...: 1. The definition of the ROUTE_FILTER option in shorewall.conf has changed as described in item 8) above. New Features: 1. A new QUEUE action has been introduced for rules. QUEUE allows you to pass connection requests to a user-space filter such as ftwall (http://p2pwall.sourceforge.net). The ftwall program allows for effective filtering of p2p applications such as Kazaa. For example, to use ftwall to filter P2P clients in the ''loc'' zone, you would add the following rules: QUEUE loc net tcp...

...ase. Migration Issues: 1. The definition of the ROUTE_FILTER option in shorewall.conf has changed as described in item 9) above. New Features: 1. A new QUEUE action has been introduced for rules. QUEUE allows you to pass connection requests to a user-space filter such as ftwall (http://p2pwall.sourceforge.net). The ftwall program allows for effective filtering of p2p applications such as Kazaa. For example, to use ftwall to filter P2P clients in your ''loc'' zone, you would add the following rules: QUEUE loc net tcp QUEUE loc net...

...er in /etc/shorewall/zones, this # connection request will be passed # to the rules defined for that # (those) zone(s). # LOG -- Simply log the packet and continue. # QUEUE -- Queue the packet to a user-space # application such as ftwall # (http://p2pwall.sf.net). # <action> -- The name of an action defined in # /etc/shorewall/actions or in # /usr/share/shorewall/actions.std. # # The ACTION may optionally be followed # by ":" and a syslog log level (e.g, REJECT:info or # DNAT:debug). This causes the packet t...

...;'# QUEUE -- Queue the packet to a user-space'' + read first rest + ''['' x# = xINCLUDE '']'' + echo ''# application such as ftwall'' + read first rest + ''['' x# = xINCLUDE '']'' + echo ''# (http://p2pwall.sf.net).'' + read first rest + ''['' x# = xINCLUDE '']'' + echo ''# <action> -- The name of an action defined in'' + read first rest + ''['' x# = xINCLUDE '']'' + echo ''# /etc/shorewall/actions or...

I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled