summaryrefslogtreecommitdiffstats
path: root/drivers/net/loopback.c
diff options
context:
space:
mode:
authorSara Sharon <sara.sharon@intel.com>2015-11-19 11:53:49 +0200
committerEmmanuel Grumbach <emmanuel.grumbach@intel.com>2015-12-16 10:19:53 +0200
commitc97dab40796c59a4b03c532603e837077718fb81 (patch)
tree2276f722f30d18fc1048c66a5f646d3f68a7e3d2 /drivers/net/loopback.c
parente6eb8ca9e486a8f73ae237630e89406683b2be75 (diff)
downloadblackbird-op-linux-c97dab40796c59a4b03c532603e837077718fb81.tar.gz
blackbird-op-linux-c97dab40796c59a4b03c532603e837077718fb81.zip
iwlwifi: mvm: change protocol offload flows
RFC4862 states that "In all cases, a node MUST NOT respond to a Neighbor Solicitation for a tentative address". Currently the driver configures the NS offload and does not wait for address to become permanent, thus violating the RFC. Just removing the address from the address list is not good enough for all cases, since the NS messages are needed for the duplicate address detection and should not be discarded. For d0i3 disable NS offload. Put tentative address in the address list so the NS packet will not be filtered out by ucode. For D3 the platform will not wake from NS packets - so enable NS offload while removing the tentative address from the list. Given that now NS offload might be disabled, and that the ucode uses the IP data for other puroposes (L3 filtering) add two independent flags indicating if IPv4\IPv6 data is valid. Signed-off-by: Sara Sharon <sara.sharon@intel.com> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Diffstat (limited to 'drivers/net/loopback.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud