From: Johannes Berg
Date: Thu, 4 Feb 2016 13:31:17 +0100
> From: Johannes Berg
>
> In order to solve a problem with 802.11, the so-called hole-196 attack,
> add an option (sysctl) called "drop_unicast_in_l2_multicast" which, if
> enabled, causes the stack to drop IPv4 unicast packets encapsula
From: Johannes Berg
In order to solve a problem with 802.11, the so-called hole-196 attack,
add an option (sysctl) called "drop_unicast_in_l2_multicast" which, if
enabled, causes the stack to drop IPv4 unicast packets encapsulated in
link-layer multi- or broadcast frames. Such frames can (as an a
From: Johannes Berg
Date: Thu, 28 Jan 2016 13:33:33 +0100
> Is there anything I should do about these patches?
>
> I see you marked them as "deferred" in patchwork, but I don't really
> know how you're using that state.
I use it in two situations, the first is the most often used case but
doesn
Hi,
Is there anything I should do about these patches?
I see you marked them as "deferred" in patchwork, but I don't really
know how you're using that state.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.or
Hello,
On Thu, 5 Nov 2015, Johannes Berg wrote:
> From: Johannes Berg
>
> In order to solve a problem with 802.11, the so-called hole-196 attack,
> add an option (sysctl) called "drop_unicast_in_l2_multicast" which, if
> enabled, causes the stack to drop IPv4 unicast packets encapsulat
From: Johannes Berg
In order to solve a problem with 802.11, the so-called hole-196 attack,
add an option (sysctl) called "drop_unicast_in_l2_multicast" which, if
enabled, causes the stack to drop IPv4 unicast packets encapsulated in
link-layer multi- or broadcast frames. Such frames can (as an a