From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Harald Welte <laforge@gnumonks.org>
Cc: Netfilter-devel <netfilter-devel@lists.samba.org>
Subject: Re: [PATCH] don't try to track broadcasts or multicasts (4/4)
Date: 08 Jun 2002 16:51:47 +0200 [thread overview]
Message-ID: <1023547908.19838.46.camel@tux> (raw)
In-Reply-To: <20020608073547.GA1109@naboo.de.gnumonks.org>
On Sat, 2002-06-08 at 09:35, Harald Welte wrote:
> hm. I would generally agree with you, but there is one issue which
> needs to be looked into before considering this patch:
>
> What happens if some client sends an ip-unicast diagram as link layer
> broadcast? How does the linux stack react to this?
>
> If the packet is processed/routed the same way like any other ip-unicast
> link-layer unicast packet, we still need to do tracking of broadcast
> packets.
>
> Could you try to look into that and keep us posted?
Hmm why didn't I think about that?
I've done some simple testing and the results are:
TCP:
send SYN to ll broadcast: ignored
send SYN,ACK to ll broadcast: ignored
UDP:
packet sent to ll broadcast: accepted
ICMP:
echo-request sent to ll broadcast: accepted
echo-reply sent to ll broadcast: accepted
port unreachable sent to ll broadcast: accepted
I havn't done any tests with multicast ll addresses.
Seeing these results there's not much need for a patch of this kind.
TCP ll broadcasts are extremely rare. almost all ll broadcasts here are
UDP.
It was a nice thought but doesn't work in the real world.
--
/Martin
Never argue with an idiot. They drag you down to their level, then beat
you with experience.
next prev parent reply other threads:[~2002-06-08 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 12:24 [PATCH] don't try to track broadcasts or multicasts (4/4) Martin Josefsson
2002-06-08 7:35 ` Harald Welte
2002-06-08 14:51 ` Martin Josefsson [this message]
2002-06-09 17:18 ` Harald Welte
2002-06-09 19:35 ` Henrik Nordstrom
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=1023547908.19838.46.camel@tux \
--to=gandalf@wlug.westbo.se \
--cc=laforge@gnumonks.org \
--cc=netfilter-devel@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 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.