From Fedora Project Wiki

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 97: Line 97:
 
| [[User:Martix|Martin Holec]]
 
| [[User:Martix|Martin Holec]]
 
| local-only
 
| local-only
| {{result|warn||885903|886107|886236}}  
+
| {{result|pass}}  
| {{result|warn||885903|886107|}} <ref>[https://bugs.kde.org/show_bug.cgi?id=311705 KDEBZ #311705]</ref>
+
| {{result|pass}}
| {{result|none}}
+
| {{result|inprogress}}
 
| {{result|pass}}
 
| {{result|pass}}
 
| <references/>
 
| <references/>
Line 105: Line 105:
 
| [[User:akostadi|Aleksandar Kostadinov]]
 
| [[User:akostadi|Aleksandar Kostadinov]]
 
| n/a
 
| n/a
| {{result|fail||885903}}
+
| {{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 group="long">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>{{bz|887505}}</ref><ref group="long">No IPv6 prefix appears to be acquired from upstream wired network using DHCPv6-PD or another mechanism. 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|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. 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>
 
| {{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||886107}}
+
| {{result|fail}} <ref>{{bz|886107}}</ref>
 
| {{result|none}}
 
| {{result|none}}
| {{result|fail||886071}}
+
| {{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||886078}}
+
| {{result|warn}} <ref>{{bz|886078}}</ref>
| {{result|warn||886078}}  
+
| {{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||886236}}
+
| {{result|fail}} <ref>{{bz|886236}}</ref>
 
| {{result|fail}}
 
| {{result|fail}}
 
| {{result|pass}}
 
| {{result|pass}}
Line 148: Line 148:
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
| {{result|pass}}
+
| {{result|success}}
 
| <references/>
 
| <references/>
 
|-
 
|-
Line 155: Line 155:
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|none}}
 
| {{result|none}}
| {{result|fail||886071}}
+
| {{result|fail}} <ref>{{bz|886071}}</ref>
 
| {{result|pass}}
 
| {{result|pass}}
 
| <references/>
 
| <references/>
Line 163: Line 163:
 
| {{result|fail}}<ref>{{bz|886107}}, {{bz|886935}}, {{bz|885903}}, {{bz|886939}}, {{bz|886946}}</ref>
 
| {{result|fail}}<ref>{{bz|886107}}, {{bz|886935}}, {{bz|885903}}, {{bz|886939}}, {{bz|886946}}</ref>
 
| N/A
 
| N/A
| N/A
+
|  
| {{result|fail||886953}}
+
|  
 
| <references/>
 
| <references/>
 
|}
 
|}
Line 186: Line 186:
 
| [[User:Martix|Martin Holec]]
 
| [[User:Martix|Martin Holec]]
 
| local-only
 
| local-only
| {{result|none}}
 
| {{result|none}}
 
| {{result|pass}}
 
| <references/>
 
|-
 
| [[User:Martix|Martin Holec]]
 
| native
 
| {{result|pass}}
 
| {{result|none}}
 
 
| {{result|pass}}
 
| {{result|pass}}
 +
| {{result|inprogress}}
 +
| {{result|inprogress}}
 
| <references/>
 
| <references/>
 
|-
 
|-
Line 202: Line 195:
 
| {{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 group="long">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>
+
| {{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 210: Line 203:
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|pass}}
 
| {{result|pass}}
| <references/>
 
|-
 
| [[User:jskarvad|Jaroslav Škarvada]]
 
| local
 
| N/A<ref>Unable to connect to the IPv6 internet natively, nor through teredo (probably blocked in the office, not the f18 failure I guess)</ref>
 
| {{result|warn}}<ref>Only tried nfsv3, and it only worked through IPv4, maybe crippled IPv6 routing in the office.</ref>
 
|
 
 
| <references/>
 
| <references/>
 
|}
 
|}
Line 242: Line 228:
 
| [[User:Martix|Martin Holec]]
 
| [[User:Martix|Martin Holec]]
 
| local-only
 
| local-only
| {{result|warn||}}<ref group="long">Gnome BZ #[https://bugzilla.gnome.org/show_bug.cgi?id=690352 690352] KDE BZ #[https://bugs.kde.org/show_bug.cgi?id=311832 311832] KDE BZ #[https://bugs.kde.org/show_bug.cgi?id=311834 311834]</ref>
 
 
| {{result|pass}}
 
| {{result|pass}}
| {{result|warn}}<ref group="long">Gnome BZ #[https://bugzilla.gnome.org/show_bug.cgi?id=690355 690355] Gnome BZ #[https://bugzilla.gnome.org/show_bug.cgi?id=690356 690356] Gnome BZ #[https://bugzilla.gnome.org/show_bug.cgi?id=690361 690361] KDE BZ #[https://bugs.kde.org/show_bug.cgi?id=311836 311836]</ref>
 
| {{result|none}}
 
 
| {{result|pass}}
 
| {{result|pass}}
 +
| {{result|inprogress}}
 +
| {{result|inprogress}}
 +
| {{result|inprogress}}
 
| <references/>
 
| <references/>
 
|-
 
|-
Line 262: Line 248:
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
| {{result|fail}} <ref group="long">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>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>
| {{result|fail}} <ref group="long">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 group="long">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>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>
| {{result|fail}} <ref group="long">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 group="long">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>
+
| {{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>
 
| <references/>
 
| <references/>
 
|-
 
|-
Line 280: Line 266:
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
| {{result|pass}}
+
| {{result|success}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
Line 289: Line 275:
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
| {{result|pass}}<ref>Using Option Globetrotter GT Max 3.6 GX0202</ref>
+
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
Line 297: Line 283:
 
=== 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.
 
== Long comments ==
 
<references group="long" />
 
 
[[Category:Fedora 18 Test Days|n]]
 

Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 3.0 Unported (see Fedora Project Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please solve the following task below and enter the answer in the box (more info):

Cancel Editing help (opens in new window)