Hurricane Electric's IPv6 Tunnel Broker Forums

Tunnelbroker.net Specific Topics => Questions & Answers => Topic started by: marins82 on October 04, 2012, 10:51:16 AM

Title: [Solved] Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 04, 2012, 10:51:16 AM
Explorer test not passed!

I made ​​the configuration of the tunnel, as well as the machine, as the wiki ubuntu:
QuoteGet connected with Hurricane Electric

First you need to register on the TunnelBroker.net Website. You will be emailed your username and password. Login and in the User Functions Box on the left side click the Create Regular Tunnel link. Put in your IPv4 address and Select a server close to you. Go to the tunnel details page. Run gksudo gedit /etc/network/interfaces and add the following, editing as directed by the comments:

auto he-ipv6
iface he-ipv6 inet6 v4tunnel
    endpoint 216.218.226.238
    address  2001:470:a:d29f::2
    netmask  64
    up ip -6 route add default dev he-ipv6
    down ip -6 route del default dev he-ipv6

Replace the endpoint setting (216.218.226.238) with the Server IPv4 address field from the tunnel details page and the address setting (2001:470:a:d29f::2) with Client IPv6 address field from the tunnel details page. Save the file.

Right click on the network manager icon in the tray and click Edit Connections. Select the connection to your local network and click Edit. Go to the IPv6 Settings tab and set the Method to Manual. Click Add. For the address put the first address in your Routed 64. (In this example it would be 2001:470:b:d29f::1 .) For the prefix put in 64. For the gateway, put in the address from the "Client IPv6 address" of the tunnel details page (in this example it would be 2001:470:a:d29f::2). Click apply.

Run sudo ifup he-ipv6 and you should have IPv6 connectivity.
https://wiki.ubuntu.com/IPv6

causes me he-ipv6 and it works, there is also sit0 that is down.  if ping ipv6.google.com, it gives me the results, same thing if I browse with w3m on ipv6.google.com makes me navigate perfectly!

these are the settings that I currently have:
Quotemarins82@ServerUbuntu:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:02:b3:2e:1e:e6
         indirizzo inet:192.168.1.105  Bcast:192.168.1.254  Maschera:255.255.25                                             5.0
         indirizzo inet6: fe80::202:b3ff:fe2e:1ee6/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:3816 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2390 errors:0 dropped:0 overruns:0 carrier:0
         collisioni:0 txqueuelen:1000
         Byte RX:493005 (493.0 KB)  Byte TX:464798 (464.7 KB)

he-ipv6   Link encap:IPv6 in IPv4
         indirizzo inet6: fe80::c0a8:169/64 Scope:Link
         indirizzo inet6: 2001:470:6c:2cc::2/64 Scope:Global
         UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
         RX packets:197 errors:0 dropped:0 overruns:0 frame:0
         TX packets:241 errors:0 dropped:0 overruns:0 carrier:0
         collisioni:0 txqueuelen:0
         Byte RX:129524 (129.5 KB)  Byte TX:26399 (26.3 KB)

lo        Link encap:Loopback locale
         indirizzo inet:127.0.0.1  Maschera:255.0.0.0
         indirizzo inet6: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:1158 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1158 errors:0 dropped:0 overruns:0 carrier:0
         collisioni:0 txqueuelen:0
         Byte RX:181167 (181.1 KB)  Byte TX:181167 (181.1 KB)

virbr0    Link encap:Ethernet  HWaddr 12:70:3a:c8:df:ac
         indirizzo inet:192.168.122.1  Bcast:192.168.122.255  Maschera:255.255.                                             255.0
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisioni:0 txqueuelen:0
         Byte RX:0 (0.0 B)  Byte TX:0 (0.0 B)


Why not pass the test?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: cholzhauer on October 04, 2012, 11:04:51 AM
I'm unable to ping 2001:470:6c:2cc::2  is your tunnel currently up?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 04, 2012, 11:06:57 AM
Yes it's up

Quotemarins82@ServerUbuntu:~$ ping6 2001:470:6c:2cc::2
PING 2001:470:6c:2cc::2(2001:470:6c:2cc::2) 56 data bytes
64 bytes from 2001:470:6c:2cc::2: icmp_seq=1 ttl=64 time=0.119 ms
64 bytes from 2001:470:6c:2cc::2: icmp_seq=2 ttl=64 time=0.143 ms
64 bytes from 2001:470:6c:2cc::2: icmp_seq=3 ttl=64 time=0.143 ms
64 bytes from 2001:470:6c:2cc::2: icmp_seq=4 ttl=64 time=0.143 ms
64 bytes from 2001:470:6c:2cc::2: icmp_seq=5 ttl=64 time=0.154 ms
64 bytes from 2001:470:6c:2cc::2: icmp_seq=6 ttl=64 time=0.155 ms
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: cholzhauer on October 04, 2012, 11:12:31 AM
Well of course it works for you...that address is local for you

