Test-ipv6

[Muredac Ford]

Ifyou use this Firefox add-on, you'll need to "Temporarily allow all this page". You will need to do this twice for everything to work. Alternately, disable NoScript entirely until you are done with this site.

How this test works: Your browser will be instructed to reach a series of URLs. The combination of successes and failures tells a story about how ready you are for when publishers start offering their web sites on IPv6.

If the summary results indicated problems, you (or your technical support) may be able to use the information above to diagnose the issues. Each of the test urls and their results is shown on the left side. To the right you'll see a description of what that URL was designed to test.

Your particular configuration is of interest. We are always striving to make the test-ipv6.com code better. Would you be willing to contribute more information about your browser and computer setup? With your help, we can document for others how to repair their systems.

This form will let you leave a comment, voice concerns, or ask questions. Your test results will be included automatically. This includes your IP address, which is shared with the site administrator in order to answer your questions. Use of this form implies consent.

(FAQ) page is available for your exact set of results. Please read it before leaving comments; many questions have already been answered. If you still have questions, comments, or concerns, feel free to use this form.

If reporting a problem with the test, or requesting help with your results, please fill out all requested information to the best of your ability. If leaving general comments, use your best judgement on how much to report.

This web site is not a tool for security or forensic analysis. If you have security concerns, please find a security professional to consult with. They can offer investigation and education that is appropriately matched to your concerns.

If your Internet help desk asks you to mail the 'results url', copy and paste the following URL.Note that this will share your current numeric Internet Protocol address(es).We do not recommend posting this link on public web sites such as forums.

It is real easy to get added to this list for basic checks. Just provide two image URLs (one IPv4-only; one IPv6-only), to Jason Fesler . Also send your general web site address and organization name.

I see that test-ipv6.com returns a different internet IPv6 address for each of my LAN-hosts' net devices alternatively there may be a way of getting that info from the output of each host. So:

will list the IPv6 addresses associated with each network device but I don't know how to identify which one of those addresses is the address "on the public internet". Is there a universal rule, a pattern that identifies that address?

A Best Current Operational Practices (BCOP) document describes best current operational practice on a particular topic, as agreed by subject matter experts and periodically reviewed by the Internet community.

This BCOP provides a basic and generic foundation for any user centric helpdesk that deals with IPv6 residential ISP customer connectivity. The focus is on techniques and solutions for the most common IPv6 user connectivity issues. While the focus of this document is on residential ISP networks, enterprise IT helpdesks and other frontline support personnel may find information in this BCOP useful.

Note that this document is also of value to ISPs who have not yet deployed IPv6, as their customers might be experiencing connectivity issues caused by inadvertent (or intentional) use of IPv6 transition technologies such as tunnel brokers, 6to4 or Teredo. The Connectivity Test tool described below will automatically detect the use of such tools and report them to your helpdesk technicians.

This document is intended to be a template that can be altered and supplemented with all the necessary individual company specifics so that each company can build the most suitable policy and procedures to follow when an IPv6 issue is detected.

Several cases rely on checking settings on the home router. The helpdesk technician will need to be familiar with router configurations on the devices their customers may use, or refer to vendor documentation. Also, the technician may need to determine whether the IPv6 address space used by the customer is allocated from the company (it may not be if the customer is using a tunnel broker, for example) so you will need to supply your helpdesk technicians with a list of valid IPv6 prefixes used by your residential service.

If the user cannot reach the site at all, have the user visit IPv6only version of the connectivity test site at ipv6.testv6.com/helpdesk. If the site is reachable, refer to the corresponding section of this document to interpret the results and follow the troubleshooting steps defined there. If the user can reach neither isp.test-ipv6.com nor ipv6.testv6.com/helpdesk, follow standard procedures and scripts to determine whether there's a physical connectivity problem or another standard complication. If the site is available to the user, continue using this document.

Interpretation: IPv6 network connectivity somewhere between the user and the website is broken. IPv6 connections are timing out instead of succeeding (or failing fast to IPv4). The user experience visiting major websites may be suffering and some applications are completely failing.

Confirm whether the user's equipment (modem, router) supports IPv6, based on company list of approved devices. Some retail equipment may also support IPv6. A firmware upgrade may be required. A reboot may trigger a firmware upgrade, or your company may have documented processes to upgrade firmware.

Network problem.

If your organisation dynamically assigns IP addresses, then escalate.

If your organisation statically assigns IP addresses, verify that the customer has the proper details as per company documentation for WAN, LAN and default gateway. If the customer confirms that the details are entered as assigned, then escalate.

This address is a known invalid address. Encourage the customer to call their router vendor for support. The vendor has incorrectly implemented IPv6, using the prefix reserved for documentation (2001:db8::) or another test prefix (e.g., 2005:123::). It is reasonable to expect a firmware update that will fix the problem. Escalate. If the ISP provided the router, escalate to an engineer to escalate to the router vendor. If the customer provided the router, they will have to contact vendor support themselves. Alternatively, the ISP might provide equipment.

It is normal for devices to have multiple IPv6 addresses. However, it's possible that the device is having trouble determining which address to use.

Source address selection problem?

Network problem? Escalate.

Follow standard procedures and scripts to determine whether there's a physical connectivity problem or other standard complication. If only IPv6 is slow; if the user is using a tunnel, suggest they change their tunnel to a closer location.

Interpretation: Teredo was used to provide an IPv6 address and the host was configured to actively take advantage of this service. Any website that has an IPv6 presence will be reached using Teredo instead of native IPv4. Modern operating systems do not prefer these kinds of tunnels by default. Be aware that the user might have a very old operating system or a non-default configuration.

Interpretation: This is an example of a healthy IPv4 + IPv6 configuration. The IPv6 connectivity appears to be announced by a different entity (or at least a different BGP ASN) than IPv4.

Ask the user to read the IPv4 and IPv6 lines. Ensure that the ASN or company name represented makes sense for your organisation. If the user is using a foreign IPv6 service, consider reprovisioning the user to your own IPv6 service.

Interpretation: IPv6 MTU issues are typically caused by ICMPv6 filtering at some point along the path. Small requests were fast, large requests were slow (and/or timed out). There are too many possible solutions to be checked.

This issue requires a deeper understanding of IPv6 protocol and solving of this issue depends on how your helpdesk is organised. If you have a two- or three-tier helpdesk, hand it over to second level support, clearly noting that there are MTU issues. If you have just one-tier helpdesk, hand it over to appropriate escalation department/contact, depending on your escalation policy.

Ensure the user is using your network services (not tunnels). If the user is using tunnels, disable the tunnel as described above. If this error condition persists, rerun the test troubleshoot as described in the section for the corresponding code.

IPv6 training for helpdesks is available from many IPv6 training companies all around the world or can be tailored to suit your needs (e.g. basic IPv6 training for engineers and technical staff ). When you are rolling out IPv6 in production you need to train all your staff to balance the IPv4 and IPv6 knowledge anyway, so talk to your training agency and ask them to adapt their IPv6 education program and train your helpdesk team.

Special thanks goes to Jernej Horvat from Amis - the idea for this document came out of a discussion with him about the hurdles that he's facing as an operator that prevent him from enabling IPv6 for all residential customers.

ok I am sorry. Somehow I got it to work with just a restart after i put in server_host: ::0 and then with feste-ip.net

So what I did:

configure Hassio. After that expose the port in the router. Put in server_host: ::0 use feste-ip net to get an adress and then reboot the pi (not just restart hassio instance). It works for me

3a8082e126