issues with new wpa adhoc fixes
Hi, I tried the adhoc wpa fixes from yesterday and found some issues: - i am connected to my wpa2 wifi network - i create a new wpa/wpa2 adhoc connection when the connection should be established, nm dies and i have to restart /etc/rc.d/networkmanager. - when it has restarted, i connect to my home wifi, then switch to the adhoc i was trying to create (selecting it from the list this time). - i get connected to the adhoc connection, nm-applet shows the signal strenght at 0, i.e. all grey bars. - i try to switch back to the home wifi connection, but when i should get connected, nm just always disconnects completely. again, restarting the daemon fixes this, as above (although it hasn't crashed this time). after restarting it, i can connect to the home wifi network again. greets, Björn 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: Mobile Broadband - how do I trace/debug the modem initialisation?
On Mon, 2008-10-20 at 13:26 -0400, Dan Williams wrote: On Mon, 2008-10-20 at 17:55 +0300, Tambet Ingo wrote: On Sat, Oct 18, 2008 at 2:59 PM, Rick Jones [EMAIL PROTECTED] wrote: Where are the actual dialling protocol exchanges defined - are they hard-coded? Not being able to script this bit of the connection seems to be problematic, compared to pppd. I'd really like to move to NM instead of messing with pppd, pon, poff etc. but I can't get past the first hurdle :( If you have recent enough NM (r4155 or newer), you can turn on serial debug with NM_SERIAL_DEBUG environment variable. The AT commands are hard coded and there are no plans to leave it to users to figure out. I actually converted NM_SERIAL_DEBUG into an environment variable about 2 weeks ago or something. No longer need to ask uses to rebuild, but can simply NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon and have them test out and report results. Dan Hi, I am having a similar issue on my Dell Latitude E6500 which has a Broadcom 5530 buildin hsdpa minicard. This device gives an ERROR when sent an ATZ command. Using a chat script or wvdial with a cusomized wvdial.conf file which leaves out the ATZ command, the modem works flawlessly. When using NetworkManager however it does not. Here is the trace from NetworkManager DEBUG: NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224572376.061516] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224572376.169089] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.196931] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.246578] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ERROR ' NetworkManager: WARN init_done(): Modem initialization failed NetworkManager: info (ttyACM0): device state change: 4 - 9 NetworkManager: debug [1224572376.247018] nm_serial_device_close(): Closing device 'ttyACM0' NetworkManager: info Marking connection 'Vodacom' invalid. NetworkManager: info Activation (ttyACM0) failed. NetworkManager: info (ttyACM0): device state change: 9 - 3 NetworkManager: info (ttyACM0): deactivating device (reason: 0). As you can see, the ATZ gives an ERROR. Is there some work around to fix this? Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 10:47 AM, Craig Main [EMAIL PROTECTED] wrote: I am having a similar issue on my Dell Latitude E6500 which has a Broadcom 5530 buildin hsdpa minicard. This device gives an ERROR when sent an ATZ command. Using a chat script or wvdial with a cusomized wvdial.conf file which leaves out the ATZ command, the modem works flawlessly. When using NetworkManager however it does not. Here is the trace from NetworkManager DEBUG: NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224572376.061516] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224572376.169089] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.196931] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.246578] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ERROR ' The init string has more commands than (AT)Z (reset): It turns off echo (E0), sets verbose mode (V1) etc... Can you try to send only ATZ and ATZ E0 V1 to your modem (using minicom or kermit or wvdial) and see if that works? Or if it's specifically Z command that doesn't work, does this command work: ATE1 V1 X4 C1 +FCLASS=0 ? I've seen a device which doesn't like +FCLASS command. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 11:03 +0300, Tambet Ingo wrote: On Tue, Oct 21, 2008 at 10:47 AM, Craig Main [EMAIL PROTECTED] wrote: I am having a similar issue on my Dell Latitude E6500 which has a Broadcom 5530 buildin hsdpa minicard. This device gives an ERROR when sent an ATZ command. Using a chat script or wvdial with a cusomized wvdial.conf file which leaves out the ATZ command, the modem works flawlessly. When using NetworkManager however it does not. Here is the trace from NetworkManager DEBUG: NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224572376.061516] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224572376.169089] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.196931] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.246578] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ERROR ' The init string has more commands than (AT)Z (reset): It turns off echo (E0), sets verbose mode (V1) etc... Can you try to send only ATZ and ATZ E0 V1 to your modem (using minicom or kermit or wvdial) and see if that works? Or if it's specifically Z command that doesn't work, does this command work: ATE1 V1 X4 C1 +FCLASS=0 ? I've seen a device which doesn't like +FCLASS command. --Minicom Trace-- Welcome to minicom 2.3 OPTIONS: I18n Compiled on May 3 2008, 10:44:23. Port /dev/ttyACM0 Press CTRL-A Z for help on special keys AT S7=45 S0=0 L1 V1 X4 c1 E1 Q0 OK atz ERROR ATE1 V1 X4 C1 +FCLASS=0 OK ATZ E0 V1 ERROR --End Trace-- On a slightly related note, this modem also requires that the RF circuit gets turned on with AT+CFUN=1 Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 11:17 AM, Craig Main [EMAIL PROTECTED] wrote: atz ERROR ATE1 V1 X4 C1 +FCLASS=0 OK ATZ E0 V1 ERROR Ah, so it is the reset command, thank you. We've been trying to avoid workarounds for different modems to NetworkManager so unfortunately for now, you'll need to change the init string in the code and recompile NM. I am working on another code base which has plugins (sort of drivers) to allow special handling of non-standard modems. I'd like to add support for your modem, can you please send me the output of 'lshal' (either privately or to list)? Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... Tambet Ingo wrote: On Tue, Oct 21, 2008 at 11:17 AM, Craig Main [EMAIL PROTECTED] wrote: atz ERROR ATE1 V1 X4 C1 +FCLASS=0 OK ATZ E0 V1 ERROR Ah, so it is the reset command, thank you. We've been trying to avoid workarounds for different modems to NetworkManager so unfortunately for now, you'll need to change the init string in the code and recompile NM. I am working on another code base which has plugins (sort of drivers) to allow special handling of non-standard modems. I'd like to add support for your modem, can you please send me the output of 'lshal' (either privately or to list)? Thanks ___ 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: Mobile Broadband - how do I trace/debug the modem initialisation?
The issue is that you have enabled unsolicited response codes. Several possable solutions 1) add +CREG=0 to your init string to disable. 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid Full command definition 3GPP 27007 defines +CREG Command Possible response(s) +CREG=[n] +CREG? +CREG: n,stat[,lac,ci[,AcT]] *+CME ERROR: err* +CREG=? +CREG: (list of supported ns) * * *Description* Set command controls the presentation of an unsolicited result code +CREG: stat when n=1 and there is a change in the MT network registration status, or code +CREG: stat[,lac,ci[,AcT]] when n=2 and there is a change of the network cell. Read command returns the status of result code presentation and an integer stat which shows whether the network has currently indicated the registration of the MT. Location information elements lac, ci and AcTare returned only when n=2 and MT is registered in the network. Refer subclause 9.2 for possible err values. *Defined values* n: *0*disable network registration unsolicited result code 1enable network registration unsolicited result code +CREG: stat 2enable network registration and location information unsolicited result code +CREG: stat[,lac,ci[,AcT]] stat: registration status 0not registered, MT is not currently searching a new operator to register to 1registered, home network 2not registered, but MT is currently searching a new operator to register to 3registration denied 4unknown 5registered, roaming lac: string type; two byte location area code in hexadecimal format (e.g. 00C3 equals 195 in decimal) ci: string type; four byte UTRAN/GERAN cell ID in hexadecimal format AcT: access technology of the registered network 0GSM 1GSM Compact 2UTRAN 3GSM w/EGPRS (see NOTE 1) 4UTRAN w/HSDPA (see NOTE 2) 5UTRAN w/HSUPA (see NOTE 2) 6UTRAN w/HSDPA and HSUPA (see NOTE 2) -- Stuart Ward M +44 7782325143 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 10:47 +0200, Per Hallsmark wrote: Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... My apologies, you are quite correct, it is a Dell Device: Bus 008 Device 004: ID 413c:8147 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x413c Dell Computer Corp. idProduct 0x8147 bcdDevice0.00 iManufacturer 1 Dell iProduct2 Dell Wireless 5530 HSPA Mobile Broadband Minicard Device The modem defaults to cfun=4 on startup, so one needs to issue a cfun=1 before using it to connect. You are also correct about ATF working. What is the mbm plugin? Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 11:50 AM, Stuart Ward [EMAIL PROTECTED] wrote: The issue is that you have enabled unsolicited response codes. Several possable solutions 1) add +CREG=0 to your init string to disable. 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid What? The issue is that there's a modem that does not like 'Z' (reset) command. It has nothing to do with +CREG or unsolicited response codes. We're talking about modem initialization, registration comes way later _after_ modem is initialized. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Hello Craig, Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) If you can be patient until next week, I hopefully can describe howto get this modem going here. I'm dependant on the driver to be released first. It's not really a Dell device either, they oem it... ;-) Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) /Per Craig Main wrote: On Tue, 2008-10-21 at 10:47 +0200, Per Hallsmark wrote: Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... My apologies, you are quite correct, it is a Dell Device: Bus 008 Device 004: ID 413c:8147 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x413c Dell Computer Corp. idProduct 0x8147 bcdDevice0.00 iManufacturer 1 Dell iProduct2 Dell Wireless 5530 HSPA Mobile Broadband Minicard Device The modem defaults to cfun=4 on startup, so one needs to issue a cfun=1 before using it to connect. You are also correct about ATF working. What is the mbm plugin? Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
-- Stuart Ward M +44 7782325143 On Tue, Oct 21, 2008 at 9:58 AM, Tambet Ingo [EMAIL PROTECTED] wrote: On Tue, Oct 21, 2008 at 11:50 AM, Stuart Ward [EMAIL PROTECTED] wrote: The issue is that you have enabled unsolicited response codes. Several possable solutions 1) add +CREG=0 to your init string to disable. 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid What? The issue is that there's a modem that does not like 'Z' (reset) command. It has nothing to do with +CREG or unsolicited response codes. We're talking about modem initialization, registration comes way later _after_ modem is initialized. With some delicate footwork I've been able to get it past that point, but it hits another one. It responds to AT+CREG? with +CREG: 1,1, but nm-gsm-device.c only accepts 0,1. I'm not an expert on these GSM commands, and a quick google only turned up this: http://doc.trolltech.com/qtopia4.2/modememulator-network.html From this I don't see why the modem shouldn't respond 1,1, or even 2,1. I did a quick hex-edit patch to NetworkManager, changing 0,1 to 1,1, and finally it connected! This is the point I was responding to. Tambet ___ 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: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 11:14 +0200, Per Hallsmark wrote: Hello Craig, Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) If you can be patient until next week, I hopefully can describe howto get this modem going here. I'm dependant on the driver to be released first. It's not really a Dell device either, they oem it... ;-) Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) /Per Thanks Per, let me know if you need info from me. I can wait as I have it working manually via wvdial. Regards Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
--On Tuesday, October 21, 2008 11:58:58 +0300 Tambet Ingo [EMAIL PROTECTED] wrote: ¦ What? The issue is that there's a modem that does not like 'Z' (reset) ¦ command. It has nothing to do with +CREG or unsolicited response ¦ codes. We're talking about modem initialization, registration comes ¦ way later _after_ modem is initialized. There are two problems here, one from me and one from Stuart Ward. Mine started as a failure to respond to AT at all, and then moved onto a problem with +CREG responses. Stuart's seems to be mainly a problem with ATZ not supported. Hope that clears up the confusion! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager applet r953 fails to compile.
On Mon, 2008-10-20 at 13:07 -0400, Dan Williams wrote: On Sat, 2008-10-18 at 19:13 +0530, Pramod Dematagoda wrote: I've just pulled r953 of network-manager-applet, however when I try to compile it I get the following errors from make:- gconf-helpers.c: In function 'write_one_secret_to_keyring': gconf-helpers.c:1254: error: 'NM_SETTING_VPN_SECRETS' undeclared (first use in this function) gconf-helpers.c:1254: error: (Each undeclared identifier is reported only once gconf-helpers.c:1254: error: for each function it appears in.) make[3]: *** [libgconf_helpers_la-gconf-helpers.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Is this something wrong with nm-applet itself or is there something I'm doing wrong here? This is on a Fedora 9 PC. What version of NetworkManager are you using? You'll generally have to build latest NetworkManager along with the applet. I bet you've got svn4022.4 installed and you're trying to build trunk applet, which isn't going to work... Dan Whoops, you are right, I only have the version of NM that comes with Fedora, although I didn't know that the NM-Core and the NM-Applet were so tied with each other. But now I tried compiling the latest SVN NM-Core, and now I get this slight headache while running make:- nm-connection.c:27:28: error: dbus/dbus-glib.h: No such file or directory I have installed the required version of dbus-glib and the path in Makefile.in states:- DBUS_CFLAGS = /usr/local/include/dbus-1.0/dbus/ -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=2 -DDBUS_VERSION_MICRO=4 which I verified contains the DBUS header files. Regards, Pramod Dematagoda ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 12:14 PM, Per Hallsmark [EMAIL PROTECTED] wrote: Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) I committed your patches from last week yesterday. Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) Yeah, it's probably a good idea. Overriding the whole Enable() is a bit too much work if you only need to use a different init string. I'll have that later today. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 10:39 +0100, Rick Jones wrote: --On Tuesday, October 21, 2008 09:50:35 +0100 Stuart Ward [EMAIL PROTECTED] wrote: ¦ The issue is that you have enabled unsolicited response codes. Several possable solutions ¦ 1) add +CREG=0 to your init string to disable. ¦ 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid Thanks, that's beginning to make sense. Do I understand unsolicited response string to mean the modem can send a +CREG code at any time, not just in response to an AT query? If so then i can see why it's better not enabled. Inelegant though it is, i think NM does need a way to define custom init ( de-init?) strings externally. This has been the bane of God no. It's like adding text boxes for arbitrary command line arguments for openvpn. How are you supposed to know what goes in there? Do you just google around and find something that some random user reported worked for them and then try it? Or if that doesn't work try something else? Then you've just wasted 4 hours for something that should Just Work. We don't need to do this, because most of the differences between hardware can be handled with quirks. Adding an arbitrary enter some command strings means you've completely lost. Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: issues with new wpa adhoc fixes
On Tue, 2008-10-21 at 08:26 +0200, Björn Martensen wrote: Hi, I tried the adhoc wpa fixes from yesterday and found some issues: Can you try with svn r4200? There were a few unrelated issues that I fixed last night/this morning that could help out some of the issues here. Also, what kernel and wpa_supplicant version are you using? They greatly affect whether you can create adhoc networks at all. Dan - i am connected to my wpa2 wifi network - i create a new wpa/wpa2 adhoc connection when the connection should be established, nm dies and i have to restart /etc/rc.d/networkmanager. - when it has restarted, i connect to my home wifi, then switch to the adhoc i was trying to create (selecting it from the list this time). - i get connected to the adhoc connection, nm-applet shows the signal strenght at 0, i.e. all grey bars. - i try to switch back to the home wifi connection, but when i should get connected, nm just always disconnects completely. again, restarting the daemon fixes this, as above (although it hasn't crashed this time). after restarting it, i can connect to the home wifi network again. greets, Björn ___ 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: How to connect to a specified wireless access point via network manager's dbus service?
On Tue, 2008-10-21 at 09:25 +0800, Zhe Su wrote:
Thanks for your feedback.
On Tue, Oct 21, 2008 at 1:28 AM, Dan Williams [EMAIL PROTECTED] wrote:
On Sat, 2008-10-18 at 23:47 +0800, Zhe Su wrote:
Hi,
I'm writing an application which needs to control network
manager
via its dbus service, especially to connect the wifi to a
specified
access point. I'm using openSUSE 11 with network manager
0.7. After
reading the documentation and source code of network manager
applet, I
found that a connection object must be created for the
access point
before calling network manager to activate the ap. However
seems that
it's only possible to create connection object by using
functions
provided by libnm-{glib,utils}. There is no corresponding
methods
exported through dbus. But I don't want to make my
application depend
on libnm.
So I'm wondering if there is any way to achieve my goal
with nm's
dbus service only?
Do you expect the applet to be running alongside your program?
Yes.
_Something_ needs to provide the Connection details to
NetworkManager,
and right now that's the applet. If you want to replace the
applet and
provide your own org.freedesktop.NetworkManagerUserSettings
service,
that would work.
I'm going to use existing settings service instead of providing a new
one. The problem is, current org.freedesktop.NetworkManagerSettings
interface doesn't have a method to create a new connection for a
specific device and access point, which makes it impossible to
activate the device in my application if there is no connection for
that device yet. And it might be handy to have a method in
org.freedesktop.NetworkManager to activate a specific device without
specifying the connection (a temporary default connection shall be
created and used by network manager), so that network manager can
still work in many cases without settings service.
No, creating a temporary connection won't work because no settings
service provides that connection over dbus. Thus, nothing (like the
applet or your application) can actually figure out the connection
details, and thus won't know what the connection's name is, what it's
uuid is, what it's IP settings are supposed to be etc. NetworkManager
_consumes_ connections, it doesn't provide them. Thus, something else
must provide them.
You could try writing out the connection you wish to use directly to
GConf, and then the applet will pick that connection up automatically
and you can tell NM to activate it.
Dan
And when will nm 0.7 be released officially?
Regards
James Su
Once you have provided the connection object over D-Bus, NM
can find it,
and you can tell NM to activate that connection. You can
BSS-lock that
connection to the particular AP you're interested in.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager applet r953 fails to compile.
On Tue, 2008-10-21 at 15:04 +0530, Pramod Dematagoda wrote: On Mon, 2008-10-20 at 13:07 -0400, Dan Williams wrote: On Sat, 2008-10-18 at 19:13 +0530, Pramod Dematagoda wrote: I've just pulled r953 of network-manager-applet, however when I try to compile it I get the following errors from make:- gconf-helpers.c: In function 'write_one_secret_to_keyring': gconf-helpers.c:1254: error: 'NM_SETTING_VPN_SECRETS' undeclared (first use in this function) gconf-helpers.c:1254: error: (Each undeclared identifier is reported only once gconf-helpers.c:1254: error: for each function it appears in.) make[3]: *** [libgconf_helpers_la-gconf-helpers.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Is this something wrong with nm-applet itself or is there something I'm doing wrong here? This is on a Fedora 9 PC. What version of NetworkManager are you using? You'll generally have to build latest NetworkManager along with the applet. I bet you've got svn4022.4 installed and you're trying to build trunk applet, which isn't going to work... Dan Whoops, you are right, I only have the version of NM that comes with Fedora, although I didn't know that the NM-Core and the NM-Applet were so tied with each other. But now I tried compiling the latest SVN NM-Core, and now I get this slight headache while running make:- nm-connection.c:27:28: error: dbus/dbus-glib.h: No such file or directory I have installed the required version of dbus-glib and the path in Makefile.in states:- DBUS_CFLAGS = /usr/local/include/dbus-1.0/dbus/ -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=2 -DDBUS_VERSION_MICRO=4 which I verified contains the DBUS header files. You also need to 'yum install dbus-glib-devel'. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hack to allow passing Vendor=nortel in network-manager-vpnc
On Mon, 2008-10-20 at 22:55 +0200, Cyril Jaquier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Sean, I have compiled the nortel branch of vpnc and can successfully connect to my corporate network. Is there a way I can use the vpnc network-manager plugin and pass the 'Vendor nortel' parameter? I tried manually editing the keys in gconf-editor, but that seems to crash nm. Wondering if there is a hack I can do to make the vendor persistent since I only connect to nortel vpn endpoints. Does it look to any config file for some default options or it is all controlled in gconf? The vendor option of vpnc is currently unsupported in the vpnc plugin :( Read this thread [1] for a similar issue with a Juniper/NetScreen firewall. Yeah, if we're going to do it, lets do it right rather than hack stuff together. If I just piled on all the hacks people want, we'd all be crushed under their weight by now :) Thus, the tradeoff between waiting a bit longer for your feature, and having it implemented more cleanly so that next year NM isn't a piece of crap. I do now have a Netscreen to test against, so you can expect that additional NM-vpnc features that I implement are tested against the Netscreen. Thus, this bug will probably get fixed sooner rather than later. Dan Regards, Cyril [1] http://mail.gnome.org/archives/networkmanager-list/2008-October/msg00072.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkj88EsACgkQlYy8cEwUMaQaxgCfYJhd0VRf7m/7SAlBvyUkF1bz GB0Ani6g90Qz+ZXEShW/8skKM87NJZAG =SW1A -END PGP SIGNATURE- ___ 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: Network-Manager applet r953 fails to compile.
On Tue, 2008-10-21 at 09:24 -0400, Dan Williams wrote: On Tue, 2008-10-21 at 15:04 +0530, Pramod Dematagoda wrote: On Mon, 2008-10-20 at 13:07 -0400, Dan Williams wrote: On Sat, 2008-10-18 at 19:13 +0530, Pramod Dematagoda wrote: I've just pulled r953 of network-manager-applet, however when I try to compile it I get the following errors from make:- gconf-helpers.c: In function 'write_one_secret_to_keyring': gconf-helpers.c:1254: error: 'NM_SETTING_VPN_SECRETS' undeclared (first use in this function) gconf-helpers.c:1254: error: (Each undeclared identifier is reported only once gconf-helpers.c:1254: error: for each function it appears in.) make[3]: *** [libgconf_helpers_la-gconf-helpers.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Is this something wrong with nm-applet itself or is there something I'm doing wrong here? This is on a Fedora 9 PC. What version of NetworkManager are you using? You'll generally have to build latest NetworkManager along with the applet. I bet you've got svn4022.4 installed and you're trying to build trunk applet, which isn't going to work... Dan Whoops, you are right, I only have the version of NM that comes with Fedora, although I didn't know that the NM-Core and the NM-Applet were so tied with each other. But now I tried compiling the latest SVN NM-Core, and now I get this slight headache while running make:- nm-connection.c:27:28: error: dbus/dbus-glib.h: No such file or directory I have installed the required version of dbus-glib and the path in Makefile.in states:- DBUS_CFLAGS = /usr/local/include/dbus-1.0/dbus/ -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=2 -DDBUS_VERSION_MICRO=4 which I verified contains the DBUS header files. You also need to 'yum install dbus-glib-devel'. Dan But that doesn't really work does it since the configure script is looking for dbus-glib = 0.75 whereas the version in Fedora 9 is 0.74. Now the thing is that I installed version 0.76 of dbus-glib manually into /usr/local, I pointed the DBUS_LIBS and DBUS_CFLAGS variables to the appropriate areas and that got the configure script happy, but it seems like the Makefile doesn't get it. Am I just doing this compile really wrong or something? Regards, Pramod Dematagoda ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 10:54 +0200, Craig Main wrote: On Tue, 2008-10-21 at 10:47 +0200, Per Hallsmark wrote: Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... My apologies, you are quite correct, it is a Dell Device: Bus 008 Device 004: ID 413c:8147 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x413c Dell Computer Corp. idProduct 0x8147 bcdDevice0.00 iManufacturer 1 Dell iProduct2 Dell Wireless 5530 HSPA Mobile Broadband Minicard Device The modem defaults to cfun=4 on startup, so one needs to issue a cfun=1 before using it to connect. You are also correct about ATF working. NM SVN since late september will power on the device with AT+CFUN=1 before trying to use it. NM SVN won't try to set the device off with CFUN=0 at all. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Dan Williams wrote: Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Ehm... not sure I agree... How many different type of broadband modems does NM/MM support? (note not rebranded but *different*...) /Per ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 15:48 +0200, Per Hallsmark wrote: Dan Williams wrote: Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Ehm... not sure I agree... How many different type of broadband modems does NM/MM support? (note not rebranded but *different*...) My main point with this is that the _entire_ flow is more standardized. You generally do not need extensive chat scripts, you don't have heavily customized PPP implementations or login methods based on provider, and you don't have every provider using a different network selection method for example. It used to be with 56k dialup that every single ISP had a different implementation of SLIP or PPP and required manual login, or custom login scripts to auth yourself, or some supported K56flex and others X2, etc. More direct hardware stuff will always be different, but overall the system is much simpler because everybody standardized everything else (ok, except Option with AT_OWANCALL...). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Dan Williams wrote: On Tue, 2008-10-21 at 15:48 +0200, Per Hallsmark wrote: Dan Williams wrote: Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Ehm... not sure I agree... How many different type of broadband modems does NM/MM support? (note not rebranded but *different*...) My main point with this is that the _entire_ flow is more standardized. You generally do not need extensive chat scripts, you don't have heavily customized PPP implementations or login methods based on provider, and you don't have every provider using a different network selection method for example. It used to be with 56k dialup that every single ISP had a different implementation of SLIP or PPP and required manual login, or custom login scripts to auth yourself, or some supported K56flex and others X2, etc. Ah, well then I agree also :-) More direct hardware stuff will always be different, but overall the system is much simpler because everybody standardized everything else (ok, except Option with AT_OWANCALL...). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager applet r953 fails to compile.
On Tue, 2008-10-21 at 09:52 -0400, Dan Williams wrote: On Tue, 2008-10-21 at 19:07 +0530, Pramod Dematagoda wrote: On Tue, 2008-10-21 at 09:24 -0400, Dan Williams wrote: On Tue, 2008-10-21 at 15:04 +0530, Pramod Dematagoda wrote: On Mon, 2008-10-20 at 13:07 -0400, Dan Williams wrote: On Sat, 2008-10-18 at 19:13 +0530, Pramod Dematagoda wrote: I've just pulled r953 of network-manager-applet, however when I try to compile it I get the following errors from make:- gconf-helpers.c: In function 'write_one_secret_to_keyring': gconf-helpers.c:1254: error: 'NM_SETTING_VPN_SECRETS' undeclared (first use in this function) gconf-helpers.c:1254: error: (Each undeclared identifier is reported only once gconf-helpers.c:1254: error: for each function it appears in.) make[3]: *** [libgconf_helpers_la-gconf-helpers.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Is this something wrong with nm-applet itself or is there something I'm doing wrong here? This is on a Fedora 9 PC. What version of NetworkManager are you using? You'll generally have to build latest NetworkManager along with the applet. I bet you've got svn4022.4 installed and you're trying to build trunk applet, which isn't going to work... Dan Whoops, you are right, I only have the version of NM that comes with Fedora, although I didn't know that the NM-Core and the NM-Applet were so tied with each other. But now I tried compiling the latest SVN NM-Core, and now I get this slight headache while running make:- nm-connection.c:27:28: error: dbus/dbus-glib.h: No such file or directory I have installed the required version of dbus-glib and the path in Makefile.in states:- DBUS_CFLAGS = /usr/local/include/dbus-1.0/dbus/ -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=2 -DDBUS_VERSION_MICRO=4 which I verified contains the DBUS header files. You also need to 'yum install dbus-glib-devel'. Dan But that doesn't really work does it since the configure script is looking for dbus-glib = 0.75 whereas the version in Fedora 9 is 0.74. Right. I've backported the necessary bits to Fedora 8 and 9's dbus-glib, so you can actually just change the NM configure script to allow anything = 0.74. Technically the required changes are only in dbus-glib 0.75 upstream, which is why upstream NM requires that version. But given that I backported the fixes to Fedora, I've also modified the Fedora rpm packages to build correctly for the distro. Dan Ah, I didn't know that. And I tried it out and it went past that problem properly. But now another headache :(. As it happens, I had to set the UUID_LIBS and UUID_CFLAGS variables manually as well because for some weird and unknown reason, they don't get set automatically. I have installed the uuid-devel package through the normal fedora repos. The new make error I get is:- nm-utils.c:38:23: error: uuid/uuid.h: No such file or directory Like the problem I had with d-bus. Sorry to keep bothering you about something this trivial, but I don't really know what to try next. Regards, Pramod Dematagoda ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager applet r953 fails to compile.
On Tue, 2008-10-21 at 19:39 +0530, Pramod Dematagoda wrote: On Tue, 2008-10-21 at 09:52 -0400, Dan Williams wrote: On Tue, 2008-10-21 at 19:07 +0530, Pramod Dematagoda wrote: On Tue, 2008-10-21 at 09:24 -0400, Dan Williams wrote: On Tue, 2008-10-21 at 15:04 +0530, Pramod Dematagoda wrote: On Mon, 2008-10-20 at 13:07 -0400, Dan Williams wrote: On Sat, 2008-10-18 at 19:13 +0530, Pramod Dematagoda wrote: I've just pulled r953 of network-manager-applet, however when I try to compile it I get the following errors from make:- gconf-helpers.c: In function 'write_one_secret_to_keyring': gconf-helpers.c:1254: error: 'NM_SETTING_VPN_SECRETS' undeclared (first use in this function) gconf-helpers.c:1254: error: (Each undeclared identifier is reported only once gconf-helpers.c:1254: error: for each function it appears in.) make[3]: *** [libgconf_helpers_la-gconf-helpers.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Is this something wrong with nm-applet itself or is there something I'm doing wrong here? This is on a Fedora 9 PC. What version of NetworkManager are you using? You'll generally have to build latest NetworkManager along with the applet. I bet you've got svn4022.4 installed and you're trying to build trunk applet, which isn't going to work... Dan Whoops, you are right, I only have the version of NM that comes with Fedora, although I didn't know that the NM-Core and the NM-Applet were so tied with each other. But now I tried compiling the latest SVN NM-Core, and now I get this slight headache while running make:- nm-connection.c:27:28: error: dbus/dbus-glib.h: No such file or directory I have installed the required version of dbus-glib and the path in Makefile.in states:- DBUS_CFLAGS = /usr/local/include/dbus-1.0/dbus/ -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=2 -DDBUS_VERSION_MICRO=4 which I verified contains the DBUS header files. You also need to 'yum install dbus-glib-devel'. Dan But that doesn't really work does it since the configure script is looking for dbus-glib = 0.75 whereas the version in Fedora 9 is 0.74. Right. I've backported the necessary bits to Fedora 8 and 9's dbus-glib, so you can actually just change the NM configure script to allow anything = 0.74. Technically the required changes are only in dbus-glib 0.75 upstream, which is why upstream NM requires that version. But given that I backported the fixes to Fedora, I've also modified the Fedora rpm packages to build correctly for the distro. Dan Ah, I didn't know that. And I tried it out and it went past that problem properly. But now another headache :(. As it happens, I had to set the UUID_LIBS and UUID_CFLAGS variables manually as well because for some weird and unknown reason, they don't get set automatically. I have installed the uuid-devel package through the normal fedora repos. The new make error I get is:- nm-utils.c:38:23: error: uuid/uuid.h: No such file or directory No problem. To get the deps solved, you can use the existing NetworkManager srpm as a guide. Grab that: http://koji.fedoraproject.org/packages/NetworkManager/0.7.0/0.11.svn4022.4.fc9/src/NetworkManager-0.7.0-0.11.svn4022.4.fc9.src.rpm and make sure you: yum install rpm-build then: rpm -Uhv NetworkManager-0.7.0-0.11.svn4022.4.fc9.src.rpm Next: cd /usr/src/redhat/SPECS rpmbuild -ba --target i386 NetworkManager.spec Then, it'll complain about packages that haven't been installed. yum install all of those. Then you should have all the required dependencies like e2fsprogs-devel, in which libuuid dev files live. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager applet r953 fails to compile.
On Tue, Oct 21, 2008 at 09:52:54AM -0400, Dan Williams wrote: On Tue, 2008-10-21 at 19:07 +0530, Pramod Dematagoda wrote: But that doesn't really work does it since the configure script is looking for dbus-glib = 0.75 whereas the version in Fedora 9 is 0.74. Right. I've backported the necessary bits to Fedora 8 and 9's dbus-glib, so you can actually just change the NM configure script to allow anything = 0.74. Technically the required changes are only in dbus-glib 0.75 upstream, which is why upstream NM requires that version. But given that I backported the fixes to Fedora, I've also modified the Fedora rpm packages to build correctly for the distro. No strong opinion, but neither sure if we really want to have this in the main tree. If we put it here, we most likely will get recurring support requests from folks that have old dbus-glib installed on other distros and run into issues with their self-baked NM build. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager applet r953 fails to compile.
On Tue, 2008-10-21 at 16:55 +0200, Alexander Sack wrote: On Tue, Oct 21, 2008 at 09:52:54AM -0400, Dan Williams wrote: On Tue, 2008-10-21 at 19:07 +0530, Pramod Dematagoda wrote: But that doesn't really work does it since the configure script is looking for dbus-glib = 0.75 whereas the version in Fedora 9 is 0.74. Right. I've backported the necessary bits to Fedora 8 and 9's dbus-glib, so you can actually just change the NM configure script to allow anything = 0.74. Technically the required changes are only in dbus-glib 0.75 upstream, which is why upstream NM requires that version. But given that I backported the fixes to Fedora, I've also modified the Fedora rpm packages to build correctly for the distro. No strong opinion, but neither sure if we really want to have this in the main tree. If we put it here, we most likely will get recurring support requests from folks that have old dbus-glib installed on other distros and run into issues with their self-baked NM build. Upstream NM should _always_ require the actual released version of its dependencies that contain the features that NM needs. Upstream needs to be pristine. But since distros don't always use the released bits (but backport stuff) it's up to the discretion of the distro to adjust the configure.ac requirements to match their distros libraries. Thus, upstream requires 0.75 which actually contains the required functionality, but since I backported the dbus-glib fixes to Fedora, I've locally patched Fedora's NM to know about this. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
-Original Message- From: Tambet Ingo [mailto:[EMAIL PROTECTED] Sent: Tue 10/21/2008 11:19 AM To: Per Hallsmark Cc: Main, Craig; networkmanager-list@gnome.org Subject: Re: Mobile Broadband - how do I trace/debug the modem initialisation? On Tue, Oct 21, 2008 at 12:14 PM, Per Hallsmark [EMAIL PROTECTED] wrote: Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) I committed your patches from last week yesterday. Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) Yeah, it's probably a good idea. Overriding the whole Enable() is a bit too much work if you only need to use a different init string. I'll have that later today. Don't know if this will help... I patched the version that comes with Ubuntu Intrepid (0.7~~svn20081018t105859-0ubuntu1) and replaced all ATZ commands with ATF. This time things got further, here is the output from the debug trace NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224608780.039115] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224608780.142898] nm_serial_debug(): Sending: 'ATF E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224608780.172375] nm_serial_debug(): Got: 'ATF E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224608780.201187] nm_serial_debug(): Got: 'ATF E0 V1 X4 C1 +FCLASS=0 OK ' NetworkManager: debug [1224608780.201297] nm_serial_debug(): Sending: 'AT+CPIN? ' NetworkManager: debug [1224608780.216403] nm_serial_debug(): Got: ' +CPIN: READY ' NetworkManager: debug [1224608780.218096] nm_serial_debug(): Got: ' +CPIN: READY OK ' NetworkManager: info (ttyACM0): powering up... NetworkManager: debug [1224608780.218226] nm_serial_debug(): Sending: 'AT+CFUN=1 ' NetworkManager: debug [1224608780.231653] nm_serial_debug(): Got: ' OK ' NetworkManager: debug [1224608780.231737] nm_serial_debug(): Sending: 'AT+CREG? ' NetworkManager: debug [1224608780.246281] nm_serial_debug(): Got: ' +CREG: 0,1 ' NetworkManager: debug [1224608780.247648] nm_serial_debug(): Got: ' +CREG: 0,1 OK ' NetworkManager: info Registered on Home network NetworkManager: debug [1224608780.247765] nm_serial_debug(): Sending: 'AT+COPS? ' NetworkManager: debug [1224608780.355308] nm_serial_debug(): Got: ' +COPS: 0,0,VodaCom,2 ' NetworkManager: debug [1224608780.356733] nm_serial_debug(): Got: ' +COPS: 0,0,VodaCom,2 OK ' NetworkManager: info Associated with network: +COPS: 0,0,VodaCom,2 NetworkManager: debug [1224608780.356885] nm_serial_debug(): Sending: 'AT+CGDCONT=1, IP, internet ' NetworkManager: debug [1224608780.429051] nm_serial_debug(): Got: ' OK ' NetworkManager: debug [1224608780.429255] nm_serial_debug(): Sending: 'ATD*99***1# ' NetworkManager: debug [1224608780.474146] nm_serial_debug(): Got: '~' NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: WARN dial_done(): Dialing timed out NetworkManager: info (ttyACM0): device state change: 4 - 9 NetworkManager: debug [1224608841.000446] nm_serial_device_close(): Closing device 'ttyACM0' NetworkManager: info Marking connection 'Vodacom' invalid. NetworkManager: info Activation (ttyACM0) failed. NetworkManager: info (ttyACM0): device state change: 9 - 3 NetworkManager: info (ttyACM0): deactivating device (reason: 0). This looks much more promising, but there still seems to be an issue when it tries to dial. Here is the trace of my wvdial exchange that works... [EMAIL PROTECTED]:~$ wvdial 5530 -- Ignoring malformed input line: aler Defaults] -- WvDial: Internet dialer version 1.60 -- Cannot get information for serial port. -- Initializing modem. -- Sending: AT AT OK -- Sending: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 OK -- Modem initialized.
laptop - ethernet up on login in KDE network manager
Hi, I'm having a strange problem, everytime I log on to kde desltop, my nm-applet tries to connect and eventually tells me it is connected through eth0 however I cant browse. Every time I want to use my ethernet card I need to login as root and go to system-config-network to reactivate my ethernet card to get browsing going. This is annoying. How do I enable my ethernet card get connected whenever I plugin the rj45 jack. Please help! -- Regards, K M Nur Tech Blogs Schedules: http://k-linuxtechs.blogspot.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 19:16 +0200, Main, Craig wrote: -Original Message- From: Tambet Ingo [mailto:[EMAIL PROTECTED] Sent: Tue 10/21/2008 11:19 AM To: Per Hallsmark Cc: Main, Craig; networkmanager-list@gnome.org Subject: Re: Mobile Broadband - how do I trace/debug the modem initialisation? On Tue, Oct 21, 2008 at 12:14 PM, Per Hallsmark [EMAIL PROTECTED] wrote: Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) I committed your patches from last week yesterday. Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) Yeah, it's probably a good idea. Overriding the whole Enable() is a bit too much work if you only need to use a different init string. I'll have that later today. Don't know if this will help... I patched the version that comes with Ubuntu Intrepid (0.7~~svn20081018t105859-0ubuntu1) and replaced all ATZ commands with ATF. This time things got further, here is the output from the debug trace ... This looks much more promising, but there still seems to be an issue when it tries to dial. Here is the trace of my wvdial exchange that works... [EMAIL PROTECTED]:~$ wvdial 5530 -- Ignoring malformed input line: aler Defaults] -- WvDial: Internet dialer version 1.60 -- Cannot get information for serial port. -- Initializing modem. -- Sending: AT AT OK -- Sending: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 OK -- Modem initialized. -- Sending: ATDT*99***1# -- Waiting for carrier. ATDT*99***1# [EMAIL PROTECTED] }9}#}%B#}%}(}}' } } } }%}mG!;J[1d]~ Holy crap, WTF is that??? I know you don't know, but wow. That can't be a valid standards-compliant implementation. Dan CONNECT -- Carrier detected. Waiting for prompt. [EMAIL PROTECTED]} }9}#}%B#}%}(}}' } } } }%}mG!;[06]p~ -- PPP negotiation detected. -- Starting pppd at Tue Oct 21 19:10:07 2008 -- Warning: Could not modify /etc/ppp/pap-secrets: Permission denied -- -- PAP (Password Authentication Protocol) may be flaky. -- Warning: Could not modify /etc/ppp/chap-secrets: Permission denied -- -- CHAP (Challenge Handshake) may be flaky. -- Pid of pppd: 27901 Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ 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: laptop - ethernet up on login in KDE network manager
On Wed, 2008-10-22 at 00:05 +0600, K M Nur wrote: Hi, I'm having a strange problem, everytime I log on to kde desltop, my nm-applet tries to connect and eventually tells me it is connected through eth0 however I cant browse. Every time I want to use my ethernet card I need to login as root and go to system-config-network to reactivate my ethernet card to get browsing going. This is annoying. How do I enable my ethernet card get connected whenever I plugin the rj45 jack. Please help! Do you use static IP or DHCP for your wired connection? Do the settings in system-config-network match what's shown in the connection editor for your connection? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: issues with new wpa adhoc fixes
On Tue, 2008-10-21 at 09:26 -0400, Dan Williams wrote: On Tue, 2008-10-21 at 08:26 +0200, Björn Martensen wrote: Hi, I tried the adhoc wpa fixes from yesterday and found some issues: Can you try with svn r4200? There were a few unrelated issues that I fixed last night/this morning that could help out some of the issues here. it definately works better now, but still has some problems. 1. applet still shows all grey bars, another icon might be better here. 2. the first time i create the connection, the radio button in the applet's list isn't selected. none is. when i connect to my home network and back to the adhoc, it's selected. 3. say i connected to my home wifi automatically after session login. now i create a new adhoc network (select it from the list, as i created it before already), and connect to the home network again. now i switch to the adhoc network again by using the create option again. this works fine. now i am connected to the adhoc network and select it in the applet's list again, sometimes the daemon crashes and sometimes i just get disconnected so i auto-connect to the home network again. i'll try to figure out what action exactly is crashing the daemon as it was pretty random, but i managed to get the crash 3 times now, so it is there ;) Also, what kernel and wpa_supplicant version are you using? They greatly affect whether you can create adhoc networks at all. kernel 2.6.27.1, iwl3945 and wpa_supplicant 0.6.4 Dan - i am connected to my wpa2 wifi network - i create a new wpa/wpa2 adhoc connection when the connection should be established, nm dies and i have to restart /etc/rc.d/networkmanager. - when it has restarted, i connect to my home wifi, then switch to the adhoc i was trying to create (selecting it from the list this time). - i get connected to the adhoc connection, nm-applet shows the signal strenght at 0, i.e. all grey bars. - i try to switch back to the home wifi connection, but when i should get connected, nm just always disconnects completely. again, restarting the daemon fixes this, as above (although it hasn't crashed this time). after restarting it, i can connect to the home wifi network again. greets, Björn ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list 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: issues with new wpa adhoc fixes
tried again, here some results: start nm * auto to home network * create new adhoc * from list * message to be connected, crash * same name, same pass, but re-entered it * message to be connected, crash * new connection name * grey bars * no radio focus * connected * select the connection from the list again * crash * select another existing wpa2 adhoc * message to be connected to that connection * connection fails * autoconnected to home network * select that same adhoc again from the create-list * crash 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: wpa_supplicant cli works, but NM insists wireless is disabled
On Tue, 2008-09-30 at 16:27 -0400, Andrew wrote: On Tue, 2008-09-30 at 15:18 -0400, Andrew wrote: On Tue, 2008-09-30 at 12:22 -0400, Andrew wrote: On Tue, 2008-09-30 at 06:30 -0400, Andrew wrote: On Mon, 2008-09-29 at 18:44 -0400, Andrew wrote: On Sun, 2008-09-28 at 19:21 -0400, Andrew wrote: Hello, I have appealed to the Fedora Forum, but no one seems to have a clue there. Here is the thread: http://forums.fedoraforum.org/showthread.php?t=199562 (A quick synopsis of the thread: I've activated/deactivated everything i could think of, related to NetworkManager; yet, everything wireless is grayed out in the applet. But wpa_supplicant (cli) works! Additional info (beyond above thread): I compiled the latest NetworkManager svn; still same grayed out behavior. ) I tried looking in the source and tracing the calls to and from nm_client_wireless_get_enabled (if that's even a function) but, ignorant of C, didn't get far. Please help! Does NM think wireless is disabled because a HAL killswitch is reporting Don't know enough about HAL to answer the above. (Where would i look?) that it's off? Could you post some logs from /var/log/messages from when NM starts up? please see attachment. (i've X'ed out some addresses (::) ooops. The list strips attachment. Here is a web link to the same /var/log/messages chunk: http://www.flight.us/bugs/var_messages_nm_chunk.txt What's the output of: dellWirelessCtl Here it is: http://www.flight.us/bugs/dellWirelessCtl.txt OK, it appears that the problem(?) /does/ originate in the BIOS (I did present this hypothesis at the Fedora forum, but no one took that path, which now seems correct) Yeah, if dellWirelessCtl says the WLAN is disabled, then that's what the BIOS thinks. The best thing I think you could do is file a bug against 'libsmbios' package in Fedora bugzilla and the Dell guys will try to help you debug. Yes, of course, my **internal** wifi card /is/ disabled in the BIOS! (You may not have read my FedoraForum thread) dellWirelessCtl is reporting correctly regarding the internal card (only). But why should this concern the external, removable cards?? Because you've flipped the kill my wireless button. If you didn't want to kill your wireless, don't flip the button. It's a decision to treat any killswitch as killing all wireless devices of the same class. I don't believe it's useful to have individual killswitches apply to individual devices of the same class. I certainly did not intentionally disable _ALL_ wifi devices; only the onboard one is disabled. You flipped the kill my wireless switch which NetworkManager (by design) takes as the sign you wish to disable all your wireless devices. So, why does wpa_supplicant see my external wifi device (wlanX), and use and connect with it happily, inspite of this killswitch? Because the kernel rfkill layer isn't completely integrated yet and thus its not actually getting killed, though NM should be setting the device's TX power off. Does anyone know where in the NM code is the querying of the status at issue? I would like to play with the code. (perhaps in src/nm-hal-manager.c ? There seems to be a kswitch_err method) That's the right place, but upstream isn't going to accept that code at this time. It's a policy decision; I made the decision to keep things simple and direct and interpret the user's intent as disabling wireless when the rfkill switch is turned on. Dan, even if I were some sort of C and networking guru and veteran member of your development team, still i would not seek to impose any modifications to your code. (And I am light years away from all the above) (I say this in response to your mentioning upstream -- a word i've not heard before but assume has something to do with committing code changes for general use). Your generous contribution of skill has made things easier for millions. However, could you please provide a quick hack to meet my rare need, to keep my wifi class always enabled, regardless of what the BIOS is reporting? It would be confined to my system strictly. You could simply not schedule killswitch checks by commenting this code in src/nm-hal-manager.c out: /* Poll switches if this is the first switch we've found */ if (!priv-killswitch_list) priv-killswitch_poll_id = g_idle_add (poll_killswitches, self); Dan Would be extremely grateful! Andrew Dan TIA andrew Dan Why should NetworkManager
static ip and kppp
I use static ip. I need to use static ip at my office however I do need to use kppp for my gprs connection when I'm mobile. Please help. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
--On Tuesday, October 21, 2008 09:21:36 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ Inelegant though it is, i think NM does need a way to define custom ¦ init ( de-init?) strings externally. This has been the bane of ¦ ¦ God no. It's like adding text boxes for arbitrary command line ¦ arguments for openvpn. How are you supposed to know what goes in there? ¦ Do you just google around and find something that some random user ¦ reported worked for them and then try it? Or if that doesn't work try ¦ something else? Then you've just wasted 4 hours for something that ¦ should Just Work. We don't need to do this, because most of the ¦ differences between hardware can be handled with quirks. Adding an ¦ arbitrary enter some command strings means you've completely lost. ¦ Mobile broadband parts are a lot more standardized than ¦ Hayes-compatible modems. i'm not saying it should be an up-front configuration for the user, but neither should it be embedded in C source. I agree that the general protocol has been well-established, but there are clearly issues with initialisation, as this thread has shown (for 2 cases). Even if these cases are dealt with in source, what happens when a future modem needs something else a bit different? Do you change the init string in source, then regression test against every modem that worked before to make sure nothing's broken, then wait for it to be pushed out to the different distros? It seems to me an external resource file, pre-built for all known cases, but editable by expert users and/or quickly updateable independently of the whole package, is much more maintainable. It's how I'd do it anyway ... Cheers, Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
--On Tuesday, October 21, 2008 14:08:25 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ On Tue, 2008-10-21 at 19:16 +0200, Main, Craig wrote: .. ¦ -- Modem initialized. ¦ -- Sending: ATDT*99***1# ¦ -- Waiting for carrier. ¦ ATDT*99***1# ¦ [EMAIL PROTECTED] }9}#}%B#}%}(}}' } } } }%}mG!;J[1d]~ ¦ ¦ Holy crap, WTF is that??? I know you don't know, but wow. That can't ¦ be a valid standards-compliant implementation. AFAIK that's the PPP negotiation. If you manually open a connection to any PPP wserver with minicom or equiv. that stuff comes back. Usually the modem returns CONNECT first, and the device is handed over to the PPP code so this doesn't get traced, but here CONNECT comes later, and then we see that PPP is correctly detected: ¦ CONNECT ¦ -- Carrier detected. Waiting for prompt. ¦ [EMAIL PROTECTED]} }9}#}%B#}%}(}}' } } } }%}mG!;[06]p~ ¦ -- PPP negotiation detected. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant cli works, but NM insists wireless is disabled
However, could you please provide a quick hack to meet my rare need, to keep my wifi class always enabled, regardless of what the BIOS is reporting? It would be confined to my system strictly. You could simply not schedule killswitch checks by commenting this code in src/nm-hal-manager.c out: /* Poll switches if this is the first switch we've found */ if (!priv-killswitch_list) priv-killswitch_poll_id = g_idle_add (poll_killswitches, self); That did it! Forever grateful. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
stupid question - duplicated list ?
this may have been addressed before, but my googling has been fruitless. Why does the dropdown list from nm-applet have all the available networks duplicated? (first the list, then its copy?) I have installed/upgraded to about 10 diffent Fedora 9 systems, and in every one I had the duplication phenomenon. How does one get rid of the duplicate? thanks andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Required libdbus-dlib-1-dev version 0.75
Hi, I'm trying to setup my environment to develop a bit on Network-Manager. I'm motivated to improve the VPN pptp module. When executing ./autogen.sh, it's required libdbus-dlib-1-dev = 0.75. I have Ubuntu hardy and got version 0.74. Where can I get the newer version ? Regards, Patrik Dufresne ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Saving only the group password in keyring
Dan, I finally got something together, following some of the ideas you pointed out. I've also done a slight change to the auth dialog to not show the passwords that are already known in the keyring, unless it's in a reprompt situation (although I haven't been able to test it without manually calling nm-vpnc-auth-dialog...), and to always prompt for a password that is marked as otp although it may already be saved in the keyring. It's a pretty crude patch, I realize it will need some rework, but if someone could test it out and let me know what parts to look at.. :) Right now, I really don't think the unused cases work properly, but I'm still looking into it -- I just don't have an easy way to test that case. Patch is attached, one gziped file and one .patch: 01-password-types.patch.gz 01-vpnc-auth-password-types.patch / Matt On Sun, Oct 12, 2008 at 10:04 PM, Dan Williams [EMAIL PROTECTED] wrote: On Sat, 2008-10-11 at 11:22 -0400, Mathieu Trudel-Lapierre wrote: Dan, Actually one other little question. How much use do you think there is for this kind of feature? Do you regularly hear about this, or is it more a user here and there? There are open bug reports for both of these and I've heard about interactive auth mode and hybrid auth support from a number of people. It was certainly on my list to do when I had the time. But hey, if patches show up first... :) Dan / Matt On Thu, Oct 9, 2008 at 12:05 PM, Dan Williams [EMAIL PROTECTED] wrote: On Thu, 2008-10-09 at 09:15 -0400, Mathieu Trudel-Lapierre wrote: Hi, First, my apologies for pushing for this, since I believe the interested parties are probably already notified through bugzilla on this... So the reason this didn't get merged in the first place is that when this is used, the auth dialog looks like ass. Having _3_ buttons there has confused every user I've ever seen, and makes me read things a few times whenever I get the dialog. It's just bad UI. Plus, it's not something you can change in the connection editor out-of-band from authentication. That's not to say it doesn't fill a need and fix the bug, but the solution is not one I'd like to have upstream. Instead, we need a better solution. We have two passwords, the user password and the group password. Each password has 3 different types: u s e r | static | unused | OTP --|--|--|-- g static| Y|Y | Y r --|--|--|-- o unused| Y|X | ? u --|--|--|-- p OTP | Y|Y | ? --|--|--|-- Legend: Y = I've heard of it being used X = Pointless ? = I don't know if this is used by anyone The cases where you don't want to save passwords in the keyring are the OTP/RSA and the unused cases. Here's my solution: for each of the group and user password entries, have a small popup menu behind each on in the main config dialog like so: .. .. User Password: | i4mvrl1337^% | | Default |V| `' `' .. .. Group Password: | my-GrOuP-PassWORD | | Default |V| `' `' Where the combo box has the following items: Default (ie, static password that rarely changes) Interactive (ie, RSA dongles) Unused (ie, no password required and nothing saved to keyring) It always defaults to Default (ie, static) so most peoples configs will work, but you have to option to change it for your config. Note that Interactive authentication can't be used yet anyway because we don't support challenge-based authentication that it requires, which will come after 0.7 when I can rework the VPN cleanup patch I've talked about before, and will require If somebody came up with the UI patch to do this, that would be awesome and I'd commit it. It would additionally mean adding two keys to the vpnc plugin's GConf data (user-password-type and group-password-type) which would then have to be added to the nm-vpnc-service's validation code and used internally if required, but that's pretty easy. These keys would store the password type (as a string) so that the auth dialog would know when to save which passwords and which password entry widgets to disable/desensitize when the user had selected unused. Thoughts? Next, we get to add authentication types to the client to support Hybrid Auth mode. Not sure if you can use all the normal Xauth stuff (like interactive) with the hybrid auth mode as well, but I have to assume you can. Dan -- Mathieu Trudel [EMAIL PROTECTED] 01-password-types.patch.gz Description: GNU Zip compressed data
