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 3/4] ipv4: add option to drop gratuitous ARP packets
Date: Wed, 04 Nov 2015 17:19:53 +0100 [thread overview]
Message-ID: <1446653993.17416.3.camel@sipsolutions.net> (raw)
In-Reply-To: <alpine.LFD.2.11.1504111340170.2449@ja.home.ssi.bg>
On Sat, 2015-04-11 at 13:59 +0300, Julian Anastasov wrote:
>
> May be only arptable_filter can help here to
> protect ARP?
>
Finally reviving an ancient thread ...
I checked, butI don't see a way to match tip==sip. You can match on
each, but not against each other.
johannes
next prev parent reply other threads:[~2015-11-04 16:19 UTC|newest]
Thread overview: 22+ 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
2015-04-10 7:54 ` Johannes Berg
2015-04-10 7:54 ` [PATCH 2/4] ipv6: " Johannes Berg
2015-04-10 7:54 ` Johannes Berg
2015-04-10 7:54 ` [PATCH 3/4] ipv4: add option to drop gratuitous ARP packets Johannes Berg
2015-04-10 7:54 ` Johannes Berg
2015-04-10 12:56 ` Sergei Shtylyov
2015-04-10 12:56 ` Sergei Shtylyov
2015-04-10 13:11 ` Johannes Berg
2015-04-11 10:59 ` Julian Anastasov
2015-04-13 11:17 ` Johannes Berg
2015-04-13 11:17 ` Johannes Berg
2015-11-04 16:19 ` Johannes Berg [this message]
2015-04-10 7:54 ` [PATCH 4/4] ipv6: add option to drop unsolicited neighbor advertisements Johannes Berg
2015-04-10 7:54 ` 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
2015-04-11 10:39 ` Julian Anastasov
2015-04-11 10:39 ` Julian Anastasov
2015-04-13 10:57 ` Johannes Berg
2015-04-13 12:04 ` Julian Anastasov
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=1446653993.17416.3.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 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.