From: Askar <askarali@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: droping too many ports
Date: Fri, 24 Sep 2004 02:45:43 +0600 [thread overview]
Message-ID: <a0f69e504092313454a9090b3@mail.gmail.com> (raw)
hi all
what if I do (and im doing this from last two hours ;))
iptables -A FORWARD -p tcp --dport 31000:65500 -j DROP
iptables -A FORWARD -p udp --dport 31000:65500 -j DROP
yes I am Droping too many ports at once, (actually its default ACCEPT
machine), as far I know not a single well known service is running on
port above 31000?
Actaully I duno what to do coz im watching (through tcpdump )lot of
clients accessing higher ports, thats why I puts these rules.
iptables -L -nvx gives too many counts whenever I checked, especailly
numbers are very high for UDP "udp --dport 31000:65500 -j DROP"
Im i doing right thing? (see im getting counts on it )
Am I droping some ligitimate packets?
or ours clients (sitting on M$ OS) are infected?
may I extend the rules to INPUT and OUTPUT ?
regards
tired :(
--
(after bouncing head on desk for days trying to get mine working, I'll make
yer life a little easier)
next reply other threads:[~2004-09-23 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 20:45 Askar [this message]
2004-09-23 20:51 ` droping too many ports Gavin Hamill
2004-09-23 21:01 ` Jason Opperisano
2004-09-23 21:14 ` Aleksandar Milivojevic
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=a0f69e504092313454a9090b3@mail.gmail.com \
--to=askarali@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.