Can you ping 2001:470:6c:2cc::1 ?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 04, 2012, 11:23:07 AM
yes

Quotemarins82@ServerUbuntu:~$ ping6 2001:470:6c:2cc::1
PING 2001:470:6c:2cc::1(2001:470:6c:2cc::1) 56 data bytes
64 bytes from 2001:470:6c:2cc::1: icmp_seq=1 ttl=64 time=116 ms
64 bytes from 2001:470:6c:2cc::1: icmp_seq=2 ttl=64 time=116 ms
64 bytes from 2001:470:6c:2cc::1: icmp_seq=3 ttl=64 time=116 ms
64 bytes from 2001:470:6c:2cc::1: icmp_seq=4 ttl=64 time=117 ms
^C
--- 2001:470:6c:2cc::1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 116.470/116.885/117.760/0.620 ms
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: cholzhauer on October 04, 2012, 11:25:37 AM
fair enough

what is the explorer test again?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 04, 2012, 11:27:19 AM
Test Not Passed
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: cholzhauer on October 04, 2012, 11:28:13 AM
That doesn't tell me what the test is.  What is the explorer test testing for?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 04, 2012, 11:30:53 AM
I log in in my account, the page that appears at the bottom http://ipv6.he.net/certification/cert-main.php.

QuoteExplorer
In the Explorer level, we will need to check if you have IPv6 connectivity:

You were unable to load a content from an IPv6 only URL. Here's an exmple of the IPv6 only URL: http://[2001:DB8::1]/

How do I obtain an IPv6 connection?

   Natively through your ISP if they operate IPv6
   If ISP doesn't operate IPv6 then use IPv6 tunneling

Why not setup a free IPv6 tunnel from Tunnelbroker.net

How to create a 6in4 tunnel, please visit our FAQ page

Video tutorials are also available at our Video Presentation page
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: broquea on October 04, 2012, 12:11:57 PM
ping ipv6@he.net

in another thread someone was able to ping the HE side but not reach beyond it. They emailed HE support, and it got fixed.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 04, 2012, 12:38:41 PM
I'm trying to access terminal on the site.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 04, 2012, 01:09:28 PM
I perform the test with the PC windows XP with IPv4, with the Ubuntu server I can not connect to the terminal.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: kasperd on October 04, 2012, 01:52:07 PM
Quote from: marins82 on October 04, 2012, 10:51:16 AMindirizzo inet:192.168.1.105
You are running the tunnel through a NAT? With some NAT devices it can work, but it will be harder to debug problems. It would be better to terminate the tunnel on the NAT device itself.

Quote from: marins82 on October 04, 2012, 01:09:28 PMI perform the test with the PC windows XP with IPv4, with the Ubuntu server I can not connect to the terminal.
What are you saying? How many different devices are involved?

Due to shortcomings of the NAT it is not possible for us to see much with a traceroute from outside. That means we can only make guesses about what is going on. My guess is you are trying to open an HTTP connection from a different computer using your tunnel endpoint as gateway, but you didn't enable forwarding of IPv6 packets.

This is just a guess. Try to run a traceroute towards an IPv6 address on the Internet from each of the involved computers. And we'll see what this tells us. (If you need an IPv6 address to traceroute to you can use reflector.easyv6.net / 2001:470:1f0b:1da2:46d9:d4a0:1844:43bd).
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: broquea on October 04, 2012, 02:08:26 PM
Quote from: marins82 on October 04, 2012, 01:09:28 PM
I perform the test with the PC windows XP with IPv4, with the Ubuntu server I can not connect to the terminal.

