1 |
> Hello list, |
2 |
Hi, |
3 |
|
4 |
> Having been inspired by the recent discussion of IPv6, I decided to try it, |
5 |
> starting with my ISP, my Billion Bipac vDSL modem-router and one host - this |
6 |
> one. Of course it isn't straightforward. |
7 |
> |
8 |
> Zen has allocated me a /64 ND prefix and a /48 PD prefix. I found a way to |
9 |
> tell the Bipac to set up IPv6, and rebooted it; it now tells me its LAN |
10 |
> address is 2a02:8010:663d:0:6203:47ff:fe2d:8eba/64. Nslookup on this host says |
11 |
> the same, without the /64. But then this: |
12 |
> |
13 |
> $ ping6 vdsl |
14 |
> ping: vdsl: No address associated with hostname |
15 |
> $ ping6 2a02:8010:663d:0:6203:47ff:fe2d:8eba |
16 |
> PING 2a02:8010:663d:0:6203:47ff:fe2d:8eba(2a02:8010:663d:0:6203:47ff:fe2d: |
17 |
> 8eba) 56 data bytes |
18 |
> 64 bytes from 2a02:8010:663d:0:6203:47ff:fe2d:8eba: icmp_seq=1 ttl=64 |
19 |
> time=1.75 ms |
20 |
> ^C |
21 |
> |
22 |
> If I add the LAN address of the Bipac to /etc/hosts, ping finds it okay, but |
23 |
> what if the address changes if the Bipac reboots? I thought this kind of |
24 |
> address fixing was unnecessary in IPv6. |
25 |
> |
26 |
> And am I supposed to fix the IPv6 addresses of the other hosts on the LAN, or |
27 |
> just stick to IPv4 for local comms? And I haven't yet even thought about the |
28 |
> wireless devices served by the Bipac, though I see my mobile phone has |
29 |
> acquired an IPv6 address starting with fe80::40be... and it doesn't look like |
30 |
> its MAC address. |
31 |
It really depends how you're setting up IPv6 on your local network. |
32 |
The easiest option is if you're using stateful DHCPv6. In this case you |
33 |
just need to set up your dhcp server to notify your dns server of any |
34 |
new leases. If you're using static IPv6 addresses you can create a |
35 |
static mapping between hostnames and addresses either in /etc/hosts or |
36 |
your dns server. If you're using SLAAC, however, the only option I can |
37 |
think of is to use stateless DHCPv6 to notify the DHCP server of your |
38 |
client fqdn which should then sync the record with the DNS server. |
39 |
|
40 |
-- |
41 |
Simon Thelen |