dslreports logo
 
    All Forums Hot Topics Gallery
spc

spacer

Search Topic:
uniqs
3059
share rss forum feed


jlivingood
Premium,VIP
join:2007-10-28
Philadelphia, PA
kudos:3

[IPv6] Monitoring World IPv6 Launch, June 5-6

Our war room is active and monitoring the event. If folks here notice anything out of the ordinary or seemingly broken due to IPv6, let us know here.

Thanks!

PS - Please don't ask general v6 questions here if you can (lots of other threads for that) -- potential v6 issues only.
--
JL
Comcast


FFH5
Premium
join:2002-03-03
Tavistock NJ
kudos:5
I've pulled an IPV6 for Comcast.net, but NOT Comcast.com.


jlivingood
Premium,VIP
join:2007-10-28
Philadelphia, PA
kudos:3

1 recommendation

said by FFH5:

I've pulled an IPV6 for Comcast.net, but NOT Comcast.com.

That's expected - the .com site has not yet moved to v6.
--
JL
Comcast


RR Conductor
NWP RR Inc.,serving NW CA
Premium
join:2002-04-02
Redwood Valley, CA
kudos:1
reply to jlivingood
According to Netdog our CMTS (Ukiah, CA, Mendocino County in Northwestern California) still isn't IPv6 ready, so the only way to get IPv6 here right now is to get a tunnel from someone like Hurricane Electric, or use the 6to4 relays Comcast is running. He is working with the local market on this, but no word back yet.

Edit-We're part of the Comcast North Bay Network, though physically we're over 100 miles north of SF.

coold8
Premium
join:2005-05-15
Arlington, VA
reply to jlivingood
Hi,

I have Comcast Extreme 105 here in Arlington, VA. My connection is rated 10/10 for ipv6. Also, I am using Google's DNS servers configured through my router 8.8.8.8 and 8.8.4.4 . The issue I am having is that when I run a IPv6 test at the end of the test the internet stops working, or if I browse the internet for 5-10 minutes, the internet suddenly crashes. While it is working, there are no problems with speed. I have tried switching browsers without avail. At the same time, my non ipv6 devices are not affected, and when I disconnect and reconnect the ethernet cord or release/renew the IP address on the computer, the internet starts working again. Any ideas? Is it a problem with my router? Problem with Comcast when access IPv6 sites?

Router Info:

Hardware Version WNDR4500 Firmware Version V1.0.1.6_1.0.24 GUI Language Version V1.0.1.6_2.1.15.15

I currently have the following settings on my Netgear WNDR4500 (IP Addresses redacted):

Internet Connection Type DHCP

User Class (if Required) Domain Name (If Required) Router's IPv6 Address On WAN 2001:558:6020:1a0:XXXX:XXXX:XXXX:XXXX/64

LAN Setup Router's IPv6 Address On LAN 2601:a:5000:21:XXXX:XXXX:XXXX:XXXX/64 IP Address Assignment:
Auto Config (Selected)

In addition, my Cable Modem is a Motorola SB6121.

Thanks.

-Dave


Clever_Proxy
Premium
join:2004-05-14
Villa Park, IL
reply to jlivingood
No issues here! I'm a dual stacking madman using prefix delegation on a cisco 881.


whfsdude
Premium
join:2003-04-05
Washington, DC
Reviews:
·Comcast
reply to coold8
said by coold8:

The issue I am having is that when I run a IPv6 test at the end of the test the internet stops working, or if I browse the internet for 5-10 minutes, the internet suddenly crashes.

This does not seem directly IPv6 related. Chrome and Firefox both support Happy Eyeballs where if an IPv6 address becomes unreachable (because IPv6 breaks or is broken), they will back off a default to using IPv4. IPv6 is given a 300 ms head start, if it is unreachable by then, IPv4 is used.

I do have one thought. Maybe your getting Comcast's DNSSEC DNS servers over IPv6 which are defaulting to those and possibly causing a problem on the machine related to DNSSEC?

IPv6 will take precedence over IPv4 for DNS.

