Bug 11697 - Does not pickup IPv6 neighbour advertisements
: Does not pickup IPv6 neighbour advertisements
Status: UNCONFIRMED
Product: Community Kernels
General
: unspecified
: N900 Maemo
: Unspecified normal (vote)
: ---
Assigned To: unassigned
: general
:
:
:
:
  Show dependency tree
 
Reported: 2010-12-16 18:05 UTC by maemo.yuri
Modified: 2010-12-23 12:01 UTC (History)
1 user (show)

See Also:


Attachments
Tcpdump while trying to ping device (24.55 KB, application/octet-stream)
2010-12-17 11:53 UTC, maemo.yuri
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description maemo.yuri (reporter) 2010-12-16 18:05:33 UTC
SOFTWARE VERSION: 2.6.18.10power46

IPv6 works at home as expected (6-over-4 tunnel). At work it does not (native
IPv6).

Case: I ping6 from my phone to my desktop (or the other way around)

What I see with tcpdump, on both devices:

desktop > phone:   echo request
phone > broadcast: IP6 Neighbour Solicitation
desktop > phone:   IP6 Neighbour Advertisement
phone > broadcast: IP6 Neighbour Solicitation
desktop > phone:   IP6 Neighbour Advertisement
...
desktop > phone:   echo request
phone > broadcast: IP6 Neighbour Solicitation
desktop > phone:   IP6 Neighbour Advertisement
phone > broadcast: IP6 Neighbour Solicitation
desktop > phone:   IP6 Neighbour Advertisement
...
desktop > broadcast: IP6 Neighbour Solicitation <-----
phone > desktop:   IP6 Neighbour Advertisement
desktop > phone:   echo request
phone > desktop:   echo reply

So it seems the phone does not actually process the advertisements, but it does
use the solicitation to fill its cache. So only when the desktop refreshes its
cache the phone manages to send data for a short while, 10 seconds or so.

REPRODUCIBILITY: Always
Comment 1 maemo.yuri (reporter) 2010-12-17 11:53:39 UTC
Created an attachment (id=3249) [details]
Tcpdump while trying to ping device

Dump while pinging phone from desktop.

- first 9 seconds unsuccessful neighbor discovery.
- desktop solicitation
- 5 seconds successful ping
- 45 seconds unsuccessful neighbor discovery.
- desktop solicitation
- 5 seconds successful ping
- Continuing neighbor discovery.