Wednesday, July 2. 2008
NetworkManager 0.7 is back (New PPA)
NetworkManager 0.7 is back. So far I received good feedback on this snapshot, so I thought it was time to get more testers involved.
To get the packages, add the network-manager team PPA to your sources.list and upgrade your system:
https://launchpad.net/~network-manager/+archive
Enjoy and remember to let me know what works and what doesnt!
Update: If you end up having two wpa_supplicant processes running (after resume) just sudo killall wpa_supplicant and all should be back to normal.
Can you upload this to Debian experimental? We’d like to give it a try too.
i think biebl is on it and will provide packages for experimental soon.
I still hope that we can maintain a single master branch for NM packaging in future, but unfortunately we were not able to agree on the modalities.
I’d love to test but need (use) the network-manager-vpnc package. Will this build break vpnc integration?
yes, you probably wont be able to use vpnc until we updated the vpn packages too.
That said, I discussed this with soren and we agree that building the vpn packages from the NM sources would make sense. If you want to help, ping me on freenode 
.
I had to mofify the follwoing file:
/etc/dbus-1/system.d/nm-dhcp-client.conf
I have added the following:
I have installed this new version, now I have a a problem, that I guess is related to permissions:
I can not edit the connections properties.
If I go to (mines is in spanish)
>Edit Conections>WiFi>(select one)>Edit>
The accept buttons is grayed out, no matter what modification I made, I can not save them
screenshot in this thread:
http://ubuntuforums.org/showthread.php?t=797059&page=9
fwiw, this turned out to be a WPA-EAP issue surrounding client cert security settings and is now tracked in bug 245184
It is possible yet to connect to a vpn while using a Dialup/GSM connection using network manager?
Here’s what I get: The NetworkManager Applet could not find some required resources. It cannot continue.
The upgrade broke suspend (actually, resuming from suspend to ram) for me. Even after downgrading again to 0.6.6 i can’t resume from suspend. any ideas?
unlikely that it would break without any package having changed. Did you downgrade the wpasupplicant package as well?
Where should I submit bug/wishlist items? LP or upstream?
The GSM support is awesome, but one thing I need is to supply my own dns servers on that connection. My carrier DNS servers often have issues and I hard code them when dialing with kppp. I’d love to see that in the "Mobile Broadband" config.
It would be nice if I could disable a specific interface. Now with 0.7 it tries to get an address on all attached nic’s. This can create problems with curtain applications. It also becomes a security risk if it connects to two networks, an internal one and a public hotspot. This makes the pc a router between networks that should be seperated by a firewall.
It appears that nm in static mode does not update the dns entries in nework-admin, or they conflict. I was unable to use nm with manual IP settings just now. This is just one network though, I’m posting this in case no one else has tried out static IP addresses. That is, static IP addresses didn’t work for me.
What about providing knetworkmanager with 0.7 support for KDE users?
we are on it. more info on knetworkmanager coming asap.
Huwaei E200 modem (external USB dongle) works just fine, but gives three entries in the dropdown menu, only one of which actually works.
I also managed to freeze all of X input when I "intuitively" tried to right-click on one of those entries, had to CTRL-ALT-BACKSPACE, but I don’t know if that was NM or something else.
I will happily join as a tester as soon as network-manager-openvpn also becomes available.
Tested on a dell m1330 (wifi intel 4965) and ubuntu 64bit.
It works fine, but I noticed a regression from 0.6.x: it does not remember if Wireless is set to disabled via the applet contextual menu. At every reboot my wireless is up and the relative led on.
Is it an intended behaviour?
Works for me (wireless), but DHCP doesn’t set the default route. If I set a default route manually, DHCP keeps deleting my default route.
Works for me (3G) too.
Some more: I’ve noticed that it drops the connection now and then. I have left the computer to download something and when I come back it has just disconnected.
Hard to give any hard data about why, but this never happens when I use the Vodafone Betavine client (which is great btw, but I’d rather have NM). Could it be that it is too sensitive to fluctuations and thinks the connection went down?
The three instances of my modem is apparently because it has several partitions, the dongle includes software and whatnot. I remember it created 3 separate /dev/ttyUSB* entries only one of which is a modem – but to complicate things further, sometimes there is only one entry… anyway, there needs to be some way of detecting what is actually a modem and display only that one.
I also wonder about the wording "GSM". All other software I’ve seen says "3G". Maybe one or the other is more correct, I don’t know, but I was looking for that and had to conclude that the one "not GPRS" is probably it. I’m still not 100% sure.
Otherwise it seems to work great. It connects really fast and generally just works.
Still even more stuff: If I’m connected at the wireless network, then plug a wired cable in – it connects to that as well, but it seems to kill networking. NM reports that everything is ok, but Firefox just stops loading pages, just saying "Looking for".... and I think IM is logged out as well. I have to disable/enable Networking, then it starts to work. ifconfig looks fine. Some kind of DNS troubles?
Todays update broke NM completely for me, couldn’t connect to either wired or wireless anymore. After downgrading to pre0 it works again.
Latest update also broke network on my machine. All the DHCP gets by okay but never applied on the nic and nameservers isn’t put into resolv.conf.
Output from syslog:
NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started…
NetworkManager: (eth0): device state change: 7 -> 9
NetworkManager: Marking connection ‘Auto eth0’ invalid.
NetworkManager: Activation (eth0) failed.
NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
NetworkManager: (eth0): device state change: 9 -> 3
NetworkManager: (eth0): deactivating device.
sorry for the glitch. i uploaded 0.7~~svn20080703t022721+eni1-0ubuntu0~pre5~hardy which should fix your issues again.
thanks for testing
Doesn’t fix DHCP default route. The default route is set to 0.0.0.0. I then manually fix it (route add…)
Ten minutes later Avahi kick in, removes the avahi interface, and sets my default route back to 0.0.0.0. Note: there is a route, but it’s 0.0.0.0
That’s on wireless.
It moans about nscd (which seems to be a nameserver thing):
NetworkManager: nm_spawn_process(): could not spawn process ’/usr/sbin/nscd -i hosts’: Failed to execute child process "/usr/sbin/nscd" (No such file or directory)
Maybe nscd should be a dependency—my machine doesn’t have it installed.
/var/log/syslog doesn’t indicate obtaining a default route from dhcp, although the DNS server hasn’t been changed in a few years:
NetworkManager: DHCP: device wlan1 state changed bound -> renew
NetworkManager: address x.x.x.x
NetworkManager: netmask 255.255.248.0
NetworkManager: nameserver ‘x.x.x.x’
NetworkManager: nameserver ‘x.x.x.x’
NetworkManager: domain name ‘domain.com’
Just installed contents of network-manager PPA on Ubuntu Intrepid. In general, all went well.
I had reboot and manually start nm-applet. It asked me for my WPA key again. Apart from that, it works.
Now looking for how to enable the modem in my Nokia E70 for internet access (either via cable or bluetooth).
Today updates provided network-manager 0.7~~svn20080720t224551+eni1-0ubuntu1~hardy1~nm2
I no longer get the bogus default route.
However, it still doesn’t add DHCP’s default route.
Default route seems OK now.
network-manager 0.7~~svn20080812t224027+eni0-0ubuntu1~nm2~hardy1
3G works too.
Can anyone make a quick writeup of how they got NM to mange their 3G connection. I have tried getting this working with a huawei e220, but I haven’t got it working(I only managed to hang X until NM was killed and restarted)
Right click->Edit Connections->Mobile Broadband->Add->Create GSM Connection
Entered APN, which you need to know, and dummy username/password (my provider needs that). Selected Prefer GSM.
That’s it for me. I understand that this may not be very helpful, but that worked for me with a Huwaei E220.
Hi Stoffe, could you add your provider information to the table https://wiki.ubuntu.com/NetworkManager/Hardware/3G as well?
Done, hope that is the info you want.
I’m not sure if NM should be able to detect this information, such as the APN, automatically? I’m also not sure if I ever tried without dummy username/password, it always needed it when I connected with other software.
Fresh install…
I can not specify static address.
... well I can write it, but the OK button grays out as soon as I select statuc from the drop down, so I can not save it…. any clues?
I got my Nokia 6300 to be detected by NM-0.7 as a 3G modem after editing one of hal’s fdi files, I wonder, is this something worth mentioning on a mailing list or bug tracker?
Yes, this is definately worth documenting. Might be a candidate for a Wiki page, too.
Please add your hardware to the page at https://wiki.ubuntu.com/NetworkManager/Hardware/3G.
Also, please file a bug for the hal’s fdi changes required (file against network-manager package for now) and link it from that page (like the others that had filed a bug)
I’ve updated https://wiki.ubuntu.com/NetworkManager/Hardware/3G
I’ll fill in the rest of the details as soon as I get the patch made and submitted as required of hal-info (upstream)
Thanks.
Just tested the ppa again on my dell m1330 (wifi intel 4965) and hardy 64bit.
Still, if I uncheck Enable wireless and reboot, the wireless is on again. Version 0.6.6 remembers correctly that wireless has to be disabled.
I noticed that key /apps/NetworkManagerApplet/wireless_enabled had no schema. Could that be the problem?
Just saw you provided an update including the openvpn-plugin. I configured my VPN, when I start it, I get an error saying: "There was a problem launching the authentication dialog for VPN connection type ‘org.freedesktop.NetworkManager.openvpn’. Contact your system administrator."
It’s configured to use TLS certificates.
Ubuntu bug filed with patch to hal-info to add Nokia 6300 as a GPRS Modem: https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/258197
Looks like the patch is committed and released. I havent’ had any word from the hal (upstream) mailing list about the status of the patch above though.
I have an idea about turning the patch to a "class" patch that applies to all Nokia devices that expose a modem interface, instead of the current setup, which will get big very quickly. I’ll post it if I succeed.
Will the same method be possible to use on say Sony Ericsson devices? What kind of information would be needed?
Stoffe: I tried playing with a friends Sony Ericsson w960i (i think that’s the model). The device exposes three ACM modems, all of which are detected fine, but none of which can connect. I have no idea why.
But yes, the idea should work with any phone. With the current method, you simply edit this line (duplicate the entire set for a working phone and edit):
and replace the "0×64" with the USB product ID of the corresponding phone. You can obtain that by running "lsusb" while the phone is connected, the product ID is the second part of the number just after ‘ID’
Right, so:
Bus 002 Device 008: ID 0fce:d0b3 Sony Ericsson Mobile Communications AB
Means that the number for a W890i is 0xd0b3?
Anyway, I was most interested in this class patch thing, which sounds like a better approach.
<match key="@info.parent:usb.product_id" int="0×64">
sorry, the server edited out the "suspicious" markup. this is just a re-post.
he he, its just a one-line patch to the current system. Just replace the "product_id" with the "vendor_id" in the case of nokia phones,
<match key="@info.parent:usb.vendor_id" int="0×421">
I haven’t tested it, for want of a second nokia phone, but i expect it to work in theory. worked with my own phone.
It will take me a while to make a new patch though (bandwidth reasons), so (anyone) feel free to patch that up.
Stoffe, have fun. l8rs
look at https://wiki.ubuntu.com/NetworkManager/Hardware/3G. There you find some nokia phones with bugs attached. maybe ask there to test your generic rule.
BTW, how sure are we that all nokia phones are GSM phones?
I believe the matching process goes like so:
If
Nokia Phone,
I suppose it would be better to find out how to add "if GSM phone" in there though. Need some more research there.
Looking at hal’s docs suggests its not quite possible to find out if a device ‘is a gsm phone’.
I’ll have to come back to this issue when i can find time to properly research what makes a phone ‘gsm’ or otherwise.
Can someone please direct me to some guides one how to get to point the rest of you are at?
I’m using ubuntu hardy.
My phone is :
Bus 007 Device 002: ID 1004:1fae LG Electronics, Inc. U8120 3G Cellphone
using a usb cable to connect it.
it might be easier for you to just add your usb product and vendor IDs at The Hardware Wiki and wait for someone who can to make a proper fdi file, get it into hal-info, and you’ll eventually receive it as an update. But it depends on you.
So knetworkmanager0.7 is at least partially working for people? I’ve installed the latest knetworkmanager version available in hardy:
1:0.7svn830754-0ubuntu1~hardy1
and it won’t touch wireless networks. It connects to wired networks just fine, but seems to not even try when I ask it to connect to wireless networks. No dmesg errors, but if I start knetworkmanager from command line it gives me errors of the flavor:
knetworkmanager: WARNING: [AccessPoint* WirelessDevice::getActiveAccessPoint()] No object for active access point found!
Activate Connection /org/freedesktop/NetworkManagerSettings/Connection/0 on Device /org/freedesktop/Hal/devices/net_00_17_3f_b0_4d_84
Is this just me, or has anyone else seen this?
It’s completely unusable for any wireless network for me.
asac: I noticed while playing with a Nokia 5310 that hal doesn’t recognise "usb.product_id" for the phone unless i write it in base 10 (Decimal).
It appears hal won’t recognise usb.product_ids of LESS THAN three hexadecimal digits. Does anyone else get that behaviour? Specifically, whoever added the entry for the Nokia E71 to hal-info
Since yesterday’s updates, my NetworkManager doesn’t survive a suspend/resume cycle anymore.
resume crashes should be fixed in latest PPA upload:
Uploading to ppa-nm (via ftp to ppa.launchpad.net):
network-manager_0.7~~svn20080908t183521+eni0-0ubuntu3~nm2~hardy1.dsc: done. network-manager_0.7~~svn20080908t183521+eni0-0ubuntu3~nm2~hardy1.diff.gz: done. network-manager_0.7~~svn20080908t183521+eni0-0ubuntu3~nm2~hardy1_source.changes: done.Successfully uploaded packages.
Uploading to ppa-nm (via ftp to ppa.launchpad.net):
network-manager_0.7~~svn20080908t183521+eni0-0ubuntu3~nm2.dsc: done. network-manager_0.7~~svn20080908t183521+eni0-0ubuntu3~nm2.diff.gz: done. network-manager_0.7~~svn20080908t183521+eni0-0ubuntu3~nm2_source.changes: done.I really like the new provider wizard: however, it provides faulty information for my provider – the correct info is already on the Wiki page. It also defaults to GPRS which is not clear until actually editing the connection.
Where and how do I report this, so it’s handled appropriately? The projects on launchpad does not seem to allow bug reports, probably for a good reason.
I am having occasional suspend resume problems with
0.7~~svn20081008t224042-0ubuntu3~nm1~hardy2for some reason the wireless comes up as eth1. where is the interface information stored (it does not seem to be in /etc/network/interface).
/me on Identi.ca
asac: enabled #gypsy backend for geoclue in !ubuntu #maverick
asac: why, oh, why is my internet provider so flaky? #alicedsl
asac: develop and run OpenGLES on x86 with Gallium - https://wiki.linaro.org/DeveloperDocs/EglWithGallium
asac: ntrack 008 released - https://launchpad.net/ntrack/main/008
asac: typos ftw!
asac: #ubuntumozilla - committed fix for ubufox about:home direction bug lp:606728
asac: sigh, #alicedsl starts getting a cold again
