similar to: block Edonkey

Hello ! I am using shorewall , it is okey. Just i like to forbid edonkey as i did for kazaa using ftwall. Thanks. Wahid.

Greetings, I''ve searched, found ftwall, and some other commercial solutions, but am wondering if anyone on this list has any solutions using a linux firewall to block p2p traffic, more specifically Kazaa. Walter Wickersham _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Hello , I installed Shorewall on a linux RedHat 8.0. No problem , it works very well. I have two interfaces: eth0 : 193.95.47.194 , mask 255.255.255.192 gateway : 193.95.47.193 dns: 193.95.66.10 eth1 : 192.168.54.250 mask 255.255.255.0 (no gateway) all computers in my local network have ip addresses 192.168.54.xx , gateway: 192.168.54.250 , dns:193.95.66.10 almost 100 local machines using

Hello , i have 2 questions 1 - how to use shorewall GUI using webming , i found nothing in the doc. 2 - after starting shorewall , is there a way to see the user connections status? Thanks Wahid

I do not how to use match string to deny kazaa traffic, if I put the word kazaa only http content is deny but the kazaa aplication is running, are there special commands to match string? thanks _________________________________________________________________ Charla con tus amigos en línea mediante MSN Messenger: http://messenger.microsoft.com/es

Hi everybody! I''m very happy with shorewall, seems to safe my computer well, a little bit to well. But i''m sure it''s a mistake of mine: I can''t get edonkey working! They say that edonkey needs the following ports enabled: 4665 udp in / out 3665,4665,7665,8665 udp out 4661,4662,4666 tcp in thats what i wrote in the rules file: ACCEPT fw net

Hi, I''m running mldonkey on same box as shorewall. I follow this http://mldonkey.sourceforge.net/ShorewallConfiguration to open ports for edonkey protocol I add in /etc/shorewall/rules: # eDonkey 2000 ACCEPT net $FW tcp 4662 ACCEPT net $FW udp 4666 but I could not connect to any edonkey server. I check logs and notice that udp traffic on port 4666 is still dropped. Jul 8 22:35:57

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there interest in ipp2p support in Shorewall? While the ipp2p code is not part of the standard kernel.org distributions, my experience is that it is very easy to install and I would be willing to provide support for it if there is interest. See http://rnvs.informatik.uni-leipzig.de/ipp2p/index_en.html for information about ipp2p. - -Tom - -- Tom

10/30/2003 - Shorewall 1.4.8 RC1 Given the small number of new features and the relatively few lines of code that were changed, there will be no Beta for 1.4.8. I am particularly interested in people testing: a) The interface to ''ftwall'' b) Handling of <zone>_frwd chains (those of you who had problems with 1.4.7b or that have reported extra rules in these chains).

----- Original Message ----- From: "Jerry Vonau" <jvonau@shaw.ca> To: "Mailing List for Shorewall Users" <shorewall-users@lists.shorewall.net> Sent: Thursday, August 19, 2004 08:06 Subject: Re: [Shorewall-users] Two Links and DNAT > > > > Btw, by "shorewall show nat" I just noticed that I was doing snat only > > for packets comming

Currently at: http://shorewall.net/pub/shorewall/shorewall-1.4.8 ftp://shorewall.net/pub/shorewall/shorewall-1.4.8 Coming soon to a mirror near you. This is a minor release of Shorewall. Problems Corrected since version 1.4.7: 1) Tuomo Soini has supplied a correction to a problem that occurs using some versions of ''ash''. The symptom is that "shorewall start"

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

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/

I am puzzled. I started setting up a new box last week with Linux 2.6.10. Everything was working fine until I went to start shorewall, when all network traffic stopped. I have little doubt that it is because I missed something in configuring the machine. I''m running shorewall 2.2 and the zone, policy, and rules files are cut and paste from a machine that has been running for over a

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

Hi all, I was trying to test ROUTE specific code with a multi-isp serviced box. There is a bug somewhere, but I''m not able to understand what the real problem is: when I issue a "shorewall show capabilities" I get: Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Shorewall has