Ubuntu addict and loving it
Is Ubuntu 9.10 fully IPv6 ready? I notice that command line tools like ping and ssh are treating IPv6 addresses, both with and without the [] characters, as hostnames to be looked up via DNS. Is something else needed to enable IPv6, like special IPv6 versions of packages?
Gee! These Aren't Roasted!
Yes, 9.10 is IPv6 ready. Head to System > Preferences > Network Connections and choose your network connection and click "Edit". Last tab.
Ubuntu addict and loving it
The interface is already configured with a local IPv6 address. The problem is getting applications such as ping and ssh to understand IPv6. Also, this is on Ubuntu Server, so I'm configuring with command lines (ifconfig for temporary changes, emacs of config files and scripts for persistent changes, apt-get for package upgrades and installs ... etc).
Way Too Much Ubuntu
I have found that most things just work with ipv6. There is ping6 and traceroute6 but I use mtr (apt-get install mtr-tiny). If I mtr to a server with both ipv6 and ipv4 dns entries then it picks ipv6.Is something else needed to enable IPv6, like special IPv6 versions of packages?
What sort of problems are you having. As above if I ssh to my server, which has both an A and AAAA dns record it connects to the ipv6 address no problems. Apache, lightppd, postfix may need a change to the config to listen on the ipv6 interface but that is about all the changes needed to have an ipv6 server running.The problem is getting applications such as ping and ssh to understand IPv6
Ubuntu addict and loving it
Yes, Ubuntu is IPv6 ready.Originally Posted by Skaperen
If you want IPv6 connectivity to the outside world, use "sudo apt-get install miredo", and then visit http://ipv6.google.com/
HTH
Ubuntu addict and loving it
I'm just wanting IPv6 within my LAN for now. Any idea why none of these work? It sure looks like they don't recognize that it is an IP (IPv6) address.Code:euler/root/x1 /root 10# ping -n 'fe80::225:11ff:fe80:993c' ping: unknown host fe80::225:11ff:fe80:993c euler/root/x1 /root 11# ping -n '[fe80::225:11ff:fe80:993c]' ping: unknown host [fe80::225:11ff:fe80:993c] euler/root/x1 /root 12# ping6 -n 'fe80::225:11ff:fe80:993c' connect: Invalid argument euler/root/x1 /root 13# ping6 -n '[fe80::225:11ff:fe80:993c]' unknown host euler/root/x1 /root 14# ssh 'fe80::225:11ff:fe80:993c' ssh: connect to host fe80::225:11ff:fe80:993c port 22: Invalid argument euler/root/x1 /root 15# ssh '[fe80::225:11ff:fe80:993c]' ssh: Could not resolve hostname [fe80::225:11ff:fe80:993c]: Name or service not known euler/root/x1 /root 16# ssh -6 'fe80::225:11ff:fe80:993c' ssh: connect to host fe80::225:11ff:fe80:993c port 22: Invalid argument euler/root/x1 /root 17# ssh -6 '[fe80::225:11ff:fe80:993c]' ssh: Could not resolve hostname [fe80::225:11ff:fe80:993c]: No address associated with hostname euler/root/x1 /root 18#
Ubuntu addict and loving it
Because it's not clear on which interface a fe80: address is, you have to specify the source interface.
See below.
Code:sander@athlon64:~$ ping6 -I eth0 fe80::21a:92ff:fe77:27ab PING fe80::21a:92ff:fe77:27ab(fe80::21a:92ff:fe77:27ab) from fe80::21a:92ff:fe77:27ab eth0: 56 data bytes 64 bytes from fe80::21a:92ff:fe77:27ab: icmp_seq=1 ttl=64 time=0.060 ms 64 bytes from fe80::21a:92ff:fe77:27ab: icmp_seq=2 ttl=64 time=0.070 ms ^C --- fe80::21a:92ff:fe77:27ab ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.060/0.065/0.070/0.005 ms sander@athlon64:~$ ping6 ip6-localhost PING ip6-localhost(localhost) 56 data bytes 64 bytes from localhost: icmp_seq=1 ttl=64 time=0.055 ms 64 bytes from localhost: icmp_seq=2 ttl=64 time=0.059 ms ^C --- ip6-localhost ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.055/0.057/0.059/0.002 ms sander@athlon64:~$
Ubuntu addict and loving it
And how is this done with ssh? How is this done with a web browser URL? Or is this a problem specific to link-local addresses?
Ubuntu addict and loving it
Typing all those IPv6 addresses is cumbersome. On your LAN, avahi (zeroconf) can take of name resolution to local IPv6 addresses.
You only have change two lines in your configs. See http://ipv6-or-no-ipv6.blogspot.com/...-in-avaha.html
Quote from that page:
After that, you will be in the IPv6 LAN Walhalla, and you can ping6 other Ubuntu (9.04+) machines on your LAN just by their <hostname> followed by ".local." (note the leading AND trailing dot):Code:make sure the /etc/avahi/avahi-daemon.conf file contains an active "use-ipv6=yes" line. To enable m(ulticast)dns resolving of IPv6 addresses change the "hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4" line to "hosts: files mdns_minimal [NOTFOUND=return] dns mdns" in the /etc/nsswitch.conf file
Code:sander@athlon64:~$ ping6 quirinius.local. PING quirinius.local.(quirinius.local) 56 data bytes 64 bytes from quirinius.local: icmp_seq=1 ttl=64 time=12.0 ms 64 bytes from quirinius.local: icmp_seq=2 ttl=64 time=2.71 ms 64 bytes from quirinius.local: icmp_seq=3 ttl=64 time=3.16 ms 64 bytes from quirinius.local: icmp_seq=4 ttl=64 time=2.87 ms ^C --- quirinius.local. ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3016ms rtt min/avg/max/mdev = 2.716/5.202/12.045/3.954 ms sander@athlon64:~$
Ubuntu addict and loving it
If I need to specify which interface to source from (under the theory that my target IP address could be present in duplicate on more than one link), how is it that giving the target a hostname avoids the need to know the interface? Is is that somehow included in a modified named lookup?
It seems link-local's semantics are too different in IPv6 to use it like I did in IPv4, and I should just exclusively go with a Unique Local Address.
Adv Reply
Bookmarks