IPv6 Day

[Snowhog]

My results:

When both protocols are available, your browser uses

IPv4

Your internet connection is IPv6 capable
2001:0:53aa:64c:18ce:4a1b:2776:176d
MTA Solutions
Address type isTeredo
Tunneling from 216.137.232.146:46564 (server 83.170.6.76)


Your internet connection is IPv4 capable
216.137.232.146
146-232-137-216.mtaonline.netMTA Solutions

[GreyGeek]

Here's my test. Also, I enabled ufw and set IPV6=yes, to give my IPv6 tunnel a firewall to supplement the firewall my IPv4 has via my wireless router.

When both protocols are available, your browser usesIPv4

Your internet connection is IPv6 capable
2001:0:53aa:64c:20e4:4586:e720:5a2
Earthlink
Address type isTeredo
Tunneling from 24.223.250.93:47737 (server 83.170.6.76)


Your internet connection is IPv4 capable
24.223.250.93
user-0cdvuit.cable.mindspring.comEarthlink

I haven't edited the gia.conf file. I'll set mine to match yours and see what it does.

[vinnywright]

I read this http://www.debian-administration.org/articles/621:


The tcp6 protocols you were getting in your netstat listing, do they suggest that your equipment is native IPv6.

I doute it my wireless router is 5-10 years old and a cheep one at that .......I did enable IPv6 in my network manager wireless settings however .

and made shure "disabel IPv6" was set to false in firefoxes "about:config" page

VINNY

[vinnywright]

ok hear we go now I'v edited /etc/gai.conf to look like this

# Configuration for getaddrinfo(3).
#
# So far only configuration for the destination address sorting is needed.
# RFC 3484 governs the sorting.  But the RFC also says that system
# administrators should be able to overwrite the defaults.  This can be
# achieved here.
#
# All lines have an initial identifier specifying the option followed by
# up to two values.  Information specified in this file replaces the
# default information.  Complete absence of data of one kind causes the
# appropriate default information to be used.  The supported commands include:
#
# reload  <yes|no>
#    If set to yes, each getaddrinfo(3) call will check whether this file
#    changed and if necessary reload.  This option should not really be
#    used.  There are possible runtime problems.  The default is no.
#
# label   <mask>   <value>
#    Add another rule to the RFC 3484 label table.  See section 2.1 in
#    RFC 3484.  The default is:
#
label ::1/128       0
label ::/0          1
label 2002::/16     2
label ::/96         3
label ::ffff:0:0/96 4
#label fec0::/10     5
#label fc00::/7      6
#label 2001:0::/32   7
#
#    This default differs from the tables given in RFC 3484 by handling
#    (now obsolete) site-local IPv6 addresses and Unique Local Addresses.
#    The reason for this difference is that these addresses are never
#    NATed while IPv4 site-local addresses most probably are.  Given
#    the precedence of IPv6 over IPv4 (see below) on machines having only
#    site-local IPv4 and IPv6 addresses a lookup for a global address would
#    see the IPv6 be preferred.  The result is a long delay because the
#    site-local IPv6 addresses cannot be used while the IPv4 address is
#    (at least for the foreseeable future) NATed.  We also treat Teredo
#    tunnels special.
#
# precedence  <mask>   <value>
#    Add another rule to the RFC 3484 precedence table.  See section 2.1
#    and 10.3 in RFC 3484.  The RFC requires:
#
precedence  ::1/128       50
precedence  ::/0          40
precedence  2002::/16     30
precedence ::/96          20
precedence ::ffff:0:0/96  10
#
#    For sites which prefer IPv4 connections change the last line to
#
#precedence ::ffff:0:0/96  100