What operating system are you using?

Also you might want check the signal levels on the modem? Should always rule out a layer 1 issue. You can do so by visiting »192.168.100.1/

Gerard1234

join:2012-04-03
Reviews:
·Comcast

2 edits
reply to jlivingood


coold8
Premium
join:2005-05-15
Arlington, VA
reply to whfsdude
Hi,

I have gone ahead and disabled "Disable IGMP Proxying" on my router because there was some issues. The service is still however dropping in and out. Please note, this only happens when I enable IPv6 on my router. When IPv6 is disabled, I notice no issues what so ever. I have also reached out to Netgear to see if there was possibly a bug involving IPv6 but have yet to hear back.

Cable Modem Levels:

Downstream Bonding Channel Value
Channel ID 5 6 7 8
Frequency 669000000 Hz 675000000 Hz 681000000 Hz 687000000 Hz
Signal to Noise Ratio 36 dB 37 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
6 dBmV 6 dBmV 6 dBmV 6 dBmV
Upstream Bonding Channel Value
Channel ID 2
Frequency 29600000 Hz
Ranging Service ID 6148
Symbol Rate 5.120 Msym/sec
Power Level 38 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM

Ranging Status Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 710932086 710932394 710932563 710932656
Total Correctable Codewords 60 34 42 40
Total Uncorrectable Codewords 637 542 520 571

Thanks.

-Dave


whfsdude
Premium
join:2003-04-05
Washington, DC
Reviews:
·Comcast
Levels look good.

Multicast forwarding should not be causing you any issues whatsoever. I assume that setting also controls MLD proxying because IGMP is for v4.

When you're on IPv6 and you can no longer browse can you:
1. ping6 ipv6.google.com
2. ping6 2001:558:6020:1a0::1 #comcast's v6 gateway for you

Additionally, can your IPv4 traffic get through?
1. ping 8.8.8.8
2. ping your_comcast_v4_gateway

coold8
Premium
join:2005-05-15
Arlington, VA
reply to jlivingood
Hi,

Let me know if there is anything else you need. What I find interesting is that Safari seems to be more affected by the crashes than Chrome. Any opinions?

ping6 2001:558:6020:1a0::1
PING6(56=40+8+8 bytes) 2601:a:5000:21:f440:6f8b:2122:d4a1 --> 2001:558:6020:1a0::1
16 bytes from 2001:558:6020:1a0::1, icmp_seq=0 hlim=63 time=23.242 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=1 hlim=63 time=11.761 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=2 hlim=63 time=78.344 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=3 hlim=63 time=11.840 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=4 hlim=63 time=9.577 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=5 hlim=63 time=7.892 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=6 hlim=63 time=8.838 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=7 hlim=63 time=9.501 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=8 hlim=63 time=9.918 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=9 hlim=63 time=10.848 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=10 hlim=63 time=9.487 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=11 hlim=63 time=20.785 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=12 hlim=63 time=8.422 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=13 hlim=63 time=9.318 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=14 hlim=63 time=10.275 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=15 hlim=63 time=8.997 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=16 hlim=63 time=16.773 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=17 hlim=63 time=12.929 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=18 hlim=63 time=11.449 ms
16 bytes from 2001:558:6020:1a0::1, icmp_seq=19 hlim=63 time=9.216 ms

