dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
26791

mackey
Premium Member
join:2007-08-20

mackey to bodosom

Premium Member

to bodosom

Re: [Internet] IPv6 just appeared on my connection

I haven't looked into it too deeply yet, but from the outside I can ping the /128 assigned to the router just fine but anything in the /64 fails.

/M

AhnHEL
Angel
Premium Member
join:2000-09-11
Orlando, FL

AhnHEL to bvierra

Premium Member

to bvierra
Click for full size
I'm finally a member of the club!

RR Wideband in Bayside, Queens, NYC

SB6141 connected to pfSense.
patt2k
join:2009-01-16

patt2k to bvierra

Member

to bvierra
so someone please explain how do I configure ipv6 no one wants to give me instructions.

I have the RT-n66u configured as native dhcp for ipv6. Thanks!

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA

NormanS

MVM

I have the AC66U. From the menu screen I see no configurable parameters when "Native with DHCP-PD" is selected. I assume the router will make a request from the ISP DHCP-PD server; but I can't prove it one way, or another.
mind21_98
join:2006-05-13
San Diego, CA

mind21_98 to bvierra

Member

to bvierra
Update: I had to reboot my router due to config changes on it. When it came back, no more IPv6. Could TWC have disabled their DHCPv6 server here, or is there something else going on?

AhnHEL
Angel
Premium Member
join:2000-09-11
Orlando, FL

AhnHEL

Premium Member

Try shutting down your router and unplugging modem. Plug modem back in, allow it to fully boot and then start up your router and see if you get your IPv6 back.
mind21_98
join:2006-05-13
San Diego, CA

mind21_98

Member

said by AhnHEL:

Try shutting down your router and unplugging modem. Plug modem back in, allow it to fully boot and then start up your router and see if you get your IPv6 back.

Just did that. Still no IPv6 address.
mind21_98

mind21_98

Member

My service went out yesterday. When it came back I noticed IPv6 came back on my connection.
mind21_98

mind21_98

Member

So it's been a few days since IPv6 came back permanently on my connection. I've noticed a few things:

  1. The AirPort Extreme seems to request and receive a /64. There seems to be no way to get a bigger block. I will probably get a router I can flash with DD-WRT or some other firmware when the APE finally dies so I can look into fixing that.

  2. Safari on my MacBook Pro always uses IPv4 when both options are available. It looks like it's because latency on IPv6 is consistently higher than on IPv4. Not sure if this will be something that gets fixed over time as TWC adds more IPv6 peering.

  3. Speaking of peering, it seems that any IPv6 traffic to AWS always goes through Seattle, at least to go to their Oregon datacenter. Is this normal?

    traceroute to newsrdr.us (2620:108:700f::36d5:ba8e) from 2605:e000:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, 30 hops max, 24 byte packets
     1  2605:e000:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (2605:e000:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx)  0.414 ms  0.286 ms  0.234 ms
     2  2605:e000:40c:46::1 (2605:e000:40c:46::1)  10.401 ms  5.602 ms  6.721 ms
     3  2605:e000:0:4::2:311 (2605:e000:0:4::2:311)  6.399 ms  6.211 ms  7.374 ms
     4  2605:e000:0:4::2:b2 (2605:e000:0:4::2:b2)  11.642 ms  9.579 ms  15.914 ms
     5  2605:e000:0:4::24 (2605:e000:0:4::24)  14.268 ms  12.071 ms  11.808 ms
     6  2001:1998:0:8::86 (2001:1998:0:8::86)  14.646 ms  12.063 ms  11.822 ms
     7  ae-0-0.pr0.lax00.tbone.rr.com (2001:1998::66:109:6:135)  9.889 ms  11.185 ms  10.977 ms
     8  2001:1998:0:8::1e6 (2001:1998:0:8::1e6)  13.208 ms  11.851 ms  9.899 ms
     9  vl-80.edge6.LosAngeles1.Level3.net (2001:1900:12:3::b)  10.085 ms  17.595 ms  10.18 ms
    10  vl-4061.edge2.SanJose1.Level3.net (2001:1900:4:1::65)  20.676 ms  21.805 ms  19.561 ms
    11  vl-4040.car1.Seattle1.Level3.net (2001:1900:4:1::49)  39.372 ms  38.411 ms  38.168 ms
    12  vl-52.edge2.Seattle1.Level3.net (2001:1900:1b:2::b)  37.871 ms  37.726 ms  37.57 ms
    13  AMAZON-CORP.edge2.Seattle1.Level3.net (2001:1900:2100::1d5a)  40.091 ms  37.692 ms  37.779 ms
    14  * * *
    15  2620:108:7000::10 (2620:108:7000::10)  52.354 ms  49.708 ms  74.497 ms
    16  2620:108:7000::11 (2620:108:7000::11)  49.636 ms  50.716 ms  49.066 ms
    17  2620:108:7000::2 (2620:108:7000::2)  50.374 ms  71.05 ms  53.873 ms
    18  *^C
     
    