#
# scopev4  <mask>  <value>
#    Add another rule to the RFC 3484 scope table for IPv4 addresses.
#    The definitions in RFC 3484 are equivalent to:
#
#scopev4 ::ffff:169.254.0.0/112  2
#scopev4 ::ffff:127.0.0.0/104    2
#scopev4 ::ffff:10.0.0.0/104     5
#scopev4 ::ffff:172.16.0.0/108   5
#scopev4 ::ffff:192.168.0.0/112  5
#scopev4 ::ffff:0.0.0.0/96       14
#
#    For sites which use site-local IPv4 addresses behind NAT there is
#    the problem that even if IPv4 addresses are preferred they do not
#    have the same scope and are therefore not sorted first.  To change
#    this use only these rules:
#
#scopev4 ::ffff:169.254.0.0/112  2
#scopev4 ::ffff:127.0.0.0/104    2
#scopev4 ::ffff:0.0.0.0/96       14
#
#    For sites which use site-local IPv4 addresses behind NAT there is
#    the problem that even if IPv4 addresses are preferred they do not
#    have the same scope and are therefore not sorted first.  To change
#    this use only these rules:
#
#scopev4 ::ffff:169.254.0.0/112  2
#scopev4 ::ffff:127.0.0.0/104    2
#scopev4 ::ffff:0.0.0.0/96       14
#
#    This is what the Red Hat / Ubuntu setting currently uses.

at default all of it is comented out

now when I do a http://ipv6-test.com/ I get this

           When both protocols are available, your browser uses
     IPv6
          
               Your internet connection is IPv6 capable
         2001:0:53aa:64c:1c7d:560e:2e99:c4f
         Lexcom Telephone Company
Address type is[URL="http://wikipedia.org/wiki/Teredo_tunneling"]Teredo[/URL]
Tunneling from [B]209.102.243.176:43505[/B] (server [B]83.170.6.76[/B])

     
               Your internet connection is IPv4 capable
         209.102.243.176
         docsis-cbm-4-176.nclxtn.lexcominc.netLexcom Telephone Company
[URL="http://ipv6-test.com/stats/country/US"][IMG]http://ipv6-test.com/img/flags/US.png[/IMG][/URL]

and when I go to my start page (google)
I get this

vinny@Vinnys-HP-G62:~$ sudo netstat -tuanp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      848/rpcbind     
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1420/dnsmasq    
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      1246/cupsd      
tcp        0      0 0.0.0.0:47004           0.0.0.0:*               LISTEN      1016/rpc.statd  
tcp        0      0 127.0.0.1:2628          0.0.0.0:*               LISTEN      1258/0          
tcp        0      0 192.168.2.3:47154       74.125.45.103:80        ESTABLISHED 2175/firefox    
tcp6       0      0 :::111                  :::*                    LISTEN      848/rpcbind     
tcp6       0      0 ::1:631                 :::*                    LISTEN      1246/cupsd      
tcp6       0      0 :::40575                :::*                    LISTEN      1016/rpc.statd  
tcp6       0      0 2001:0:53aa:64c:1:44942 2607:f8b0:4002:802:::80 ESTABLISHED 2175/firefox    
tcp6       0      0 2001:0:53aa:64c:1:35882 2001:4860:800a::63:80   TIME_WAIT   -               
tcp6       0      0 2001:0:53aa:64c:1:44940 2607:f8b0:4002:802:::80 ESTABLISHED 2175/firefox    
udp        0      0 0.0.0.0:36909           0.0.0.0:*                           1280/avahi-daemon: 
udp        0      0 127.0.0.1:53            0.0.0.0:*                           1420/dnsmasq    
udp        0      0 0.0.0.0:68              0.0.0.0:*                           1400/dhclient   
udp        0      0 0.0.0.0:111             0.0.0.0:*                           848/rpcbind     
udp        0      0 0.0.0.0:45335           0.0.0.0:*                           1016/rpc.statd  
udp        0      0 0.0.0.0:43505           0.0.0.0:*                           1680/miredo     
udp        0      0 127.0.0.1:768           0.0.0.0:*                           1016/rpc.statd  
udp        0      0 0.0.0.0:1015            0.0.0.0:*                           848/rpcbind     
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1280/avahi-daemon: 
udp6       0      0 :::111                  :::*                                848/rpcbind     
udp6       0      0 :::47347                :::*                                1280/avahi-daemon: 
udp6       0      0 :::37387                :::*                                1016/rpc.statd  
udp6       0      0 :::1015                 :::*                                848/rpcbind     
udp6       0      0 :::5353                 :::*                                1280/avahi-daemon: 
vinny@Vinnys-HP-G62:~$

even though my ISP gives this

vinny@Vinnys-HP-G62:~$ host -t aaaa lexcominc.net
lexcominc.net has no AAAA record

so I think we are getting some where 8)

however that silly telnet star wars thing is still black and white ...........O well

VINNY

[GreyGeek]

