This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/bcop@ripe.net/
[bcop] Some test results and suggestions to IPv6 Troubleshooting
- Next message (by thread): [bcop] BCOP TF meeting at RIPE70 in Amsterdam
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
朱彥如
yjchui at cht.com.tw
Wed Apr 8 10:30:36 CEST 2015
I have setup IPv6 environment and use test-v6.com to make some tests. I have some suggestions according to my test results: 1. In section 6, for the example result for “624-6to4”, I suggestion to use <2002:c000:0201::c000:0201> for the IPv6 address, instead of original <2001:db8::1>. <2002:c000:0201::c000:0201> is derived from “2002::/16+ <192.0.2.1>”, which I think is more easily understood by users. 2. In section 6, Interpretation for “624-6to4”, I have questions about the sentence: “Any web site that has an IPv6 presence, will be reached using 6to4 instead of native IPv4” I use win 7 with only IPv4 address configured, and thus 6to4 works. Then, I add an IPv6 default route to 6to4 relay router (anycast). The test result show that * IPv4 is preferred rather than Ipv6 6to4 (Only when connecting to IPv6-only servers, IPv6 6to4 will be used) * The test result of using test-v6.com show 624 (Help desk code) So, I think the interpretation does not match the real condition. The following is my test result and give you as a reference (if gif can be accepted and shown): [cid:image001.jpg at 01D06BAB.3047DCE0] [cid:image002.png at 01D06BAB.3047DCE0] Regards Yann-Ju ChungHwa Telecom. Co. Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/bcop/attachments/20150408/4faa054e/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 37842 bytes Desc: image001.jpg URL: </ripe/mail/archives/bcop/attachments/20150408/4faa054e/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 273796 bytes Desc: image002.png URL: </ripe/mail/archives/bcop/attachments/20150408/4faa054e/attachment.png>
- Next message (by thread): [bcop] BCOP TF meeting at RIPE70 in Amsterdam
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ BCOP Archives ]