Changing Default APNs for 3G Operators?
Hey All, I'm in Ericsson Ltd, and we work closely with 3G Operators in areas of HSDPA modem testing. We test our modems with NetworkManager, and one of the observations we have is that the APNs for some operators (especially the one we test with - Hutchison 3G) are not current. Operator is quite concerned, because in the long run, IF the old APNs are made inactive, it'll affect Linux Modem users majorly. Any idea who I can get in touch with/what the process is for getting this issue sorted in the next release of NetworkManager? --Shriansh Shrivastava Ericsson Ltd. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
PEAP CA certificate error
Hello- I'm attempting to connect to a PEAP and msCHAPv2 network using network manager 0.7 (openSUSE 11.1). The wpa_supplicant.log file is showing that the verification of the certificate is failing but I'm unclear how to overcome this. The IS group has Windows machines not checking the validity of the certificate; I presume because it's broken or expired. Can anyone offer suggestions on how I can around the error on my Linux laptop and connect? Many thanks in advance, Jon wpa_supplicant.log Output: CTRL-EVENT-SCAN-RESULTS Trying to associate with 00:11:22:33:44:55 (SSID='thessid' freq=2462 MHz) Associated with 00:11:22:33:44:55 CTRL-EVENT-EAP-STARTED EAP authentication started CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected TLS: Certificate verification failed, error 20 (unable to get local issuer certificate) depth0 for '/CN=ca.domain.com' SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed CTRL-EVENT-EAP-FAILURE EAP authentication failed CTRL-EVENT-EAP-STARTED EAP authentication started CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected TLS: Certificate verification failed, error 20 (unable to get local issuer certificate) depth0 for '/CN=ca.domain.com' SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed CTRL-EVENT-EAP-FAILURE EAP authentication failed CTRL-EVENT-EAP-STARTED EAP authentication started CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected TLS: Certificate verification failed, error 20 (unable to get local issuer certificate) depth0 for '/CN=ca.domain.com' SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed CTRL-EVENT-EAP-FAILURE EAP authentication failed CTRL-EVENT-EAP-STARTED EAP authentication started CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected TLS: Certificate verification failed, error 20 (unable to get local issuer certificate) depth0 for '/CN=ca.domain.com' SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed CTRL-EVENT-EAP-FAILURE EAP authentication failed CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM DBus API
Hi! Where can I find the docs for the NM DBus API? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
specifications
Where could I get network-manager 0.7 dbus specifications? The link on website is broken. Is there a list of specifications diif from 0.6 to 0.7? I have to update my software so it supports network-manager 0.7. Thanks -- Yann ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Detection for ZTE AC8700 usb modem - provider BSNL India
Hi, I have just tested this patch (not patch actually ;)) with the same BSNL provided ZTE AC8700 evdo modem. I need to change it by adding product id `0x6000`. So my 10-modem.fdi has... !-- BSNL -- match key=@info.parent:usb.vendor_id int=0x5c6 !-- ZTE EVDO AC8700 -- match key=@info.parent:usb.product_id int_outof=0x3197;0x6000 match key=@info.parent:usb.interface.number int=0 append key=modem.command_sets type=strlistIS-707-A/append /match /match /match Thanks Chetan for work... Regards -- Amit Chetan S wrote: Hi, Could you please add the following entry to hal-info for the BSNL usb modem for EVDO broadband ? The make of the modem is ZTE AC8700. file : 10-modem.fdi Content to be put after !--Novatel-- entry. !-- BSNL -- match key=@info.parent:usb.vendor_id int=0x5c6 !-- ZTE EVDO AC8700 -- match key=@info.parent:usb.product_id int_outof=0x3197 match key=@info.parent:usb.interface.number int=0 append key=modem.command_sets type=strlistIS-707-A/append /match /match /match Do let me know if you need a patch. It currently works. I can request more tests via LUG groups if you need, however I am sure it'll work :) regards, Chetan Shringarpure ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- View this message in context: http://www.nabble.com/Detection-for-ZTE-AC8700-usb-modem---provider-BSNL-India-tp21086309p21182724.html Sent from the Gnome - NetworkManager mailing list archive at Nabble.com. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: specifications
On Mon, Jan 05, 2009 at 12:58:39PM +0200, Tambet Ingo wrote: On Sun, Jan 4, 2009 at 13:02, Yann Leboulanger aste...@lagaule.org wrote: Where could I get network-manager 0.7 dbus specifications? The link on website is broken. I assume Yann means http://projects.gnome.org/NetworkManager/developers/spec.html on http://projects.gnome.org/NetworkManager/developers/ Is there a list of specifications diif from 0.6 to 0.7? I have to update my software so it supports network-manager 0.7. Download NetworkManager sources, run configure with '--with-docs' flag and then run make. That'll create the DBus API documentation file docs/spec.html. People *using* NM, even as an API, should not need to run ./configure. I have updated http://live.gnome.org/NetworkManagerDBusInterface with the released 0.7 specs. Please link to it from or put a copy to a more official place (like the 1st URL above). -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: specifications
On Sun, Jan 4, 2009 at 13:02, Yann Leboulanger aste...@lagaule.org wrote: Where could I get network-manager 0.7 dbus specifications? The link on website is broken. Is there a list of specifications diif from 0.6 to 0.7? I have to update my software so it supports network-manager 0.7. Download NetworkManager sources, run configure with '--with-docs' flag and then run make. That'll create the DBus API documentation file docs/spec.html. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM DBus API
On Thu, Jan 1, 2009 at 00:24, Gabriel Joel Perez gabrielj...@gmail.com wrote: Hi! Where can I find the docs for the NM DBus API? Download NetworkManager sources, run configure with '--with-docs' flag and then run make. That'll create the DBus API documentation file docs/spec.html. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Mobile broadband connects to wrong USB device
Hello, I have a Dell Mini which uses a 5530 mobile wireless card. This works fine with wvdial etc. When I try to add a new wireless broadband connection using Network Manager, I select Vodafone (as they are the provider), and then when I try to connect to it, I can see in the top right where the Network Manager icon is trying to connect, if I move my mouse over it I can see that it says it's trying to connect to USB0, however the wireless card is actually using USB4. So, my question is, how can I get behind the scenes of the new network connection to make it try to connect to USB4 (/dev/ttyUSB4) instead of USB0? There doesn't seem to be anything of interest in my ~/.gconf/* dirs. Thanks, Ben. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
On Tue, 2009-01-06 at 11:27 +1100, Ben wrote: Hello, I have a Dell Mini which uses a 5530 mobile wireless card. This works fine with wvdial etc. When I try to add a new wireless broadband connection using Network Manager, I select Vodafone (as they are the provider), and then when I try to connect to it, I can see in the top right where the Network Manager icon is trying to connect, if I move my mouse over it I can see that it says it's trying to connect to USB0, however the wireless card is actually using USB4. So, my question is, how can I get behind the scenes of the new network connection to make it try to connect to USB4 (/dev/ttyUSB4) instead of USB0? There doesn't seem to be anything of interest in my ~/.gconf/* dirs. So this would be a problem in the Hal entry for your modem. /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi I have attached one that should fix it. Can you copy it over the one you have (back yours up first) and reboot your system. See if it works. I see that what is in there now it's going to try ttyUSB0. This probably needs to be changed. Once you have tested it, I will submit the fix upstream. Thanks, Ben. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list 10-modem.fdi Description: XML document 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 connects to wrong USB device
Actually try the one I have here. The one in my last email didn't have the comment correctly. copy over /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi Jerone On Mon, 2009-01-05 at 18:48 -0600, Jerone Young wrote: that what is in there now it's going to try ttyUSB0. This probably needs to be changed. Once you have tested it, I will submit the fix upstream. Thanks, Ben. 10-modem.fdi Description: XML document 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 connects to wrong USB device
Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
Ok I might have screwed it up. You can hack your local copy easily though. First back it up. Then edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi line 334 You will see match key=@info.parent:usb.interface.number int=0 Change this to match key=@info.parent:usb.interface.number int=4 Let us know if that works. On Tue, 2009-01-06 at 12:24 +1100, Ben wrote: Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: 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 connects to wrong USB device
Hmmm no if I change the int to a 4 and reboot, it tries to connect but about half a second later it instantly connects back to what it had originally connected to (LAN or whatever). There is nothing in the log (/var/log/messages) about what it's doing so it's hard to say. But if I set int to be 3 for example and then connect, it says it's trying to dial ttyUSB3, so setting it to 4 I am assuming it is trying to connect to ttyUSB4. Any other suggestions? Is there any other place where it could be logging failed attempts? I read somewhere that it could put info in /var/log/networkmanager but I don't have that file. Thanks for the help. Jerone Young wrote: Ok I might have screwed it up. You can hack your local copy easily though. First back it up. Then edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi line 334 You will see match key=@info.parent:usb.interface.number int=0 Change this to match key=@info.parent:usb.interface.number int=4 Let us know if that works. On Tue, 2009-01-06 at 12:24 +1100, Ben wrote: Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
You can look in /var/log/daemon.log. You can also run Network Manager in debug mode (as root): 1) /etc/init.d/network-manager stop 2) NetworkManager --no-daemon You will see debug message in the Window. On Tue, 2009-01-06 at 13:36 +1100, Ben wrote: Hmmm no if I change the int to a 4 and reboot, it tries to connect but about half a second later it instantly connects back to what it had originally connected to (LAN or whatever). There is nothing in the log (/var/log/messages) about what it's doing so it's hard to say. But if I set int to be 3 for example and then connect, it says it's trying to dial ttyUSB3, so setting it to 4 I am assuming it is trying to connect to ttyUSB4. Any other suggestions? Is there any other place where it could be logging failed attempts? I read somewhere that it could put info in /var/log/networkmanager but I don't have that file. Thanks for the help. Jerone Young wrote: Ok I might have screwed it up. You can hack your local copy easily though. First back it up. Then edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi line 334 You will see match key=@info.parent:usb.interface.number int=0 Change this to match key=@info.parent:usb.interface.number int=4 Let us know if that works. On Tue, 2009-01-06 at 12:24 +1100, Ben wrote: Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: 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 connects to wrong USB device
Ahh OK thanks. Here is the output when I select the connection: NetworkManager: info Activation (ttyUSB4) starting connection 'Vodafone' NetworkManager: info (ttyUSB4): device state change: 3 - 4 NetworkManager: info Activation (ttyUSB4) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyUSB4) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1231210578.256890] nm_serial_device_open(): (ttyUSB4) opening device... NetworkManager: info Activation (ttyUSB4) Stage 1 of 5 (Device Prepare) complete. NetworkManager: WARN init_done(): Modem initialization failed NetworkManager: info (ttyUSB4): device state change: 4 - 9 NetworkManager: debug [1231210578.418451] nm_serial_device_close(): Closing device 'ttyUSB4' NetworkManager: info Marking connection 'Vodafone' invalid. NetworkManager: info Activation (ttyUSB4) failed. NetworkManager: info (ttyUSB4): device state change: 9 - 3 NetworkManager: info (ttyUSB4): deactivating device (reason: 0). NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx = 0' failed NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx = 0' failed Is it possible that it's trying to open ttyUSB4 instead of /dev/ttyUSB4 ? Jerone Young wrote: You can look in /var/log/daemon.log. You can also run Network Manager in debug mode (as root): 1) /etc/init.d/network-manager stop 2) NetworkManager --no-daemon You will see debug message in the Window. On Tue, 2009-01-06 at 13:36 +1100, Ben wrote: Hmmm no if I change the int to a 4 and reboot, it tries to connect but about half a second later it instantly connects back to what it had originally connected to (LAN or whatever). There is nothing in the log (/var/log/messages) about what it's doing so it's hard to say. But if I set int to be 3 for example and then connect, it says it's trying to dial ttyUSB3, so setting it to 4 I am assuming it is trying to connect to ttyUSB4. Any other suggestions? Is there any other place where it could be logging failed attempts? I read somewhere that it could put info in /var/log/networkmanager but I don't have that file. Thanks for the help. Jerone Young wrote: Ok I might have screwed it up. You can hack your local copy easily though. First back it up. Then edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi line 334 You will see match key=@info.parent:usb.interface.number int=0 Change this to match key=@info.parent:usb.interface.number int=4 Let us know if that works. On Tue, 2009-01-06 at 12:24 +1100, Ben wrote: Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
Is there a way to change the init string? When I run: NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon I can see that it's trying to send an init string that is different to the one that I'm using in my /etc/wvdial.conf file. Then, an error gets returned saying that it couldn't initialise the modem. I'm pretty sure that if I change this init string in NetworkManager that it will work. Ben. Jerone Young wrote: You can look in /var/log/daemon.log. You can also run Network Manager in debug mode (as root): 1) /etc/init.d/network-manager stop 2) NetworkManager --no-daemon You will see debug message in the Window. On Tue, 2009-01-06 at 13:36 +1100, Ben wrote: Hmmm no if I change the int to a 4 and reboot, it tries to connect but about half a second later it instantly connects back to what it had originally connected to (LAN or whatever). There is nothing in the log (/var/log/messages) about what it's doing so it's hard to say. But if I set int to be 3 for example and then connect, it says it's trying to dial ttyUSB3, so setting it to 4 I am assuming it is trying to connect to ttyUSB4. Any other suggestions? Is there any other place where it could be logging failed attempts? I read somewhere that it could put info in /var/log/networkmanager but I don't have that file. Thanks for the help. Jerone Young wrote: Ok I might have screwed it up. You can hack your local copy easily though. First back it up. Then edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi line 334 You will see match key=@info.parent:usb.interface.number int=0 Change this to match key=@info.parent:usb.interface.number int=4 Let us know if that works. On Tue, 2009-01-06 at 12:24 +1100, Ben wrote: Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
Before you decide to do that. What is the output if you swith it back to ttyUSB0? To change the initialization commands you can start in src/nm-gsm-device.c On Tue, 2009-01-06 at 16:40 +1100, Ben wrote: Is there a way to change the init string? When I run: NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon I can see that it's trying to send an init string that is different to the one that I'm using in my /etc/wvdial.conf file. Then, an error gets returned saying that it couldn't initialise the modem. I'm pretty sure that if I change this init string in NetworkManager that it will work. Ben. Jerone Young wrote: You can look in /var/log/daemon.log. You can also run Network Manager in debug mode (as root): 1) /etc/init.d/network-manager stop 2) NetworkManager --no-daemon You will see debug message in the Window. On Tue, 2009-01-06 at 13:36 +1100, Ben wrote: Hmmm no if I change the int to a 4 and reboot, it tries to connect but about half a second later it instantly connects back to what it had originally connected to (LAN or whatever). There is nothing in the log (/var/log/messages) about what it's doing so it's hard to say. But if I set int to be 3 for example and then connect, it says it's trying to dial ttyUSB3, so setting it to 4 I am assuming it is trying to connect to ttyUSB4. Any other suggestions? Is there any other place where it could be logging failed attempts? I read somewhere that it could put info in /var/log/networkmanager but I don't have that file. Thanks for the help. Jerone Young wrote: Ok I might have screwed it up. You can hack your local copy easily though. First back it up. Then edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi line 334 You will see match key=@info.parent:usb.interface.number int=0 Change this to match key=@info.parent:usb.interface.number int=4 Let us know if that works. On Tue, 2009-01-06 at 12:24 +1100, Ben wrote: Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: 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 connects to wrong USB device
Yeah, I just saw that that was where you change the init string before. After compiling this, it got passed the error and a it tried to do a few more things which all were successful. Then it comes up with an error: Invalid byte sequence in conversion input Well actually after a reboot and trying again (running the /usr/local/sbin/NetworkManager which is the newly installed one) I get: symbol lookup error: NetworkManager: undefined symbol: nm_setting_connection_get_autoconnect So that's not good, looks like a library hasn't installed correctly or something. Jerone Young wrote: Before you decide to do that. What is the output if you swith it back to ttyUSB0? To change the initialization commands you can start in src/nm-gsm-device.c On Tue, 2009-01-06 at 16:40 +1100, Ben wrote: Is there a way to change the init string? When I run: NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon I can see that it's trying to send an init string that is different to the one that I'm using in my /etc/wvdial.conf file. Then, an error gets returned saying that it couldn't initialise the modem. I'm pretty sure that if I change this init string in NetworkManager that it will work. Ben. Jerone Young wrote: You can look in /var/log/daemon.log. You can also run Network Manager in debug mode (as root): 1) /etc/init.d/network-manager stop 2) NetworkManager --no-daemon You will see debug message in the Window. On Tue, 2009-01-06 at 13:36 +1100, Ben wrote: Hmmm no if I change the int to a 4 and reboot, it tries to connect but about half a second later it instantly connects back to what it had originally connected to (LAN or whatever). There is nothing in the log (/var/log/messages) about what it's doing so it's hard to say. But if I set int to be 3 for example and then connect, it says it's trying to dial ttyUSB3, so setting it to 4 I am assuming it is trying to connect to ttyUSB4. Any other suggestions? Is there any other place where it could be logging failed attempts? I read somewhere that it could put info in /var/log/networkmanager but I don't have that file. Thanks for the help. Jerone Young wrote: Ok I might have screwed it up. You can hack your local copy easily though. First back it up. Then edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi line 334 You will see match key=@info.parent:usb.interface.number int=0 Change this to match key=@info.parent:usb.interface.number int=4 Let us know if that works. On Tue, 2009-01-06 at 12:24 +1100, Ben wrote: Thanks for the suggestion. I tried your fix however when I copied this file over the original one (made backup first) and then reboot, I can create a connection but now I no longer see it in the connection list. I'm using NetworkManager applet 0.7.0. Jerone Young wrote: ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
Got passed that error, but am receiving some other weird problems. After rebooting and re-running NetworkManager, I add a new connection but it doesn't save it for some reason. Sometimes the whole icon disappears but NetworkManager still continues to run. No errors or warnings in the debugging output. I guess some things are not meant to be. It would be nice if the init string was not hard coded =) Ben wrote: Yeah, I just saw that that was where you change the init string before. After compiling this, it got passed the error and a it tried to do a few more things which all were successful. Then it comes up with an error: Invalid byte sequence in conversion input Well actually after a reboot and trying again (running the /usr/local/sbin/NetworkManager which is the newly installed one) I get: symbol lookup error: NetworkManager: undefined symbol: nm_setting_connection_get_autoconnect So that's not good, looks like a library hasn't installed correctly or something. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
