From: Juergen Schmidt <ju@ct.heise.de>
To: netfilter@lists.netfilter.org
Subject: using iptables states to avoid pppd timeout problems ?
Date: Thu, 21 Nov 2002 16:45:24 +0100 [thread overview]
Message-ID: <3DDCFF94.80A3DBBC@ct.heise.de> (raw)
Hello,
I get an increasing number of reports from people, who have to pay a lot
of money, because their linux router didn't close an open internet
connection. In many cases, those people
just had bad luck, and they received the (dynamic) ip adress of a former
edonkey participant (or any other p2p net). Because edonkey links live
quite long, even after somebody quit the net, clients still send their
requests to this adress.
One strategy to avoid this, is starting ppp with the following option:
active-filter filter-expression
Specifies a packet filter to be applied to data
packets to determine which packets are to be
regarded as link activity, and therefore reset the
idle timer, or cause the link to be brought up in
demand-dialling mode.
The filter-expression is specified in tcpdump syntax. This means it
works like a dumb packet filter. This has the drawback, that established
connections, that match, also do not get counted and might get
interrupted. And it still leaves the door open for a "Enforcement of
Service" attack -- i.e. somebody can keep my link open, by just sending
an unsolicited packet every now and then.
The better way to get hold of this, would be to use something like
iptables/netfilter rules and count only packets of "ESTABLISHED"
connections (or ignore state "NEW").
Is there a way to do this.
Is it perhaps possible to do something like this in iptables PREROUTING
chain? Perhaps mark the packtes as "to be counted" ?
thanks in advance, juergen
PS:
Please CC any answers to me, as I do not regularly read this list.
--
Juergen Schmidt Leitender Redakteur/senior editor c't magazin
Heise Zeitschriften Verlag, Helstorferstr. 7, D-30625 Hannover
Tel. +49 511 5352 300 FAX +49 511 5352 417 EMail ju@ct.heise.de
reply other threads:[~2002-11-21 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DDCFF94.80A3DBBC@ct.heise.de \
--to=ju@ct.heise.de \
--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