1 |
* Peter Humphrey: |
2 |
|
3 |
> $ ping6 vdsl |
4 |
> ping: vdsl: No address associated with hostname |
5 |
|
6 |
The outcome of ping depends on /etc/resolv.conf and /etc/hosts, and even |
7 |
on the OS of the IPv6 nodes involved. Apple devices will be available as |
8 |
somename.local, with "somename" being what the user configured as the |
9 |
device's name in Preferences->Sharing. I can for example ping my iPhone |
10 |
via "ping6 silver.local". |
11 |
|
12 |
> If I add the LAN address of the Bipac to /etc/hosts, ping finds it |
13 |
> okay, but what if the address changes if the Bipac reboots? |
14 |
|
15 |
Your Bipac will have multiple "LAN addresses", or rather addresses that |
16 |
are bound to the LAN-facing network interface. In your example, you were |
17 |
pinging the global scope address 2a02:x which may change over time, |
18 |
unless your provider assigns static networks (mine does not). However, |
19 |
the router should also have at least one link-local address and one |
20 |
unique local address (ULA): |
21 |
|
22 |
Global scope: 2a02:8010:x (may change or may not) |
23 |
Link local: fe80:y (may change with SLAAC privacy extensions) |
24 |
ULA: fd67:z (should be fixed) |
25 |
|
26 |
With my router, the ULA was set up once when I first picked a random ULA |
27 |
prefix, and has remained immutable since then. |
28 |
|
29 |
> I see my mobile phone has acquired an IPv6 address starting with |
30 |
> fe80::40be... and it doesn't look like its MAC address. |
31 |
|
32 |
That's not actually a bad thing. I mentioned SLAAC privacy extensions |
33 |
(RFC 4941) before; [1] offers some explanations. |
34 |
|
35 |
[1] https://www.internetsociety.org/resources/deploy360/2014/privacy-extensions-for-ipv6-slaac/ |
36 |
|
37 |
-Ralph |