• Test IPv6
• Ofte Stilte Spørsmål
• World IPv6 Launch
• Local Times
• Speil
• Broken!

Hva du bør gjøre om du har problem...

Om du leser denne siden, betyr det at vi har har konkludert med at din datamaskin vil få problemer under World IPv6 Day. Enhvert nettsted som aktiverer IPv6 i tillegg til IPV4 vil bli utilgjengelig for deg.

For å løse dette, må du først identifisere hva din IPv6-adresse er (om du har en), samt din IPv6 standard-rute (om du har en). Dette vil hjelpe til med å bestemme hvilket avsnitt du bør lese.

Om du mener at ditt spesifikke problem ikke er godt beskrevet, eller om du har forslag til forbedringer, vennligst legg igjen en tilbekemlding ved å bruke skjemaet (eller ta kontakt med jfesler@test-ipv6.com).

• Finn ut din IP-adresse
• Om du har satt opp en IPv6-tunnel
• Om du bruker 6to4 (IPv6-adressen starter med 2002)
• Om du har ULA (IPv6-adressen starter med FC or FD)
• Om du har en uventet IPv6-adresse
• Om alle andre forsøk ikke hjelper, deaktiver eller de-prioriter IPv6

---

Finn ut din IP-adresse

Identify your IPv6 address, and your default router (if you have one).

Finding your IPv6 address and default router can be a challenge if you are not familiar with your OS's network configuration. Instructions for your OS are below.

When looking for your IPv6 address, skip any fe80: address. Everyone has them if their OS supports IPv6; this is regadless of whether or not your ISP supports IPv6 yet. Those are "link local" addresses; used just for communicating to other hosts in the same physical network as you.

---

Om du har satt opp en IPv6-tunnel

If you set up a tunnelbroker tunnel: The most common causes for tunnelbroker users to fail are:

• Your IPv4 address may have changed; you need to tell the tunnelbroker server this happened.
• If you are using your router to do the 6in4 (sometimes called 6to4 with explicit provider):
  • Make sure tunnelbroker knows your current IPv4 address. Our site tells you your public IPv4 address.
  • Make sure your router can ping the other side of the tunnel. Don't waste your time fixing computers until the router works!
• If you are using your Linux, BSD, Mac, or Windows box to "talk 6to4" specifically:
  • Make sure your router is passing "protocol 41" to you.
  • Make sure any software firewall you are operating is passing "protocol 41" to you.
  • If everything worked before your reboot but fails now, check your firewall settings.
  • Make sure the box "doing 6to4" can ping the other side of the tunnelbroker gateway before working on any other hosts.

---

Om du bruker 6to4

(IPv6-adressen starter med 2002)

If you use 6to4 (without a tunnel broker; ie, using anonymous 6to4):

The use of "automatic" 6to4, or the use of 6to4 without explicit configuration of the gateways, is not recommended. For more information see 6to4.

If you want to continue trying to debug anonymous 6to4:

• If you are using your router to do the 6to4:
  • Make sure your router has a public IPv4 address. Without this, 6to4 fails.
  • If your router permits you to log in, use "ping" or "ping6" and see if you can ping "ipv6.test-ipv6.com". Don't waste your time fixing computers until the router works!
• If you are using your Linux, BSD, Mac, or Windows box to "talk 6to4" specifically:
  • Make sure your router is passing "protocol 41" to you.
  • Most home systems have private IPv4 addresses; this won't work with 6to4 (unless..)
  • Make sure your 6to4 interface knows your public IPv4 address.
  • Make sure that your router permits protocol 41 from any IP address - not just 192.88.99.1. This will allow web sites to operate their half of 6to4, even if they can not spoof the 192.88.99.1 anycast address.
  • Linux users using iptables connection tracking: take heed of the previous note!
• Consider changing how you connect.
• • Ask your ISP if they offer any IPv6 connectivity (including possibly 6in4 tunnels, or tunnelbroker type tunnels).
  • See 6to4 for more information on why you would want to switch; and some options.

---

Om du har ULA

(IPv6-adressen starter med FC or FD)

ULA or Unique-Local-Unicast: If you have an IP address starting with FC or FD, you have what is effectively a private IPv6 address. It might be usable for talking to other devices within your home, or within your company. It also allows you to have a steady IPv6 address inside, even if your public IPv6 address changes regularly.

The main problem with ULA is that certain home routers are now offering ULA, *and* giving you a default route. This route is offered regardless of whether or not your router actually has IPv6 connectivity. From your browser's point of view, it doesn't know that your default route goes nowhere; there is no feedback mechanism. Since IPv6 is (roughly speaking) preferred over IPv4, your browser will try using this broken route. It may take minutes before giving up.

Our advice: Enable ULA only if your router has full time IPv6 connectivity. Disable it, otherwise. If you do disable it on your router, you will likely need to reboot your router first, then reboot your host, before the symptoms go away.

Specific instructions for boxes with known ULA problems:

• AVM FritzBox

---

Om du har en uventet IPv6-adresse

(IPv6-adressen starter med noe annet enn FE80

Unexpected IPv6 address?

Modern operating systems all have IPv6 enabled. This feature is dormant until someone explicitly configures IPv6, or a device on the local network offers it. Autoconfigured IPv6 hosts learn their IPv6 address and their gateway through the use of IPv6 router announcements (RAs). The network you are on may intentionally offer IPv6; you'll automatically use it when your computer sees it.

Where this goes wrong: Some people plug their router into the network (wired or wireless) and inadvertantly offer IPv6 services to everyone. Classic examples of this are where people add an early version of an Apple router (with 6to4 automatically enabled); another example is someone who has Windows Internet Connection Sharing enabled. In both cases, there is a chance they offer their services - and become your IPv6 router of choice, without any notification to you.

If these IPv6 routers don't work, you will fail to connect to any web site that offers services on both IPv4 and IPv6. Even if they do work, if the router in question is unplugged (the owner packs up, leaves the hotel/conference) your host never gets the notice; and it can be hours before it gives up.

This is similiar to someone accidentially (or intentionally) running a rogue DHCP server.

If you are are not the network admin - and have no access to fix the problem - consider disabling IPv6, at least for the location you are in. Another option might be to try turning off, and turning back on, your network interface (clearing the IP address), in case the source of the problem has left the network.

If you are the network administrator: You can use the default route information to identify the ethernet address; and then search for the owner of that ethernet address. Some network vendors have features that will suppress the advertisements of unauthorized RAs (router announcements); consider enabling those feaatures. More reactive measures involve finding (by ethernet address) the owner of the device; or possibly spoofing RA's from their device to indicate the device is going away.

---

Om alle andre forsøk ikke hjelper

(Instruksjoner for å skru av eller de-prioritere IPv6)

Disabling or Deprioritizing your IPv6 address

Copyright (C) 2010, 2012 Jason Fesler. All rights reserved. -- r692
Mirrors | Mission | Source | Email -   - Attributions
Dette er et speil av test-ipv6.com.