Re: [PATCH] au: add Telstra BigPond plan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks! Committed. commit 64f0eb3fcc7893d47e5d6228a6246e5ac992458b Author: Antti Kaijanmäki an...@canonical.com Date: Tue Apr 10 13:08:12 2012 +0300 au: add Telstra BigPond plan (lp:941773) On 16.03.2012 15:24, Mathieu Trudel-Lapierre wrote: --- serviceproviders.xml |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/serviceproviders.xml b/serviceproviders.xml index 73315fe..4deb3d9 100644 --- a/serviceproviders.xml +++ b/serviceproviders.xml @@ -745,6 +745,12 @@ conceived. usage type=mms/ nameTelstra MMS/name /apn +apn value=telstra.bigpond +plan type=postpaid/ + usage type=internet/ + nameTelstra BigPond/name + !-- username/password per-user -- + /apn /gsm /provider provider - -- Antti Kaijanmäki Software Engineer Canonical Ltd. +358 40 0243 413 https://launchpad.net/~kaijanmaki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPhAo9AAoJEPzFBNE+d1r0dwsH+wY7aBiORq7bMAFjYwGjFrYK 3OqTZLx4T3bbW4gWdlvH8izv/a/imos3xbZCYgyBytN/XI4sItpMcEgxL9TFijLL RtamJPayVZzaUebyORUs2qX79e3/vkwUoSCsuykQdXpi9HXRwBJLMkPkN76Nyzy9 rNEtShTPmlO3Ao+HKmd125HMhAMPT2fGUm6/ueocW5ihxNGauXZn17QmX2QUsB/+ OVJ20QUsTAGOTwmSp3+lZkTKH63bEIPH5U3Pr0BahTYzUEQvLSVFmBgYn6zyZal0 KAx3clUFtd80go/mkK0mTCdlTcq/Lc3OBaL6QRtL8PrOLTwyLTWauQjdsuadRxA= =cz4Y -END PGP SIGNATURE- ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Back to the Game
Hello List! It's been a while, but I've pleased to inform you that I would like to return back to help maintaining mobile-broadband-provider-info. It's heart warming to see how you have kept the database up to date and evolved and embraced it. Thank you! :) I'm also so happy to see a variety of direct committers in the git log. I noticed I still have my access to git.gnome.org, so I committed a couple of fixes. I don't seem to have rights to close the bugs on BGO, though. There seems to be new tags like plan and usage. Are those documented anywhere? -- Antti Kaijanmäki Software Engineer Canonical Ltd. +358 40 0243 413 https://launchpad.net/~kaijanmaki ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Back to the Game
On 11.10.2011 16:38, Dan Williams wrote: I've also seen submissions for empty GSM networks (no APN provided) because that provider is actually a CDMA network. CDMA networks *do* have MCC/MNC numbers, but no APNs, so these aren't valid either. The correct thing to do there is add MCC/MNC to the CDMA block DTD. Stuff like that. Trust, but Verify. Hmm.. how about writing a XML Schema which would allow precise introspection of the data for silly things? We could then instruct the submitter to run verify.sh before submitting a patch. I think we could update the instructions how to draft the updates and then you simply require that every patch is done accordingly: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders I also received a couple of patches back in the days directly from some service providers. I think we could instruct people to turn directly to their service providers customer care for right information. If we have good instructions how to update the database we could get more direct updates from service providers. Other stuff I'd like to see: - MMS details - proxy servers - SMSC addresses But those are harder to find on the web. One more reason why we should encourage the users to raise awareness in side their own providers to give us direct support. They just need very clear instructions and point of contact. :) -- Antti Kaijanmäki Software Engineer Canonical Ltd. +358 40 0243 413 https://launchpad.net/~kaijanmaki ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband Provider Info patch updating a Nigerian Provider
On Tue, 2009-12-22 at 14:46 +0100, Fanen Ahua wrote: Attached. The provider has introduced subscription plans, and adjusted billing for each of their access points accordingly. The patch adds the new access point, and properly labels the pay-as-you-go access point. thanks! committed[0]. The patch was made against an SVN checkout. I hope that is still okay. I had to change the patch a little bit as the database format has changed. No big deal. If possible try to provide any future patches in new format :) -- Antti [0] http://git.gnome.org/browse/mobile-broadband-provider-info/commit/?id=dd5ee5381302aedb90d1ba985caefb82a73be853 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: Augmenting mobile-broadband-provider-info
On Mon, 2009-11-23 at 00:05 +0100, Michael 'Mickey' Lauer wrote: * dial prefix per country Do you mean the international dial code like +1 for the US, etc? We could do this. Yes, that's what I mean. At least in the case of the timezone db, I think there's better places to put that. I realize not all platforms use glibc, but I have to believe that even if you don't, there's going to be some timezone/locale information already on the system that it would be a shame to duplicate. Ok, I agree with that. Could we at least add countries and provider's that do not necessarily offer mobile broadband but just telephony? A mapping from MCC MNC to country and provider name can be helpful in various ways. I agree. This would turn m-b-p-i into cellular-provider-info. When we are now talking about augmenting, I would like to make some proposals also. I would like to have optional network-name field added to gsm section. Virtual providers use same parent networks with same mcc/mnc pairs and there's no way telling them a part. Here's an example with two Finnish operators which both operate on DNA network: DNA: at+cops=0,2 at+cops? +COPS: 0,2,24412,2 GoMobile: at+cops=0,2 at+cops? +COPS: 0,2,24412,2 Fortunately each provider conveniently happens to claim they own the network they are operating in: DNA: at+cops=0,0 at+cops? +COPS: 0,0,dna,2 GoMobile: at+cops=0,0 at+cops? +COPS: 0,0,go.mobile,2 We can use this long alphabetical format of the network to identify the virtual providers from each other: provider nameDna/name gsm network-namedna/network-name network-id mcc=244 mnc=12/ apn value=internet dns217.78.192.22/dns dns217.78.192.78/dns /apn /gsm /provider provider nameGoMobile/name gsm network-namego.mobile/network-name network-id mcc=244 mnc=12/ apn value=internet.gomobile.fi dns217.78.192.22/dns dns217.78.192.78/dns /apn /gsm /provider This allows us to automatically select the correct provider. Any thoughts? The first proposal is pretty easy to add on top of the current format. It just adding one field. However in the current format the network-id fields have to be duplicated with each virtual provider. For example in Finland there are at least three virtual operators operating on DNA network which has four mcc/mnc pairs[0]. Database looks like this: provider nameDna/name gsm network-namedna/network-name network-id mcc=244 mnc=03/ network-id mcc=244 mnc=04/ network-id mcc=244 mnc=12/ network-id mcc=244 mnc=13/ apn value=internet dns217.78.192.22/dns dns217.78.192.78/dns /apn /gsm /provider provider nameGoMobile/name gsm network-namego.mobile/network-name network-id mcc=244 mnc=03/ network-id mcc=244 mnc=04/ network-id mcc=244 mnc=12/ network-id mcc=244 mnc=13/ apn value=internet.gomobile.fi dns217.78.192.22/dns dns217.78.192.78/dns /apn /gsm /provider I suggest that the next database format has structure based on parent network, something like this: country network gsm network-id mcc=244 mnc=03/ network-id mcc=244 mnc=04/ network-id mcc=244 mnc=12/ network-id mcc=244 mnc=13/ provider nameDna/name network-namedna/network-name apn value=internet dns217.78.192.22/dns dns217.78.192.78/dns /apn provider provider nameGoMobile/name network-namego.mobile/network-name apn value=internet.gomobile.fi dns217.78.192.22/dns dns217.78.192.78/dns /apn provider /gsm /network /country Naturally the fields can be nested and structured differently. We must first decide what information we could and want to include in cellular-provider-info. I'm anyway planning to provide converter script which allows to convert the current database into
Re: Augmenting mobile-broadband-provider-info
On Mon, 2009-11-23 at 10:30 +0100, Marcel Holtmann wrote: Hi Antti, you can't trust the network name string returned by AT+COPS since there are so many factors coming into play here. So first of all you have the names stored in the modem itself, then the names stored on the SIM card and then the potential updates over the network. Every hardware does different things to present the result of AT+COPS. AFAIK if there's a name stored in the SIM card it will have precedence over the ones stored inside the modem. And the ones that network sends are probably most reliable. I have to look though the specs if there's any information on this. Anyway the point is that in most situations we should have a correct alphabetical name for the provider, right? And to make it even more complex, in case of roaming situations some devices actually to weird concat of home network and current network. In this situation we simply have a miss in database search and user is presented with all the available configuration choices. Can you provide some real life example where the long alphabetical form is misleading and would cause selecting wrong operator? At least the devices I've tested return reliable results, but they are so few that I can't claim anything based on those. -- Antti 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: Augmenting mobile-broadband-provider-info
On Mon, 2009-11-23 at 11:41 +0200, Antti Kaijanmäki wrote: In this situation we simply have a miss in database search and user is presented with all the available configuration choices. Can you provide some real life example where the long alphabetical form is misleading and would cause selecting wrong operator? At least the devices I've tested return reliable results, but they are so few that I can't claim anything based on those. Actually it would be nice to have other people testing this, too. If someone wants to help, just take your devices and SIM-cards and post the results. For example with cu: connect to the modem: cu -s 115200 -l /dev/ttyXXX enter pin code: at+cpin= get network code: at+cops=0,2 at+cops? get the name: at+cops=0,0 at+cops? exit: ~. Execute the above procedure with GSM equipment and SIM cards available to you and post the results of network code and name here and tell if the name doesn't match your provider or if it changes with different devices. -- Antti 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: Augmenting mobile-broadband-provider-info
On Mon, 2009-11-23 at 11:54 +0200, Antti Kaijanmäki wrote: On Mon, 2009-11-23 at 11:41 +0200, Antti Kaijanmäki wrote: In this situation we simply have a miss in database search and user is presented with all the available configuration choices. Can you provide some real life example where the long alphabetical form is misleading and would cause selecting wrong operator? At least the devices I've tested return reliable results, but they are so few that I can't claim anything based on those. Actually it would be nice to have other people testing this, too. If someone wants to help, just take your devices and SIM-cards and post the results. For example with cu: BTW, don't bother trying this on Nokia phones. Alphanumerical operator codes on +cops? are not supported[0] or only partly supported[1][2]. One tester reported that when using +cops=0,2, he received the numerical network ID: +COPS: 0,2,24405 But when he tried with +cops=3,2 he received: +COPS: 0,0,elisa but at+cops=? revealed: +COPS: (2,Saunalahti,,24405), (3,SONERA,,24491), (3,dna,,24412),,(0,1,3),(0,2) And this test was done on Saunalahti SIM-card. So in this case the name received from +cops? was misleading when tested with the mode 3 so the values from Nokia phones are not reliable. Anyway we can detect that we are using Nokia phone and simply filter the operator list by network-id:s alone. -- Antti [0] http://www.bengkelprogram.com/download-ATNOKIA.pdf [1] http://sw.nokia.com/id/803db634-f447-4085-a893-91c0aa9d0cfe/AT_Command_Set_For_Nokia_GSM_And_WCDMA_Products_v1_1_en.pdf [2] http://discussion.forum.nokia.com/forum/showthread.php?t=20942 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: Augmenting mobile-broadband-provider-info
On Mon, 2009-11-23 at 15:24 +0100, Mark Haack wrote: Hi here is a live sample from Berlin. Huawei K3520 data stick + Base SIM. As you can see MVNO Base is not shown in broadband info (E-Plus) snip at+cops? +COPS: 0,0,BASE DE,2 OK This is exactly what I want to see. You have bought your SIM card from Base operator which happens to be a MVNO of E-Plus, right? If this is consistent over different devices we could augment the entry for Base in the database with network-name BASE DE. If you get E-Plus with some equipment, then guessing with this augmentation will fail. I would really like to see some results with other GSM devices (not Nokia!) with the same SIM card. If you have access to any could you please test with other devices, too? +COPS: (2,E-Plus,E-Plus,26203,2),(1,E-Plus,E-Plus,26203,0),(3,T-Mobile D,TMO D,26201,2),(3,T-Mobile D,TMO D,26201,0),(3,o2 - de,o2 - de,26207,0),(3,Vodafone.de,,26202,0),(3,o2 - de,o2 - de,26207,2),(3,Vodafone.de,,26202,2),,(0,1,2,3,4),(0,1,2) OK, so +cops=? shows the real network owner in this particular case and it's different from +cops? output. If we can solely use the output of +cops? then this doesn't matter. No one wants to use the +cops=? anyway as it's too slow :) -- Antti 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: Augmenting mobile-broadband-provider-info
On Mon, 2009-11-23 at 17:15 +0100, Marcel Holtmann wrote: Hi Antti, you can't trust the network name string returned by AT+COPS since there are so many factors coming into play here. So first of all you have the names stored in the modem itself, then the names stored on the SIM card and then the potential updates over the network. Every hardware does different things to present the result of AT+COPS. AFAIK if there's a name stored in the SIM card it will have precedence over the ones stored inside the modem. And the ones that network sends are probably most reliable. I have to look though the specs if there's any information on this. Anyway the point is that in most situations we should have a correct alphabetical name for the provider, right? I have seen different hardware with the same SIM card give different names. And I also have seen different SIM card with the same hardware result in different results. I'm not expecting this to work on every device with every SIM card. When it doesn't work and the selected provider is wrong we just offer the user the change to manually select the correct option. But when it does work and just magically out of the blue your computer or netbook or what ever just knows your provider and it's just a single click away to get connected, that's something that would be really cool :) Also you have the problem that names change over time and some hardware and SIM card combination returns still the old one, while newer pieces would give you the new name. Sure, just like APNs do change sometimes. It's just the matter of information gathering and maintenance. And if an operator changes the string to be something else, there's nothing stopping us to include the new and the old one. And if there's something conflicting then the final solution is to leave the network-name data out from the database so that manual selection is implicitly required. -- Antti 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: Service Provider Database
ti, 2009-09-22 kello 23:03 -0700, Dan Williams kirjoitti: (do you still want your name in configure.ac?) I think it's better to have an active maintainer there, so please go ahead and change it. And while you are at it last time I checked there was many obsolete files in the mbpi tree like README.svn and other stuff that contain outdated information. I think those should be either removed or updated. Thanks! -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Service Provider Database
Hello! I can't even describe how happy it made me feel when I discovered that you guys had taken over the m-b-p-i and even rolled out an upstream assistant and new database format with MCC/MCN codes. Thank you! It means so much to me to finally see that the database has taken a life of it's own and truly shown to be something that can make a difference. I haven't had any time to work on the database and quite frankly it made me really sad and frustrated. Patches piled up on my inbox and I fell into some kind of apathetic state of mind regarding the database and just started to ignore it[0]. I decided to finally do something about the patches and get them forward. Here's a list of bug reports I've created based on the emails: https://bugzilla.gnome.org/show_bug.cgi?id=594836 https://bugzilla.gnome.org/show_bug.cgi?id=594838 https://bugzilla.gnome.org/show_bug.cgi?id=594839 https://bugzilla.gnome.org/show_bug.cgi?id=594841 https://bugzilla.gnome.org/show_bug.cgi?id=594842 https://bugzilla.gnome.org/show_bug.cgi?id=594843 https://bugzilla.gnome.org/show_bug.cgi?id=594844 https://bugzilla.gnome.org/show_bug.cgi?id=594845 https://bugzilla.gnome.org/show_bug.cgi?id=594846 https://bugzilla.gnome.org/show_bug.cgi?id=594848 https://bugzilla.gnome.org/show_bug.cgi?id=594849 https://bugzilla.gnome.org/show_bug.cgi?id=594850 https://bugzilla.gnome.org/show_bug.cgi?id=594851 https://bugzilla.gnome.org/show_bug.cgi?id=594852 https://bugzilla.gnome.org/show_bug.cgi?id=594853 https://bugzilla.gnome.org/show_bug.cgi?id=594854 Note that I've intentionally left out information about the original senders as I'm not certain all of them want to be publicly named. I've sent links to them to bug reports that are based on their emails so that they can provide more information if they wish. I also took the liberty to advise them to contact Dan directly if they do not want to have a discussion out in in the public. Cheers! -- Antti PS. there are also bug reports at Launchpad in two separate locations: https://bugs.edge.launchpad.net/mobile-broadband-provider-info https://bugs.edge.launchpad.net/ubuntu/+source/mobile-broadband-provider-info [0] exactly like David Allen describes in his book Getting Things Done. It's odd how simple things like writing an email or applying a patch can become a big mental obstacle when there's a ton of other Stuff that needs your attention too. signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
mobile-broadband-provider-info 20090309 released
mobile-broadband-provider-info 20090309 === * Andres Mujica added Tele2, Lithuania * Updated Italian information * Andres Mujica and Andreas Kostyrka added FONIC, Germany * Andres Mujica added Wataniya, Kuwait * Andres Mujica and Chris Jones added user/pass to Orange (contact), UK * Felix Danso-Quayson added Zain, Ghana * Savvas Radevic provided multiple fixes gathered from ubuntu bug tracker * Timothy Kyalo added Econet, Kenya * Andrei Bordei added Eventis, Republic of Moldova * Edison Mera added Jazztel, Spain * Stefan Andersen added Fullrate Denmark * Val Zak added provider Unitel, Angola * Dominic Evans added Vodafone (TopUp and Go) UK * Carlos Arenas added authentication credentials for Comcel Colombia * Pramod Dematagoda added Sri Lankan provider Airtel * 3 UK: Separate APNs for dedicated mobile broadband devices and handsets. * Andrés Mauricio Mujica Zalamea added Orange Internet Everywhere 3G in France * Thomas Lee added Three Prepaid in Australia * Serge de Souza added Movinet Angola * Jacob Nielsen added Danish provider Oister.dk * Mykhailo Korbakov added Ukrainian provider Utel * Sunatomo Masuda added some Japanese CDMA providers * Johannes Hessellund added Danish provider BiBoB * Manuel Gomez added Colombian providers Tigo and Movistar, and removed redundant user/pass from Comcel * Rodrigo Linfati added Claro Chile - Prepago * Andreas Kostyrka added Austrian provider Yesss * Paul Sisnett added Digicel Barbados * Steven Lizarazo added Colombian provider Comcel * Rodrigo Linfati updated Chilean service providers http://svn.gnome.org/viewvc/mobile-broadband-provider-info/tags/ What is mobile-broadband-provider-info === The module contains mobile broadband settings for different service providers in different countries. The package contains only informational files so it's safe for distributions to grab updates even during feature freeze and maintenance stages. Service provider specific information is stored in a XML file. XML is not the most optimized format for a database, but it's easy to read, understand and edit. The database is released under Creative Commons Public Domain (CC-PD). for more info, see: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth support
On Wed, 2009-01-14 at 12:27 -0500, Dan Williams wrote: On Tue, 2009-01-13 at 19:11 +0200, Antti Kaijanmäki wrote: snip Now we are focusing on GSM and CDMA so there are NMGsmInterface and NMCdmaInterface which pretty much contain the code currently present in NMGsmDevice and NMCdmaDevice. Then there are corresponding NMBluetoothGsmDevice, NMDeviceKitGsmDevice, NMBluetoothCdmaDevice and NMDeviceKitCdmaDevice implementing the interfaces. Yeah, though given that we've already had a few different HAL-type things over the lifetime of NM, I'm a bit reluctant to use DeviceKit in the HAL/DeviceKit/udev discovered devices. And given that most devices are discovered using these services it should be perfectly clear not to state DeviceKit or anything else, just think it as default if nothing else is stated. But I would like to prefix Bluetooth devices for example with NMBT. I don't know.. The chart seems kind off messy. Would there actually be any differences between, say, NMDeviceKitCdmaDevice and NMDeviceKitGsmDevice; both just look at the device properties from DeviceKit to determine the path to serial port, what else? There may be later on, though if more functionality is moved to ModemManager the difference between the two gets less. Still makes some sense to me to keep them separate for now, and they will be pretty small if we do our jobs correctly. OK. Oh, and btw, I added NMSerialGsmDevice and NMSerialCdmaDevice for serial devices with arbitrary serial port paths. Settings would be something like: Arbitrary device node entry shouldn't be part of NM anywhere. Nobody should have to type that in, nor does a field like that have any place in a UI. The only type that *might* require that is old-school serial-attached RS232 modems for 56k POTS dialup, and those should get handled through directed probing instead. NM would then pick up the udev capabilities of the device automatically and add it to the internal device list. I have one mobile phone with RS232 connector for GRPS, but that falls close to 56k use case. It's not a good idea to probe random devices that are connected to COM-ports, but one solution would be to inject necessary capabilities into DeviceKit, udev or whatever. Back to discovering Bluetooth devices.. I'm not sure what would be the best way of doing this, but I would suggest that we add a new settings-table bluetooth which can be attached to appropriate connection hashes. For example adding bluetooth-settings object to GSM connection hash would signal NM to create a new Bluetooth GSM device. Same would go for Bluetooth PAN devices. key key type value notes - name STRINGbluetooth address STRINGXX:XX:XX:XX:XX:XX bluetooth address of the device aliasSTRING optional, nice name for the device. if not set device remote name will be used After we have BT address we can use SDP to query needed service on remote device upon activation. -- Antti 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: Prevent auto scan in wireless devices
On Wed, 2009-01-14 at 12:02 -0500, Dan Williams wrote: On Tue, 2009-01-13 at 23:17 +0200, Antti Kaijanmäki wrote: [Aloisio, sorry for double reply, I forgot to CC the list] On Tue, 2009-01-13 at 17:45 -0300, Aloisio Almeida wrote: Hi all, I noticed that wireless devices are always scanning, and this is very bad to power consuption in embedded systems. I would like to create a way to prevent automatic scan and just perform it when some cliente ask for it. Is it possible to do this? I mean, does it brake in some way the nm structure? Sounds good. Actually if you look at some current embedded devices they are performing wireless scan only after user has indicated he wants to create a wireless connection. I tend to think this is mainly because it's always been done this way rather than for the reason that it's actually a smoother experience for users. Chips used to suck enough that they actually did require more power to scan, but these days with passive scans, you don't even need to TX, and thus you don't need to increase power that much. If this is really a concern, the best approach is to simply disable the device (or rfkill or whatever) until the user wants to use it, at which point you bring the device out of rfkill and let NM go wild. Obviously I'm not an expert on WLAN chips ;) I just looked at this and saw we are doing periodical scans and someone said it's consuming power. Actually, I already did this patch to 0.6.6 version, but zero lines applied in new code :) Now i would like to create the patch and submit to upstream. The basic idea is just make can_scan function (src/nm-device-wifi.c) return FALSE due to some user configurations or run flags (--no-bg-scan). In this case, performScan dbus method and ScanPerformed dbus signal must be created to allow clients to ask for a scan and to notice that the scan has been performed. Would those be added in org.freedesktop.NetworkManager interface or per wireless device in Device.Wireless? Not going to happen... Again, we don't just toss stuff in before actually *understanding* what the problem is, and then determining if there are better ways of solving the problem instead of these sorts of hacks. Nothing is being tossed in. The way I see this discussion was all about understanding the problem and the proposed solution in the first place, and it worked! I'm sure everyone is now convinced that this is not the way to go :) I'm attaching the 0.6.6 patch, as I said before the idea is the same. Any comments? Is it a good way to implement that? I would like to have also a dbus option which you can change without restarting the daemon; setScanningEnabled() or something like that. '--no-bg-scan' would initialize it as false on daemon startup. It could be changed during system operation based on power profiles or something like that. Anyway it would give more flexibility. Of course that could be too close to wirelessEnabled (), though... Again, what's the use-case here? Are there better ways of solving this issue that don't impact the roaming ability performance or user experience? I think there's nothing more to add. :) -- Antti 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: Bluetooth support
On Mon, 2009-01-12 at 13:14 -0500, Dan Williams wrote:
On Mon, 2009-01-12 at 09:29 +0200, Antti Kaijanmäki wrote:
On Thu, 2009-01-08 at 13:26 -0500, Dan Williams wrote:
DUN on the other hand can not be made as a new device class as it's just
a way to get a serial device for NMGsmDevice and NMCdmaDevice. It would
be clear to separate NMSerialDevice to NMHalSerialDevice,
NMBluetoothSerialDevice, and NMPathSerialDevice (for arbitrary paths
like '/dev/ttyS0' or '/dev/foo/bar/proprietary69'), but because
NMGsmDevice and NMCdmaDevice are derived directly from NMSerialDevice we
can't do the split; that would lead to NMBluetoothGsmDevice,
NMHalGsmDevice, NMHalCdmaDevice, etc and also break the current device
type enumeration.
Instead I suggest that we handle the different serial types inside
NMSerialDevice. Let's add a 'type' option to serial configuration.
NMSerialDevice would then handle these different types internally. The
different types would be specified as an enumeration like {hal,
bluetooth, path, irda, ...} The option would be optional and default to
HAL.
Or, make the GSM and CDMA bits GInterfaces instead that any particular
device can implement... That's the cleaner route actually.
Wouldn't we still end up with HalGsmDevice, BtGsmDevice, ..., which
would implement either GSM or CDMA interfaces? The only difference
between e.g. HalGsmDevice and BtGsmDevice is the way how serial device
is discovered and initialized and all GSM funtionality would have to be
duplicated..
No, because you would make the GSM and CDMA code a GInterface which the
straight serial or BT class would implement, but of course all the
common code can still live in the GInterfaces. As you correctly point
out, the behavior is the same once you have a serial port, so I doubt
the BT class would need to override much of anything in the
NMGsmInterface or NMCdmaInterface code. GInterfaces are slightly
different than Java, for example, in that the interface itself can also
have a bunch of code and the class that implements it only needs to
override that code if necessary.
OK, sounds good. I was thinking about Java style interfaces, but now I
see your point.
IMO the right place for abstraction would be NMSerialDevice; we could
turn that to a GInterface. We can't derive NMGsmDevice and NMCdmaDevice
directly from GInterface, but we could have the NMSerialDevice as a
member of those both classes. Then on device creation time just specify
which class implementing NMSerialDevice interface you actually want. Of
course this would prevent us from casting e.g. NMGsmDevice directly to
NMSerialDevice and thus break backward compatibility;
instead of NM_SERIAL_DEVICE (foo)-bar ();
we would do NM_GSM_DEVICE (foo)-get_serial_device ()-bar();
NMSerialDevice may well be the best place to put the abstraction, but I
don't think it needs to be done as you've described it. Most of
NMSerialDevice will go away pretty soon and be replaced with
ModemManager, thus there will be a *lot* less code there that needs to
be shared. All that's left is PPP handling. We may well be able to get
away with killing NMSerialDevice as a class in the first place, and
putting its functionality into a small helper file instead.
Then we're left with NMBluetoothDevice, from which is derived
NMBTGsmDevice and NMBTCdmaDevice, and the old NMGsmDevice and
NMCdmaDevice which all just talk to ModemManager for the device setup,
and share the common PPP handler code.
I attached a quick UML chart; is that something we are after here?
First off there's new device classes NMDeviceKitDevice and
NMBluetoothDevice that indicate where the devices are coming from. Of
course that might be over engineering, but anyway..
Now we are focusing on GSM and CDMA so there are NMGsmInterface and
NMCdmaInterface which pretty much contain the code currently present in
NMGsmDevice and NMCdmaDevice. Then there are corresponding
NMBluetoothGsmDevice, NMDeviceKitGsmDevice, NMBluetoothCdmaDevice and
NMDeviceKitCdmaDevice implementing the interfaces.
I don't know.. The chart seems kind off messy. Would there actually be
any differences between, say, NMDeviceKitCdmaDevice and
NMDeviceKitGsmDevice; both just look at the device properties from
DeviceKit to determine the path to serial port, what else?
Oh, and btw, I added NMSerialGsmDevice and NMSerialCdmaDevice for serial
devices with arbitrary serial port paths. Settings would be something
like:
==
name: serialpath
type: gsm, cdma
gsm-capabilities: GSM-07.07, GSM-07.10 (could be probed?)
path: [path to serial port character file]
===
When NM sees that on a SettingsService it would create a new device
object. The settings could be bundled as optional part of GSM and CDMA
Re: Prevent auto scan in wireless devices
[Aloisio, sorry for double reply, I forgot to CC the list] On Tue, 2009-01-13 at 17:45 -0300, Aloisio Almeida wrote: Hi all, I noticed that wireless devices are always scanning, and this is very bad to power consuption in embedded systems. I would like to create a way to prevent automatic scan and just perform it when some cliente ask for it. Is it possible to do this? I mean, does it brake in some way the nm structure? Sounds good. Actually if you look at some current embedded devices they are performing wireless scan only after user has indicated he wants to create a wireless connection. Actually, I already did this patch to 0.6.6 version, but zero lines applied in new code :) Now i would like to create the patch and submit to upstream. The basic idea is just make can_scan function (src/nm-device-wifi.c) return FALSE due to some user configurations or run flags (--no-bg-scan). In this case, performScan dbus method and ScanPerformed dbus signal must be created to allow clients to ask for a scan and to notice that the scan has been performed. Would those be added in org.freedesktop.NetworkManager interface or per wireless device in Device.Wireless? I'm attaching the 0.6.6 patch, as I said before the idea is the same. Any comments? Is it a good way to implement that? I would like to have also a dbus option which you can change without restarting the daemon; setScanningEnabled() or something like that. '--no-bg-scan' would initialize it as false on daemon startup. It could be changed during system operation based on power profiles or something like that. Anyway it would give more flexibility. Of course that could be too close to wirelessEnabled (), though... -- Antti 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
mobile-broadband-provider-info 20081124 released
mobile-broadband-provider-info 20081124 === * Bjørn Lie added NetworkNorway and a bunch of other operatorusing the same network * Matheus Pacheco de Andrade added Brazilian provider Vivo * Anton Blanchard added Australian provider Exetel * Joseph Price fixed the APN of 3 UK * Konstantinos Togias fixed the APN of Vodafone Greece * Martin Pitt and Alejandro Romero Herrera provided WebSessions * Aldo Bassanini added Ecuadorian provider Porta 3G * Gabor Kelemen updated Hungarian providers * Florian Eberle updated APN of Orange Switzerland http://svn.gnome.org/viewvc/mobile-broadband-provider-info/tags/ What is mobile-broadband-provider-info === The module contains mobile broadband settings for different service providers in different countries. The package contains only informational files so it's safe for distributions to grab updates even during feature freeze and maintenance stages. Service provider specific information is stored in a XML file. XML is not the most optimized format for a database, but it's easy to read, understand and edit. The database is released under Creative Commons Public Domain (CC-PD). for more info, see: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Add a mobile network service provider -
ke, 2008-11-19 kello 15:45 -0800, Craig Carl kirjoitti: All - I have figured out how to modify the default ATT profile to support my Sprint USB modem, it connects and works with no problem. Where/how do I create a service provider ?file? I can distribute? Thanks, great! :) Here's the instructions: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mbca: CDMA operator issues
ti, 2008-10-28 kello 11:03 -0400, Dan Williams kirjoitti: On Tue, 2008-10-28 at 14:07 +0200, Antti Kaijanmäki wrote: pe, 2008-10-24 kello 19:02 -0400, Dan Williams kirjoitti: Hi, I notice the Wizard in Ubuntu also doesn't filter for CDMA vs. GSM, which can obviously be autodetected based on probing of the HAL information. For a given GSM device, you shouldn't show CDMA, but for a given CDMA device, you shouldn't show GSM operators. I plugged my Sprint card into an 8.10 beta system running NM packages from 2008-10-15 and it just showed GSM providers, which obviously won't work for my card. The reason why the wizard is showing only GSM providers is that the database doesn't yet contain many CDMA providers :) The US should be mostly populated by now. Thanks! :) The list of operators could easily be filtered based on network type, but libmbca API doesn't support that ATM :/ Should probably add that API then, it's pretty crucial. Well I don't think that it's _crucial_ because if the list of service providers is complete for a given country then the user will choose the CDMA setting from the list anyway. But it's anyway a problem and let's see what we can do about this. snip There's also http://bugzilla.gnome.org/show_bug.cgi?id=557819 which has a few more CDMA things for mbca. I will look into this. This was a libmbca bug. It's now fixed in libmbca trunk. We are preparing updates for Ubuntu ASAP. -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
libmbca 0.0.4 released
2008-10-29 libmbca 0.0.4 what's new: * translation updates * bug fix (see below) - libtool version information 0:1:0 - 0:2:0 bug fixes: * gnome.org bug #557819: New CDMA entries added as GSM get it from: http://svn.gnome.org/viewvc/libmbca/tags/ What is libmbca === libmbca provides Mobile Broadband Configuration Assistant which is a GObject and GtkAssistant based utility that splits the configuration of a new mobile broadband connection into small easy steps. In the simplest form libmbca offers an frontend for mobile-broadband-provider-info. libmbca is released under the GNU General Public License version 3. signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
mobile-broadband-provider-info 20081029 released
mobile-broadband-provider-info 20081029 === * Removed German Quam as suggested by Julius Bloch * Piotr Makowski added Polish operator Play Online * Daniel Wiberg added operator 3 for Denmark and fixed some settings for 3 Sweden * Alejandro Romero Herrera added Mexican Iusacell * Kenneth Mokkelbost added Norwegian TDC * Update OneNet - Orange for Austria (Wolfgang Silbermayr) * Dan Williams updated US CDMA providers * Ævar Arnfjörð Bjarmason added Icelandic provider Nova * Fanen Ahua updated Nigerian provider information * Gilbert Mendoza added Sprint CDMA for US * Gilbert Mendoza added Verizon EV-DO for US http://svn.gnome.org/viewvc/mobile-broadband-provider-info/tags/ What is mobile-broadband-provider-info === The module contains mobile broadband settings for different service providers in different countries. The package contains only informational files so it's safe for distributions to grab updates even during feature freeze and maintenance stages. Service provider specific information is stored in a XML file. XML is not the most optimized format for a database, but it's easy to read, understand and edit. The database is released under Creative Commons Public Domain (CC-PD). for more info, see: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mbca: CDMA operator issues
pe, 2008-10-24 kello 19:02 -0400, Dan Williams kirjoitti: Hi, I notice the Wizard in Ubuntu also doesn't filter for CDMA vs. GSM, which can obviously be autodetected based on probing of the HAL information. For a given GSM device, you shouldn't show CDMA, but for a given CDMA device, you shouldn't show GSM operators. I plugged my Sprint card into an 8.10 beta system running NM packages from 2008-10-15 and it just showed GSM providers, which obviously won't work for my card. The reason why the wizard is showing only GSM providers is that the database doesn't yet contain many CDMA providers :) The list of operators could easily be filtered based on network type, but libmbca API doesn't support that ATM :/ It's also sometimes possible to pull out what CDMA provider the card is meant for by grepping the output of ATI, because the firmware strings will sometimes contain the provider name. Might be a future optimization to suggest the provider based on that, but let the user override if they wish. True, but let's see if we can get network ID's to the database. We can use those to present smart suggestions to the users and since network id is inquired from the phone it's pretty accurate. There's also http://bugzilla.gnome.org/show_bug.cgi?id=557819 which has a few more CDMA things for mbca. I will look into this. -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
mobile-broadband-provider-info 20081015 released
--- Välitetty viesti - Lähettäjä: Antti Kaijanmäki [EMAIL PROTECTED] Vastausosoite: networkmanager-list@gnome.org Vastaanottaja: [EMAIL PROTECTED] Aihe: mobile-broadband-provider-info 20081015 released Päiväys: Wed, 15 Oct 2008 14:58:32 +0300 mobile-broadband-provider-info 20081015 === * Andreas Schildbach pointed out that o2 is spelled o2 (small letter) or (capital letter, subscript digit), but never O2 (capital letter, plain digit) * Chris Jones fixed APN of UK o2 * Stefano Rivera updated Vodacom South Africa * Stefan Andersen removed Danish service provider Orange as it has been merged with Telia * Carlos Perelló Marín sdded Simyo and Orange to the Spanish list. * Martijn van de Streek added Dutch service provider xs4all * Pramod Dematagoda updated Sri Lankan provider information * Fanen Ahua updated Nigerian provider information * Raphael Finke provided information for Irish provider Three * Vitja Makarov added xml:lang=ru names for Russian providers and * provided information for service provider Skylink (Moscow) * Carlos Santiago updated Portuguese provider information * Istvan Szollosi provided information for Romanian service provider Zapp * Daniel Nylander updated Swedish provider information and provided information for Scandinavian operator ice.net http://svn.gnome.org/viewvc/mobile-broadband-provider-info/tags/ What is mobile-broadband-provider-info === The module contains mobile broadband settings for different service providers in different countries. The package contains only informational files so it's safe for distributions to grab updates even during feature freeze and maintenance stages. Service provider specific information is stored in a XML file. XML is not the most optimized format for a database, but it's easy to read, understand and edit. The database is released under Creative Commons Public Domain (CC-PD). for more info, see: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
libmbca 0.0.3 released
2008-10-15 libmbca 0.0.3 what's new: * the assistant window now has type hint GDK_WINDOW_TYPE_HINT_DIALOG - assistant is now longer left behind any other dialog * Translations moved from Betawiki to Gnome Translators * New translations and updates * some internal restructuring and changes - libtool version information 0:0:0 - 0:1:0 get it from: http://svn.gnome.org/viewvc/libmbca/tags/ What is libmbca === libmbca provides Mobile Broadband Configuration Assistant which is a GObject and GtkAssistant based utility that splits the configuration of a new mobile broadband connection into small easy steps. In the simplest form libmbca offers an frontend for mobile-broadband-provider-info. libmbca is released under the GNU General Public License version 3. signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [ANNOUNCE] ModemManager (for GSM and CDMA)
pe, 2008-09-19 kello 23:02 +0100, Fanen Ahua kirjoitti: Patch attached as promised. One of the entries Glo-Ng with APN glogwap does not work when connected to a PC (I think the traffic is routed through a proxy that only opens port 80), so I wonder what use it is in there. Making the patch wasn't so hard :) thanks! committed: 2008-09-23 Antti Kaijanmäki [EMAIL PROTECTED] * [r24] serviceproviders.xml: Fanen Ahua updated Nigerian provider information -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Fixes some errors in the Modem-Manager Database
la, 2008-09-20 kello 19:38 +0530, Pramod Dematagoda kirjoitti: Hello there, I've seen some errors in the entries for Sri Lanka in the Modem-Manager Database and thought I should fix them, which I have in this patch as much as possible. If I have made some mistakes in the patch or posted this in the wrong place or with the wrong topic, I am sincerely sorry, this is the first patch I've ever submitted and because of that I am not so sure of myself, in any case I hope the patch is useful. Thank you for this patch! It seems to be perfectly fine and is very useful. Hopefully you will be submitting more patches to various other projects, too, now that you managed to get this one out :) committed: 2008-09-23 Antti Kaijanmäki [EMAIL PROTECTED] * [r25] serviceproviders.xml: Pramod Dematagoda updated Sri Lankan provider information -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Adding the MCC/MNC codes to m-b-p-i
[moved to own thread from [ANNOUNCE] ModemManager (for GSM and CDMA)] ke, 2008-09-17 kello 14:10 +0100, Stuart Ward kirjoitti: Antti Is it possible to add fields to this database. I am thinking of adding the MCC/MNC codes (Mobile Country code / mobile network code) Yes. We can do that. Do you have any suggestions how the database format[1] should be changed? Would it be sufficient to add a 'mcc' attribute to country element and a 'mnc' attribute to provider element? country=foo mcc=000 provider mnc=00 nameFoo Provider/name cdma / /provider /country some phones that perhaps do not have a complete list will show these codes rather than the network name if they do not have the correct mapping stored in them. Would it be possible to query the phone for mcc/mnc ID and based on that suggest the user a list of providers which she might be using? -- Antti [1] http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [ANNOUNCE] ModemManager (for GSM and CDMA)
Fanen, sorry for duplicate. I forgot to CC the nm-list. ti, 2008-09-16 kello 08:06 +0100, Fanen A. kirjoitti: I tried using adding a new mobile connection with the wizard and noticed that it contains the wrong settings for most networks in my country, as well as duplicate entries. I'd like to fix that. Thanks. Great! :) Detailed instructions are found here under How to Contribute: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Stop this APN madness!
This is quite old mail, but I forgot to CC the list back then. --- Välitetty viesti - Lähettäjä: Antti Kaijanmäki [EMAIL PROTECTED] Vastaanottaja: Dan Williams [EMAIL PROTECTED] Aihe: Re: Stop this APN madness! Päiväys: Mon, 25 Aug 2008 07:05:10 +0300 pe, 2008-08-22 kello 11:05 -0400, Dan Williams kirjoitti: On Fri, 2008-08-22 at 13:46 +0300, Antti Kaijanmäki wrote: Hi, snip So it's not safe to blindly override CID 1 or anything else for that matter. Probably not. As an enhancement, NM should: 1) Issue AT+CGDCONT=? to get the allowable range of CID slots; not all devices conform to the standard here of course so you have to quirk stuff. Some phones may have fewer than 10 slots. Some devices may have all slots filled. 2) Iterate over all the slots with AT+CGDCONT? and search for the user-specified APN. 3) If the user-specified APN is found, use that slot. 4) If the user-specified APN is not found, use a free slot. 3) If there are no free slots, use the last slot and overwrite whatever is there. this is almost exactly what I proposed :) great! let's do it! Now let's talk about APNs, shall we. Once again you hear a lot of just use 'internet' as APN and you should be ready to go. Well that might be true for some providers, but just for example take a look provider information of India[3]. That's where MBCA comes into play, to gently ask the user which APN they need :) Yes, that's the whole point of MBCA :) On most cases if you use wrong APN you just don't get connected. No true harm there except frustrated users. But now a more disturbing scenario; some service providers have multiple billing methods for mobile broadband. There's at least constant monthly fees, pay-per-Mb and even pay-per-time. The selection between these is done by selecting a specific APN. Just think for a minute here if we just blindly issue *99* and that's a pay-per-Mb APN (CID 1) when the user thinks he has constant monthly fee (CID 2). Or internet is the pay-per-Mb APN of users service provider. Or we break the users phone by overriding CID 1 with something. I think if you don't enter an APN, it'll just use the default APN which should have been set up from your provider as such. Of course that might be the wrong APN, but at some point the user needs to take responsbility for knowing how to operate their equipment. Umm, there's nothing that states that CID 1 contains the default APN. Okay. Enough hot air. Now some concrete solutions. on nm-connection-editor: * remove the dial number entry and move the APN entry to it's place Probably; I'm not aware of any mobile broadband providers that don't use the standard numbers, so we can hide this for now. * under the hood set gsm.number to ### (see below for explanation) Well, we'd just make it NULL/blank actually, that means not present. OK. What ever :) NM (or modem-manager): * when mobile broadband connection is activated check the dial number * if the number is not ###, just dial the damn thing - don't set APN or anything. User clearly knows which CID is correct. You can find wrong directions all over the web. What I'd prefer to do is require an APN, and if the APN is not present, dial the default APN. In conjunction with that, make it really easy to select the APN via the assistant and require this on creation of the connection. Perhaps don't immediately connect GSM-based devices from the applet, but bring up the mobile broadband wizard and select an APN for the connection first. As I said there's no such thing as default APN. We can't trust what ever that's set to CID 1 is correct. Indeed we should bring up MBCA if compiled in or the manual mobile broadband settings dialog if MBCA is not available. * if the number is ### do something smart - first check if specified APN is already assigned to some CID - get the list using AT+CGDCONT? and iterate that - if found, use that CID for dialing (ATD*99***cid#) Yes. - if the APN is not set then try to append it to the list - AT+CGDCONT=cids+1,IP,apn Yup, but subject to the maximum number of CIDs available which has to be queried too. - check that it really was appended to the list and use it - if appending fails for some reason just override CID 1 - AT+CGDCONT=1,IP,apn - good fail safe would be storing the original CID to a file so that it can be manually restored if we manage to break someones phone. Maybe, but that's icing on the cake after doing the rest of the stuff. I'm a big fan of not coding something until you actually find out it's needed. So you need at least one user with bricked phone? :) -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org
Re: Fwd: Stop this APN madness!
to, 2008-08-28 kello 21:49 +0100, Stuart Ward kirjoitti: We could be realy clever in the configuration screen and query the current operator, look up the APN for that oprtator. The only problem with this is that the operator names are sometimes come out as MCC/MNC numbers rather than the marketing name, but I can supply a list of all the MCC/MNC numbers to network names. This is all in a GSMA database. -- Stuart Ward M +44 7782325143 Hi! I've been really busy in these couple or so weeks and I haven't had time to look into this and probably don't have much time in the following weeks either, but let's keep up the conversation! I'm sure we can get somewhere :) Isaac from Wader[0] project contacted me and they might be willing to use[1] m-b-p-i if those MCC/MNC[2] codes are added to database format[3]. It only requires a new netid element for provider element and everyone would be happy, no? So wouldn't it make sense to include these codes in mobile-broadband-provider-info? Stuart, can the IDs you provide be licensed under Creative Commons Public Domain? -- Antti [0]http://public.warp.es/wader [1]http://public.warp.es/wader/browser/trunk/resources/extra/networks.py [2]http://en.wikipedia.org/wiki/Mobile_Network_Code [3]http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders PS. I added Pablo Martí from Wader project to CC as the link to their -devel mailing list didn't work. signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] add libmbca support
ti, 2008-08-19 kello 14:25 +0300, Antti Kaijanmäki kirjoitti: Hi, here's a patch to add libmbca support to network-manager-applet. Support has to be enabled by --with-mbca configure flag, so the support (and dependency) is not mandatory. I've tested the patch against the latest trunk (r859). If the support gets compiled in, libmbca does not have to be present on the users system as the library is dynamically loaded at runtime. There's one change that has unconditional effect. I've added IPv4 tab to mobile broadband connection editor, because it's needed with certain service providers. comments appreciated! Br, Antti No comments, no objections, right ;P So am I good to merge this to trunk? Dan? -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
ANNOUNCE: libmbca and mobile-broadband-provider-info
Hello, I'm proud to announce the first releases of libmbca and mobile-broadband-provider-info. Releases are available from GNOME SVN. libmbca 0.0.1: http://svn.gnome.org/viewvc/libmbca/tags/ mobile-broadband-provider-info 20080814: http://svn.gnome.org/viewvc/mobile-broadband-provider-info/tags/ What is mobile-broadband-provider-info === The module contains mobile broadband settings for different service providers in different countries. The package contains only informational files so it's safe for distributions to grab updates even during feature freeze and maintenance stages. Service provider specific information is stored in a XML file. XML is not the most optimized format for a database, but it's easy to read, understand and edit. The database is released under Creative Commons Public Domain (CC-PD). for more info, see: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders What is libmbca === libmbca provides Mobile Broadband Configuration Assistant which is a GObject and GtkAssistant based utility that splits the configuration of a new mobile broadband connection into small easy steps. In the simplest form libmbca offers an frontend for mobile-broadband-provider-info. libmbca is released under the GNU General Public License version 3. More information These modules are resulting from Kesäkoodi (Summercode Finland) project Mobile Broadband Configuration Assistant for NetworkManager. For more information, see: http://www.coss.fi/kesakoodi http://www.kaijanmaki.net/blog http://live.gnome.org/NetworkManager/MobileBroadband signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[PATCH] add libmbca support
Hi,
here's a patch to add libmbca support to network-manager-applet. Support
has to be enabled by --with-mbca configure flag, so the support (and
dependency) is not mandatory. I've tested the patch against the latest
trunk (r859).
If the support gets compiled in, libmbca does not have to be present on
the users system as the library is dynamically loaded at runtime.
There's one change that has unconditional effect. I've added IPv4 tab to
mobile broadband connection editor, because it's needed with certain
service providers.
comments appreciated!
Br,
Antti
Index: src/applet-device-gsm.c
===
--- src/applet-device-gsm.c (revision 859)
+++ src/applet-device-gsm.c (working copy)
@@ -36,6 +36,13 @@
#include nm-setting-ppp.h
#include nm-gsm-device.h
+#ifdef WITH_MBCA
+#include netinet/in.h
+#include arpa/inet.h
+#include nm-setting-ip4-config.h
+#include nm-utils.h
+#endif
+
#include applet.h
#include applet-device-gsm.h
#include utils.h
@@ -52,6 +59,149 @@
g_slice_free (GSMMenuItemInfo, data);
}
+#ifdef WITH_MBCA
+
+static void
+assistant_state_changed_cb (MBCAAssistant* assistant,
+ MBCAAssistantState state,
+ gpointer data)
+{
+ NMApplet *applet = data;
+ GSList* iter;
+
+ NMAGConfConnection *exported;
+
+ NMConnection *connection;
+ NMSettingGsm *s_gsm;
+ NMSettingSerial *s_serial;
+ NMSettingPPP *s_ppp;
+ NMSettingConnection *s_con;
+
+ NMSettingIP4Config* ipv4conf;
+ gboolean ignore_auto_dns = FALSE;
+ GArray *dns_servers = FALSE;
+ const char *method;
+
+ MBCAConfiguration* conf;
+
+ if (!applet_open_mbca (applet))
+ g_return_if_reached (); /* this cb should not be called without
+ * libmbca */
+
+ switch (state)
+ {
+ case MBCA_STATE_READY:
+ case MBCA_STATE_RUNNING:
+ {
+ break;
+ }
+ case MBCA_STATE_DONE:
+ {
+ conf = applet-mbca_assistant_get_configuration_func (assistant);
+ connection = nm_connection_new ();
+
+ s_con = NM_SETTING_CONNECTION (nm_setting_connection_new ());
+ nm_connection_add_setting (connection, NM_SETTING (s_con));
+
+ ipv4conf = NM_SETTING_IP4_CONFIG (nm_setting_ip4_config_new ());
+ nm_connection_add_setting (connection, NM_SETTING (ipv4conf));
+
+ s_con-id = g_strdup (conf-name);
+ s_con-type = g_strdup (NM_SETTING_GSM_SETTING_NAME);
+ s_con-autoconnect = FALSE;
+
+ /* Serial setting */
+ s_serial = (NMSettingSerial *) nm_setting_serial_new ();
+ s_serial-baud = 115200;
+ s_serial-bits = 8;
+ s_serial-parity = 'n';
+ s_serial-stopbits = 1;
+ nm_connection_add_setting (connection, NM_SETTING (s_serial));
+
+ method = NM_SETTING_IP4_CONFIG_METHOD_AUTO;
+
+ s_gsm = NM_SETTING_GSM (nm_setting_gsm_new ());
+ s_gsm-number = g_strdup (*99***1#);
+
+ s_gsm-apn = g_strdup (conf-provider-gsm.apn);
+
+ s_gsm-username = g_strdup (conf-provider-username);
+ s_gsm-password = g_strdup (conf-provider-password);
+
+ if (conf-provider-dns1) {
+struct in_addr tmp_addr;
+ignore_auto_dns = TRUE;
+dns_servers = g_array_new (FALSE, FALSE, sizeof (guint));
+
+inet_aton (conf-provider-dns1, tmp_addr);
+g_array_append_val (dns_servers, tmp_addr.s_addr);
+
+if (conf-provider-dns2) {
+ inet_aton (conf-provider-dns2, tmp_addr);
+ g_array_append_val (dns_servers, tmp_addr.s_addr);
+}
+ }
+
+ /* TODO: gateway */
+
+ g_object_set (ipv4conf,
+ NM_SETTING_IP4_CONFIG_METHOD, method,
+ NM_SETTING_IP4_CONFIG_DNS, dns_servers,
+ NM_SETTING_IP4_CONFIG_IGNORE_AUTO_DNS, ignore_auto_dns,
+ NULL);
+
+ nm_connection_add_setting (connection, NM_SETTING (s_gsm));
+
+ s_ppp = (NMSettingPPP *) nm_setting_ppp_new ();
+ nm_connection_add_setting (connection, NM_SETTING (s_ppp));
+
+
+ applet-mbca_free_configuration_func (conf);
+ if (dns_servers)
+g_array_free (dns_servers, TRUE);
+
+ exported = nma_gconf_settings_add_connection (applet-gconf_settings, connection);
+ if (!exported) {
+g_object_unref (connection);
+g_return_if_reached ();
+ }
+ g_object_unref (connection);
+
+ applet_do_notify (applet, NOTIFY_URGENCY_LOW,
+ _(New Configuration Created),
+ _(You can activate the connection by clicking this icon.\n
+ \n
+ Use connection editor to add new and to change settings if necessary),
+ nm-device-wwan, NULL, NULL, NULL, NULL);
+
+ /* FALLTHROUGH */
+ }
+ case MBCA_STATE_ABORTED:
+ {
+ for (iter = applet-mbca_assistants; iter; iter = iter-next){
+if ((MBCAAssistant*)(iter-data) == assistant) {
+ UdiAssistant* ua = iter-data;
+ g_object_unref (G_OBJECT (ua-assistant));
+ g_free (ua-udi);
+ applet-mbca_assistants = g_slist_remove_all (applet-mbca_assistants,
+ ua);
+
+ g_free (ua);
+
+}
+ }
+ break;
+ }
+ default:
+ {
+ g_return_if_reached ();
+ }
+ }
+
+}
+#endif
+
+
#define DEFAULT_GSM_NAME _(Auto
Re: Service Provider Database
ma, 2008-06-02 kello 14:39 +0300, Antti Kaijanmäki kirjoitti: Hello, one part of my project is to create and specify a database for service provider specific settings. I've created an example page in live.gnome.org[1]. Please, comment if you find something missing or you disagree. I will begin with the implementation next week. I updated the page. There's now a DTD + some other changes. -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
ma, 2008-06-02 kello 13:18 +0100, Bastien Nocera kirjoitti: On Mon, 2008-06-02 at 15:12 +0300, Antti Kaijanmäki wrote: snip provider nameService Provider - CDMA/name cdma / /provider provider nameService Provider - GSM/name gsm apninternet/apn /gsm /provider provider nameService Provider - GSM prepaid/name gsm apnprepaid.provider/apn /gsm /provider I'd rather have: provider type=gsm nameService Provider - GSM prepaid/name apnprepaid.provider/apn /provider I see your point and this was my first idea also. But the problem with this approach is that I can't validate this with a DTD. At least I didn't find any way to state: 'if provider element has property type set as gsm the element must contain child element apn ' But I can state: 'provider must have either gsm, cdma or phs child element' -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
to, 2008-06-05 kello 10:52 +0100, Bastien Nocera kirjoitti: On Thu, 2008-06-05 at 11:50 +0300, Antti Kaijanmäki wrote: snip I also mentioned another option which you seem to have discounted, and can easily be used in a DTD. provider gsm / nameService Provider - GSM prepaid/name apnprepaid.provider/apn /provider Your previous mail had type property also with this one and it had the same problem as the first one had. That's why I didn't comment on that. You can: (gsm, name, apn)? | name Would make sure you have an apn when you have a gsm tag. and this would mean something like this: provider gsm / namefoo/name apnfoo.internet/apn /provider which is not far away from: provider namefoo/name gsm apnfoo.internet/apn /gsm /provider In all cases, you could also use a C program to validate your XML file, which would give you more options. True, but our discussion has been, the way I see it, only about semantics. Our opinions differ, but as I haven't seen any technical arguments that make my proposal invalid, I am going to stick with it. I truly appreciate your input and I hope this doesn't leave hard feelings to anyone. Thanks, Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
Hi, I changed alpha-3 codes to alpha-2 because /usr/share/zoneinfo/zone.tab and /usr/share/zoneinfo/iso3166.tab use them. -- Antti ma, 2008-06-02 kello 14:39 +0300, Antti Kaijanmäki kirjoitti: Hello, one part of my project is to create and specify a database for service provider specific settings. I've created an example page in live.gnome.org[1]. Please, comment if you find something missing or you disagree. I will begin with the implementation next week. Br, Antti PS. Is there someone on this list who can shed some light on PHS[2]? Is it something that could be used with GNU/Linux and does it require service provider specific configuration? [1]http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders [2]http://en.wikipedia.org/wiki/Personal_Handy-phone_System ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
ma, 2008-06-02 kello 12:48 +0100, Bastien Nocera kirjoitti: On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: Hello, one part of my project is to create and specify a database for service provider specific settings. I've created an example page in live.gnome.org[1]. Please, comment if you find something missing or you disagree. I will begin with the implementation next week. Will you be using the XML file I sent as an example? I could use it, but I would have to write a conversion script from your XML format to the format we decide to use. I rather modify my existing python script instead and make direct conversion from the last GPRS EC database. Also, I don't think that the gsm and cdma tags are really that useful, they could be properties of the provider instead (or do we have any providers that do both?). with properties you mean attributes? If so then w3school says[1]: There are no rules about when to use attributes and when to use elements. Attributes are handy in HTML. In XML my advice is to avoid them. Use elements instead. And I prefer elements :) If a service provider offers different types of subscriptions then there would be provider element for every different type and the name element would distinguish the types from each other. provider nameService Provider - CDMA/name cdma / /provider provider nameService Provider - GSM/name gsm apninternet/apn /gsm /provider provider nameService Provider - GSM prepaid/name gsm apnprepaid.provider/apn /gsm /provider The user would see a drop-down menu with items: Service Provider - CDMA Service Provider - GSM Service Provider - GSM prepaid -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
I forgot the link.. [1] http://www.w3schools.com/xml/xml_attributes.asp ma, 2008-06-02 kello 15:12 +0300, Antti Kaijanmäki kirjoitti: ma, 2008-06-02 kello 12:48 +0100, Bastien Nocera kirjoitti: On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: Hello, one part of my project is to create and specify a database for service provider specific settings. I've created an example page in live.gnome.org[1]. Please, comment if you find something missing or you disagree. I will begin with the implementation next week. Will you be using the XML file I sent as an example? I could use it, but I would have to write a conversion script from your XML format to the format we decide to use. I rather modify my existing python script instead and make direct conversion from the last GPRS EC database. Also, I don't think that the gsm and cdma tags are really that useful, they could be properties of the provider instead (or do we have any providers that do both?). with properties you mean attributes? If so then w3school says[1]: There are no rules about when to use attributes and when to use elements. Attributes are handy in HTML. In XML my advice is to avoid them. Use elements instead. And I prefer elements :) If a service provider offers different types of subscriptions then there would be provider element for every different type and the name element would distinguish the types from each other. provider nameService Provider - CDMA/name cdma / /provider provider nameService Provider - GSM/name gsm apninternet/apn /gsm /provider provider nameService Provider - GSM prepaid/name gsm apnprepaid.provider/apn /gsm /provider The user would see a drop-down menu with items: Service Provider - CDMA Service Provider - GSM Service Provider - GSM prepaid -- Antti ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: de-facto standard dial number for CDMA
pe, 2008-05-09 kello 20:41 +0900, Masato Taruishi kirjoitti: ke, 2008-05-07 kello 19:17 +0900, Masato Taruishi kirjoitti: Hi, guys. According to the source code of network-manager-applet, Auto CDMA network connection assumes the dial number is #777, but CDMA network providers in Japan don't use this number. For example, EMobile, HSDPA provider in Japan, is using *99***1#, and AU, CDMA mobile phone service by KDDI company, is using *99**24#. I was under the impression that this *99***foo# is only for GMS modems, but now this makes it very interesting. Very interesting indeed. I would really appreciate if you could send me some pppd, chat, pon, whatever configuration files and scripts that you have used with these Japanese devices. Could you also do some additional testing[1]? Sorry, I was misunderstanding. I investigated the emobile card. It's a HSDPA, kind of GSM, modem, but supports only AT+CGDCONT. It doesn't support AT+CREG nor AT+COPS. OK. And that AU (by KDDI) you mentioned is also GSM, right? type: mobile data card model: D01NE provider: emobile Minicom 2.3-rc1 AT+CGDCONT? +CGDCONT: 1,IP,emb.ne.jp,,0,0 Great. Thanks. OK AT+CREG? ERROR So in order to use the card in NetworkManager, I had to register the card as a cdma device though it should work as a gsm device. Is there any other card which doesn't support CREG? Best regards I have an EMobile card, and successfully can use the card with NetworkManager, but I had to create manual connection because the dial number is different from #777. s_cdma-number = g_strdup (#777); /* De-facto standard for CDMA */ In order to make the card available by Auto CDMA network connection, one possible solution is to put the dial number into its hal fdi database because each card is only used for a specific provider in Japan. However, I wonder if it's applicable in other countries. I'm working with a mobile broadband service provider database, but I have not nailed down the specification yet. These dial numbers could go there if they truly are service provider specific. -- Antti [1] http://live.gnome.org/NetworkManager/MobileBroadband/GprsCid Is t here any better way to support multiple auto CDMA network in NetworkManager? Thanks in advance ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: de-facto standard dial number for CDMA
Hi, Masato. ke, 2008-05-07 kello 19:17 +0900, Masato Taruishi kirjoitti: Hi, guys. According to the source code of network-manager-applet, Auto CDMA network connection assumes the dial number is #777, but CDMA network providers in Japan don't use this number. For example, EMobile, HSDPA provider in Japan, is using *99***1#, and AU, CDMA mobile phone service by KDDI company, is using *99**24#. I was under the impression that this *99***foo# is only for GMS modems, but now this makes it very interesting. Very interesting indeed. I would really appreciate if you could send me some pppd, chat, pon, whatever configuration files and scripts that you have used with these Japanese devices. Could you also do some additional testing[1]? I have an EMobile card, and successfully can use the card with NetworkManager, but I had to create manual connection because the dial number is different from #777. s_cdma-number = g_strdup (#777); /* De-facto standard for CDMA */ In order to make the card available by Auto CDMA network connection, one possible solution is to put the dial number into its hal fdi database because each card is only used for a specific provider in Japan. However, I wonder if it's applicable in other countries. I'm working with a mobile broadband service provider database, but I have not nailed down the specification yet. These dial numbers could go there if they truly are service provider specific. -- Antti [1] http://live.gnome.org/NetworkManager/MobileBroadband/GprsCid Is t here any better way to support multiple auto CDMA network in NetworkManager? Thanks in advance ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
GPRS CID and APN
Hi! I was supposed to take on this matter at the end of May, but there already was some discussion[1] about GPRS CIDs and APNs and I think that this is something that should be investigated properly. This stuff is not as clear to me as I want it to be and it's crucial that I and others too understand this completely. First of all APN is always needed with GSM Internet connection. APN are also used to select between different subscription models of a service provider. Many (most?) service providers use internet as APN, but not everyone, and there is no way to automatically detect the correct APN. If a wrong APN is selected modem just connects to the network, but Internet connection does not work. There is no error messages or what so ever. APN can be set by initializing the modem with special command. AT+CGDCONT=CID, IP, APN some resources[2] claim that defining settings with AT+CGDCONT could be dangerous as it might mess up some settings on the phone. Of course we do not want that. But I have never or heard someone would have experienced any side effects. The other suggested method is to use *99# as dial sequence as it should use the default connection settings set on a mobile phone. This does not work at least for me. There also might be wrong configuration in mobile phone or the configuration might be missing. Besides, if *99# just magically works my job will be rather pointless ;) Some modems contain preloaded connection settings. Each setting is identified with Connection ID, CID. I would like to investigate how different mobile phones and data modems provide these preloaded or default settings, if any, and if these default CIDs are only related to data modems. Unfortunately I have very limited set of devices at my disposal and all of them are made by Nokia. Therefore I have written some instructions[3] how you all can help me to understand this field better :) = I propose that NM should always define the APN. This way there would be no surprises. I also think that user should create configuration for his devices even though they might use internet as an APN or work with *99#. This way configuring a new device would be unified between different devices. I suggest that NM would initialize GSM modems with AT+CGDCONT=1, IP, APN and to select the CID defined above the dial sequence would be ATD*99***1# -- Antti [1] http://mail.gnome.org/archives/networkmanager-list/2008-April/msg00256.html [2] http://www.woggledog.com/index.asp?subject=GPRS [3] http://live.gnome.org/NetworkManager/MobileBroadband/GprsCid ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
ma, 2008-04-28 kello 09:52 +0400, Vitja Makarov kirjoitti: 2008/4/28 Antti Kaijanmäki [EMAIL PROTECTED]: Hi, ma, 2008-04-28 kello 09:16 +0400, Vitja Makarov kirjoitti: Hi! Will it be possible to manually specify serial interface for broadband connection, as well as its type. I don't think hal could take care of all the mobile phones. It couldn't guess what is attached to RS-232 port which could be still used. That should make bluethooth integration easy. atleast my assistant will have an option to specify an arbitrary path for serial interface. And naturally I want to see NetworkManager supporting this also. What is the right way to go? IMHO, Bluetooth binding should be left to BlueZ to handle. NetworkManager would pass a binding request over D-BUS to BlueZ and BlueZ would return the path to the correct char device under /dev/.. I was thinking about using bluez dbus-interface or AF_BLUETOOTH sockets that doesn't make sens now. May be serial device should be created for all serial interfaces and hals modem command set info will be just a hint, not the rule? Then it will be possible to add nm-bluetooth-device that will create nm-serial-device on demand. Yes, Bluetooth device might be just floating around without being used and the binding should be done only when necessary. That should be pretty well to bind profiles to serial device you may have two phones with different operators, both GSM, also you may only change your SIM-card. The way I see it is that Bluetooth devices are identified only using BT MAC. If user has multiple SIMs he must have a configuration for every different operator and choose the appropriate configuration for the SIM that is in the phone. -- Antti vitja. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
Hi, ma, 2008-04-28 kello 09:16 +0400, Vitja Makarov kirjoitti: Hi! Will it be possible to manually specify serial interface for broadband connection, as well as its type. I don't think hal could take care of all the mobile phones. It couldn't guess what is attached to RS-232 port which could be still used. That should make bluethooth integration easy. atleast my assistant will have an option to specify an arbitrary path for serial interface. And naturally I want to see NetworkManager supporting this also. What is the right way to go? IMHO, Bluetooth binding should be left to BlueZ to handle. NetworkManager would pass a binding request over D-BUS to BlueZ and BlueZ would return the path to the correct char device under /dev/.. -- Antti vitja. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ANNOUNCE: Mobile Broadband Configuration Assistant
Hello, pe, 2008-04-11 kello 09:13 +0200, Stefan Seyfried kirjoitti: Dan Williams wrote: On Thu, 2008-04-10 at 07:08 -0700, Michael wrote: Hi, I have a Verizon broadband card and my experience has been that the card acts as a modem. I also use Fedora 7 and setting up the device in the Network applet as a modem allows NM to control the card as a dial-up connection. The specific card support is still required from the Verizon software to program the card for specific stuff (tower info, other programming - SPL). Although it would be nice to have some kind of signal strength meter... Unfortunately, the interfaces to get this additional data are all proprietary vendor interfaces, with the exception of a few Sierra GSM cards that accept AT commands on the second tty. So this is not currently possible without licensing the SDKs of each vendor and using non-free, binary blobs. Sorry, but that's simply not true (to not call it FUD or BS). Almost all cards work just fine using UMTSmon (http://umtsmon.sf.net). Klaas is acquiring those cards that don't right now and then they will work, too. Whoa! This is fantastic! I've been interested in mobile broadband under GNU/Linux for three years now and this is the first time I hear about UMTSmon. Well, it's never too late to find out something new ;-) The only thing that is still needed is a port multiplexer for single-port cards like my novatel xu870, but there was just no pressing need for having signal strength while being connected, so i did not yet look into that :-) It seems to me (after looking at the screen shots:) that NetworkManager and UMSTmon could definitely have a some sort of future together. -- Antti ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
ANNOUNCE: Mobile Broadband Configuration Assistant
Hello, I am happy to announce that I will be developing mobile broadband configuration assistant for NetworkManager during this summer. The assistant will make configuration of mobile broadband, GPRS, EDGE, UMTS, CDMA and etc. connections easy and as automated as possible. My project[1] is a part of Kesäkoodi2008[2] (Summer Code Finland) and thus I will receive funding. Dan Williams mentors the project. You can find more information through my blog[3]. I will be using the blog during the summer to share frequent updates about my progress. Yours sincerely, Antti Kaijanmäki [1] http://www.kaijanmaki.net/kesakoodi/projectplan.pdf [2] http://www.coss.fi/kesakoodi [3] http://www.kaijanmaki.net/blog ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ANNOUNCE: Mobile Broadband Configuration Assistant
Hello, to, 2008-04-10 kello 14:15 +0400, Vitja Makarov kirjoitti: Hi! Nice to hear this. Are you going to add bluetooth support? vitja. I'm not going to add Bluetooth support to NetworkManager. At least that is not the plan right now. However there are some couple of weeks reserved for working on NetworkManager itself and thus if it's later decided I should work on Bluetooth support, I will. -- Antti ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ANNOUNCE: Mobile Broadband Configuration Assistant
to, 2008-04-10 kello 09:12 -0400, Matt Burkhardt kirjoitti: On Thu, 2008-04-10 at 16:00 +0300, Antti Kaijanmäki wrote: Hello, to, 2008-04-10 kello 14:15 +0400, Vitja Makarov kirjoitti: Hi! Nice to hear this. Are you going to add bluetooth support? vitja. I'm not going to add Bluetooth support to NetworkManager. At least that is not the plan right now. However there are some couple of weeks reserved for working on NetworkManager itself and thus if it's later decided I should work on Bluetooth support, I will. -- Antti ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list I am so happy you're working on this. I've been wanting to get a mobile broadband card, but Verizon only supports Linux for their Enterprise customers. Unfortunately I can't make any promises regarding any particular mobile broadband card or dedicated data modem, but hopefully plenty of them get supported by the end of summer. -- Antti -- Matt Burkhardt, MSTM President Impari Systems, Inc. Phone: (301) 644-3911 [EMAIL PROTECTED] http://www.imparisystems.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
