From: Sudheimer <sudix@f3g.de>
To: linux-diald@vger.kernel.org
Subject: How to ignore incoming packets
Date: Wed, 27 Aug 2003 16:19:24 +0200 [thread overview]
Message-ID: <3F4CBDEC.6F623298@f3g.de> (raw)
Hi everyone,
I would like diald to ignore any incoming connection attempts.
For example if I get incoming packages to my tcp port 23 (telnet), they
fit the default rule of diald and keep up the line for 2 minutes (keepup
tcp 120 any). I do not have telnetd running on this port and have also
an ipchains packet denying these packets.
Nevertheless these packages match the final catch-all rule of diald and
keep up the line for 2 minutes (keepup tcp 120 any).
On the other hand, I do not want to define a rule like "ignore telnet
packets" because this would also match my own telnet-sessions to remote
telnet servers.
If it were possible for diald to distinguish between incoming and
outgoing packets one could say somthing like "ignore incoming tcp SYN
packets". Is there something like that?
Joachim
next reply other threads:[~2003-08-27 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 14:19 Sudheimer [this message]
2003-08-27 21:36 ` How to ignore incoming packets Mark Frey
2003-08-28 8:19 ` Sudheimer
2003-08-28 11:25 ` Mark Frey
2003-08-28 23:47 ` Mark Frey
2003-08-29 16:34 ` sudix
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=3F4CBDEC.6F623298@f3g.de \
--to=sudix@f3g.de \
--cc=linux-diald@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).