I read this http://www.debian-administration.org/articles/621:

miredo is a Unix daemon program which mostly implements the Teredo: Tunneling IPv6 over UDP through NAT Internet proposed standard (RFC 4380) - in short it turns your home connection into an IPv6 client.

The tcp6 protocols you were getting in your netstat listing, do they suggest that your equipment is native IPv6.

[GreyGeek]

Ah, Vinny, I could not understand how miredo was working without access to an IPv4-->IPv6 web server.

I checked /etc/miredo.conf and found

~$ cat /etc/miredo.conf # Please refer to the miredo.conf(5) man page for details.
InterfaceName teredo


# Pick a Teredo server:
#ServerAddress teredo.ipv6.microsoft.com
ServerAddress teredo-debian.remlab.net


# Some firewall/NAT setups require a specific UDP port number:
#BindPort 3545

Instead of Hurricane or SIXXS the tunnel server is teredo-debian.remlab.net, but

:
~$ host -t aaaa teredo-debian.remlab.net
teredo-debian.remlab.net is an alias for teredo.remlab.net.
:~$ host -t aaaa teredo.remlab.net
teredo.remlab.net has no AAAA record

it doesn't have an AAAA record! It's not running IPv6!

[GreyGeek]

I missed the breaking points on the ipv6 IP.
Mine is:

2001:0:53aa:64c:20e4:4586:e720:5a2/32

Yours is:
2001:0:53aa:64c:1c7e:581d:2e99:c4f/32

The numbers in red are the same. I read somewhere that "2001:0" indicates a Teredo tunnel. I don't know what the "53aa:64c" represents.

I am running wireless, too. My ISP is Earthlink and they piggy back on top of TimeWarner.

You can use
host -t aaaa domainname
to check your ISP's support for IPv6.


:~$ host -t aaaa timewarnercable.com
timewarnercable.com has IPv6 address 2001:1998:2002:402::200
and as you can see TimeWarnerCable is IPv6 ready.

Is yours?

https://lists.ubuntu.com/archives/ub...ch/240807.html

You should now be able to ping and surf IPv6 enabled sites like
ipv6.google.com or www.kame.net. For a ping perform ping6 ipv6.google.com. It's a good idea to think about firewalling within yourclients, because all clients have now a public reachable IPv6 IP. In Ubuntu this is also an very easy task with the new UbuntuFirewall (ufw or uncomplicated firewall), just edit /etc/default/ufw and set IPV6=yes to get started.

But, I don't know if activating the ufw will cause the browser hanging I experienced when I modprobed ipv6_tables manually.

[Snowhog]

Just installed miredo and went to http://test-ipv6.com/ and these are my results.

Your IPv4 address on the public Internet appears to be 216.137.232.146

Your IPv6 address on the public Internet appears to be 2001:0:53aa:64c:18ce:4a1b:2776:176d Your IPv6 service appears to be: Teredo

(unknown result code: teredo-ipv4pref)

The World IPv6 Launch day is June 6th, 2012. Good news! Your current browser, on this computer and at this location, are expected to keep working after the Launch. [more info]

Congratulations! You appear to have both IPv4 and IPv6 Internet working. If a publisher publishes to IPv6, your browser will connect using IPv6. Note: Your browser appears to prefer IPv4 over IPv6 when given the choice. This may in the future affect the accuracy of sites who guess at your location.

Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access.

10/10	for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
10/10	for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

Added:
Just signed up for my SixXS IPv6 account. Awaiting the 'human' verification of my registration email response. Thinking about the results above, I wonder if a SixXS IPv6 account is even necessary. Guess it won't hurt to have it. I still don't get the color Star Wars console test.

[vinnywright]

@GreyGeek
Hmmm same as yours I think

vinny@Vinnys-HP-G62:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 2c:27:d7:cf:df:91 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1492 qdisc mq state UP qlen 1000
link/ether c0:f8:da:a8:39:5e brd ff:ff:ff:ff:ff:ff
inet 192.168.2.3/24 brd 192.168.2.255 scope global wlan0
inet6 fe80::c2f8:daff:fea8:395e/64 scope link
valid_lft forever preferred_lft forever
5: teredo: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
link/none
inet6 2001:0:53aa:64c:1c7e:581d:2e99:c4f/32 scope global
valid_lft forever preferred_lft forever
inet6 fe80::ffff:ffff:ffff/64 scope link
valid_lft forever preferred_lft forever
vinny@Vinnys-HP-G62:~$

