What you should end up with after following the steps in the article is that your RPi should have a new network device called sixxs with one IPv6 address and an IPv6 address on the eth0 interface. At this point the RPi should be able to e.g. ping6 google.com
. You can also try connecting to it via port 80: `telnet ipv6.google.com
Additionally, your laptop and other devices on your LAN should acquire their own IPv6 addresses. Using these, you should be able to ping RPi's IPv6 address that is assigned to its eth0 interface. If you can do that, then the next step would be test connecting to e.g. ipv6.google.com
If this works, then apt-get and wget should start working normally: they will prefer IPv6 to IPv4. Note that you may
see a difference in performance as IPv6 will likely hit different hosts between you and your target. It may be faster and it may be slower. What you should watch out for is a situation where wget tries to connect to an IPv6 address, times out, then tries IPv4. This means that there is a problem either on your end or on the server's end. It is not uncommon to have a problem on the server's end (for example the IRS website has had some issues I have seen in the past), so it is always good to run the ipv6.google.com
test to determine where things are broken. You can also use traceroute6 for this purpose.
Without seeing further details of your setup (what router are you using, do you have any other IPv6 traffic on your net that is not going through SixXS, what firewall rules are in place, etc.) it is hard to give more specific advice.