| Summary: | Update candidate for knetworkmanager | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | John Balcaen <balcaen.john> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | balcaen.john, eeeemail, qa-bugs, stormi-mageia, sysadmin-bugs, tmb |
| Version: | 1 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | knetworkmanager-0.9-1.20110810.1.1.mga1.src.rpm | CVE: | |
| Status comment: | |||
|
Description
John Balcaen
2011-09-02 01:47:42 CEST
There is potentially alot to test here but very little information to go on so I think testing is going to be limited, especially with specific hardware required. I've installed the packages but struggling to do anything with it (No Network Interfaces). Is it incompatible with Mageia Network Centre? I managed to add a ptpp vpn connection but unable to activate it anywhere. All the other tabs are greyed out and non clickable. I usually use Gnome so don't want to leave it unable to connect other than in KDE which I'm not very familiar with. I'm happy to test if possible. Could you give some instructions please to reproduce some of the bugs, thanks. CC:
(none) =>
eeeemail Well you can't possibly check all thoses bugfixes. Regarding configuration with Mageia Network Center you need to enable Nm support in the Mageia Network Center & disable the start of the interface on boot so it's going to be managed by Networkmanager. An ugly & fast workaround is to do this -> service network stop -> rm /etc/sysconfig/network-scripts/ifcfg-eth0 (for a wired connection) -> service networkmanager restart & then nm should managed your connection network. You should be then able to configure/enable/add options via the networkmanagement applet (available in the systray if enable) or directly via systemsettings Thankyou John I'll check it out. Maybe mv instead of rm though! Already had it unable to boot to a desktop after installing NetworkManager. Should it be made to conflict with that do you think? unable to boot ? It should not be related at all with NetworkManager since the one available in Mageia 1 does support ifcfg and should not conflict at all with mandriva's scripts. Do you have the error message eventually ? It booted but after logging in the Gnome desktop would not start properly until I killed and disabled the NetworkManager service, which started at boot. I'll try and reproduce it and see if I can find any error messages. I am able to use networkmanager by chmod'ing ifcfg by the way. Just trying to reproduce bugs from the list and I will update it. I've been unable to reproduce the desktop problems John so not sure what was going on there. I've been mostly unable to reproduce any of the major bugs in the list too so testing is going to be limited to whether it updates and works as it should. The update was OK. I have tried to setup and connect to a vpn, so far I get connection failed. Syslog snippet: Sep 7 16:02:37 localhost NetworkManager[20022]: <info> Starting VPN service 'pptp'... Sep 7 16:02:37 localhost NetworkManager[20022]: <info> VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 21863 Sep 7 16:02:37 localhost NetworkManager[20022]: <info> VPN service 'pptp' appeared; activating connections Sep 7 16:02:37 localhost NetworkManager[20022]: <info> VPN plugin state changed: 1 Sep 7 16:02:37 localhost NetworkManager[20022]: <info> VPN plugin state changed: 3 Sep 7 16:02:37 localhost NetworkManager[20022]: <info> VPN connection 'vpntest' (Connect) reply received. Sep 7 16:02:37 localhost pppd[21864]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Sep 7 16:02:37 localhost pppd[21864]: pppd 2.4.5 started by clairer, uid 0 Sep 7 16:02:37 localhost pppd[21864]: Using interface ppp0 Sep 7 16:02:37 localhost pppd[21864]: Connect: ppp0 <--> /dev/pts/3 Sep 7 16:02:37 localhost NetworkManager[20022]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring... Sep 7 16:02:37 localhost pptp[21866]: nm-pptp-service-21863 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Sep 7 16:03:08 localhost pppd[21864]: LCP: timeout sending Config-Requests Sep 7 16:03:08 localhost pppd[21864]: Connection terminated. Sep 7 16:03:08 localhost pppd[21864]: Modem hangup Sep 7 16:03:08 localhost NetworkManager[20022]: <warn> VPN plugin failed: 1 Sep 7 16:03:08 localhost NetworkManager[20022]: <warn> VPN plugin failed: 1 Sep 7 16:03:13 localhost pppd[21864]: Exit. Sep 7 16:03:13 localhost NetworkManager[20022]: <warn> VPN plugin failed: 1 Sep 7 16:03:13 localhost NetworkManager[20022]: <info> VPN plugin state changed: 6 Sep 7 16:03:13 localhost NetworkManager[20022]: <info> VPN plugin state change reason: 0 Sep 7 16:03:13 localhost NetworkManager[20022]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Sep 7 16:03:13 localhost NetworkManager[20022]: <info> Policy set 'mynetwork' (eth1) as default for IPv4 routing and DNS. Sep 7 16:03:18 localhost NetworkManager[20022]: <info> VPN service 'pptp' disappeared I'm not sure if this is down to the host vpnreactor or something wrong here. They don't give instructions for linux ptpp on their website, only openvpn (which isn't supported for free accounts), but I can't see how it could be a problem. FWIW openvpn did try and connect but was refused as I only registered for a free account. I have tried with bestfreevpn.com now too and unable to connect using pptp. Same logs. Well i'm only using openvpn plugin but i can't be part of the test :p Regarding pptp i'll try tonight if i can provide more informations for testing it. Hmm OK, so I needed to enable PPTP passthrough on the router. After doing, that much more happens. It tries to negotiate the connection but says it require MPPE When I enable MPPE in NetworkManager settings I get another error and it fails instantly. Sep 7 16:35:44 localhost pppd[23220]: unrecognized option 'require-mppe' Also every 10 minutes, more or less exactly it gives these messages, not sure if it is normal behaviour.. Sep 7 18:13:02 localhost NetworkManager[20022]: <info> (eth1): supplicant connection state: completed -> group handshake Sep 7 18:13:02 localhost NetworkManager[20022]: <info> (eth1): supplicant connection state: group handshake -> completed John I'm assigning back to you to look at. There appears to be a bug with the PPTP VPN or one with pppd which you might decide will block it. See comment 10 and comment 11. Overall, aside conflicting with the normal network daemon which causes the desktop to become unresponsive if ifcfg-eth* exist (difficult to workaround on boot as they are created automatically even with network daemon disabled), it connects fine and the plasma applet works well. Tested well i586. Please reassign to QA when you're happy and I'll test x86_64 also. Assignee:
qa-bugs =>
balcaen.john ok after trying with vpnreactor i'm having the same problem as you because in fact our pppd does not support mppe. The support is in fact disable in mageia (there's a patch for it) due to license & patent restrictions. The vpn is working here as expected :) CC:
(none) =>
balcaen.john What's the status for this update candidate? Must QA testing continue? (currently assigned to maintainer) CC:
(none) =>
stormi We should push it as the problem discovers by claire is not related with knetworkmanager but rather with ppp itself. so we can test x86_64 (claire wanted to do it, from comment #12) and then push it. Assignee:
balcaen.john =>
qa-bugs I will test this next week x86_64 Testing x86_64 service network stop removed ifcfg-* service networkmanager start networkmanager controls the connection with no problems. I'm having problems with the plasma applet. Hovering over it says No Network Interfaces If i click on the spanner to bring up the widget settings it is stuck on VPN and everything else is greyed out, including the add edit delete buttons. If I click on the red cross on the where the widget should be it brings up a window with Interfaces and Connections. No interfaces are shown but enable networking is checked. If I click in there on Manage Connections it brings up KDE Control Module which shows eth0 and all the other tabs which should be available in the widget. All are accessible and usable apart from VPN which has the buttons greyed out. NetworkManager is controlling eth0 and I'm using it now. did you log out/log in after starting nm ? The vpn is available only if you're installing a vpn plugin for knetworkmanager. Yes you're right - it was that simple :D duhhh! plasma widget now working. I'll do some other tests and then validate Thankyou John Everything seems OK I couldn't find a free openvpn provider I trusted to give my details to to test it with but as far as the interface is concerned it is at least accessible to configure. I'm going to validate Advisory ------------- This update provides a more recent snapshot of knetworkmanager fixing essentially some crashes but also some bugs regarding VPN support. Connections should also work correctly now with modem HUAWEI E220. ------------- SRPM: knetworkmanager-0.9-1.20110810.1.1.mga1.src.rpm Could sysadmin please push from core/updates_testing to core/updates Thankyou! Keywords:
(none) =>
validated_update Update pushed. Status:
NEW =>
RESOLVED |