![]() My modem is a Cisco DPC3000 and the router is a D-Link DIR-850L. I live in Blenheim ON I can successfully ping and. My IPv4 works perfectly and fast I have High Speed Internet - UltraFibre 60. The server assigns residential clients a dynamic IPv4 and IPv6 address that changes periodically. I've been a Cogeco customer for several years and I do not yet have IPv.6.Ĭogeco uses a cable modem technology that works with a DHCP server. Why lie and say the hardware doesn't support it?ĭid I get an incompetent support agent? should I try again? anyone from Cogeco care to comment? If they haven't yet implemented IPv6 for the static users, I get it. Even the product page for the router onsite says "IPv6 support on all models" ( » I was promptly told that the hardware used for static IPv4 does not support IPv6, which is complete rubbish, it's an 800 series Cisco router as the gateway onsite (Cogeco's gear) I've used the previous generation Cisco 800 series which had support for IPv6. ![]() So I called the business helpdesk and asked them if they would be so kind as to allocate our little subnet (it's not a big company) a /64 or similar so we could get our IPv6 going. firm) moved offices, including shiny new IPv6 compliant border hardware, I decided to give it a go and try to get IPv6 going. This is a really interesting post for me, I've been trying to get IPv6 working with Cogeco natively for years This week, my company (an I.T. connection timed out no servers could be reached ![]() What are you using as your local DNS Cache?See Reply below. Your dns cache should have been able to find and talk to the working one, however, and get your fast fail. One of the two reverse DNS servers (v6ns1) for Cogeco IPv6 appears to be having troubles. Any Cogeco engineers lurking out there that could help with this? :-) Since ipv6 is working so well otherwise, this little issue seems a pity. Mar 22 17:02:01 x named: error (unexpected RCODE REFUSED) resolving '.ip6.arpa/PTR/IN': 24.226.14.60#53Ĭogeco support, once I was able to explain the issue, basically said they don't support ipv6 so screw off. On one remote server I manage, for example, it takes about 15s to login via sshd or imapd, and this is in the logs of the nameserver: While this is not normally a problem, it causes delays in some cases where the remote server is doing a reverse DNS lookup, which becomes very slow because the PTR lookup. >HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25192 IPv6: Good, AS7992 - COGECOWAVE - Cogeco Cable,CAĮxcept for one issue - the authoritative DNS servers for Cogeco do not respond to requests for PTR records for ipv6 addresses, and worse they don't fail-fast but force the client to time out:ĭig -x 2001:1970:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx ![]() IPv4: Good, AS7992 - COGECOWAVE - Cogeco Cable,CA As a new Cogeco customer I was pleasantly surprised to see that Cogeco ipv6 works very very well - with no hassles, I was able to get a native ipv6 address and assign LAN addresses via DHCPv6 IA-PD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |