Test Day:2011-06-08 IPv6

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Example tunnel script)
m (Updated category)
 
(47 intermediate revisions by 19 users not shown)
Line 2: Line 2:
 
| name = Fedora Test Days
 
| name = Fedora Test Days
 
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]]
 
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]]
| caption = [[World IPv6 Test Day]]
+
| caption = [http://www.worldipv6day.org/ World IPv6 Test Day]
 
| date = June-08-2011
 
| date = June-08-2011
 
| time = all day
 
| time = all day
Line 20: Line 20:
  
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion...
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion...
* Development - [[User:Thomas Graf]] (irc: tgraf), [[User:Herbert Xu]] (irc: herbert), [[User: lwang]] (irc: lwang)
+
* [[User:tgraf|Thomas Graf]], [[User:herbert|Herbert Xu]], [[User:lwang|Linda Wang]]
  
 
== Prerequisite for Test Day ==  
 
== Prerequisite for Test Day ==  
 
List any prerequisite needs for the test event. 
 
  
 
* An up-to-date Fedora 15 system with IPv6 enabled  
 
* An up-to-date Fedora 15 system with IPv6 enabled  
* An internet connection via an ISP who supports IPv6 and an IPv6 address from that ISP, or an IPv6 tunnel broker (see below for instructions on this)
+
* An internet connection via an ISP who supports IPv6 and an IPv6 address from that ISP, or an IPv6 tunnel broker (refer to [[#Prepare an IPv6 connection]])
  
 
== How to test? ==
 
== How to test? ==
Line 37: Line 35:
 
=== '''Live image''' ===
 
=== '''Live image''' ===
  
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
+
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be downloaded [http://fedoraproject.org/get-fedora here].
  
 
=== Prepare an IPv6 connection ===
 
=== Prepare an IPv6 connection ===
  
# Check if your ISP offers native IPv6 connectivity. If so, follow the instructions of your ISP. If not you are going to need a tunnel broker: proceed to step 2.
+
Check if your ISP offers native IPv6 connectivity. If so, follow the instructions provided by your ISP.
# For this example we are going to use http://www.tunnelbroker.net/ by Hurricane Electric but any tunnel broker will work.
+
# Go to http://www.tunnelbroker.net/register.php and fill out the form to create a new account.
+
# Login to your account and click on ''Create Regular Tunnel''.
+
# Enter your public IPv4 address in the ''IPv4 Endpoint'' field. To find this address, visit http://www.whatismyip.com (Note: You can change your endpoint address later any time if your address is not 100% static). Select the tunnel server closest to you and click on the ''Create Tunnel'' button.
+
# You will be given multiple example scripts to set up the tunnel on your end or you can use the [[#Example_tunnel_script|script provided below.]] (Select OS: linux-route2)
+
# Click on ''Main Page'' to find a list of your tunnels at the end. You can modify your tunnel, allocate your own /48 or set up rDNS delegation by clicking on the tunnel.
+
# Feel free to enable forwarding on your tunnel machine and assign addresses from your own /64 or /48 to the machines on your network to provide IPv6 connectivity to your own network.
+
  
{{admon/warning | Security | The default firewall will also apply to IPv6 traffic but be aware that if you assigned public addresses to the machines on your network, those machine may now be reachable directly from the outside, whereas before they were inaccessible except via explicit port forwarding from your gateway.}}
+
* [[How to setup IPv6 connectivity with your ISP]]
  
=== Example tunnel script ===
+
Otherwise, you will need to setup a tunnel broker following one of the suggestions below.
  
Go to the configuration page of your tunnel (Main Page => Click on your tunnel) to find the settings needed to fill into the script to replace ''CHANGE!!!''. Then save the script to your home directory or to {{filename|/usr/local/bin}} - for example, {{filename|/usr/local/bin/ipv6-tunnel.sh}} - and make it executable: {{command|chmod ugo+x /usr/local/bin/ipv6-tunnel.sh}}.
+
* [[How to setup tunnel broker via Hurricane Electric]]
 +
* [[How to setup a tunnel broker via Sixxs.net]]
 +
* [[How to setup a 6to4 tunnel using anycast (RFC 3056)]]
  
<pre>
+
== Test Cases ==
#!/bin/sh
+
  
LOCAL=CHANGE!!!                    # Client Ipv4 address
+
The following list of tests are simply suggested test areas.  Participants are encouraged to test and provide feedback for areas not listed below.
ADDR=CHANGE!!!                      # Client Ipv6 address
+
REMOTE=CHANGE!!!                    # Server IPv4 address
+
  
ip tunnel del he-ipv6 > /dev/null 2>&1
+
* Exploratory Testing...
 +
*# ifconfig your interface to make sure your IPv6 address are setup correctly.
 +
*# ping various external ipv6 websites such as <code>ipv6.google.com</code> to see if you can download the web content through your ipv6 connection
 +
* Run http://test-ipv6.com
 +
* [[QA:Testcase_NetworkManager_ipv6]] - To test IPv6 on Network Manager, please see following link for instruction:
 +
* [[QA:Testcase_NFS_IPv6]] - To test IPv6 on NFS filesystem, please see following link for instruction:
 +
* [[QA:Testcase_IPv6_printing]] - 1. setup the system using ipv6 address, 2. setup printer's ipv6 address via printer instructions, 3. setup the printer queue as if the the printer uses ipv6 address.
 +
* [[QA:Testcase_various_IPv6_commands]] - Test various command-line IPv6 utilities
  
ip tunnel add he-ipv6 mode sit remote ${REMOTE} local ${LOCAL} ttl 255
+
== Test Results ==
ip link set he-ipv6 up
+
 
+
ip addr add ${ADDR} dev he-ipv6
+
ip route add ::/0 dev he-ipv6
+
</pre>
+
  
=== Exploratory testing ===
+
If you have problems with any of the tests, try and report a bug.  Most bugs in this event should be reported to [http://bugzilla.redhat.com Fedora Bugzilla].  You will need a bugzilla account to report bugs, but creating one is easy, and we will help you do this if you ask in [irc://irc.freenode.net/#fedora-test-day IRC].
  
# ifconfig your interface to make sure your IPv6 address are setup correctly.
+
If you are not sure of the appropriate component, please check in [irc://irc.freenode.net/#fedora-test-day IRC] before filing, there are many possibilities. If you are unsure about exactly how to file the report or what other information to include, just ask on [irc://irc.freenode.net/#fedora-test-day IRC] and we will help you.  
# ping various external ipv6 websites such as 'ipv6.google.com' to see if you can download the web content through your ipv6 connection
+
# run test program here: http://test-ipv6.com/
+
  
=== Reporting results ===
+
Once you have completed the tests, add your results to the appropriate table below, following the example results from the first line as a template.  The results use the wiki template <code><nowiki>{{result}}</nowiki></code>.  For guidance an syntax, refer to [[Template:Result]].
  
Send email to kernel-network-list@redhat.com.
+
=== Things that work ===
 
+
== Test Cases ==
+
 
+
Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
+
 
+
== Test Results ==
+
 
+
Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
+
 
+
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
+
  
 +
Use the following table to record tests successfully completed.
 
{|
 
{|
! User
+
! Tester
! Smolt Profile
+
! Test Performed / Description
! [[QA:Testcase_sample_1|Sample test 1]]
+
! Result
! [[QA:Testcase_sample_2|Sample test 2]]
+
! [[QA:Testcase_sample_3|Sample test 3]]
+
! [[QA:Testcase_sample_4|Sample test 4]]
+
 
! References
 
! References
 
|-
 
|-
 
| [[User:SampleUser|Sample User]]
 
| [[User:SampleUser|Sample User]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
+
| [[QA:Testcase_NetworkManager_ipv6]]
| {{result|none}}  
+
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Athmane|Athmane Madjoudj]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Dramsey|David Ramsey]]
 +
| [[QA:Testcase_NetworkManager_ipv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Dramsey|David Ramsey]]
 +
| [[QA:Testcase_IPv6_printing]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Dramsey|David Ramsey]]
 +
| [[QA:Testcase_NFS_IPv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Dramsey|David Ramsey]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Raina|Raina Otoni]]
 +
| [[QA:Testcase_NetworkManager_ipv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Raina|Raina Otoni]]
 +
| [[QA:Testcase_NFS_IPv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Raina|Raina Otoni]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:lintweaker|Jurgen Kramer]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Lintweaker|Jurgen Kramer]]
 +
| [[QA:Testcase_NFS_IPv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Evillagr|Eduardo Villagrán]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Evillagr|Eduardo Villagrán]]
 +
| [[QA:Testcase_NFS_IPv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:jbastian|Jeff Bastian]]
 +
| [[QA:Testcase_NetworkManager_ipv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:jbastian|Jeff Bastian]]
 +
| [[QA:Testcase_IPv6_printing]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:ricky|Ricky Zhou]]
 +
| [[QA:Testcase_NetworkManager_ipv6]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:ricky|Ricky Zhou]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:lmacken|Luke Macken]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:fbl|Flavio Leitner]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 
| {{result|pass}}
 
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 
| {{result|fail}} <ref>{{bz|12345}}</ref>
 
 
| <references/>
 
