diff options
| author | Josua Mayer <[email protected]> | 2019-07-06 17:54:47 +0200 |
|---|---|---|
| committer | Marcel Holtmann <[email protected]> | 2019-07-06 21:33:55 +0200 |
| commit | 5636376c26502c39260853e529e9467f79f95931 (patch) | |
| tree | 3d2c1a58b55197596b8580fec3466015abb777b2 /drivers/fpga/fpga-bridge.c | |
| parent | b188b03270b7f8568fc714101ce82fbf5e811c5a (diff) | |
Bluetooth: 6lowpan: check neighbour table for SLAAC
Like any IPv6 capable device, 6LNs can have multiple addresses assigned
using SLAAC and made known through neighbour advertisements.
After checking the destination address against all peers link-local
addresses, consult the neighbour cache for additional known addresses.
RFC7668 defines the scope of Neighbor Advertisements in Section 3.2.3:
1. "A Bluetooth LE 6LN MUST NOT register its link-local address"
2. "A Bluetooth LE 6LN MUST register its non-link-local addresses with
the 6LBR by sending Neighbor Solicitation (NS) messages ..."
Due to these constranits both the link-local addresses tracked in the
list of 6lowpan peers, and the neighbour cache have to be used when
identifying the 6lowpan peer for a destination address.
Acked-by: Jukka Rissanen <[email protected]>
Tested-by: Michael Scott <[email protected]>
Signed-off-by: Josua Mayer <[email protected]>
Signed-off-by: Marcel Holtmann <[email protected]>
Diffstat (limited to 'drivers/fpga/fpga-bridge.c')
0 files changed, 0 insertions, 0 deletions