and yes I'm using wireless .
I was thinking of setting up that SIXXS account as well !!

[GreyGeek]

Vinny,

I think I found wny the slowdown. Yesterday I only used the ping6 and such (*6) tools to test the internet, and I modprobe'd ipv6_tables and later installed miredo. Doing that allowed me to test ipv6.google.com, which reported I was ready. The other test site said I wasn't and gave me a paragraph like yours except that my IPv6 score was 0/10.

Just now I only installed miredo and here is my test results:

Your IPv4 address on the public Internet appears to be 24.223.250.93

Your IPv6 address on the public Internet appears to be 2001:0:53aa:64c:20e4:4586:e720:5a2 Your IPv6 service appears to be: Teredo

(unknown result code: teredo-ipv4pref)

The World IPv6 Launch day is June 6th, 2012. Good news! Your current browser, on this computer and at this location, are expected to keep working after the Launch. [more info]

Congratulations! You appear to have both IPv4 and IPv6 Internet working. If a publisher publishes to IPv6, your browser will connect using IPv6. Note: Your browser appears to prefer IPv4 over IPv6 when given the choice. This may in the future affect the accuracy of sites who guess at your location.

Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites.[more info]

10/10	for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
9/10	for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

But, the telnet StarWars epic, like yours, is not in color.

I've begun procedures to establish an SIXXS account and use their AICCU tunneling through their server.

P.S. -- I get only one tcp6 and three udp6 protocols when miredo is running.

tcp6       0      0 ::1:631                 :::*                    LISTEN      1051/cupsd   
udp6       0      0 :::5353                 :::*                                1031/avahi-daemon: 
udp6       0      0 :::38240                :::*                                1031/avahi-daemon:

P.S.-P.S.-- After running miredo WITHOUT modprobing ipv6_tables for an hour or so I am having a smooth internet experience, without any hangs. It may have been some ip6tables errors that caused the hang.

[GreyGeek]

Vinny,
What does "ip addr" give you? Mine gives me this:

:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 38:60:77:78:40:c8 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 74:de:2b:36:e4:35 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global wlan0
    inet6 fe80::76de:2bff:fe36:e435/64 scope link 
       valid_lft forever preferred_lft forever
17: teredo: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
    link/none 
    inet6 2001:0:53aa:64c:20e4:4586:e720:5a2/32 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::ffff:ffff:ffff/64 scope link 
       valid_lft forever preferred_lft forever

and, I can display http://ipv6.google.com/
Without miredo I cannot display the ipv6 google.com page.

As I understand it, the teredo inet6 address is that created by using the mac of my wireless, sticking "fffe" in the middle of it, and removing the odd numbered colons. Then attach the prefix "2001:0:53aa:" to it, or something like that.

Did you "modprobe ipv6"?

P.S. -- also, are you connecting via a wireless router or an ethernet cable to you box?

[vinnywright]

@GreyGeek strange .......I get NO slowdown at all using miredo (with no IPv6 internet services) and seem to be abel to get the http://ipv6.google.com/ page no prob

hear

