Native IPv6 with Airport stops working

Question

Hi!
My ISP has just started supporting native IPv6, which I would like to get working with my Airport Extreme as router.
After configuring the Airport in Router mode (AU 5.6), with automatic configuration, my router and all my devices are in fact configured with an IPv6 address.
However, now the weird problem starts:
After configuring the airport, it reboots, my devices receive an address, and IPv6 works!
....for about 10 seconds. During these 10 seconds, ping6 and telnet/browser to IPv6 addresses respond and work.
However, after about 10 seconds, ping stops responding, and new connections time out.
If I connect my computer directly to the cable modem, IPv6 works flawlessly.
I can also see the IPv6 router advertisement, where I receive a /64 network delegation.
I also know other users of the same ISP who have got this working fine with other routers.
Are there any known problems with the Airport Extreme with IPv6 in native mode?

Answer 1

jvbrandis wrote:
that is kind of a circular argument, isn't it? Unless people start using IPv6, the usage will not become any higher...
I was speaking of ISP's use of IPv6 when I cited only 1%. For users who's ISP's have not implemented it yet, they won't be able to use it.
I for one would like to perform some testing from my home environment, and if the Airport Express is not able to function as an IPv6 router, I will need to replace it with a devices that works.
Again, as far as I know it does, but in order to use it in your home environment, won't your ISP have to have implemented it natively as well (I know you said they did).
Btw; I have been using the Aiport Express in tunnel mode, which seems to work just fine (but has very bad performance, due to the 6to4 tunneling).
So perhaps your ISP only provides 6to4 tunneling when they said they implemented it. I know that has occurred in some Comcast areas. Perhaps a call to your ISP for some details is in order.