Anyway, no real problems here :)

mackey
Premium Member
join:2007-08-20

mackey

Premium Member

said by mind21_98:

%u2022Safari on my MacBook Pro always uses IPv4 when both options are available. It looks like it's because latency on IPv6 is consistently higher than on IPv4. Not sure if this will be something that gets fixed over time as TWC adds more IPv6 peering.
%u2022Speaking of peering, it seems that any IPv6 traffic to AWS always goes through Seattle, at least to go to their Oregon datacenter. Is this normal?

For me, v6 is actually a few ms FASTER then v4:

v4: rtt min/avg/max/mdev = 11.748/15.571/26.633/5.685 ms
v6: rtt min/avg/max/mdev = 8.674/12.925/22.533/4.907 ms

Also, here in LA both v4 and v6 to newsrdr.us go through Seattle.

/M
mind21_98
join:2006-05-13
San Diego, CA

mind21_98

Member

said by mackey:

For me, v6 is actually a few ms FASTER then v4

Are you using TWC's DNS or some other DNS provider? I'm using Google's so I can get 10/10 at test-ipv6.com

mackey
Premium Member
join:2007-08-20

mackey

Premium Member

Goog for both v4 and v6 servers.

/M
mind21_98
join:2006-05-13
San Diego, CA

mind21_98

Member

Hmm. Might be within the margin of error. It's possible the router has something to do with it, but we won't know without additional data.
34764170 (banned)
join:2007-09-06
Etobicoke, ON

34764170 (banned) to mackey

Member

to mackey
said by mackey:

For me, v6 is actually a few ms FASTER then v4:

I have seen a good number of sites where that is the case, but of course it can go the other way around. It all depends on the path taken and the connectivity / peering with that path.
bodosom
Leger de main
Premium Member
join:2004-03-05
WNY/Niagara
ARRIS SB6183
Ubiquiti EdgeRouter X
pfSense SG-2220

bodosom to mind21_98

Premium Member

to mind21_98
said by mind21_98:

Are you using TWC's DNS or some other DNS provider? I'm using Google's so I can get 10/10 at test-ipv6.com

I use my own DNS caches. The score you get at test-ipv6 depends on the browser and the mirror. E.g. at the moment I have trouble using anything but the vr.org mirrors and while I can get an ideal 10/10 with Linux+Chromium I get "prefer ipv4" 10/10 on my Mac with all browsers.

socalSimiVly to bvierra

Anon

to bvierra
Click for full size
Click for full size
Click for full size
Native IPv6
Motorola SB6141 with Netgear WNR2000. Just checked today for IPv6 and it showed up. No idea how long it has been active! Southern California: Simi Valley.

tonyram57
join:2001-11-08
Brooklyn, NY

tonyram57 to bvierra

Member

to bvierra
Still confused. I have the Netgear WNDR4300. How do I activate it on my router?
dcn66100
join:2012-08-07

dcn66100

Member

In settings set ipv6 to auto config then power off router and then modem then turn modem on and wait til it is completely on the turn on wndr4300 it worked for me I have the same router.

Suit Up
join:2003-07-21
Los Angeles, CA
Ubiquiti EdgeRouter X
TP-Link Archer C7

1 edit

Suit Up to socalSimiVly

Member

to socalSimiVly
Tried it out tonight and I finally got a native IPv6 address! Requested a /64 prefix and that worked too. Awesome!

Surprisingly I got better speed results over IPv6 than IPv4:



Shutdown my he.net tunnel for now and I'll give this a few days to see how this works out.
Suit Up

Suit Up

Member

Well, I'm back on the he.net tunnel. The TWC IPv6 keeps making me manually renew the DHCPv6 lease every couple of hours, which I thought I had read someone else mention having a problem with, but I don't see it in this thread.

Also, for those interested, I was not able to request a /60 or /56. Only a /64.
34764170 (banned)
join:2007-09-06
Etobicoke, ON

34764170 (banned)

Member

said by Suit Up:

