Looking for advice about using NM with a Sprint U301 modem
Hi all, I'm trying to find out some information regarding the Sprint U301 3G modem. Our use case for it is that it will be attached to an embedded machine running ubuntu with networkmanager, in addition to our software. I've been trying to get this modem to connect reliably and am having some issues with it. I've added a udev rule so that the usbserial driver is given the correct vendor/product information, and it connects automatically on boot, but not reliably. Some boots it does not connect at all and won't until I reboot. Sometimes it disconnects while the machine is running. If it disconnects either by itself or from deactivating the connection, it will not connect again and needs a reboot. The nm/mm logs say that serial requests are timing out when it's in the non-connected state. I haven't been able to recover from the disconnected state with anything about a reboot. Is there anything we can do with this device to increase reliability? Failing that, can you recommend a usb Sprint 3G modem that will be more reliable? If there are none, do you have any recommendations for any brand of 3G modem that will work well in this situation? The boxes will be deployed where manual access is not easy, so it needs to be able to connect and recover from disconnections automatically, or at least in a way that can be scripted easily. Thanks, -- Daenyth ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
MeeGo support
Hello all, I am trying to install NetworkManager in MeeGo. When I run ./autogen.sh I get the following (selected) output: [...] checking for /etc/frugalware-release... no checking for /etc/mandriva-release... no checking for /etc/pardus-release... no ./configure: line 13672: lsb_release: command not found Linux distribution autodetection failed, you must specify the distribution to target using --with-distro=DISTRO How difficult is it to have NetworkManager work on MeeGo? How can I help? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: network-manager 0.8.1-beta2 does not work with isc dhcp-clients 3.1.3 and 4.1.1
On Sun, May 30, 2010 at 11:01:24PM +0200, Thomas Schmidt wrote: Hi, Am Sonntag, den 30.05.2010, 20:24 +0200 schrieb Michael Biebl: NM 0.8.1 requires ISC dhcp-client with DHCPv6 support enabled. The isc-dhcp package from experimental has DHCPv6 support disabled, due to build failures in the past, which have been sorted out in 4.1.1. Ok, thank you for the information. Hopefully Andrew finds the time to upload a new version with DHCPv6 support enabled (I CCed just in case). Yes, i really hope this too. I'd appreciate if people interested in seeing DHCP v4 in Debian could test out the packages I have in experimental and file bugs as necessary. At some point, as time permits, I will upload these packages to unstable. I've gone to great pains to make the new packages a drop in replacement for the old v3 packages, but I've done limited testing myself due to resource constraints at the moment. signature.asc Description: Digital signature ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
network discovery interval in network manager?
Hi, does anybody know the interval of the network search that is internally used by the network manager and where it is implemented. So far i know there is no dbus interface where such an interval can be changed. Is there an other possibility to change these value or is it planned to make such parameter available for the user? Thnx a lot Mario -- Dipl.-Inf. Mario Pink p...@informatik.tu-cottbus.de LS Networks Communication Systems Technical University of Cottbus Walther-Pauer-Str.2 03046, Cottbus Germany http://www-rnks.informatik.tu-cottbus.de/ ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modem-manager fails on Gobi 2000 UMTS card in a Thinkpad W510, error in AT+CMEE
Hi Stefan, Stefan Armbruster wrote, Hi, I'm trying to enable the builtin Gobi 2000 UMTS card on a Thinkpad W510. System is a Ubuntu Lucid 64bit, modem-manager compiled from current git. UMTS card's USB-ID: 05c6:9205 (after loading the firmware, 05c6:9204 before) When trying to connect, modem-manager sends a CMEE command resulting in an error: DEBUG: 1275421334.403788 (ttyUSB0): -- 'AT+CMEE=1CR' DEBUG: 1275421334.415006 (ttyUSB0): -- 'CRLFERRORCRLF' I've followed the debugging procedure from https://wiki.ubuntu.com/DebuggingModemmanager. In order not to pollute the list, the logs are placed on pastebin: mm-test.py output: http://pastebin.com/pRiinrSU modem-manager output: http://pastebin.com/HyHSpGhN (esp. l. 53f) network-manager output: http://pastebin.com/x7UZ20zm I assume the UMTS card is not detected correctly. Can anyone give me some hints how to get that stuff running? Not sure if the modem is the same as in a Lenovo Thinkpad X201. But I only got this working with a patched kernel: http://www.codon.org.uk/~mjg59/gobi_loader/ http://www.codon.org.uk/~mjg59/gobi_loader/kernel_patches/ Which firmware do you loaded and how? best regards Waldemar ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM under Fedora-13
On Sun, 2010-05-30 at 12:43 +0100, Timothy Murphy wrote: I am running Fedora-13 on my laptop, installed from the KDE Live CD. I had a little difficulty starting NM; it didn't seem to work properly until I had re-booted a couple of times. However, it seems to be working fine now. Odd. NM itself starts as a system service, so when you've booted up, you can: ps ax | grep Network or just run 'nm-tool' in a terminal and you'll see if NM is indeed running. (Fortunately, I find the network service actually works nowadays, so I have a backup if NM fails for some reason.) It will, for wired and open/wep wifi, but not for WPA or 3G. I notice that the icon in my panel has changed, to something that looks like a petrol pump at a filling station, or maybe a piece of chemical apparatus. I think the old icon (with bars to indicate signal strength) was better. Yeah, I'm not sure what the KDE people are doing WRT to icons, but the icons come from your desktop's current icon theme. So this would be an issue for KDE developers to handle. I also notice that I am running knetworkmanager (maybe this is his/her icon?) but I don't understand who told this program to run, as it doesn't seem to be mentioned in /etc/NetworkManager? The graphical NM applets (knetworkmanager and nm-applet) are run automatically on login. They usually hide themselves when NM isn't running. Look at /etc/xdg/autostart/nm-applet.desktop for the GNOME applet, or in whatever location KDE login items are normally handled. The applet startup is all handled by your desktop environment, not by NM itself. Dan I'm a bit puzzled which files NM looks at? I've kept the same /home partition I had in Fedora-12. Does NM look at anything there? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wireless options not implemented
On Tue, 2010-06-01 at 07:46 -0700, Sean D'Epagnier wrote: I really need to set the wireless bit rate otherwise the packet loss is so high I cannot use the network. I can get by for now by issuing manually iwconfig wlan3 txpower 1M often That is clearly a driver problem that should probably be fixed in the driver; pounding the TX power and bitrate is a pretty fragile hack. Do you mean 1W there instead of 1M? Or do you really mean iwconfig wlan3 rate 1M? I noticed in finish_setup in page-wireless.c the band, channel, tx power, and rate widgets are purposefully hidden so they cannot be used. I removed the code hiding them, and they work in the GUI, but they still don't actually change wireless settintgs. Does anyone know why they are not implemented and how to make them work? They weren't implemented yet because most people didn't have a use for them, or the supplicant (which is used to control all network settings) didn't support them on a per-network basis. TX power also used to be very inconsistently implemented between different drivers and thus is often useless or not even supported by a driver, and the user has no idea if it is supported or not. Drivers also do not reliably implement allowed power level reporting, which doesn't help NM determine what the right levels are for each driver. Second, we don't want to be using WEXT at all really, we want to be using cfg80211 instead. Jirka has just added support for the band/channel setting to git master for Ad-Hoc connections, but we can't use that yet for infrastructure-mode connections because only wpa_supplicant 0.7.x has that capability at this time. We probably do want some kind of TX Power configuration, but that would likely be a choice between Auto (ie allow power saving and auto TX Power adaptation if the driver supports it), Maximum power (use the max supported level the driver reports, if it does report anything). But in reality, what you probably want to do at this time to work around the broken driver that you're using is: 1) report the bug upstream to help get the driver fixed 2) as long as initial association succeeds, you can use a dispatcher script (man NetworkManager for more details) to set the bitrate manually when the connection is activated But again, not all drivers support locking in a TX power and a bitrate, and may ignore whatever you've set. That could be the case for you since you seem to need to run iwconfig often. In the end, the best thing to do is to fix the driver. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modem-manager fails on Gobi 2000 UMTS card in a Thinkpad W510, error in AT+CMEE
On Tue, 2010-06-01 at 22:04 +0200, Stefan Armbruster wrote: Hi, I'm trying to enable the builtin Gobi 2000 UMTS card on a Thinkpad W510. System is a Ubuntu Lucid 64bit, modem-manager compiled from current git. UMTS card's USB-ID: 05c6:9205 (after loading the firmware, 05c6:9204 before) When trying to connect, modem-manager sends a CMEE command resulting in an error: DEBUG: 1275421334.403788 (ttyUSB0): -- 'AT+CMEE=1CR' DEBUG: 1275421334.415006 (ttyUSB0): -- 'CRLFERRORCRLF' I've followed the debugging procedure from https://wiki.ubuntu.com/DebuggingModemmanager. In order not to pollute the list, the logs are placed on pastebin: mm-test.py output: http://pastebin.com/pRiinrSU modem-manager output: http://pastebin.com/HyHSpGhN (esp. l. 53f) network-manager output: http://pastebin.com/x7UZ20zm I assume the UMTS card is not detected correctly. Can anyone give me some hints how to get that stuff running? You're loading CDMA2000/EVDO firmware on your card, not UMTS/HSPA firmware. Chances are, since you're in Germany, you want the UMTS firmware. Unfortunately, you have to figure out from the Windows drivers what firmware files are for what technology. There's a text file that describes what the firmware directory numbers mean, and what provider they are for thats stored somewhere under the Gobi downloader directory, which is often stuffed directly onto C:\. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: network discovery interval in network manager?
On Tue, 2010-06-01 at 19:11 +0200, pink wrote: Hi, does anybody know the interval of the network search that is internally used by the network manager and where it is implemented. So far i know there is no dbus interface where such an interval can be changed. It currently starts at 0 seconds from when the device is found, and increases by 20 seconds every scan until 2 minutes, after which scans are done every 2 minutes. Is there an other possibility to change these value or is it planned to make such parameter available for the user? It's something we're investigating, but likely it'll take the form of an additional D-Bus method which clients can use to request a scan. This D-Bus method may rate-limit scan requests or otherwise require privileges to call since scan requests are effectively a DoS against the wifi card. Recent improvements to the kernels' mac80211 stack have mitigated that effect (with background scanning) but drivers that do not use mac80211 don't get that and thus may interrupt traffic during the scan. So you can guess what happens if something in userspace continually requested scans... But yeah, I'd take a patch for something like that. I know Ubuntu is carrying on in their Netbook remixes which isn't acceptable as-is, but could be cleaned up. Ground rules are: 1) a method called RequestScan(aay: ssids) on the wifi device object 2) if a scan is in progress, the method simply returns success 3) resets the scan interval to 20 seconds after the requested scan is done 4) is PolicyKit protected, which is easy to do using some of the infrastructure I'm working on in the 'perm' branch upstream right now Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Why no refresh option?
On Mon, 2010-05-31 at 02:38 -0600, Matt Warnock wrote: Can anyone explain why there is no refresh button? Running Ubuntu 10.04, moving from home to work and vice versa. Only way to get the list of available Wifi networks to refresh is to turn networking off, then on again. I've read that it should automatically refresh, but in my experience, it doesn't. Or is there something I should be doing differently? Are you suspending during that time? What driver are you using and what wifi hardware do you have? Do you see the messages sleeping... or waking up... in the NetworkManager logs in /var/log/daemon.log or /var/log/NetworkManager.log? NM scans at *most* every 2 minutes unless it's been altered by the distribution. Your case sounds like either stupid drivers or a well-known-but-supposedly-fixed D-Bus bug with the suspend/resume scripts. - if you see sleeping/waking up in the logs then it's likely a driver problem - if you dont' see sleeping/waking up but you do see other NM messages, then it's likely the d-bus thing which we can further diagnose. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Installation problem with Ubuntu Lynx?
On Mon, 2010-05-31 at 10:25 +0900, Jacobs Shannon wrote: I hope this is a trivial and non-problematic thing, but I've been watching for a report here and haven't spotted anything. Since Ubuntu 10.04 was released, I've done a number of upgrades and installations, and several times I've seen it stop during the installation with a message about the nm applet being unable to find some required resources. I've just been skipping over it without problems, either it's spurious or self-repairing, but I'm still wondering. So what's happening here is that the applet uses icons with certain names. On upgrade, sometimes these names change. When the icon files are changed underneath the applet this triggers (via GTK+) a theme change so that the applet can start using the new icon. But in this case, since the name has changed, the old icon may no longer be on disk, and the applet can't find the icons it needs to display. This is one reason why many Windows updates wait until shutdown, or why Firefox often stops working reliably if you update it while running it. In the end, it's harmless, since when you log out and log back in again, the new applet is running and it has all the resources it needs when it starts again (since you just installed the correct set of icons). Recent fixes to the applet have mitigated this and future upgrades shouldn't trigger that warning any more, though you may see some odd icons until you log out and back in. It was just changed to stop throwing up the stupid dialog and just fall back to a know-good icon name when it couldn't find what it was looking for. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: MeeGo support
On Mon, 2010-05-31 at 11:45 +0100, Tiago Cogumbreiro wrote: Hello all, I am trying to install NetworkManager in MeeGo. When I run ./autogen.sh I get the following (selected) output: [...] checking for /etc/frugalware-release... no checking for /etc/mandriva-release... no checking for /etc/pardus-release... no ./configure: line 13672: lsb_release: command not found Linux distribution autodetection failed, you must specify the distribution to target using --with-distro=DISTRO How difficult is it to have NetworkManager work on MeeGo? How can I help? Probably not too difficult as long as Meego has the basic dependencies (dbus-glib, policy-kit, libgudev, etc). That could be the sticking point. The configure stuff you see is largely ignorable, we can easily add some new checks to recognize Meego. There are only a few things that depend on the distribution these days, and those usually have sane defaults. So, what do you have for: ls /etc/*-release ? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Internet sharing over multiple interfaces
On Sun, 2010-05-30 at 18:44 +0200, Frederik Nnaji wrote: Danke, Lutz! On Fri, May 28, 2010 at 11:19, lutz lutz.reinha...@tu-bs.de wrote: yeah, i'm having a hard time trying to share my internet connection. I have mobile broadband, want to share it via LAN, no success.. what would it take to pull this off with a couple of clicks and NM's help? I have difficulties understanding your problem, because of some missing English experience, so here is the answer from what I understood. If you want to make your mobile Internet connection available for computers, which are connected to you via LAN, you have to go to the settings of your LAN adapter in NM and go to its IPv4 tab. There you change the method from DHCP or anything else to Shared to Then will be the computer which are connected to your LAN card be able to get an IP via DHCP. i will try this out again, when i get back home later on. Perhaps i was a little forgetful, when i said LAN, my greatest difficulties started with trying tethering via Wireless LAN. My mobile phone does this in 4 clicks / touches, including installation of the necessary software. How many interactions would NM ask of me before this becomes active? To start sharing your primary internet connection via WiFi, it takes 3 clicks: Click on the applet Click on Create New Wireless Network... Fill in the details Click on Create... and as long as your driver doesn't suck (they have often sucked in the past) NM will start up a new Ad-Hoc wifi network, assign your machine a 10.x.x.x address on that wifi net, and start NAT-ing anything that connects to that wifi net to your primary internet connection. The primary internet connection can be anything, ethernet, 3G, or even another wifi network if you have two wifi cards plugged in. Remember, if you have two ethernet cards, or two wifi cards, make sure to fill in the MAC Address part of the connection editor to ensure that the connection profile you're creating is only used with that specific hardware. This is only necessary if you have more than one ethernet or more than one wifi device though. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Internet sharing over multiple interfaces
On Thu, 2010-05-27 at 16:04 +0200, lutz wrote: Hi, the power adapter of my router broke and atm I am using NetworkManager to create a Internet connection and share it with other PCs. The network setup is, that all devices (including the ADSL-modem) are connected to an Ethernet switch. The computer, which is managing the Internet connection got two wired network interfaces eth0 and eth1. eth1 is used to create the ppp0 connection and was at the beginning the only card, which is connected to the switch. I activated Shared to other computers in the IPv4-tab of both cards, but only with eth1 this seems to work. So i had to use another Ethernet cable for connecting eth1 with the switch, too. Initially I wanted to use eth0 for my notebook. Make sure in the connection editor you paste in the MAC address of the card for each one, otherwise the connection settings might be applied randomly to each of the two ethernet devices. If you lock the connection to a specific MAC address, NM will only apply those settings to that specific piece of hardware. I am using Debian Sid AMD64 together with NetworkManager 0.8 and dnsmasq-base at version 2.52. Here is what ifconfig tells me about the interfaces eth0 and eth1: $ ifconfig eth0 Link encap:Ethernet Hardware Adresse 00:22:15:81:5a:c5 inet Adresse:10.42.43.1 Bcast:10.42.43.255 Maske:255.255.255.0 inet6-Adresse: fe80::222:15ff:fe81:5ac5/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:49966 errors:0 dropped:134 overruns:0 frame:0 TX packets:61232 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:5844382 (5.5 MiB) TX bytes:74125324 (70.6 MiB) Interrupt:17 eth1 Link encap:Ethernet Hardware Adresse 00:22:15:81:78:1a inet6-Adresse: fe80::222:15ff:fe81:781a/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:205201 errors:0 dropped:0 overruns:0 frame:0 TX packets:92754 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:239220870 (228.1 MiB) TX bytes:11124327 (10.6 MiB) Interrupt:18 If you're are already locking the connections, let me know and we can debug further. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: network-manager 0.8.1-beta2 does not work with isc dhcp-clients 3.1.3 and 4.1.1
On Sun, 2010-05-30 at 20:24 +0200, Michael Biebl wrote: On 30.05.2010 11:38, Thomas Schmidt wrote: Hi, i am currently testing the beta2 of network-manager 0.8.1 on my Debian Testing system, which has the isc dhcp3-client 3.1.3 installed by default. The new network-manager seems to use some commandline options for calling the dhcp-client which are not available in version 3.1.3 because i can see the following in the syslog: NM 0.8.1 requires ISC dhcp-client with DHCPv6 support enabled. The isc-dhcp package from experimental has DHCPv6 support disabled, due to build failures in the past, which have been sorted out in 4.1.1. Hopefully Andrew finds the time to upload a new version with DHCPv6 support enabled (I CCed just in case). Not sure if he still plans to upload isc-dhcp 4.x to unstable so it has a chance to get into squeeze. Of course I would prefer to have a newer dhcp version in Debian (and Ubuntu fwiw), on the other hand if NM 0.8.1 could safely fall back to not use dhcpv6 if older dhclient versions are detected, it would be even better. I'll take a patch for that. If we can autodetect the version of dhclient at %configure time, lets AC_DEFINE something like HAVE_DHCLIENT_V4 and if that's not defined, we fail any connection that requests DHCPv6. That part isn't hard. Plus, then we can get the arguments right when calling dhclient too. I'd like to fix this as well. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: gsm roaming enabling
On Fri, 2010-05-28 at 12:26 +0200, Maxime Boure wrote: Hello I have a french SIM card and I would like to connect it in Canada. It seems that the roaming is not enabled. What kind of 3G stick do you have again? This isn't by chance a Huwei E1552? ** Message: Loaded plugin Generic ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin Ericsson MBM ** Message: Loaded plugin Huawei ** Message: Loaded plugin ZTE ** (modem-manager:1472): DEBUG: (Huawei): (ttyUSB1) deferring support check ** Message: (ttyUSB0) opening serial device... ** (modem-manager:1472): DEBUG: (ttyUSB0): probe requested by plugin 'Huawei' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+GCAPCR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLF+GCAP: +CGSM, +FCLASS,+DSCRLFCRLFOKCRLF' ** Message: (ttyUSB0) closing serial device... ** Message: (Huawei): GSM modem /sys/devices/platform/ehci-omap.0/usb1/1-1 claimed port ttyUSB0 ** (modem-manager:1472): DEBUG: Added modem /sys/devices/platform/ehci-omap.0/usb1/1-1 ** (modem-manager:1472): DEBUG: Exported modem /sys/devices/platform/ehci-omap.0/usb1/1-1 as /org/freedesktop/ModemManager/Modems/0 NetworkManager: info (ttyUSB0): new GSM device (driver: 'option1') NetworkManager: info (ttyUSB0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager: info (ttyUSB0): now managed NetworkManager: info (ttyUSB0): device state change: 1 - 2 (reason 2) NetworkManager: info (ttyUSB0): deactivating device (reason: 2). NetworkManager: info (ttyUSB0): device state change: 2 - 3 (reason 0) NetworkManager: info Activation (ttyUSB0) starting connection 'bouyguestel' NetworkManager: info (ttyUSB0): device state change: 3 - 4 (reason 0) NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... ** Message: (ttyUSB0) opening serial device... NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled - enabling) ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'ATZ E0 V1 +CMEE=1CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'ATE0 +CMEE=1CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'ATX4 C1CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CREG=0CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CFUN=1CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLFOKCRLF' ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling - enabled) ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CPIN?CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLF+CPIN: READYCRLFCRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+COPS=0,,CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CREG?CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLF+CREG: 0,2CRLFCRLFOKCRLF' ** (modem-manager:1472): DEBUG: Registration state changed: 2 ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled - searching) ** (modem-manager:1472): DEBUG: (ttyUSB1): re-checking support... ** Message: (ttyUSB1) opening serial device... ** (modem-manager:1472): DEBUG: (ttyUSB1): -- 'CRLF^BOOT:35591147,0,0,0,31CRLF' ** Message: (ttyUSB1) closing serial device... ** Message: (Huawei): GSM modem /sys/devices/platform/ehci-omap.0/usb1/1-1 claimed port ttyUSB1 ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CREG?CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLF+CREG: 0,2CRLFCRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CREG?CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLF+CREG: 0,2CRLFCRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CREG?CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLF+CREG: 0,2CRLFCRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CREG?CR' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'CRLF+CREG: 0,2CRLFCRLFOKCRLF' ** (modem-manager:1472): DEBUG: (ttyUSB0): -- 'AT+CREG?CR' Status '2' in the +CREG response means searching. Normally this is simply that the device cannot find a compatible provider to use, either because your SIM card is not loaded with roaming networks, or because the frequency bands your device supports are not supported in the country you're in. However, on the E1552 specifically we've identified a problem where ModemManager sending AT+COPS=0,, causes the card to stay in 'searching' mode indefinitely. Last month I fixed MM to *not* send AT+COPS=0,, if the card was already registered on a network, so you may be able to get connected if you wait 30 seconds or so after
Re: Looking for advice about using NM with a Sprint U301 modem
On Thu, 2010-05-27 at 12:04 -0400, Daenyth Blank wrote: Hi all, I'm trying to find out some information regarding the Sprint U301 3G modem. Our use case for it is that it will be attached to an embedded machine running ubuntu with networkmanager, in addition to our software. I've been trying to get this modem to connect reliably and am having some issues with it. I've added a udev rule so that the usbserial driver is given the correct vendor/product information, and it connects automatically on boot, but not reliably. Some boots it does not connect at all and won't until I reboot. Sometimes it disconnects while the machine is running. If it disconnects either by itself or from deactivating the connection, it will not connect again and needs a reboot. The nm/mm logs say that serial requests are timing out when it's in the non-connected state. I haven't been able to recover from the disconnected state with anything about a reboot. Is there anything we can do with this device to increase reliability? Failing that, can you recommend a usb Sprint 3G modem that will be more reliable? If there are none, do you have any recommendations for any brand of 3G modem that will work well in this situation? The boxes will be deployed where manual access is not easy, so it needs to be able to connect and recover from disconnections automatically, or at least in a way that can be scripted easily. You're certainly not going to be able to get the WiMAX part of the device working automatically since we dont' have drivers for the Beceem chipset of the WiMAX side. However, the EVDO side should work with cdc-acm, so if you have to use 'usb-serial' there's already something wrong. I suspect you need to use usb_modeswitch to eject the fake CD that the device provides too, correct? Honestly, UTStarcom-based devices (which the 300 and 301 are rebrands of) often don't work that well as you've found out. I'd recommend a Sierra device instead, as Sierra is also very active in Linux kernel development and has great support for their devices. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: MeeGo support
On Wed, Jun 2, 2010 at 7:59 AM, Dan Williams d...@redhat.com wrote: On Mon, 2010-05-31 at 11:45 +0100, Tiago Cogumbreiro wrote: Hello all, I am trying to install NetworkManager in MeeGo. When I run ./autogen.sh I get the following (selected) output: [...] checking for /etc/frugalware-release... no checking for /etc/mandriva-release... no checking for /etc/pardus-release... no ./configure: line 13672: lsb_release: command not found Linux distribution autodetection failed, you must specify the distribution to target using --with-distro=DISTRO How difficult is it to have NetworkManager work on MeeGo? How can I help? Probably not too difficult as long as Meego has the basic dependencies (dbus-glib, policy-kit, libgudev, etc). That could be the sticking point. The configure stuff you see is largely ignorable, we can easily add some new checks to recognize Meego. There are only a few things that depend on the distribution these days, and those usually have sane defaults. So, what do you have for: ls /etc/*-release I think its meego-release, it might still be moblin-release. They don't have the usual init system, they replaced it with fastinit but I don't think that would cause a massive issue for NM. Peter ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: MeeGo support
On Wed, 2010-06-02 at 08:18 +0100, Peter Robinson wrote: On Wed, Jun 2, 2010 at 7:59 AM, Dan Williams d...@redhat.com wrote: On Mon, 2010-05-31 at 11:45 +0100, Tiago Cogumbreiro wrote: Hello all, I am trying to install NetworkManager in MeeGo. When I run ./autogen.sh I get the following (selected) output: [...] checking for /etc/frugalware-release... no checking for /etc/mandriva-release... no checking for /etc/pardus-release... no ./configure: line 13672: lsb_release: command not found Linux distribution autodetection failed, you must specify the distribution to target using --with-distro=DISTRO How difficult is it to have NetworkManager work on MeeGo? How can I help? Probably not too difficult as long as Meego has the basic dependencies (dbus-glib, policy-kit, libgudev, etc). That could be the sticking point. The configure stuff you see is largely ignorable, we can easily add some new checks to recognize Meego. There are only a few things that depend on the distribution these days, and those usually have sane defaults. So, what do you have for: ls /etc/*-release I think its meego-release, it might still be moblin-release. They don't have the usual init system, they replaced it with fastinit but I don't think that would cause a massive issue for NM. Nah, MM doesn't care since it usually gets auto-started by the connection manager via dbus activation. Ideally udev rules could start MM for any class of hardware it migth be able to drive, and if it can't actually drive it, MM quits. ie, if there arent' any usable modems, MM shouldn't really be running. That's either a udev thing, or an init-daemon (ie upstart, systemd, or whatever) thing. Haven't quite gotten there yet though. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] add UnlockRetries property to the modem dbus interface
On Sun, 2010-05-30 at 18:53 +0200, Frederik Nnaji wrote: hahaah, here's why: On Fri, May 28, 2010 at 15:25, Torgny Johansson torgny.johans...@ericsson.com wrote: While not entirely sure how, I'm still very glad to hear that my contribution may have that unexpected positive impact! ;) Here's the most personal Use Case you'll probably ever get out of me: Fred visits his girlfriend. As he swaps SIM cards with his girlfriend for performance reasons, the new SIM simply doesn't work. He selects the appropriate connection from the Network Manager applet in his panel repeatedly, as it does not seem to work immediately. After trying unsuccessfully for a while, Fred inserts the SIM card into a mobile phone for more verbose debugging (to see what's wrong). The phone reports SIM permanently locked, enter PUK to unlock Fred is pissed, because the PUK to the SIM is in an other town. Recent versions of NM (0.8.1) and MM (0.4) will request the PIN to unlock the device when the device is plugged in so the SIM won't get PUK locked there. We still do need to get a better way of tying a cached PIN code to the specific SIM card, though this isn't possible for a lot of devices that don't allow access to the SIM's IMSI until you've entered the PIN. Some devices do allow it though. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modemmanager broken?
On Mon, 2010-05-31 at 10:17 +0200, wp1191918-hgvs wrote: Hi, I have updated network-manager, network-manager-applet and modem-manager to the following git versions: modemmanager 1:0.3.1~git.20100525t222447.6c3ae7d-1hgvs network-manager 1:0.8.1~git.20100526t083526.8bd5168-1hgvs network-manager-gnome 1:0.8.1~git.20100526t065235.25dedfb-1hgvs Now I have the problem, that the internal sierra 3g modem does not get initialized by modem-manager. In /var/log/syslog I see the following looping messages: . May 31 10:05:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 May 31 10:05:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 . The complete syslog is on patebin.com: http://pastebin.com/download.php?i=HW39cShc The interesting thing is: it sometimes work but sometimes not. It looks like that everything is fine when first starting network-manager / modem-manager and then enable the device. When I change this sequence - first starting the device, then starting nm / mm it fails. Is there any chance you could run modem-manager with --debug for me? 1) stop NM 2) killall -TERM modem-manager 3) modem-manager --debug 4) start NM 5) reproduce the problem so we can see what's stopping ttyUSB0 in that log from being handled by Sierra? This part isn't supposed to happen: May 31 10:05:28 nc0631 modem-manager: (ttyUSB0): probe requested by plugin 'Generic' since the same device that provides ttyUSB0 also also provides ttyUSB2 and the other ports. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [RFC] Fast-user-switching plans
On Fri, 2010-05-21 at 08:53 +0200, Ludwig Nussel wrote: Daniel Gnoutcheff wrote: I've been spending some time thinking about how to get N-M to work with fast-user-switching. Here are some possible solutions that I have heard of or thought of, presented for review. [...] Well, once again, thanks for reading all that! Comments, corrections, better ideas? 5. (or rather 2b?) Get rid of the user settings concept I always found that concept weird and the wrong way around. Those network connections are not private to some user anyways. So always have all network connection settings system global (ie in /etc). You don't need to store an owner of a connection at all, owner is always root. Use polkit to determine whether a user trying to edit, start/stop network connections etc is allowed to do so. Credentials such as passwords or client certificates could still be requested from the frontend (ie the user that tries to start a connection) if storing them in plain text globally isn't desired. Yeah, I've been thinking more about that recently too. The main cases are more personal connections like VPNs where often you don't want to grant VPN access to anyone you happen to let use your computer. There certainly has to be some gating of who can start, stop, and modify connection information, and that's probably got to based on users. Essentially, ACLs on a per-connection basis. PolicyKit has some neat stuff here, but there's also always the fallback of having a list of users stored along with the connection data itself that can start/stop the connection, and another list that can modify that connection. And further posts are correct; network namespaces may well provide the ability in the future to tie a specific user's traffic to a specific outgoing interface and prevent others from using that connection. Network interfaces and routing are not necessarily machine-wide when network namespaces enter the picture, and we should have a story around that. But going forward, I think we do need to evaluate whether user connections should really stick around given that we can get the same security benefits by ACL-ing system connections. The one benefit of user connections is that they follow you if you back up your homedir and switch machines :) I don't think that's enough of a benefit to keep them around though. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
access to ppp0 on dbus
Hi, is it somehow possible to get the ppp device of a mobile broadband connection (e.g. ppp0), which was created by a dial-in connection, over dbus? Up to now we only found the physical device name (ttyUSB0) and the Udi. Thanks, Markus | ATTENTION: NEW TELEPHONE EXTENSION! | Dipl.-Ing. Markus Becker | Communication Networks | Mobile Research Center | TZI - Center for Computing Technologies | University Bremen | Germany ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
On Thu, 2010-05-27 at 18:34 +0200, Tom wrote: Hi Dan, i think the important line from debug output is: ** (modem-manager:17984): DEBUG: (net/ppp0): could not get port's parent device i tried to understand/change the source in src/mm-manager.c but without any results. That line is actually harmless. Dan any ideas? cheers, tom On Wed, 2010-05-26 at 17:59 +0200, Tom wrote: Hi Dan, On Wed, 2010-05-26 at 02:08 -0700, Dan Williams wrote: If you manually set the modem to 57600 and then run modem-manager, does that work? as mentioned in the last mail, the modem is detected. But i can not connect to the internet over ppp. Output is: ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889434.174622 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: (ttyUSB1): probe requested by plugin 'Generic' ** (modem-manager:17984): DEBUG: 1274889434.275168 (ttyUSB1): -- 'AT +GCAPCR' ** (modem-manager:17984): DEBUG: 1274889435.76137 (ttyUSB1): -- 'CRLF+GCAP: +CGSM,+FCLASSCRLFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889435.76290 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** Message: (ttyUSB1) type primary claimed by /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889435.78881 (ttyUSB1) device open count is 1 (open) ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 claimed port ttyUSB1 ** (modem-manager:17984): DEBUG: Added modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: 1274889435.79125 (ttyUSB1): -- 'AT +CPIN?CR' ** (modem-manager:17984): DEBUG: 1274889435.148615 (ttyUSB1): -- 'CRLF+CPIN: READYCRLF' ** (modem-manager:17984): DEBUG: 1274889435.152584 (ttyUSB1): -- 'CRLFOK' ** (modem-manager:17984): DEBUG: 1274889435.157066 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889435.157150 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** (modem-manager:17984): DEBUG: Exported modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 as /org/freedesktop/ModemManager/Modems/4 ** (modem-manager:17984): DEBUG: (/org/freedesktop/ModemManager/Modems/4): data port is ttyUSB1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889474.123884 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: 1274889474.123947 Modem /org/freedesktop/ModemManager/Modems/4: state changed (disabled - enabling) ** (modem-manager:17984): DEBUG: 1274889474.224318 (ttyUSB1): -- 'ATZ E0 V1CR' ** (modem-manager:17984): DEBUG: 1274889474.368589 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.368738 (ttyUSB1): -- 'ATE0CR' ** (modem-manager:17984): DEBUG: 1274889474.428616 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.428741 (ttyUSB1): -- 'AT +CMEE=1CR' ** (modem-manager:17984): DEBUG: 1274889474.504607 (ttyUSB1): -- 'CRLFERRORCRLF' ** (modem-manager:17984): DEBUG: Got failure code 100: Unknown error ** (modem-manager:17984): DEBUG: 1274889474.504762 (ttyUSB1): -- 'ATX4 C1CR' ** (modem-manager:17984): DEBUG: 1274889474.580632 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.580757 (ttyUSB1): -- 'AT +CFUN=1CR' ** (modem-manager:17984): DEBUG: 1274889474.640615 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.640775 (ttyUSB1): -- 'AT +IFC=1,1CR' ** (modem-manager:17984): DEBUG: 1274889474.708594 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.708714 (ttyUSB1): -- 'AT +GMICR' ** (modem-manager:17984): DEBUG: 1274889474.772586 (ttyUSB1): -- 'CRLFSIEMENSCR' ** (modem-manager:17984): DEBUG: 1274889474.776565 (ttyUSB1): -- 'LFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.776670 (ttyUSB1): -- 'AT +GMMCR' ** (modem-manager:17984): DEBUG: 1274889474.832606 (ttyUSB1): -- 'CRLFTC63CRLF' ** (modem-manager:17984): DEBUG: 1274889474.840584 (ttyUSB1): -- 'CR' ** (modem-manager:17984): DEBUG: 1274889474.844586 (ttyUSB1): -- 'LFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.844683 (ttyUSB1): -- 'AT +GMRCR' ** (modem-manager:17984): DEBUG: 1274889474.904630 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889474.908557 (ttyUSB1): -- 'REVISION 02.500CRLF' ** (modem-manager:17984): DEBUG: 1274889474.912571 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.912669 (ttyUSB1): -- 'AT +CGMICR' ** (modem-manager:17984): DEBUG: 1274889474.976609 (ttyUSB1): -- 'CRLFSIEMENSCRLF' **
Re: IP4Config and routes
On 12/18/2009 03:14 PM, Daniel Drake wrote: On Thu, 2009-12-17 at 14:22 -0800, Dan Williams wrote: What would you expect the routing table to look like in your case? I suppose we could do a default route for link-local. Not sure if that will confuse apps that expect a default route to mean an internet connection though. I would expect the subnet route, as NM is creating already: dest=169.254.0.0 gateway=0.0.0.0 genmask=255.255.0.0 I would also like the routing table to either include a default route: dest=0.0.0 gateway=0.0.0.0 genmask=0.0.0.0 or a multicast one: dest=224.0.0.0 gateway=0.0.0.0 genmask=240.0.0.0 The routing table that NM is setting up now is reasonable, in my opinion, but there should be some way of customizing the behaviour in the settings object. Daniel Hi, what is the status on this one? Was there a conclusion on whether NM should set a default route for link local? Thanks, Simon ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Source for nmcli
On Thu, 2010-05-27 at 17:48 +0200, Ralph Aichinger wrote: Hello! I am a Debian user and want to control NM from the command line. Unfortunately cnetworkmanager seems to have no features to deal with wireless broadband (UMTS). Where can I get the sources for nmcli, the CLI that seems to be supplied with recent versions of RedHat/Fedora? Will I run into troubles when compiling this on Debian? Or does anybody know about packages for nmcli for Debian unstable? nmcli sources live in NetworkManager git alongside NM itself: http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/cli So you can get them if you check NM out. At the moment they don't build well standalone, but you can ./configure the NM sources and then just cd cli make and you'll come out with cli/src/nmcli or cli/src/.libs/nmcli which shoudl be more or less usable with recent versions of NM. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Question about Network Manager on FreeBSD
On Wed, 2010-05-26 at 20:32 -0300, Jesse Smith wrote: Hello, I've really been enjoying using Network Manager on my Linux machine and I'd like to be able to use NM on my FreeBSD machine too. Will Network Manager compile and run on BSD? Is there any work in progress to add Network Manager to the FreeBSD Ports system? No, there isn't any effort going towards this at this time. While a lot of NM is actually agnostic, there are critical parts that are tied to Linux infrastructure like udev and netlink. There have been discussions in the past at making those parts more generic, but there haven't yet been any useful libraries that make these operations generic across platforms. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mount on VPN-Connection
On Wed, 2010-05-26 at 09:24 -0500, Greg Oliver wrote: On Wed, May 26, 2010 at 9:22 AM, rh lis...@singsang.at wrote: I want to mount some samba shares every time a special VPN-connection is established. How can I do this? Thanks for your hints. Reinhard I vote for passing the connection name to the dispatcher, so dispatcher could do all sorts of cool things! Wishlist. I do not know of a way to do it currently by connection though. 'man NetworkManager' You'll get a 'vpn-up' even for your dispatcher script, and you'll get a ton of info in the script's environment. Including the UUID of the connection that just got brought up, which you can use to figure out if you want to start the samba share or not. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: service-provider extension patch
On Tue, 2010-05-25 at 10:37 +0100, Neil Williams wrote: On Mon, 24 May 2010 16:46:34 -0700 Dan Williams d...@redhat.com wrote: On Mon, 2010-05-24 at 16:54 +0100, Neil Williams wrote: Toby Churchill have been running an internal project to compile a list of gsm network operators and the relevant information such as MCC/MNC codes, voicemail, balance check methods etc for use in a mobile-phone enabled communication aid. We created an XML document for our use internally but have since come across the the serviceprovider package which has a fair amount of overlap. So it has been suggested that it may be worthwhile adding our information with the serviceprovider list... Please find attached a patch (serviceprovider.2.tdt serviceprovider.xml) to extend the gsm node to incorporate voicemail and balance-check methods for a network provider. - When two dtmf are listed, what's the difference between the two? Do both do the same thing? Or are they different? The same networkID can have differing implementations from which the user needs to select according to local requirements like tariff or locality or handset. Our UI offers a default and then allows the user to choose from the alternatives. Is it useful to tag those different implementations with a name? We could add a name to each of the items that need it, though it can't be a property, it'd have to be a sub-element so that it could be localized. We also fallback to SMS when our own communication aid is set to silent mode (to silence normal dialling noises / notifications etc.) - For the USSD stuff, when would ussd be used, and when would ussd-response be used? ussd is fire and forget. ussd-response needs to have the modem hang on for a response from the user before the balance will be sent. The UI passes the network prompt back to the user. (Choose 1 for X, 2 for Y etc.) Which to use is down to handset/tariff variability. Ok. - For the SMS balance check, when two sms items are listed, what's the different between the two? Handset / regional / tariff based differentiation. The user configures which of the available methods to use, the choice is then stored in the application. Again, might make sense to have name and desc subelements to give users some help here too. That would mean changing the format a bit though to something more like: voicemail dtmf=901 name xml:lang=deasdfadfadf/name desc xml:lang=deBlah Blah/desc /voicemail and the same for the rest of the items. Or replace the dtmf attribute with an element inside voicemail perhaps. Either way. Maybe we don't actually need name/description for some of these? The issue is that if we go with the format you're suggesting, it's really hard to add localized name or description later without breaking the DTD. I'd also like to see comments in the DTD if we can stuff them in about what each of the new fields is, like you've described them here. That makes the DTD more of a specification. Or if that's not the right way to do it, at least comment about them at the top of the XML file. - Also for SMS, what is the meaning of the text attribute, and what's the meaning of the data inside the sms/sms item? For balance check enquiries by SMS, the text is the keyword passed as the body of the SMS and then recognised by the network. The content of the SMS tag is then used as the number to which the SMS is sent. - If you could also add voicemail to the CDMA stanza that would be great since all of these have voicemail #s too. Not testable in TCL, so that's harder. We only support GSM currently. Thanks for sending the patches! No problem. Further updates may follow as more devices get out to real users. Network methods can be impossible to test without real access to the network itself. Completely understood. Think you'd be able to respin the patch with the suggested changes? Thanks! Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
On Wed, 2010-06-02 at 00:53 -0700, Dan Williams wrote: What do you mean with Hardware IDs? It's possible to use the following commands: AT+CGMI - Request manufacturer identification AT+CGMM - Request model identification AT+CGMR - Request revision identification of software status Section Right, but sending those commands requires that we already know what baudrate we need, which I'd like to get from hardware IDs before talking to the device in the first place. It's possible to change the baudrate of the device, so IDs don't solve the problem. I think it would be best to probe the baudrate. I mean stuff like USB VID/PID, PCI VID/PID, SDIO IDs, etc. Even parallel-port devices like printers have IDs. But for serial ports, they might not. i don't know that. sorry. Cheers, Tom ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
On Wed, 2010-06-02 at 00:54 -0700, Dan Williams wrote: Hmm, what are you using to connect with PPP? If you're using NetworkManager, you can: NM_PPP_DEBUG=1 NetworkManager --no-daemon and get verbose PPP output which could help to debug the issue. Note that PPP uses it's *own* baudrate, which you have to send to pppd on the command line. So if we dont' set that correctly, PPP may not work. But debug output from pppd including it's command-line options might help us figure that out. i set the baudrate for ppp (in my system-settings connection). The output of NetworkManager (0.8 from debian testing repository) follows. In this case i used the modem with a usb-adapter on my Lenovo R400 laptop. But this should work, too. NetworkManager: info Activation (ttyUSB1) starting connection 'TC63' NetworkManager: info (ttyUSB1): device state change: 3 - 4 (reason 0) NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting... NetworkManager: info (ttyUSB1): device state change: 4 - 5 (reason 0) NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful. NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (ttyUSB1): device state change: 5 - 7 (reason 0) NetworkManager: info Starting pppd connection NetworkManager: debug [1275473061.909184] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute debug user vodafone ttyUSB1 noipdefault 57600 noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so NetworkManager: debug [1275473061.971552] nm_ppp_manager_start(): ppp started with pid 7242 NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) started... NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) complete. Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. ** Message: nm-ppp-plugin: (plugin_init): initializing ** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' using channel 1 Using interface ppp0 Connect: ppp0 -- /dev/ttyUSB1 ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x74efb434 pcomp accomp] NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. rcvd [LCP ConfNak id=0x1 asyncmap 0xa] sent [LCP ConfReq id=0x2 asyncmap 0xa magic 0x74efb434 pcomp accomp] rcvd [LCP ConfAck id=0x2 asyncmap 0xa magic 0x74efb434 pcomp accomp] rcvd [LCP ConfReq id=0x3 mru 1600 auth pap magic 0xb9051aaa asyncmap 0xa pcomp accomp] sent [LCP ConfAck id=0x3 mru 1600 auth pap magic 0xb9051aaa asyncmap 0xa pcomp accomp] ** Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... ** Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager sent [PAP AuthReq id=0x1 user=vodafone password=hidden] rcvd [PAP AuthAck id=0x1 TTP Com PPP - Password Verified OK] Remote message: TTP Com PPP - Password Verified OK PAP authentication succeeded ** Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase 'network' sent [CCP ConfReq id=0x1 deflate 15 deflate(old#) 15 bsd v1 15] sent [IPCP ConfReq id=0x1 compress VJ 0f 01 addr 0.0.0.0 ms-dns1 0.0.0.0 ms-dns3 0.0.0.0] rcvd [LCP ProtRej id=0x0 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f 32] Protocol-Reject for 'Compression Control Protocol' (0x80fd) received rcvd [LCP TermReq id=0x0 Normal Termination by NCP] LCP terminated by peer (Normal Termination by NCP) ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP TermAck id=0x0] ** Message: nm-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect' Connection terminated. NetworkManager: info (ttyUSB1): device state change: 7 - 9 (reason 13) NetworkManager: info Marking connection 'TC63' invalid. NetworkManager: info Activation (ttyUSB1) failed. NetworkManager: info (ttyUSB1): device state change: 9 - 3 (reason 0)
Re: Internet sharing over multiple interfaces
Am Mittwoch, den 02.06.2010, 00:05 -0700 schrieb Dan Williams: If you're are already locking the connections, let me know and we can debug further. I used the interfaces eth0 and eth1, which were there right from the beginning, after installing NetworkManager and they both had their MAC address filled in. The DSL connection has this field left blank, allowing me to choose the network adapter to use for dialing in. Because a new power adapter for my router arrived, there is no need for me to have this fixed at the moment. But if you want to fix it, I will help you. I have rebuild a similar setup for testing. So there is a Ethernet switch to which 2 computer (PC and laptop) and a DSL-modem are connected. All are connected with only one Ethernet card/cable. The PC is connected via eth1 and dials in. I also told NetworkManager in the IPv4 settings of eth1, that it is to be shared among other computers. This time eth0 is not involved and NetworkManager will not even start dnsmasq, as it did the last time for eth0. If I repeat this with my laptop, which is running Ubuntu 10.04, I see that I can either dial in using DSL, or participate in the network over Ethernet. Maybe I am wrong, but at the moment it seems not to be possible to create more than one connection over an wired interface. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [RFC] Fast-user-switching plans
On Wed, 2010-06-02 at 00:45 -0700, Dan Williams wrote: The one benefit of user connections is that they follow you if you back up your homedir and switch machines :) I don't think that's enough of a benefit to keep them around though. Also if you periodically update your OS - e.g installing a new Ubuntu release every six months. Stuff in $HOME stays - stuff in /etc doesn't. Simon. signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modem-manager fails on Gobi 2000 UMTS card in a Thinkpad W510, error in AT+CMEE
Waldemar and Dan, thanks for your hints. You're right, I loaded the wrong firmware, now lib/firmware/gobi contains (with md5sum): 84d002b0ef003cde6c95826bfbf067fe amss.mbn d7496085f1af3d1bfdf0fa60c3222766 apps.mbn 1aa5727b034dd1f371a3412d5800c1a3 UQCN.mbn When looking at the unpacked windows drivers, these files reside in the original directories: ./Images/Lenovo/UMTS/apps.mbn ./Images/Lenovo/UMTS/amss.mbn ./Images/Lenovo/6/UQCN.mbn I tried 6 because of http://www.thinkwiki.org/wiki/Qualcomm_Gobi_2000 and http://www.thinkwiki.org/wiki/Talk:Qualcomm_Gobi_2000 @Waldemar: I'm using a pretty recent mainline kernel that should have included the patch you mentioned. With this fireware loaded, network manager comes up with asking for the PIN but fails to establish a connection afterwards, the modem-manager debug output is available at http://pastebin.com/fTgVkf5L, PIN data has been replaced by for privacy reasons. In l. 88 an error is returned upon AT+CFUN=1. What does that mean? Is there an AT command reference available for this device? Thanks once more, Stefan Am 02.06.2010 08:39, schrieb Dan Williams: On Tue, 2010-06-01 at 22:04 +0200, Stefan Armbruster wrote: You're loading CDMA2000/EVDO firmware on your card, not UMTS/HSPA firmware. Chances are, since you're in Germany, you want the UMTS firmware. Unfortunately, you have to figure out from the Windows drivers what firmware files are for what technology. There's a text file that describes what the firmware directory numbers mean, and what provider they are for thats stored somewhere under the Gobi downloader directory, which is often stuffed directly onto C:\. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Programmatically set the MTU for ALL Ethernet Adapters
Why don't you set the new MTU value in DHCP??? 2010/6/2 Jeffersen Sylvia jeff.syl...@comcast.net I am running into an issue with programmatically changing the MTU settings for an Ethernet adapter within SUSE Enterprise 11. Issue: We have configured an OS to run within VMware Player that will be transferred between multiple PCs on removable media. By nature (as well as design) VMware will assign a new MAC Address (and therefore a new virtual adapter) at each new PC, or location on the same PC. Because we are using Lotus Notes 8.5.1, and Cisco AnnyConnect VPN Tunneling, we need to set the MTU for the adapter **WITHOUT** user intervention. When Using **ifup** we can change global settings in the “/etc/sysconfig/network/config” and adapter based settings in “/etc/sysconfig/network/ifcfg.template” files, however once the adapter is created, it must be manually activated and set to DHCP which requires “root” permissions. When using NetworkManager, the process is automated for the creation and default activation of the ethx adapter, however the MTU must be set manually, per adapter by the user. I am trying to find a way (similar to adjusting the configurations of config/ifcfg.template) that will programmatically set the MTU for ALL new ethx adapters to 1492. Any ideas will be GREATLY appreciated… J Thanks Much Jeff Sylvia ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list image001.gif___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Looking for advice about using NM with a Sprint U301 modem
On Wed, Jun 2, 2010 at 08:12, Daenyth Blank daen...@gmail.com wrote: On Wed, Jun 2, 2010 at 03:16, Dan Williams d...@redhat.com wrote: On Thu, 2010-05-27 at 12:04 -0400, Daenyth Blank wrote: Hi all, I'm trying to find out some information regarding the Sprint U301 3G modem. Our use case for it is that it will be attached to an embedded machine running ubuntu with networkmanager, in addition to our software. I've been trying to get this modem to connect reliably and am having some issues with it. I've added a udev rule so that the usbserial driver is given the correct vendor/product information, and it connects automatically on boot, but not reliably. Some boots it does not connect at all and won't until I reboot. Sometimes it disconnects while the machine is running. If it disconnects either by itself or from deactivating the connection, it will not connect again and needs a reboot. The nm/mm logs say that serial requests are timing out when it's in the non-connected state. I haven't been able to recover from the disconnected state with anything about a reboot. Is there anything we can do with this device to increase reliability? Failing that, can you recommend a usb Sprint 3G modem that will be more reliable? If there are none, do you have any recommendations for any brand of 3G modem that will work well in this situation? The boxes will be deployed where manual access is not easy, so it needs to be able to connect and recover from disconnections automatically, or at least in a way that can be scripted easily. You're certainly not going to be able to get the WiMAX part of the device working automatically since we dont' have drivers for the Beceem chipset of the WiMAX side. However, the EVDO side should work with cdc-acm, so if you have to use 'usb-serial' there's already something wrong. I suspect you need to use usb_modeswitch to eject the fake CD that the device provides too, correct? Honestly, UTStarcom-based devices (which the 300 and 301 are rebrands of) often don't work that well as you've found out. I'd recommend a Sierra device instead, as Sierra is also very active in Linux kernel development and has great support for their devices. Dan Thanks Forest, Dan. I'm going to recommend to our client that we use the Sierra cards. Appreciate the advice! I'm looking into the 598 now, and I'm having a little trouble getting NM to recognize it. I plug in the device and I can see by using dmesg that the sierra driver gets loaded, but when I run nm-connection-editor and try to edit the connection, it doesn't get listed in the device dropdown. Is there anything I have to do to get it recognized? I also haven't been able to find any good guides on setting it up. I'm running Ubuntu Karmic right now. Thanks, ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Looking for advice about using NM with a Sprint U301 modem
Hi Daenyth,
On Wed, Jun 02, 2010 at 12:54:40PM -0400, Daenyth Blank wrote:
I'm looking into the 598 now, and I'm having a little trouble getting
NM to recognize it. I plug in the device and I can see by using dmesg
that the sierra driver gets loaded, but when I run
nm-connection-editor and try to edit the connection, it doesn't get
listed in the device dropdown. Is there anything I have to do to get
it recognized? I also haven't been able to find any good guides on
setting it up. I'm running Ubuntu Karmic right now.
In Hardy, I have to use the option driver:
modprobe option
echo -n '1199 0025' /sys/bus/usb-serial/drivers/option1/new_id
I use these udev rules to automate this:
SUBSYSTEM==usb, SYSFS{idVendor}==1199, SYSFS{idProduct}==0025,
RUN+=/sbin/modprobe option
SUBSYSTEM==drivers, DEVPATH==/bus/usb-serial/drivers/option1,
RUN+=/path/to/new_id 1199 0025 %p
SUBSYSTEM==tty, ATTRS{idVendor}==1199, ATTRS{idProduct}==0025,
SYMLINK+=modem
This is the script called new_id:
#!/bin/sh
if [ $# -lt 3 ]; then
echo 'too few arguments' 2
exit 1
fi
VENDOR=${1}
PRODUCT=${2}
DEVPATH=${3}
echo -n ${VENDOR} ${PRODUCT} /sys/${DEVPATH}/new_id
I believe that proper support from Sierra is forthcoming ... ?
Hope this helps.
Thanks,
Forest
signature.asc
Description: Digital signature
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
