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 105: | Line 105: | ||
| [[User:akostadi|Aleksandar Kostadinov]] | | [[User:akostadi|Aleksandar Kostadinov]] | ||
| n/a | | n/a | ||
| {{result|fail | | {{result|fail}} <ref>{{bz|885903}}</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
Line 113: | Line 113: | ||
| [[User:tore|Tore Anderson]] | | [[User:tore|Tore Anderson]] | ||
| native | | native | ||
| {{result|fail}} <ref | | {{result|fail}} <ref>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.</ref><ref>No IPv6 prefix appears to be acquired from upstream wired network using DHCPv6-PD or another mechanism.</ref><ref>{{bz|887505}}</ref><ref>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 upstream wired interface.</ref><ref>[https://bugzilla.gnome.org/show_bug.cgi?id=593815 bgo#593815]</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
Line 121: | Line 121: | ||
| [[User:Benesv|Vladimir Benes]] | | [[User:Benesv|Vladimir Benes]] | ||
| local-only | | local-only | ||
| {{result|fail | | {{result|fail}} <ref>{{bz|886107}}</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|fail | | {{result|fail}} <ref>{{bz|886071}}</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| <references/> | | <references/> | ||
Line 129: | Line 129: | ||
| [[User:Jsedlak|Jan Sedlak]] | | [[User:Jsedlak|Jan Sedlak]] | ||
| local-only | | local-only | ||
| {{result|warn | | {{result|warn}} <ref>{{bz|886078}}</ref> | ||
| {{result|warn | | {{result|warn}} <ref>{{bz|886078}}</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|pass}} | | {{result|pass}} | ||
Line 137: | Line 137: | ||
| [[User:Julroy67|Julroy67]] | | [[User:Julroy67|Julroy67]] | ||
| native | | native | ||
| {{result|fail | | {{result|fail}} <ref>{{bz|886236}}</ref> | ||
| {{result|fail}} | | {{result|fail}} | ||
| {{result|pass}} | | {{result|pass}} | ||
Line 155: | Line 155: | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|fail | | {{result|fail}} <ref>{{bz|886071}}</ref> | ||
| {{result|pass}} | | {{result|pass}} | ||
| <references/> | | <references/> | ||
Line 202: | Line 202: | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|pass}} <ref>Only tested NFSv3 client. NAS hardware: EMC VNX.</ref> | | {{result|pass}} <ref>Only tested NFSv3 client. NAS hardware: EMC VNX.</ref> | ||
| {{result|pass}} <ref | | {{result|pass}} <ref>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.</ref> | ||
| <references/> | | <references/> | ||
|- | |- | ||
Line 242: | Line 242: | ||
| [[User:Martix|Martin Holec]] | | [[User:Martix|Martin Holec]] | ||
| local-only | | local-only | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result| | | {{result|pass}} | ||
| {{result|pass}} | |||
| {{result|none}} | | {{result|none}} | ||
| {{result|pass}} | | {{result|pass}} | ||
Line 262: | Line 262: | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|fail}} <ref | | {{result|fail}} <ref>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.</ref><ref>[https://bugzilla.gnome.org/show_bug.cgi?id=682623 bgo#682623]</ref> | ||
| {{result|fail}} <ref | | {{result|fail}} <ref>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."</ref><ref>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."</ref><ref>An "IPv6 Settings" tab is notably absent in the VPN connection editor GUI, while there is one for IPv4.</ref><ref>[https://bugzilla.gnome.org/show_bug.cgi?id=682620 bgo#682620]</ref> | ||
| {{result|fail}} <ref | | {{result|fail}} <ref>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."</ref><ref>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.</ref><ref>An "IPv6 Settings" tab is notably absent in the VPN connection editor GUI, while there is one for IPv4.</ref><ref>[https://bugzilla.gnome.org/show_bug.cgi?id=682622 bgo#682622]</ref> | ||
| <references/> | | <references/> | ||
|- | |- | ||
Line 297: | Line 297: | ||
=== Unplanned testing === | === Unplanned testing === | ||
* {{bz|12345}} - Bug summary | * {{bz|12345}} - Bug summary | ||
[[Category:Test Days]] | |||
[[Category:QA Templates]] | |||
===== Other ====== | ===== Other ====== | ||
The StrongSwan Plugin for Network Manager does not appear to work for basic IKEv2 tunnels from roadwarrior to gateway (endpoint to subnet) using certificates for authentication. | The StrongSwan Plugin for Network Manager does not appear to work for basic IKEv2 tunnels from roadwarrior to gateway (endpoint to subnet) using certificates for authentication. | ||