Well, I'm back on the he.net tunnel. The TWC IPv6 keeps making me manually renew the DHCPv6 lease every couple of hours, which I thought I had read someone else mention having a problem with, but I don't see it in this thread.

Also, for those interested, I was not able to request a /60 or /56. Only a /64.

What sort of device is connected to the cable connection?

It would seem that is expected so far. TWC will probably end up offering shorter prefixes at some point down the road once they are further along with their roll out.

AhnHEL
Angel
Premium Member
join:2000-09-11
Orlando, FL

AhnHEL

Premium Member

I can request a /60 using pfSense and it will assign me 4 ipv6 addresses for my 4 LAN networks. Only thing is, testing IPv6 always fails saying no IPv6 address. When I request a /64 for just my main LAN, everything works perfectly and I get a 10/10 from test-ipv6.com. So something is not right with anything bigger than a /64

Suit Up
join:2003-07-21
Los Angeles, CA
Ubiquiti EdgeRouter X
TP-Link Archer C7

Suit Up to 34764170

Member

to 34764170
said by 34764170:

What sort of device is connected to the cable connection?

I've got a Netgear WNDR3800 running a custom OpenWRT build.

tonyram57
join:2001-11-08
Brooklyn, NY

1 edit

tonyram57 to dcn66100

Member

to dcn66100
said by dcn66100:

In settings set ipv6 to auto config then power off router and then modem then turn modem on and wait til it is completely on the turn on wndr4300 it worked for me I have the same router.

Yea that work. Just went from 7/10 to 0/10. Now I have zero IPv6.
This is why IPv4 will be around forever and IPv6 will flop and go the way of the dinasours because no one can figure out how to get it to work. 6to4, Tureno crap. Just work like IPv4 does, stupid.

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA
TP-Link TD-8616
Asus RT-AC66U B1
Netgear FR114P

NormanS

MVM

said by tonyram57:

This is why IPv4 will be around forever and IPv6 will flop and go the way of the dinasours because no one can figure out how to get it to work.

I tried the Netgear WNDR4300. Trouble was, it wouldn't allow a "6in4" tunnel configuration. "6to4", but not "6in4"; two very different tunnel mechanisms. Both my ISP and Hurricane Electric require "6in4" tunnels. I returned the Netgear, and did a little more research. I bought an Asus RT-AC66U, which is able to set up either "6to4", or "6in4", as necessary. It can also handle "native" IPv6, though I currently have no way to test it.

Configuring a tunnel.

As for actually getting it to work:

Hurricane Electric

Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : Miyuki
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : aosake.net
 
Ethernet adapter Local Area Connection:
 
   Connection-specific DNS Suffix  . : aosake.net
   Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physical Address. . . . . . . . . : 00-00-00-00-00-00
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:1f05:448:zzzz:zzzz:zzzz:zzzz(Preferred)
   Temporary IPv6 Address. . . . . . : 2001:470:1f05:448:zzzz:zzzz:zzzz:zzzz(Preferred)
   Link-local IPv6 Address . . . . . : fe80::5d0f:704b:98b7:ff56%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.102.222(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, September 25, 2013 025222
   Lease Expires . . . . . . . . . . : Wednesday, October 09, 2013 073527
   Default Gateway . . . . . . . . . : fe80::62a4:4cff:fedc:9198%11
                                       192.168.102.1
   DHCP Server . . . . . . . . . . . : 192.168.102.1
   DHCPv6 IAID . . . . . . . . . . . : 248823513
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-89-27-65-D4-BE-D9-3F-82-EB
 
   DNS Servers . . . . . . . . . . . : 2001:470:20::2
                                       2001:4860:4860::8888
                                       2001:4860:4860::8844
                                       192.168.102.1
   Primary WINS Server . . . . . . . : 192.168.102.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
And an example trace route:
Tracing route to v6v4.portal-standard.aol.akadns.net [2001:4b0:1668:3c06:1::1]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Chihiro [2001:470:1f05:448::1]
  2    37 ms    36 ms    37 ms  NKonaya-1.tunnel.tserv3.fmt2.ipv6.he.net [2001:470:1f04:448::1]
  3    37 ms    31 ms    42 ms  gige-g5-19.core1.fmt2.he.net [2001:470:0:45::1]
  4    34 ms    32 ms    39 ms  10gigabitethernet1-1.core1.sjc2.he.net [2001:470:0:31::2]
  5    31 ms    36 ms    31 ms  as1668-aol-atdn.v309.core1.sjc2.he.net [2001:470:0:1df::2]
  6    32 ms    31 ms    32 ms  ipv6-portal-sjg-1.evip.aol.com [2001:4b0:1668:3c06:1::1]
 
Trace complete.
 
Once the hardware manufacturers figure it out, and the ISPs figure it out; it will happen.
smcallah
join:2004-08-05
Home

smcallah

Member

Just so you know, you only zzzz'd out the address of your computer in that output. The HE.net /64 is still visible, you are the "owner" of that entire block and it can be traced back to you. Your traceroute also exposes your router IP as the ::1 and exposes the /64 that HE.net uses to connect to you and only you.

So if you're trying to hide that it's you, you should only show 2001:470:, which is HE.net's /32.
smcallah

1 recommendation

smcallah to tonyram57

Member

to tonyram57
The only way that IPv4 is going to be able to stay around is by getting worse and similar to what IPv6 is facing now. 4in4 tunnels, 4in6 tunnels, NAT444. Carrier grade-NAT.

IPv6 just works on Windows 7+, Mac OS X, and Linux now. It also works on the ISP end just fine, but the large network vendors have just now been releasing hardware that will deliver IPv6 and IPv4 levels. And consumer grade network hardware is barely anywhere on this front. Not to mention the actual websites and other services that don't even have IPv6 enabled yet.

UKEE
join:2012-05-14
Lexington, KY

1 recommendation

UKEE

Member

said by smcallah:

IPv6 just works on Windows 7+, Mac OS X, and Linux now. It also works on the ISP end just fine, but the large network vendors have just now been releasing hardware that will deliver IPv6 and IPv4 levels. And consumer grade network hardware is barely anywhere on this front. Not to mention the actual websites and other services that don't even have IPv6 enabled yet.

So the patches by MS for XP and Vista don't work even though IP6 shows up in my Network Properties?

tonyram57
join:2001-11-08
Brooklyn, NY

tonyram57 to NormanS

Member

to NormanS

I tried the Netgear WNDR4300. Trouble was, it wouldn't allow a "6in4" tunnel configuration. "6to4", but not "6in4"; two very different tunnel mechanisms. Both my ISP and Hurricane Electric require "6in4" tunnels. I returned the Netgear, and did a little more research. I bought an Asus RT-AC66U, which is able to set up either "6to4", or "6in4", as necessary. It can also handle "native" IPv6, though I currently have no way to test it.

All that crap is confusing to anyone and you are still using IPv4. Teredo, tunneling, Hurricane Electric a big mess. It is not worth the hassle. IPv4 you just punch in a simple IP address for DNS and it works.

Also now IPv6 is showing on my connection using Teredo whatever that means again with IPv6 disabled in my router. If I enable IPv6 and then reboot my router it will not reconnect online unless I run setup again then I am back to 0/10 from 7/10. No amount of rebooting fixes it and it will show 7/10 after a couple of days of doing nothing after being disabled in my router.

There will always be IPv4 addresses so don't listen to these tech sites. There are many dormant addresses for sites that don't exist anymore.

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA
TP-Link TD-8616
Asus RT-AC66U B1
Netgear FR114P

1 recommendation

NormanS

MVM

said by tonyram57:

All that crap is confusing to anyone and you are still using IPv4. Teredo, tunneling, Hurricane Electric a big mess. It is not worth the hassle. IPv4 you just punch in a simple IP address for DNS and it works.

Hurricane Electric does not use Teredo tunneling; and my Teredo interface is disabled. While I am using IPv4 to get to HE, they are using IPv6 to get me to IPv6 web sites. Somewhat like using VPN, I imagine. My HE "6in4" (NOT Teredo!) tunnel is working fine, thank you.

Also now IPv6 is showing on my connection using Teredo whatever that means again with IPv6 disabled in my router. If I enable IPv6 and then reboot my router it will not reconnect online unless I run setup again then I am back to 0/10 from 7/10. No amount of rebooting fixes it and it will show 7/10 after a couple of days of doing nothing after being disabled in my router.

Teredo is a Microsoft tunneling mechanism which supposedly works through NAT. You should not need it; and HE gives instructions on disabling it in Windows XP. For Windows 7, I disabled it in Device Properties.

There will always be IPv4 addresses so don't listen to these tech sites. There are many dormant addresses for sites that don't exist anymore.

There will come a day when some interesting "hole-in-the-wall" site in some remote corner of the world won't have an IPv4 IP address. Should I just pretend it doesn't exist because it is not present on the IPv4 Internet?

Or is that just a "Sour Grapes" rhetorical argument?