Ping Comcast Gateway
PING 69.140.0.1 (69.140.0.1): 56 data bytes
64 bytes from 69.140.0.1: icmp_seq=0 ttl=254 time=39.502 ms
64 bytes from 69.140.0.1: icmp_seq=1 ttl=254 time=9.637 ms
64 bytes from 69.140.0.1: icmp_seq=2 ttl=254 time=12.008 ms
64 bytes from 69.140.0.1: icmp_seq=3 ttl=254 time=9.208 ms
64 bytes from 69.140.0.1: icmp_seq=4 ttl=254 time=27.411 ms
64 bytes from 69.140.0.1: icmp_seq=5 ttl=254 time=18.832 ms
64 bytes from 69.140.0.1: icmp_seq=6 ttl=254 time=8.648 ms
64 bytes from 69.140.0.1: icmp_seq=7 ttl=254 time=9.015 ms
64 bytes from 69.140.0.1: icmp_seq=8 ttl=254 time=10.984 ms
64 bytes from 69.140.0.1: icmp_seq=9 ttl=254 time=10.331 ms
64 bytes from 69.140.0.1: icmp_seq=10 ttl=254 time=10.563 ms
64 bytes from 69.140.0.1: icmp_seq=11 ttl=254 time=8.051 ms
64 bytes from 69.140.0.1: icmp_seq=12 ttl=254 time=8.177 ms
64 bytes from 69.140.0.1: icmp_seq=13 ttl=254 time=11.561 ms
64 bytes from 69.140.0.1: icmp_seq=14 ttl=254 time=9.333 ms
64 bytes from 69.140.0.1: icmp_seq=15 ttl=254 time=18.997 ms
64 bytes from 69.140.0.1: icmp_seq=16 ttl=254 time=7.904 ms
64 bytes from 69.140.0.1: icmp_seq=17 ttl=254 time=8.156 ms
64 bytes from 69.140.0.1: icmp_seq=18 ttl=254 time=27.132 ms
64 bytes from 69.140.0.1: icmp_seq=19 ttl=254 time=46.424 ms
64 bytes from 69.140.0.1: icmp_seq=20 ttl=254 time=10.670 ms

Davids-MacBook-Pro:~ XXXX$ ping6 ipv6.google.com
ping6: getaddrinfo -- nodename nor servname provided, or not known

PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=16.622 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=17.292 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=16.435 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=13.385 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=13.932 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=16.388 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=16.037 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=54 time=20.071 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=54 time=64.684 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=54 time=12.482 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=54 time=11.922 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=54 time=27.958 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=54 time=11.618 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=54 time=21.566 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=54 time=21.953 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=54 time=12.231 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=54 time=13.662 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=54 time=22.065 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=54 time=12.070 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=54 time=15.669 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=54 time=18.020 ms

Test-ipv6.com Check: (USING COMCAST DNS)
Test with IPv4 DNS record
 
ok (0.196s) using ipv4
Test with IPv6 DNS record
 
ok (0.109s) using ipv6
Test with Dual Stack DNS record
 
ok (0.096s) using ipv6
Test for Dual Stack DNS and large packet
 
ok (0.103s) using ipv6
Test IPv4 without DNS
 
ok (0.194s) using ipv4
Test IPv6 without DNS
 
ok (0.301s) using ipv6
Test IPv6 large packet
 
ok (0.099s) using ipv6
Test if your ISP's DNS server uses IPv6
 
ok (0.095s) using ipv6

Test-ipv6.com Check: (USING GOOGLE DNS)
Test with IPv4 DNS record 
ok (1.732s) using ipv4
Test with IPv6 DNS record 
ok (0.160s) using ipv6
Test with Dual Stack DNS record 
ok (0.097s) using ipv4
Test for Dual Stack DNS and large packet 
ok (0.103s) using ipv4
Test IPv4 without DNS 
ok (0.107s) using ipv4
Test IPv6 without DNS 
ok (0.110s) using ipv6
Test IPv6 large packet 
ok (0.109s) using ipv6
Test if your ISP's DNS server uses IPv6 
ok (0.122s) using ipv4

Comcast IPv6 Check: (USING GOOGLE DNS)

Test with IPv4 DNS record
 
ok (0.230s) using ipv4
Test with IPv6 DNS record
 
timeout (15.014s)
Test with Dual Stack DNS record
 
ok (0.152s) using ipv4
Test for Dual Stack DNS and large packet
 
ok (0.141s) using ipv4
Test IPv4 without DNS
 
ok (0.144s) using ipv4
Test IPv6 without DNS
 
timeout (15.010s)
Test IPv6 large packet
 
timeout (15.010s)
Test if your ISP's DNS server uses IPv6
 
