From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: netfilter@lists.samba.org
Subject: simple rules and unexpected traffic
Date: Thu, 4 Jul 2002 10:10:48 -0400 [thread overview]
Message-ID: <20020704141048.GB19446@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 2618 bytes --]
Hi,
I use a simple set of iptables rules for my laptop to reject everything
from outside using ip_conntrack (from the howto) :
# Generated by iptables-save v1.2.6a on Thu Jul 4 09:54:11 2002
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [43965:4118502]
:block - [0:0]
-A INPUT -j block
-A FORWARD -j block
-A block -m state --state RELATED,ESTABLISHED -j ACCEPT
-A block -i ! eth0 -m state --state NEW -j ACCEPT
-A block -i eth0 -m limit --limit 3/hour -j LOG --log-prefix "Bad packet from eth0:"
-A block -i ! eth0 -m limit --limit 3/hour -j LOG --log-prefix "Bad packet not from eth0:"
-A block -j DROP
COMMIT
# Completed on Thu Jul 4 09:54:11 2002
I have a ADSL connection and only a hub between my laptop and the
ADSL-modem. Recently something changed, I guess on the router from my
provider and now I see unexpected traffic.
I see it with the eth0 monitor in gkrellm and with iftop but not with
lsof -i.
I was not expecting this traffic and the pattern seems strange : a
constant 20kB incoming traffic during a few seconds. So I started
looking closer. With ethereal I saw that it was a kind of flooding
most of the time a lot of SYN packet but also netbios ....
Each time both IPs are not one of my computer. For example I see during
one of this flooding with 'tcpdump -c 2 -e'
tcpdump: listening on eth0
10:00:39.946940 0:0:c:c3:a:88 ff:ff:ff:ff:0:30 ip 62: 216-203-233-196.customer.algx.net.3574 > adsl-216-158-52-76.cust.oldcity.dca.net.www: S 2011680397:2011680397(0) win 16384 <mss 1460,nop,nop,sackOK> (DF)
10:00:39.949401 0:0:c:c3:a:88 ff:ff:ff:ff:0:30 ip 62: 216-203-233-196.customer.algx.net.3574 > adsl-216-158-52-76.cust.oldcity.dca.net.www: S 2011680397:2011680397(0) win 16384 <mss 1460,nop,nop,sackOK> (DF)
I am not sure how to interpret 'ff:ff:ff:ff:0:30' is it a kind of
broadcasting at the ethernet level ?
Why can I see these packets that are not for me ?
Why this traffic is not dropped by netfilter ?
It seems to be a miss-configuration of my ISP router, no ? I believe it's
harmless (except for my bandwidth) but I don't understand why I see
(with gkrellm) this traffic which seems to be rejected before netfilter.
Is gkrellm using packets information before the iptable processing ?
I have tried to set /proc/.../eth0/rp_filter to 0 without any
difference.
Thanks,
Christophe
--
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
Dogs come when they're called;
cats take a message and get back to you later. --Mary Bly
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-07-04 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 14:10 christophe barbé [this message]
2002-07-04 21:01 ` simple rules and unexpected traffic christophe barbé
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 22:35 George Vieira
2002-07-04 22:45 ` christophe barbé
2002-07-04 22:54 ` Jan Humme
2002-07-04 22:57 ` christophe barbé
2002-07-04 23:44 George Vieira
2002-07-04 23:47 ` christophe barbé
2002-07-04 23:54 George Vieira
2002-07-05 0:34 ` christophe barbé
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=20020704141048.GB19446@localhost \
--to=christophe.barbe.ml@online.fr \
--cc=netfilter@lists.samba.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