1 |
Hello list, |
2 |
|
3 |
Having been inspired by the recent discussion of IPv6, I decided to try it, |
4 |
starting with my ISP, my Billion Bipac vDSL modem-router and one host - this |
5 |
one. Of course it isn't straightforward. |
6 |
|
7 |
Zen has allocated me a /64 ND prefix and a /48 PD prefix. I found a way to |
8 |
tell the Bipac to set up IPv6, and rebooted it; it now tells me its LAN |
9 |
address is 2a02:8010:663d:0:6203:47ff:fe2d:8eba/64. Nslookup on this host says |
10 |
the same, without the /64. But then this: |
11 |
|
12 |
$ ping6 vdsl |
13 |
ping: vdsl: No address associated with hostname |
14 |
$ ping6 2a02:8010:663d:0:6203:47ff:fe2d:8eba |
15 |
PING 2a02:8010:663d:0:6203:47ff:fe2d:8eba(2a02:8010:663d:0:6203:47ff:fe2d: |
16 |
8eba) 56 data bytes |
17 |
64 bytes from 2a02:8010:663d:0:6203:47ff:fe2d:8eba: icmp_seq=1 ttl=64 |
18 |
time=1.75 ms |
19 |
^C |
20 |
|
21 |
If I add the LAN address of the Bipac to /etc/hosts, ping finds it okay, but |
22 |
what if the address changes if the Bipac reboots? I thought this kind of |
23 |
address fixing was unnecessary in IPv6. |
24 |
|
25 |
And am I supposed to fix the IPv6 addresses of the other hosts on the LAN, or |
26 |
just stick to IPv4 for local comms? And I haven't yet even thought about the |
27 |
wireless devices served by the Bipac, though I see my mobile phone has |
28 |
acquired an IPv6 address starting with fe80::40be... and it doesn't look like |
29 |
its MAC address. |
30 |
|
31 |
-- |
32 |
Regards, |
33 |
Peter. |