vinny@Vinnys-HP-G62:~$ sudo netstat -tuanp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:34219           0.0.0.0:*               LISTEN      1027/rpc.statd  
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      879/rpcbind     
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1487/dnsmasq    
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      1120/cupsd      
tcp        0      0 127.0.0.1:2628          0.0.0.0:*               LISTEN      1295/0          
tcp6       0      0 :::111                  :::*                    LISTEN      879/rpcbind                                                                                                     
tcp6       0      0 ::1:631                 :::*                    LISTEN      1120/cupsd                                                                                                      
tcp6       0      0 :::51447                :::*                    LISTEN      1027/rpc.statd                                                                                                  
tcp6       0      0 2001:0:53aa:64c:1:37325 2607:f8b0:4002:802:::80 TIME_WAIT   -                                                                                                               
tcp6       0      0 2001:0:53aa:64c:1:37321 2607:f8b0:4002:802:::80 ESTABLISHED 4284/firefox    
tcp6       0      0 2001:0:53aa:64c:1:37323 2607:f8b0:4002:802:::80 TIME_WAIT   -               
tcp6       0      0 2001:0:53aa:64c:1:37324 2607:f8b0:4002:802:::80 ESTABLISHED 4284/firefox    
tcp6       0      0 2001:0:53aa:64c:1:37322 2607:f8b0:4002:802:::80 ESTABLISHED 4284/firefox    
udp        0      0 0.0.0.0:42978           0.0.0.0:*                           1720/miredo     
udp        0      0 127.0.0.1:53            0.0.0.0:*                           1487/dnsmasq    
udp        0      0 0.0.0.0:68              0.0.0.0:*                           1460/dhclient   
udp        0      0 0.0.0.0:111             0.0.0.0:*                           879/rpcbind     
udp        0      0 0.0.0.0:41449           0.0.0.0:*                           1027/rpc.statd  
udp        0      0 0.0.0.0:622             0.0.0.0:*                           879/rpcbind     
udp        0      0 127.0.0.1:779           0.0.0.0:*                           1027/rpc.statd  
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1097/avahi-daemon: 
udp        0      0 0.0.0.0:60663           0.0.0.0:*                           1097/avahi-daemon: 
udp6       0      0 :::57227                :::*                                1097/avahi-daemon: 
udp6       0      0 :::111                  :::*                                879/rpcbind     
udp6       0      0 :::622                  :::*                                879/rpcbind     
udp6       0      0 :::5353                 :::*                                1097/avahi-daemon: 
udp6       0      0 :::56867                :::*                                1027/rpc.statd

notice the tcp6 in the protocol line
am I missing something hear?

VINNY

[GreyGeek]

What benefits does one gain by installing miredo? Should one install it?

When you install miredo from the repository it automatically installs the daemon and modprobes ipv6_tables, ipv6table_filter, x_tables and some other kernel modules whose names I can't remember. So, when you do "ip addr" in a Konsole you'll see the Teredo device and IPv6 address attached to it, but the link property will be empty. The wiki article then tells you how to use Hurricane or the other two IPv6 internet services to complete setting up your dual IPv4 and IPv6 stack.

Like I said, the problem I had while miredo was running is that the IPv6 connection attempt on an IPv4 website would have to time out before my desktop responded to my mouse or keyboard inputs. When it passed off to IPv4, which immediately make a connection, control was returned and all those events waiting in the que responded and I'd get an explosion of browser, email, or Konsole apps onto the screen. Teredo just can't shut down after failing to get an ACK on its first handshake attempt so there is no way to bypass the repeated handshake tries until timeout, unless one changes the timeout duration. But, perhaps they could put the connection attempt into a thread and return control to the desktop so the user could do other things while the busy wheel circled the tab waiting for a response. As it is, the connection attempt appears to be a polling loop that doesn't check the event que until the counter max is reached ... a really poor way to code for an event. An interrupt via a thread would be a lot nicer. That way, IPv6 could take its sweet time but we could continue browsing on other sites until the IPv6 site connected, or it timed out because the site wasn't an IPv6 site. In that event the tab could automatically close to signify that.

Anyway, IPv4 will, IMO, be around for a LONG time. I suspect that it will be the major protocol even five years from now, and possibly longer.

[vinnywright]

well I installed miredo and got my test up to this...............

Your IPv4 address on the public Internet appears to be 209.102.243.176

Your IPv6 address on the public Internet appears to be 2001:0:53aa:64c:1c7e:581d:2e99:c4f Your IPv6 service appears to be: Teredo

(unknown result code: teredo-ipv4pref)

The World IPv6 Launch day is June 6th, 2012. Good news! Your current browser, on this computer and at this location, are expected to keep working after the Launch. [more info]

Congratulations! You appear to have both IPv4 and IPv6 Internet working. If a publisher publishes to IPv6, your browser will connect using IPv6. Note: Your browser appears to prefer IPv4 over IPv6 when given the choice. This may in the future affect the accuracy of sites who guess at your location.

Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites. [more info]

10/10	for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
9/10	for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

but that telnet thing tells me my IPv6 address is the same as my IPv4 one ......hummmm

@SteveRiley wanna nmap or something that IP for me and see how tight I am or not

VINNY

[vinnywright]

No color, so IPv4 here.

ya me to .........hears where I got that http://www.sixxs.net/misc/coolstuff/

VINNY