dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
3030
share rss forum feed

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

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

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:23

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
·WOW Internet and..
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


RR Conductor
NWP RR Inc.,serving NW CA
Premium
join:2002-04-02
Redwood Valley, CA
kudos:1

1 edit
reply to jlivingood
IPv6 is enabled here in the Ukiah, CA area now, but the native IPv6 isn't working with my Asus RT-N66U router, at least not Comcast's, either that or they haven't fully enabled IPv6 here yet. I guess I'll wait until Asus releases the new firmware this month and see if it addresses that, in the meantime I can run IPv6 using Comcast's 6to4 relay, and also using a HE 6in4 Tunnel. Netdog is working with me on this, thanks mi amigo!

AVonGauss
Premium
join:2007-11-01
Boynton Beach, FL

1 edit

1 recommendation

Which firmware version are you currently using? If you're using .112 you might want to try .108 (either the Asus official build or the Merlin modified version). For me at least, .112 broke IPv6 functionality.


RR Conductor
NWP RR Inc.,serving NW CA
Premium
join:2002-04-02
Redwood Valley, CA
kudos:1
I'm using the .116 beta build, I guess I could try going back to .108 and see if it makes a difference.


RR Conductor
NWP RR Inc.,serving NW CA
Premium
join:2002-04-02
Redwood Valley, CA
kudos:1
reply to jlivingood
Well, .108 didn't make a difference, Native IPv6 just isn't working on this router with Comcast's IPv6 here. I can get IPv6 using a HE 6in4 Tunnel and Comcast's Anycast 6to4 relay, so I guess all I can do is wait for Asus's FW release this month and see if it fixes this issue.

jsilver153

join:2007-08-11
Toms River, NJ
reply to jlivingood
Hi,

I am using a Netgear router and a Ubee Emta both are IPV6 capable. My Netgear is set as auto (6to4) yet when I ran IPV testing it comes back with a slow speed.

Has IPV6 been turned on in Toms River, NJ (08857).

Thanks


Mike Wolf

join:2009-05-24
Beachwood, NJ
kudos:4
said by jsilver153:

Hi,

I am using a Netgear router and a Ubee Emta both are IPV6 capable. My Netgear is set as auto (6to4) yet when I ran IPV testing it comes back with a slow speed.

Has IPV6 been turned on in Toms River, NJ (08857).

Thanks

yes it has, it's been turned on for about two weeks now.
»Re: [IPv6] Evidence of Comcast IPv6 CPE Dual Stack (CPE and CPEP

I would try setting the router to "native" or "auto" or "dhcp" or whichever the option is called for automatic configuration.
Also make sure your router is IPv6 supported.

jsilver153

join:2007-08-11
Toms River, NJ
Tks Mike. I set it to DHCP (it was on auto) now its working.

Joel


Mike Wolf

join:2009-05-24
Beachwood, NJ
kudos:4
sweet!

aers

join:2011-08-12
reply to jlivingood
Has anyone gotten this to work w/ OpenWRT? I have dhcp6c running and both my WAN and LAN interfaces have IPs:

eth1
inet6 addr: 2001:558:6045:46:705d:794f:XXXX:XXXX/128
br-lan
inet6 addr: 2601:9:1c00:2d:226:f2ff:XXXX:XXXX/64

However, I can't get any IPv6 traffic out of my router. I added a default route via the WAN interface and still no luck. I've confirmed everything works fine using stock firmware, but I'd rather use OpenWRT..