ok (0.144s) using ipv4

Comcast IPv6 Check: (USING COMCAST DNS)

Test with IPv4 DNS record
 
ok (0.217s) using ipv4
Test with IPv6 DNS record
 
timeout (15.025s)
Test with Dual Stack DNS record
 
ok (0.433s) using ipv4
Test for Dual Stack DNS and large packet
 
ok (0.439s) using ipv4
Test IPv4 without DNS
 
ok (0.140s) using ipv4
Test IPv6 without DNS
 
timeout (15.023s)
Test IPv6 large packet
 
timeout (15.011s)
Test if your ISP's DNS server uses IPv6
 
ok (0.444s) using ipv4

Thanks.

-Dave

coold8
Premium
join:2005-05-15
Arlington, VA
reply to jlivingood
Hi,

All of these results were confirmed when it dropped again. Seems like the DNS just stops working but the actually IP addresses keeping working. Very strange.

jsilver153

join:2007-08-11
Toms River, NJ
reply to whfsdude
Works here but slow.


Gerard1234

join:2012-04-03
You are not Native IPV6 you are on the 6 to 4 tunnel.

Gerard1234

join:2012-04-03
Reviews:
·Comcast

1 edit
reply to jlivingood



I disabled IPV4 to see how fast the pages that support IPV6 work and sometimes the pages load faster than the IPV4. On some test sites IPV6 rains supreme as far as uploads and downloads.

coold8
Premium
join:2005-05-15
Arlington, VA
reply to jlivingood
I have a brilliant response from our friends at Netgear:

"From Agent ID: 1295

Case ID: 18717063

Dear David,

Thank you for choosing NETGEAR. My name is Rukzana, and I am your support engineer today.

I understand that you have Intermittent connection while connecting to the Ipv6. We apologize for this inconvenience. Because we are doing this online, it might require a few email exchanges to resolve the issue. Rest assured that we will do our best to resolve your case quickly.

Here are the troubleshooting steps we recommend you try:

Please click on the link below and follow the steps to download and reflash the latest firmware to the router:

»support.netgear.com/app/answers/ ··· id/20066

NOTE: In this window you see the option "Click here to download". Click on it and select the option "Save file" and save it to the desktop.

You can reflash by using the Web interface Router Upgrade menu. Firmware reflash should be done with the wired computer (connect your computer to any of the four LAN ports of the NETGEAR router and follow the steps to upgrade the firmware).

1) Download the firmware and save it in the desktop.
2) Open Internet Explorer or any other browser and access the site:
»192.168.1.1, »10.0.0.1 or »routerlogin.com/basicsetting.htm. By default, enter the User Name as 'admin' and Password as 'password' (If you have changed the password then try with that password).
3) Click Router Upgrade under Maintenance.
4) Click Browse and find the file you just downloaded.
5) Click Upload. Do not interrupt the upgrade and wait till the router reboots when the upgrade is done.
6) After the router boots up, you must reset the router to default settings after upgrading the firmware.

We hope this resolves the problem. Please contact us again if the issue is not fixed. We can reset and reconfigure the settings in order to isolate the issue.

Please do visit »support.netgear.com for any technical queries regarding NETGEAR products.

A notice will automatically be sent to your email address when we have responded to your inquiry. Please DO NOT REPLY to that email. Instead, to add additional information to your case, click No to the question "Was your problem resolved with the information provided by the NETGEAR representative above?"

If you click YES, your case will be closed and a separate email containing a survey link will be sent so you can share with us your customer support experience.

Thanks again for choosing NETGEAR. Have a great day!

Sincerely,
Rukzana
Technical Support
NETGEAR, Inc.
»my.netgear.com

***NOTE: Your case will auto close after 7 days of inactivity.***

Did you know that NETGEAR provides support for all your home networking devices and PCs? We can provide a one-stop solution - no need to call multiple vendors* for support. If you would like to learn more about the NETGEAR Gearhead services, go to »kbserver.netgear.com/kb_web_file ··· e.html."

