From: "Matias Bjørling" <mb@ncparty.dk>
To: netfilter@lists.netfilter.org
Subject: Yet Another Kazaa Issue
Date: Tue, 19 Nov 2002 21:55:22 +0100 [thread overview]
Message-ID: <001001c2900d$fa96b2f0$0200000a@parseerror.dk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
Hey
Im trying like hell to get Kazaa to stop connect successfully... Whatever i do, blocking port 1214 in ANY possible way, it still resist and connect sucessfully, even with thoes firewall rules
iptables -A FORWARD -m string --string "X-Kazaa-Username:" -j DROP
iptables -A FORWARD -m string --string "X-Kazaa-Network:" -j DROP
iptables -A FORWARD -m string --string "X-Kazaa-IP:" -j DROP
iptables -A FORWARD -m string --string "X-Kazaa-SupernodeIP" -j DROP
iptables -A FORWARD -m string --string "Kazaa" -j DROP
Chain FORWARD (policy DROP)
target prot opt source destination
DROP all -- anywhere anywhere STRING match X-Kazaa-Username:
DROP all -- anywhere anywhere STRING match X-Kazaa-Network:
DROP all -- anywhere anywhere STRING match X-Kazaa-IP:
DROP all -- anywhere anywhere STRING match X-Kazaa-SupernodeIP
DROP all -- anywhere anywhere STRING match Kazaa
LOG all -- anywhere anywhere STRING match User LOG level warning
DROP all -- anywhere anywhere STRING match User
state_chk all -- anywhere anywhere
It catch the "kazaa" thingie on the homepage... But.. anyhow it somehow seem to connect to the supernode outside... Im getting nuts.. Why can't i stop it?.. What am i doing wrong.. I tried to ages now.. and it dont work :(
Any help will be appreciated :D
Thanks
- SilverWolf
[-- Attachment #2: Type: text/html, Size: 3828 bytes --]
next reply other threads:[~2002-11-19 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 20:55 Matias Bjørling [this message]
2002-11-22 1:36 ` Yet Another Kazaa Issue Luciano Ruete
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 20:55 Matias Bjørling
2002-11-21 22:15 ` Aldo S. Lagana
2002-11-22 11:19 ` Maciej Soltysiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001001c2900d$fa96b2f0$0200000a@parseerror.dk' \
--to=mb@ncparty.dk \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox