-
All replies
-
Helpful answers
-
-
-
Feb 11, 2013 9:06 PM in response to Bradley Froehleby jocover,IPv6 tunnel broker no work!!! help me !!!!!!
-
Feb 12, 2013 5:23 AM in response to jocoverby John Vestal1,Ok. You need to provide us some more information. What kind of tunnel do you have. What are your settings that don't appear to work.
John
-
Feb 12, 2013 3:23 PM in response to John Vestal1by Mike Baehr,John, I, like you, have a SixXS tunnel (with a routed /48) that stopped working after I upgraded to 7.6.3.
The new firmware insists on specifying a delegated prefix, which is fine... I carved a /64 off of my /48 and set it as the delegated prefix in Airport Utility. However, the change does not take. In fact, if I open the IPv6 config again, the delegated prefix field is empty.
Airport Utility seems to be doing some sort of validation of the delegated prefix field that is rejecting everything I put in there. I've had to downgrade to 7.6.1 to get my tunnel working.
-
Feb 12, 2013 3:51 PM in response to Mike Baehrby John Vestal1,MIke,
Do you want to debug this or are you happy with the roll-back? I suspect that you have a configuration issue.
John
-
Feb 12, 2013 3:57 PM in response to John Vestal1by Mike Baehr,I'd like to debug it, if possible. The problem, as far as I can tell, is in Airport Utility, not the firmware. Airport Utility will not accept anything I specify as the delegated prefix. I've slightly scrambled my information so as to avoid giving my actual IP:
IPv6 WAN Address: 2001:1939:85:271::2
IPv6 Default Route: 2001:1939:85:271::1
Remove IPv4 Address: 209.197.5.66
IPv6 Delegated Prefix: 2001:1939:3df:ada::/64
IPv6 LAN Address: 2001:1939:3df:ada::1
When I click "Save", it appears to have been successful. But when I open "Internet Options" back up, the IPv6 Delegated Prefix field is blank.
-
Feb 12, 2013 4:01 PM in response to Mike Baehrby John Vestal1,Mike,
One thing I see:
LAN Address should look like this;
2001:3948:0011:410d::
Prefix is:
2001:3948:0011:410d::/64
John
-
Feb 12, 2013 4:04 PM in response to John Vestal1by Mike Baehr,Even if I specify it like that, leaving in all the leading zeroes, it still rejects it silently.
Below example still does not work:
Prefix: 2001:1939:3df:ada::/64
LAN Address: 2001:1939:3df:ada::
I feel like it is rejecting it due to something else, perhaps because the third "octet" of the /48 does not match the IPv6 WAN address, but that is SixXS's doing and it's never been a problem before...
-
Feb 12, 2013 4:08 PM in response to Mike Baehrby John Vestal1,Test that theory. Put 2001:1939:85:ada::/64 in prefix and 2001:1939:85:ada:: just to see if it will save that.
John
-
Feb 12, 2013 4:11 PM in response to John Vestal1by Mike Baehr,No dice. I've posted to ipv6-dev list (https://lists.apple.com/mailman/listinfo/ipv6-dev) to see if they have any ideas.
-
Feb 12, 2013 4:14 PM in response to Mike Baehrby John Vestal1,Mike,
Let me send you my IPV6 configuration values for IPV6 prefix and LAN address to see if my values will save. Email me at john.c.vestal@mailzone.com and we will see if we can get any values to save.
John
-
Feb 12, 2013 4:17 PM in response to Mike Baehrby It_caveman,Here is a good read on setting up your tunnel for an AirPort Extreme. It was posted using earlier firmware but maybe it'll help.
-
-
Feb 16, 2013 7:17 PM in response to Speledingby Annorax64,Unfortunately, the ars technica fix does not seem to work for 1st Gen. Time Capsules.
I've tried quite a few combinations using the instructions for the ars technica mentioned by @Speleding and I cannot get IPv6 tunneling to work on my 1st Gen. Time Capsule.
I too get the silent rejection of the setting which aren't saved as has been previously described.
Reverting back to 7.6.1 yet again..