I asked to be escalated which the agent did agree to do. Too bad about those intermittent connection issues while connecting to the IPv6. Looks like we got a long way to go before every household has IPv6!

-Dave

Gerard1234

join:2012-04-03
reply to jlivingood
dslreports is not ipv6?


Tibby
Winbeta
Premium
join:2002-06-01
Oswego, IL
reply to jlivingood
Working well so far in Oswego, IL
--
VP - WinBeta

34764170

join:2007-09-06
Etobicoke, ON
reply to Gerard1234
said by Gerard1234:

dslreports is not ipv6?

No. Try posting...

»[request] IPv6 enabled, when? (version 2)


jlivingood
Premium,VIP
join:2007-10-28
Philadelphia, PA
kudos:3
reply to coold8
said by coold8:

Hi,

All of these results were confirmed when it dropped again. Seems like the DNS just stops working but the actually IP addresses keeping working. Very strange.

Please run this test: »netalyzr.icsi.berkeley.edu/m=com ··· =comcast

I recommend for now you use our DNS while you isolate this. Sounds a bit like something odd with your home gateway device. When you see "DNS stop working" it'd be good to have you run some DNS tests - like "dig www.comcast6.net AAAA" to see what, if any, DNS errors you see. It is possible your gateway is doing DNS proxying (and not well).
--
JL
Comcast

ctggzg
Premium
join:2005-02-11
USA
kudos:2
reply to FFH5
said by FFH5:

I've pulled an IPV6 for Comcast.net, but NOT Comcast.com.

Actually I get a 6 for www.comcast.net but not comcast.net.

coold8
Premium
join:2005-05-15
Arlington, VA
reply to jlivingood
Hi,

I am using Comcast DNS.

The ICSI Netalyzr
Start » Analysis » Results
Result Summary + – (help)
c-69-140-2-84.hsd1.va.comcast.net / 69.140.2.84
Recorded at 10:44 EDT (14:44 UTC), Jun 06 2012. Permalink. Referrer. Client/server transcript.
Summary of Noteworthy Events + –
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
Some DNS resolvers appear to be down
Address-based Tests + –
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Yes +
Reachability Tests + –
TCP connectivity (?): Note –
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): OK +
Traceroute (?): OK +
Path MTU (?): OK +
Network Access Link Properties + –
Network latency measurements (?): Latency: 15ms Loss: 0.0% +
TCP connection setup latency (?): 22ms +
Network background health measurement (?): no transient outages +
Network bandwidth (?): Upload 10 Mbit/sec, Download >20 Mbit/sec +
Network buffer measurements (?): Uplink 340 ms, Downlink is good +
HTTP Tests + –
Address-based HTTP proxy detection (?): OK +
Content-based HTTP proxy detection (?): OK +
HTTP proxy detection via malformed requests (?): OK +
Filetype-based filtering (?): OK +
HTTP caching behavior (?): OK +
JavaScript-based tests (?): OK +
DNS Tests + –
Restricted domain DNS lookup (?): OK +
Unrestricted domain DNS lookup (?): OK +
Direct DNS support (?): OK +
Direct EDNS support (?): OK +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 100ms +
Direct probing of DNS resolvers (?) –
Your system is configured to use 2 DNS resolver(s).
The resolver at 10.1.1.1 can process all tested types. It validates DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
The resolver at fe80::2eb0:5dff:fe26:4bd6 is not responding to requests.
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
DNS results wildcarding (?): OK +
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?): +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): OK +
IPv6 connectivity (?): OK +
IPv6 TCP connectivity (?): OK +
IPv6 Path MTU (?): OK +
IPv6 Traceroute (?): OK +
Host Properties + –
System clock accuracy (?): OK +
Browser properties (?): OK +
Uploaded data (?): OK +
Feedback + –
User-provided feedback +
ID ae81b058-1461-c993767d-f873-4d63-bf81 FAQs + Blog + Links + ICSI

Thanks.

-Dave


whfsdude
Premium
join:2003-04-05
Washington, DC
Reviews:
·Comcast
Dave,