| <references/>
 
|-
 
|-
 
|}
 
|}
  
[[Category:Test Days]]
+
=== Problems Identified ===
 +
Use the following table to record tests that highlight defects or otherwise inconsistent behaviours.
 +
 
 +
{|
 +
! Tester
 +
! Test Performed / Description
 +
! Result
 +
! References
 +
|-
 +
| [[User:Lintweaker|Jurgen Kramer]]
 +
| [[QA:Testcase_NetworkManager_ipv6]]
 +
| {{result|fail|DHCPv6 blocked by firewall|650615}}
 +
| <references/>
 +
|-
 +
|[[User:Tuju|Tuju]]
 +
|
 +
| CUPS queue discovery doesn't work.
 +
| [https://bugzilla.redhat.com/show_bug.cgi?id=611213 bug 611213]
 +
|-
 +
| [[User:Rombobeorn|Björn Persson]]
 +
| [[QA:Testcase_various_IPv6_commands]]
 +
| {{result|fail|ping6 tries to ping an IPv4 address when a domain name has both IPv4 and IPv6 addresses.|711827}}
 +
| <references/>
 +
|-
 +
| [[User:jbastian|Jeff Bastian]]
 +
| [[QA:Testcase_NFS_IPv6]]
 +
| {{result|fail|cannot automount NFSv4 over IPv6|711844}}
 +
| <references/>
 +
|-
 +
| [[User:Adamwill|Adam Williamson]]
 +
|
 +
| Bip (IRC proxy) behaves badly when system has a global IPv6 address but is not capable of IPv6 DNS resolution: doesn't fall back to IPv4 and fails to connect to anything. Will report upstream
 +
| <references/>
 +
|}
 +
 
 +
 
 +
[[Category:Fedora 16 Test Days]]

Latest revision as of 19:10, 30 June 2011

Fedora Test Days
Echo-testing-48px.png
World IPv6 Test Day

Date June-08-2011
Time all day

Website http://isoc.org/wp/worldipv6day/
IRC #fedora-test-day (webirc)

Mailing list
MailSubscribeArchives


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

Contents

[edit] What to test?

Since June 8, 2011 is the World IPv6 Day, today's installment of Fedora Test Day will focus on IPv6 testing.

[edit] Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion...

[edit] Prerequisite for Test Day

  • An up-to-date Fedora 15 system with IPv6 enabled
  • An internet connection via an ISP who supports IPv6 and an IPv6 address from that ISP, or an IPv6 tunnel broker (refer to #Prepare an IPv6 connection)

[edit] How to test?

[edit] Update your machine

If you're running Fedora 15, make sure you have all the current updates for it installed, using the update manager.

[edit] Live image

Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be downloaded here.

[edit] Prepare an IPv6 connection

Check if your ISP offers native IPv6 connectivity. If so, follow the instructions provided by your ISP.

Otherwise, you will need to setup a tunnel broker following one of the suggestions below.

[edit] Test Cases

The following list of tests are simply suggested test areas. Participants are encouraged to test and provide feedback for areas not listed below.

  • Exploratory Testing...
    1. ifconfig your interface to make sure your IPv6 address are setup correctly.
    2. ping various external ipv6 websites such as ipv6.google.com to see if you can download the web content through your ipv6 connection
  • Run http://test-ipv6.com
  • QA:Testcase_NetworkManager_ipv6 - To test IPv6 on Network Manager, please see following link for instruction:
  • QA:Testcase_NFS_IPv6 - To test IPv6 on NFS filesystem, please see following link for instruction:
  • QA:Testcase_IPv6_printing - 1. setup the system using ipv6 address, 2. setup printer's ipv6 address via printer instructions, 3. setup the printer queue as if the the printer uses ipv6 address.
  • QA:Testcase_various_IPv6_commands - Test various command-line IPv6 utilities

[edit] Test Results

If you have problems with any of the tests, try and report a bug. Most bugs in this event should be reported to Fedora Bugzilla. You will need a bugzilla account to report bugs, but creating one is easy, and we will help you do this if you ask in IRC.

If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Once you have completed the tests, add your results to the appropriate table below, following the example results from the first line as a template. The results use the wiki template {{result}}. For guidance an syntax, refer to Template:Result.

[edit] Things that work

Use the following table to record tests successfully completed.

Tester Test Performed / Description Result References
Sample User QA:Testcase_NetworkManager_ipv6
Pass pass
Athmane Madjoudj QA:Testcase_various_IPv6_commands
Pass pass
David Ramsey QA:Testcase_NetworkManager_ipv6
Pass pass
David Ramsey QA:Testcase_IPv6_printing
Pass pass
David Ramsey QA:Testcase_NFS_IPv6
Pass pass
David Ramsey QA:Testcase_various_IPv6_commands
Pass pass
Raina Otoni QA:Testcase_NetworkManager_ipv6
Pass pass
Raina Otoni QA:Testcase_NFS_IPv6
Pass pass
Raina Otoni QA:Testcase_various_IPv6_commands
Pass pass
Jurgen Kramer QA:Testcase_various_IPv6_commands
Pass pass
Jurgen Kramer QA:Testcase_NFS_IPv6
Pass pass
Eduardo Villagrán QA:Testcase_various_IPv6_commands
Pass pass
Eduardo Villagrán QA:Testcase_NFS_IPv6
Pass pass
Jeff Bastian QA:Testcase_NetworkManager_ipv6
Pass pass
Jeff Bastian QA:Testcase_IPv6_printing
Pass pass
Ricky Zhou QA:Testcase_NetworkManager_ipv6
Pass pass
Ricky Zhou QA:Testcase_various_IPv6_commands
Pass pass
Luke Macken QA:Testcase_various_IPv6_commands
Pass pass
Flavio Leitner QA:Testcase_various_IPv6_commands
Pass pass

[edit] Problems Identified

Use the following table to record tests that highlight defects or otherwise inconsistent behaviours.

Tester Test Performed / Description Result References
Jurgen Kramer QA:Testcase_NetworkManager_ipv6
Fail fail DHCPv6 blocked by firewall [1]
  1. RHBZ #650615
Tuju CUPS queue discovery doesn't work. bug 611213
Björn Persson QA:Testcase_various_IPv6_commands
Fail fail ping6 tries to ping an IPv4 address when a domain name has both IPv4 and IPv6 addresses. [1]
  1. RHBZ #711827
Jeff Bastian QA:Testcase_NFS_IPv6
Fail fail cannot automount NFSv4 over IPv6 [1]
  1. RHBZ #711844
Adam Williamson Bip (IRC proxy) behaves badly when system has a global IPv6 address but is not capable of IPv6 DNS resolution: doesn't fall back to IPv4 and fails to connect to anything. Will report upstream