So how are you delivering IPv6 connectivity through your Ubuntu machine to your antiquated Windows platform?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 05, 2012, 01:25:15 AM
if I install the desktop on ubuntu server, can I fix it?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: kasperd on October 05, 2012, 01:28:06 AM
2001:470:6c:2cc::2 was responding to pings for about an hour, then it stopped responding again. No idea if that is due to how the NAT is behaving or if the tunnel was brought up for an hour and then brought down again.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: kasperd on October 05, 2012, 01:32:20 AM
Quote from: marins82 on October 05, 2012, 01:25:15 AMif I install the desktop on ubuntu server, can I fix it?
Are you sure that's what you want to do? Why not instead install a router advertisement daemon such that the rest of your network can have IPv6?
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 05, 2012, 10:04:05 AM
Quote from: kasperd on October 05, 2012, 01:32:20 AM
Quote from: marins82 on October 05, 2012, 01:25:15 AMif I install the desktop on ubuntu server, can I fix it?
Are you sure that's what you want to do? Why not instead install a router advertisement daemon such that the rest of your network can have IPv6?


These instructions are correct, to put IPv6 in your network?


QuoteConfigure your Ubuntu box as a IPv6 router

    Edit /etc/sysctl.conf

Uncomment the line which contains net.ipv6.conf.default.forwarding=1. This is a common step to enable IPv6 routing.

You can learn how to install and enable DHCPv6 on your network here.

Alternatively, if you want to use radvd which will advertise your prefix and let the network's systems select their own IP address:

    Install radvd

sudo aptitude install radvd

    Edit /etc/radvd.conf (see following sample)

Note: If the computer is only routing IPv6, then only uncomment net.ipv6.conf.default.forwarding=1 and leave the IPv4 stuff unchanged.

Note: /etc/radvd.conf: This file does not exist after a fresh install. You can look at the sample configuration files in usr/share/doc/radvd/examples/ for further studies.

Sample /etc/radvd.conf:

interface eth0
{
   AdvSendAdvert on;
   prefix 2001:xxxx:xxxx::/64
   {
        AdvOnLink on;
        AdvAutonomous on;
   };
};

eth0 is the interface which is used for the Router Advertising messages (RAs). If you are not sure about the interface, check with <tt>ip addr</tt> on the command line.

The prefix you have to take from the information given by SixXS or Hurricane Electric.

Restart the router advertising daemon to propagate your IPv6 address space

sudo /etc/init.d/radvd restart

Now router should automatically send "Router Advertising Messages" to your network and your IPv6 clients should auto configure them self.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: kasperd on October 05, 2012, 10:56:51 AM
Quote from: marins82 on October 05, 2012, 10:04:05 AMThese instructions are correct, to put IPv6 in your network?
It looks correct. I noticed that you have IPv4 addresses on both eth0 and virbr0. I don't know if you need radvd to handle both of them or just one.

If you only need IPv6 on eth0 and not on virbr0, then you can just follow the instructions. The prefix to use in the configuration file is the routed prefix. The page with information about IP addresses for your tunnel contains both the tunnel endpoint addresses and the routed prefix, the digit which differs between them is highlighted.

If you do need IPv6 on both eth0 and vibr0, then you'll have to request a /48. But I guess you can finish the certification with IPv6 on just one of them.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 05, 2012, 11:33:59 PM
In theory, I should use radvd to make use of ipv6 for the entire home network. What do you advise me to do? Thus, in addition to the server, all the pc benefit from ipv6.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: kasperd on October 06, 2012, 01:11:18 AM
Quote from: marins82 on October 05, 2012, 11:33:59 PMWhat do you advise me to do?
Skip the DHCPv6 part. Setup radvd as described.
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 06, 2012, 04:49:32 AM
I installed radvd on the server by following the simple instructions, I radvd.com configured as follows:
Quoteinterface eth0
{
   AdvSendAdvert on;
   prefix 2001:470:6c:2cc::/64
   {
        AdvOnLink on;
        AdvAutonomous on;
   };
};

I rebooted and radvd works.
In the windows pc I installed ipv6 running the command: ipv6 install from cmd.
But in the test, not even pass this time. Maybe I should do something else?
Title: Re: [Solved] Explorer Test - on Ubuntu Server 12.04
Post by: marins82 on October 06, 2012, 12:35:23 PM
I solved it by installing the xfce desktop on the server. Thanks for the help, you have been really nice!
Title: Re: Explorer Test - on Ubuntu Server 12.04
Post by: kasperd on October 06, 2012, 03:30:16 PM
Quote from: marins82 on October 06, 2012, 04:49:32 AM
I installed radvd on the server by following the simple instructions, I radvd.com configured as follows:
Quoteinterface eth0
{
   AdvSendAdvert on;
   prefix 2001:470:6c:2cc::/64
   {
        AdvOnLink on;
        AdvAutonomous on;
   };
};
You are specifying the wrong prefix. That is the tunnel prefix. You need to use the routed prefix.