netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Julian Anastasov <ja@ssi.bg>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	matti.gottlieb@intel.com
Subject: Re: [PATCH 1/4] ipv4: add option to drop unicast encapsulated in L2 multicast
Date: Mon, 13 Apr 2015 12:57:16 +0200	[thread overview]
Message-ID: <1428922636.2355.7.camel@sipsolutions.net> (raw)
In-Reply-To: <alpine.LFD.2.11.1504111305440.2449@ja.home.ssi.bg>

Hi Julian,

> > Hm. I didn't see this in my testing so far, but I only enable this
> > temporarily, so perhaps by that time it was already done.
> 
> 	I didn't tested it myself, may be you can try:
> 
> other_host_on_LAN# arp -d patched_box
> other_host_on_LAN# arping -c 1 -I eth0 patched_box
> 
> 	There must be reply for broadcast requests.

Sure; I would have expected this to have broken my network but as I
said, it was only enabled temporarily.

> > On the other hand, there's not all that much reason not to put this into
> > ip_rcv_finish(), we already touch the rt->rt_type there for MIB
> > counters. I'll look into that.
> 
> 	May be in ip_local_deliver_finish because:
> 
> - ip_forward() already has PACKET_HOST check.
> 
> - for broadcast/multicast dests we do not care
> 
> - CLUSTERIP works in LOCAL_IN (after ip_rcv_finish), LOCAL_IN
> is here: ip_rcv_finish->dst_input->ip_local_deliver->
> ip_local_deliver_finish

It's just that the later this is, the more nervous I get about it being
really effective. :)

I'm willing to discount the CLUSTERIP case, it seems insane to want to
run CLUSTERIP over wifi on a network that explicitly limits multicast.

Other than that, do you see any reason for not putting it in
ip_rcv_finish()?

johannes

  reply	other threads:[~2015-04-13 10:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  7:54 [PATCH 1/4] ipv4: add option to drop unicast encapsulated in L2 multicast Johannes Berg
     [not found] ` <1428652454-1224-1-git-send-email-johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-04-10  7:54   ` [PATCH 2/4] ipv6: " Johannes Berg
2015-04-10  7:54   ` [PATCH 3/4] ipv4: add option to drop gratuitous ARP packets Johannes Berg
     [not found]     ` <1428652454-1224-3-git-send-email-johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-04-10 12:56       ` Sergei Shtylyov
2015-04-10 13:11         ` Johannes Berg
2015-04-11 10:59     ` Julian Anastasov
     [not found]       ` <alpine.LFD.2.11.1504111340170.2449-c1lBKlETG9EWAawoAK+ZAw@public.gmane.org>
2015-04-13 11:17         ` Johannes Berg
2015-11-04 16:19       ` Johannes Berg
2015-04-10  7:54   ` [PATCH 4/4] ipv6: add option to drop unsolicited neighbor advertisements Johannes Berg
2015-04-10 12:19 ` [PATCH 1/4] ipv4: add option to drop unicast encapsulated in L2 multicast Julian Anastasov
2015-04-10 13:10   ` Johannes Berg
     [not found]     ` <1428671435.1890.22.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-04-11 10:39       ` Julian Anastasov
2015-04-13 10:57         ` Johannes Berg [this message]
     [not found]           ` <1428922636.2355.7.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-04-13 12:04             ` Julian Anastasov

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=1428922636.2355.7.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ja@ssi.bg \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matti.gottlieb@intel.com \
    --cc=netdev@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).