From Fedora Project Wiki
Fedora Test Days
Network Test Week (Network Manager + IPv6)
Date 2012-12-10
Time all day
Website QA/Fedora_18_test_days
IRC #fedora-test-day (webirc)
Mailing list test


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.

What to test?

Today's instalment of Fedora Test Day will focus on Network Manager: IPv6, Bonding, NetworkManager Hotspots, nm-applet, kdeplasma-applets-networkmanagement, Bluetooth

Who's available

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

Prerequisite for Test Day

  • Installed Fedora 18 Beta with latest updates.
  • IPv6 connectivity on local network
    • Native IPv6 connectivity from your IPS, at work, at school (Eduroam), remote server (dedicated, VPS).
    • Local network router/gateway with IPv6 over IPv4 tunnel setup (6to4, 6in4 or Teredo).
  • Wi-Fi adapter
  • multiple network cards
  • 3G modem
  • Bluetooth adapter and a phone capable of Internet connection sharing over Bluetooth
IPv6 over IPv4 tunnelling
Tunnel ending on localhost is not enough for some testing. Consider using tunnel with endpoint on LAN router/gateway.

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.

Network Manager features

IPv6

Desktop integration

Unplanned testing

Testing IPv6 - component perspective

  • not restricted only for today (you can do it also later) ideally this week
  • focus on component you would like to test (have some possibility to work over IPv6)
    • for example components - postfix, bind, samba, openswan, openldap, tomcat, apache, etc ... . Try if component is able work over IPv6 properly
  • Suggestions
    • you can try ipv6 only enviroment on localhost(disable ipv4 also for localhost, remove locahost ipv4 record from /etc/hosts, remove any other network from computer)
    • install F18/rawhide into KVM or other type of virtualized solution
      • add IPv6 adreses manually (same network subnet, add both records to your /etc hosts)
      • disable ipv4 on guest network interface or restrict IPv4 communication by iptables
      • configure & start your service to communicate over IPv6
      • comunication from host to guest service have to work

Test Results

If you have problems with any of the tests, report a bug to Gnome Bugzilla. If problem is Fedora distribution related, report a bug to Red Hat Bugzilla usually for the component NetworkManager. 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. For each test case, use the result template to enter your result, as shown in the example result line.

Network Manager features

User IPv6 connection Gnome Hotspot KDE Hotspot Bluetooth PAN nmcli References
Sample User native / tunnel / local-only / none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
Martin Holec local-only
Pass pass
Pass pass
Inprogress inprogress
Pass pass
Aleksandar Kostadinov n/a
Fail fail
[1]
none
none
Pass pass
  1. ↑ RHBZ #885903
Tore Anderson native
Fail fail
[1][2]
none
none
Pass pass
  1. ↑ Fails repeatedly with kernel messages à la "iwl3945: 0000:03.00.1: Microcode SW error detected. Restarting 0x230000008" and lots of other errors looking hardware-related.
  2. ↑ No IPv6 prefix appears to be acquired from upstream network using DHCPv6-PD or other mechanisms. Only RFC1918 IPv4 addressing appears to be configured on the wlan0 hotspot interface (disregarding link-local IPv6). It's highly unlikely that this could possibly work, considering the lack of IPv4 connectivity on the wired interface.

IPv6

User IPv6 connection IPv6 websites NFS over IPv6 IPv6 commands References
Sample User native / tunnel / local-only / none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
Martin Holec local-only
Pass pass
Inprogress inprogress
Inprogress inprogress
Tore Anderson native
Pass pass
Pass pass
[1]
Pass pass
[2]
  1. ↑ Only tested NFSv3 client. NAS hardware: EMC VNX.
  2. ↑ Test 6.1 (nc listening test) failed initially due to default F18 firewall rules, "ip6tables -I INPUT -p tcp --dport 8080 -j ACCEPT" fixed that.

Desktop integration

User IPv6 connection Ethernet Wireless Mobile Broadband OpenVPN VPNC References
Sample User native / tunnel / local-only / none
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
Martin Holec local-only
Pass pass
Pass pass
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Aleksandar Kostadinov
none
none
none
Fail fail
works with vodafone k3565-z USB dongle but not with Huawei [1]
Warning warn
[2]
Warning warn
[3]
  1. ↑ {will be fixed}
  2. ↑ test passed but encountered RHBZ #885263
  3. ↑ test passed but encountered RHBZ #885263
Tore Anderson native
Pass pass
Pass pass
Fail fail
[1]
Fail fail
[2][3][4]
Fail fail
[5][6][7]
  1. ↑ Connection comes up with only IPv4 connectivity although network supports IPv6 too. Issuing AT+CGDCONT? to modem shows only "IP" (IPv4) PDP context being set up. No apparent way to enable IPv6 in GUI tools, there's no IPv6 settings tab like there is for IPv4. Hardware used: Nokia 21M-02.
  2. ↑ If on single-stack IPv6 network: Connection attempt fails with log message "NetworkManager[765]: <warn> conenction /org/freedesktop/NetworkManager/Settings/6 failed to activate: (1) Could not find source connection, or the source connection had no active device."
  3. ↑ If on dual-stack network: Entering a literal IPv6 address or IPv6-only hostname in the gateway field results in the following syslog errors being reported by nm-openvpn: "RESOLVE: Cannot resolve host address [2001:db8::1|v6only.domain.tld]: [HOST_NOT_FOUND] The specified host is unknown."
  4. ↑ An "IPv6 Settings" tab is notably absent in the VPN connection editor GUI, while there is one for IPv4.
  5. ↑ If on single-stack IPv6 network: Connection attempt fails with log message "NetworkManager[765]: <warn> conenction /org/freedesktop/NetworkManager/Settings/6 failed to activate: (1) Could not find source connection, or the source connection had no active device."
  6. ↑ If on dual-stack network: vpnc plugin fails with log message: "NetworkManager[754]: <warn> VPN plugin failed: 1". No packets are seen in tcpdump on configured VPN gateway.
  7. ↑ An "IPv6 Settings" tab is notably absent in the VPN connection editor GUI, while there is one for IPv4.

Unplanned testing

  • RHBZ #12345 - Bug summary
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2012-12-10_Network_Manager_and_IPv6&oldid=314398"