quote:
The resolver at fe80::2eb0:5dff:fe26:4bd6 is not responding to requests.

Looks like your router might be running its own DNS server, which I bet has a broken v6 implementation.

What happens if you set Comcast's v6 DNS servers statically on one of your machines.

Comcast's DNS Servers:
2001:558:FEED::1
2001:558:FEED::2

coold8
Premium
join:2005-05-15
Arlington, VA

1 recommendation

Hi there,

I tried that and when manually set the problem goes away. I went ahead and bought a Linksys EA4500 just to see how it would respond. So far there are 0 problems with it. I have a feeling Netgear's firmware just is not ready for IPv6 yet. There is something funky going on with it's DNS, and it is likely a firmware update issue.

Thanks for your help.

-Dave


jlivingood
Premium,VIP
join:2007-10-28
Philadelphia, PA
kudos:3
said by coold8:

Hi there,

I tried that and when manually set the problem goes away. I went ahead and bought a Linksys EA4500 just to see how it would respond. So far there are 0 problems with it. I have a feeling Netgear's firmware just is not ready for IPv6 yet. There is something funky going on with it's DNS, and it is likely a firmware update issue.

Interesting -- glad it is now fixed with the new Linksys device!
--
JL
Comcast


sortofageek
Runs from Clowns
Premium,Mod
join:2001-08-19
kudos:24

1 recommendation

There is a beta firmware out for the Netgear WNDR3700 v1 router, which seems to have fixed issues with Native IPv6 for at least one person so far. It is probably a similar issue since it has "dns" in the file name.

See this topic ---> »[IPv6] Netgear WNDR3700v1 and Ipv6 Issues
--
Join Team Helix * I am praying for these friends .

Dumaine

join:2010-12-05
Detroit, MI
the beta Firmware didnt help me here in Detroit on the 3700 at all (still no Ip on WAN) yet my Linksys E4200 had no problems at all

Gerard1234

join:2012-04-03
Reviews:
·Comcast
Do you have a eMTA, like an arris model. If you do then unplug your WAN cable from the netgear v1 router press the power button on the back off wait for 30 seconds then push the button to turn on the netgear v1 router, wait for the router to completely boot for example the power light will turn from yellow to green, then plug the WAN cable back in. Now wait to the WAN light turns green, then check the router's ipv6 configuration page and see if you have a prefix of 2001 on the WAN and 2006 and the LAN. You can use auto config or DHCP, but DHCP is preferred with this firmware. You should not have to do this again once it is done once even if the power goes out.

Dumaine

join:2010-12-05
Detroit, MI

1 edit
Thanks..............low and behold that fixed it......you are a lifesaver. Although I have the Ubee modem, I did it your way with success!


Streetlight

join:2005-11-07
Colorado Springs, CO

1 recommendation

reply to sortofageek
said by sortofageek:

There is a beta firmware out for the Netgear WNDR3700 v1 router, which seems to have fixed issues with Native IPv6 for at least one person so far. It is probably a similar issue since it has "dns" in the file name.

See this topic ---> »[IPv6] Netgear WNDR3700v1 and Ipv6 Issues

The application of the beta firmware update for my WNDR3700 V1 solved the problem I had getting IPv6 to work. This firmware update results in the router's firmware being updated to V1.0.16.98-dnsNA.

I also had a problem with Firefox 13.0. According to Mozilla, FF should be IPv6 ready by default. For some reason, my Firefox 13.0 had network.dns.disableIPv6 in about:config set to true, so IPv6 tests failed. Mozilla says this should be false by default. Took much time to find the problem!

This transition to IPv6 could be very difficult for those who are much less tech savvy than those who visit DSLreports. Most PC users turn on their computers and expect to get connected and will be frustrated when trying to get to IPv6 only sites. Maybe there's a business opportunity here.
--
There is nothing more deceptive than an obvious fact.

Sherlock Holmes in
The Boscombe Valley Mystery
A. C. Doyle
Strand Magazine, October 1891