From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
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 = [ | | caption = [[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... | ||
* [[User: | * Development - [[User:Thomas Graf]] (irc: tgraf), [[User:Herbert Xu]] (irc: herbert), [[User: lwang]] (irc: lwang) | ||
== 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 ( | * 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) | ||
== How to test? == | == How to test? == | ||
Line 35: | Line 37: | ||
=== '''Live image''' === | === '''Live image''' === | ||
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. | 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]. | ||
=== Prepare an IPv6 connection === | === Prepare an IPv6 connection === | ||
Check if your ISP offers native IPv6 connectivity. | ==== Native IPv6 ==== | ||
# 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: see below. | |||
==== Tunnel Broker via Hurricane Electric ==== | |||
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. | |||
===== Example tunnel script ===== | |||
Go to the configuration page of your tunnel (Main Page => Click on your tunnel) to find the settings needed to fill into the sample script below to replace the places where the word ''CHANGE!!!'' appears. 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}}. Then simply run the script to bring up the IPv6 tunnel. | |||
<pre> | |||
#!/bin/sh | |||
LOCAL=CHANGE!!! # Client Ipv4 address | |||
ADDR=CHANGE!!! # Client Ipv6 address | |||
REMOTE=CHANGE!!! # Server IPv4 address | |||
ip tunnel del he-ipv6 > /dev/null 2>&1 | |||
ip tunnel add he-ipv6 mode sit remote ${REMOTE} local ${LOCAL} ttl 255 | |||
ip link set he-ipv6 up | |||
ip addr add ${ADDR} dev he-ipv6 | |||
ip route add ::/0 dev he-ipv6 | |||
</pre> | |||
===== Network configuration file ===== | |||
The tunnel can also be configured like any other physical interface. Once this is done, the tunnel can be started and stopped via {{command|ifup}}/{{command|ifdown}}, and the interface can be configured to start on boot. To do so, use the settings from the script above to create the file, {{filename|/etc/sysconfig/network-scripts/ifcfg-he-ipv6}}, as follows: | |||
<pre> | |||
DEVICE=he-ipv6 | |||
TYPE=sit | |||
BOOTPROTO=none | |||
ONBOOT=yes # set to "no" if you prefer to start the tunnel manually | |||
IPV6INIT=yes | |||
IPV6TUNNELIPV4=CHANGE!!! # Server IPv4 address | |||
IPV6ADDR=CHANGE!!! # Client IPv6 address | |||
</pre> | |||
== Test | Also, add the following to {{filename|/etc/sysconfig/network}}: | ||
<pre> | |||
IPV6_DEFAULTDEV=he-ipv6 | |||
</pre> | |||
This ensures that IPv6 traffic is sent via the tunnel interface. | |||
To bring up the interface, run {{command|ifup he-ipv6}}. To bring the interface down, run {{command|ifdown he-hpv6}}. | |||
==== Tunnel Broker via Sixxs.net ==== | |||
For this example, we are going to use http://www.sixxs.net/ which provides tunnels to ISP-hosted servers in several countries. | |||
# Request a new account at https://www.sixxs.net/main/ and select "Signup for new users". See https://www.sixxs.net/faq/account/?faq=10steps for further details on creating and configuring your account, and requesting your first tunnel. Account requests are processed manually and may take a few days, so start early. | |||
# Install aiccu. <code>sudo yum install aiccu</code> | |||
# Configure your /etc/aiccu.conf file with your sixxs.net username, password, and optionally, your tunnel ID as obtained above. | |||
# Test your aiccu configuration. <code>sudo /usr/sbin/aiccu autotest</code> | |||
# Start aiccu. <code>sudo /sbin/chkconfig aiccu on; sudo /sbin/service aiccu start</code> | |||
# If you provide sixxs.net a LinkedIn or Xing profile, you will be given enough credits to request a /48 subnet delegation immediately. Once approved, you may enable forwarding on your tunnel machine and assign addresses from your own /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.}} | |||
=== Exploratory testing === | |||
# ifconfig your interface to make sure your IPv6 address are setup correctly. | |||
# 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 === | |||
Send email to kernel-network-list@redhat.com. | |||
== Test | == 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. | ||
{| | {| | ||
! | ! User | ||
! | ! Smolt Profile | ||
! | ! [[QA:Testcase_NetworkManager_ipv6]] | ||
! [[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] | ||
| {{result|none}} | |||
| {{result| | |||
| {{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]] | |||
[[Category: |