Re: Mobile broadband connects to wrong USB device
--On Friday, January 16, 2009 17:20:33 -0500 Dan Williams wrote: > I've changed it to \rAT&F V1 X4 &C1 +CREG=0. It will also > accept E0 and +FCLASS=0, but I overwrote those because I tweaked the > embedded string in binary and couldn't extend it - those settings > happen to be the defaults in USBModem. Applied to git head, will get cherry-picked to 0.7 too. Please test it out if you can. Last time I tried building NM from source I never managed to get the right combination of dev libraries for a successful compilation. I think I'll wait until someone does a PPA build - these usually come out fairly quickly after a source release. My time's being taken up with some personal issues at the moment too. -- Cheers Rick ___ 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 Thu, 2009-01-15 at 17:46 +, Rick Jones wrote: > Hi Dan > > --On Wednesday, January 14, 2009 18:29:51 -0500 Dan Williams > wrote: > > On Tue, 2009-01-06 at 16:03 +, Rick Jones wrote: > > > > > > a) it requires an initial otherwise it fails to see a clean > AT > > > command and doesn't respond - resulting in an init. timeout. > > > > With this, my Sierra 860 doesn't respond and times out. Were you > ever > > able to find out from the MobileStream guys why this might be > required? > > It might also be something that NetworkManager isn't doing when > setting > > up the serial port. Does USBModem need specific serial port > settings? > > I didn't get much response from MobileStream, and also the problem > doesn't happen on Windows :(. It seems to be some interaction with the > Linux USB/serial driver, because I can prove the problem simply by > connecting to the modem with telnet to /dev/USB0. The first command > after connection is ignored. I thought initially that it needed to > receive 2 AT commands before it would respond, but in fact it just > needs \r before the first AT. I suspect that it picks up a bogus byte > or two when the connection is opened, and thus the first AT is not > seen as starting a new line, and hence ignored. > > > > b) its initial CREG state is 1, meaning that NM gets incorrect > > > responses to its CREG queries later in the conversation. It > requires > > > +CREG=0 in the init string. > > > > With this also, my Sierra 860 doesn't respond and times out. > > Hmmm, that's a blow, I would have thought that a modem that responds > to CREG queries would allow +CREG=n. > > > > By hacking these fixes into the init string it works fine. It's a > soft > > > modem running in a Palm Treo handheld: USBModem by MobileStream. > At > > > least one other poster on this list is using (or trying to) the > same > > > software. > > > > What's the init string you currently use? Long ago you mentioned: > > > > AT&F\rATV1 X4 &C1 +CREG=0 > > > > Is that still correct? Or can you move the AT&F after the \r? > > I've changed it to \rAT&F V1 X4 &C1 +CREG=0. It will also > accept E0 and +FCLASS=0, but I overwrote those because I tweaked the > embedded string in binary and couldn't extend it - those settings > happen to be the defaults in USBModem. Applied to git head, will get cherry-picked to 0.7 too. Please test it out if you can. Dan > > > Regarding ATZ v. AT&F, I believe the latter should always be > > > supported, as it is a full reset. ATZ restores to settings saved > using > > > AT&W, but if that's never been used it's the same as AT&F. If AT&W > is > > > not supported, then ATZ may not be either; and if you don't use > AT&W > > > to save settings (does NM?) then there is no reason to use ATZ. > > > > The Sierra 860 also doesn't like AT&F *at all*. Whee! If we can > put > > together an init string that works for now, we can add it to the > bottom > > of the list. > > USBModem works with ATZ or AT&F, but I noticed a post from someone > else saying their modem didn't like ATZ. I was recalling my memories > of programming "real" modems, where AT&F was always the full "factory > reset", and hence the only thing that could be guaranteed to put the > modem into a known state. > > This is always the problem - somewhere along the line someone > re-interprets the "standard", so it's never quite as standard as we'd > all like :-/. > > Maybe it's possible to have an init string that's close to universal > at the moment, but I think everything said above illustrates that it's > probably impossible to get a single string that works (and will work) > for everything. To deal with the security issue, how about a > configuration file writable only by root, containing a list of > possible of init strings? This would be shipped with a selection of > strings to cater for currently known variants, which the user can > select from. In the case of a user having an even more oddball device, > with tech knowledge and admin privilege they can add other entry. > > Getting closer > > Cheers, Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
Hi Dan --On Wednesday, January 14, 2009 18:29:51 -0500 Dan Williams wrote: On Tue, 2009-01-06 at 16:03 +, Rick Jones wrote: > > a) it requires an initial otherwise it fails to see a clean AT > command and doesn't respond - resulting in an init. timeout. With this, my Sierra 860 doesn't respond and times out. Were you ever able to find out from the MobileStream guys why this might be required? It might also be something that NetworkManager isn't doing when setting up the serial port. Does USBModem need specific serial port settings? I didn't get much response from MobileStream, and also the problem doesn't happen on Windows :(. It seems to be some interaction with the Linux USB/serial driver, because I can prove the problem simply by connecting to the modem with telnet to /dev/USB0. The first command after connection is ignored. I thought initially that it needed to receive 2 AT commands before it would respond, but in fact it just needs \r before the first AT. I suspect that it picks up a bogus byte or two when the connection is opened, and thus the first AT is not seen as starting a new line, and hence ignored. > b) its initial CREG state is 1, meaning that NM gets incorrect > responses to its CREG queries later in the conversation. It requires > +CREG=0 in the init string. With this also, my Sierra 860 doesn't respond and times out. Hmmm, that's a blow, I would have thought that a modem that responds to CREG queries would allow +CREG=n. > By hacking these fixes into the init string it works fine. It's a soft > modem running in a Palm Treo handheld: USBModem by MobileStream. At > least one other poster on this list is using (or trying to) the same > software. What's the init string you currently use? Long ago you mentioned: AT&F\rATV1 X4 &C1 +CREG=0 Is that still correct? Or can you move the AT&F after the \r? I've changed it to \rAT&F V1 X4 &C1 +CREG=0. It will also accept E0 and +FCLASS=0, but I overwrote those because I tweaked the embedded string in binary and couldn't extend it - those settings happen to be the defaults in USBModem. > Regarding ATZ v. AT&F, I believe the latter should always be > supported, as it is a full reset. ATZ restores to settings saved using > AT&W, but if that's never been used it's the same as AT&F. If AT&W is > not supported, then ATZ may not be either; and if you don't use AT&W > to save settings (does NM?) then there is no reason to use ATZ. The Sierra 860 also doesn't like AT&F *at all*. Whee! If we can put together an init string that works for now, we can add it to the bottom of the list. USBModem works with ATZ or AT&F, but I noticed a post from someone else saying their modem didn't like ATZ. I was recalling my memories of programming "real" modems, where AT&F was always the full "factory reset", and hence the only thing that could be guaranteed to put the modem into a known state. This is always the problem - somewhere along the line someone re-interprets the "standard", so it's never quite as standard as we'd all like :-/. Maybe it's possible to have an init string that's close to universal at the moment, but I think everything said above illustrates that it's probably impossible to get a single string that works (and will work) for everything. To deal with the security issue, how about a configuration file writable only by root, containing a list of possible of init strings? This would be shipped with a selection of strings to cater for currently known variants, which the user can select from. In the case of a user having an even more oddball device, with tech knowledge and admin privilege they can add other entry. Getting closer Cheers, Rick ___ 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 16:03 +, Rick Jones wrote: > --On Tuesday, January 06, 2009 15:00:50 +0100 Patryk Zawadzki > wrote: > > ¦ Allowing one to edit the init string is a security threat similar to > ¦ allowing users to provide custom firmware. > > OK, i can see there's an issue there. > > ¦ Other than that there seem to be only two differences between > devices > ¦ reported so far. One is the initial echo state which is > insignificant, > ¦ the second one is whether the device supports ATZ or requires AT&F + > ¦ defaults. > > Not true. I've reported here on more than one occasion the problems > with my modem. > > a) it requires an initial otherwise it fails to see a clean AT > command and doesn't respond - resulting in an init. timeout. With this, my Sierra 860 doesn't respond and times out. Were you ever able to find out from the MobileStream guys why this might be required? It might also be something that NetworkManager isn't doing when setting up the serial port. Does USBModem need specific serial port settings? > b) its initial CREG state is 1, meaning that NM gets incorrect > responses to its CREG queries later in the conversation. It requires > +CREG=0 in the init string. With this also, my Sierra 860 doesn't respond and times out. > By hacking these fixes into the init string it works fine. It's a soft > modem running in a Palm Treo handheld: USBModem by MobileStream. At > least one other poster on this list is using (or trying to) the same > software. What's the init string you currently use? Long ago you mentioned: AT&F\rATV1 X4 &C1 +CREG=0 Is that still correct? Or can you move the AT&F after the \r? > Regarding ATZ v. AT&F, I believe the latter should always be > supported, as it is a full reset. ATZ restores to settings saved using > AT&W, but if that's never been used it's the same as AT&F. If AT&W is > not supported, then ATZ may not be either; and if you don't use AT&W > to save settings (does NM?) then there is no reason to use ATZ. The Sierra 860 also doesn't like AT&F *at all*. Whee! If we can put together an init string that works for now, we can add it to the bottom of the list. Dan ___ 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 Wed, 2009-01-07 at 22:01 -0700, Mike Butash wrote: > Hi, > > I tend to agree with Ben that alternative/roaming usb serial devices > tend to be a common issue for me, especially usb to serial adapters (I > do networks, so usb to serial console ports are a big thing). Problem > for me has always been NOT to have my serial console adapter attached in > older versions of ubuntu using pon/poff lest it come up not on ttyUSB0 > and 1, but still a relevant issue apparently with a functional NM > handling broadband wwan in ibex. > > I've considered using udev rules to recognize the card specifically and > name it a unique device(s). I was hoping with changes to NM and hal, > that hal would be able to track which usb devices actually when it roams > (where my card by its usb id or vendor), but alas it still does not. The solution to this problem is a modem prober, which is now in udev-extras (see git.kernel.org), which will populate the udev database with the capabilities of a particular USB TTY device. NetworkManager will be modified to ask the udev database about these capabilities, and thus automatically determine what ports will work and what ports won't, and thus take the fdi file stuff out of the loop. It's a problem, and it's being fixed. Dan > Reading this with Ben's issue also being similar to mine, do others > experience the same? Would it be worth doing so? Granted the same > could be said for my usb->serial consoles, but seems these should be > made to be a bit less generic than a common serial tty port, or at least > symlink to the right ports dynamically with something more identifiable. > > Thanks! > > -mb > > > On Tue, 2009-01-06 at 11:02 +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. > > > > Thanks, > > Ben. > > ___ > > 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
Hi, I tend to agree with Ben that alternative/roaming usb serial devices tend to be a common issue for me, especially usb to serial adapters (I do networks, so usb to serial console ports are a big thing). Problem for me has always been NOT to have my serial console adapter attached in older versions of ubuntu using pon/poff lest it come up not on ttyUSB0 and 1, but still a relevant issue apparently with a functional NM handling broadband wwan in ibex. I've considered using udev rules to recognize the card specifically and name it a unique device(s). I was hoping with changes to NM and hal, that hal would be able to track which usb devices actually when it roams (where my card by its usb id or vendor), but alas it still does not. Reading this with Ben's issue also being similar to mine, do others experience the same? Would it be worth doing so? Granted the same could be said for my usb->serial consoles, but seems these should be made to be a bit less generic than a common serial tty port, or at least symlink to the right ports dynamically with something more identifiable. Thanks! -mb On Tue, 2009-01-06 at 11:02 +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. > > Thanks, > Ben. > ___ > 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 connects to wrong USB device
--On Tuesday, January 06, 2009 15:00:50 +0100 Patryk Zawadzki wrote: ¦ Allowing one to edit the init string is a security threat similar to ¦ allowing users to provide custom firmware. OK, i can see there's an issue there. ¦ Other than that there seem to be only two differences between devices ¦ reported so far. One is the initial echo state which is insignificant, ¦ the second one is whether the device supports ATZ or requires AT&F + ¦ defaults. Not true. I've reported here on more than one occasion the problems with my modem. a) it requires an initial otherwise it fails to see a clean AT command and doesn't respond - resulting in an init. timeout. b) its initial CREG state is 1, meaning that NM gets incorrect responses to its CREG queries later in the conversation. It requires +CREG=0 in the init string. By hacking these fixes into the init string it works fine. It's a soft modem running in a Palm Treo handheld: USBModem by MobileStream. At least one other poster on this list is using (or trying to) the same software. Regarding ATZ v. AT&F, I believe the latter should always be supported, as it is a full reset. ATZ restores to settings saved using AT&W, but if that's never been used it's the same as AT&F. If AT&W is not supported, then ATZ may not be either; and if you don't use AT&W to save settings (does NM?) then there is no reason to use ATZ. Cheers, Rick ___ 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, Jan 6, 2009 at 3:19 PM, julien bresciani wrote: > why not putting init strings able to be changed in gconf registry for > example, only the advanced user will touch these parameters. Again, what is there to change? You have to keep echo off and the only possible change current NM requires is changing ATZ to AT&F. I propose another solution: * either always perform AT&F and set all attributes as needed * or try ATZ0 and if it fails, fall back to AT&F None of these require any configuration. Again, allowing the user to override the init command in gconf would make it easy to trick people into dialing into pay-per-minute lines or do other nasty stuff (using operator dialtone codes to reconfigure your phone line to redirect incoming calls to a sex line anybody?). Just tell 'em to "overwrite that config string with this one to increase your network speed up to 13%" and people will blindly do so. > to solve some problems , why not create a dummy class adapter, this adapter > should be held by network manager but his comportement completely scriptable > linkable to wvdial and other advanced scriptable linux connection tools : > waking up , creating a ppp interface for example, initializing a modem... Just stop NM daemon if you do not want to use it. > this could solve the problems with pidgin firefox and all other stuff always > waiting for network manager if you use bluetooth connection with wvdial for > example... (I waiting with impatience the bluetooth coming to NM.) Follow the above and all the above should assume the network to be up. -- Patryk Zawadzki ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband connects to wrong USB device
Patryk Zawadzki wrote: On Tue, Jan 6, 2009 at 2:40 PM, Rick Jones wrote: --On Tuesday, January 06, 2009 18:03:53 +1100 Ben wrote: I guess some things are not meant to be. It would be nice if the init string was not hard coded =) I agree completely. I too have posted about problems with the init string. I think it's wildly optimistic to assume that you can hard-code an init string that will work with all the modems out there, including ones to be produced in future. Actually the ones to be produced in the future are guaranteed to be in a much better shape than those in the past. i understand that NM is trying to avoid presenting the user with nasty technical configuration issues, but there are already many "technical" conifigs available in the connection-setting dialogs. Most users probably don't fully understand these either, but they are of course necessary in order to be able to make connections work in all circumstances. The defaults work in most cases, but can be tweaked - usually with help - if required. My view is the modem init string falls into this category. Allowing one to edit the init string is a security threat similar to allowing users to provide custom firmware. Other than that there seem to be only two differences between devices reported so far. One is the initial echo state which is insignificant, the second one is whether the device supports ATZ or requires AT&F + defaults. why not putting init strings able to be changed in gconf registry for example, only the advanced user will touch these parameters. to solve some problems , why not create a dummy class adapter, this adapter should be held by network manager but his comportement completely scriptable linkable to wvdial and other advanced scriptable linux connection tools : waking up , creating a ppp interface for example, initializing a modem... this could solve the problems with pidgin firefox and all other stuff always waiting for network manager if you use bluetooth connection with wvdial for example... (I waiting with impatience the bluetooth coming to NM.) ___ 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, Jan 6, 2009 at 2:40 PM, Rick Jones wrote: > --On Tuesday, January 06, 2009 18:03:53 +1100 Ben wrote: > >> I guess some things are not meant to be. It would be nice if the init >> string was not hard coded =) > I agree completely. I too have posted about problems with the init string. I > think it's wildly optimistic to assume that you can hard-code an init string > that will work with all the modems out there, including ones to be produced > in future. Actually the ones to be produced in the future are guaranteed to be in a much better shape than those in the past. > i understand that NM is trying to avoid presenting the user with nasty > technical configuration issues, but there are already many "technical" > conifigs available in the connection-setting dialogs. Most users probably > don't fully understand these either, but they are of course necessary in > order to be able to make connections work in all circumstances. The defaults > work in most cases, but can be tweaked - usually with help - if required. My > view is the modem init string falls into this category. Allowing one to edit the init string is a security threat similar to allowing users to provide custom firmware. Other than that there seem to be only two differences between devices reported so far. One is the initial echo state which is insignificant, the second one is whether the device supports ATZ or requires AT&F + defaults. -- Patryk Zawadzki ___ 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 Tuesday, January 06, 2009 18:03:53 +1100 Ben wrote: I guess some things are not meant to be. It would be nice if the init string was not hard coded =) I agree completely. I too have posted about problems with the init string. I think it's wildly optimistic to assume that you can hard-code an init string that will work with all the modems out there, including ones to be produced in future. i understand that NM is trying to avoid presenting the user with nasty technical configuration issues, but there are already many "technical" conifigs available in the connection-setting dialogs. Most users probably don't fully understand these either, but they are of course necessary in order to be able to make connections work in all circumstances. The defaults work in most cases, but can be tweaked - usually with help - if required. My view is the modem init string falls into this category. I am dealing with my situation by binary patching NetworkManager, rather than set up all the libraries needed to compile the whole thing. This is hardly ideal (nor is having to re-complile come to that). My €.02 Rick ___ 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
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
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 Change this to 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 > >>> > >>> > >>> Change this to > >>> > >>> > >>> 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
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 Change this to 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
Ahh OK thanks. Here is the output when I select the connection: NetworkManager: Activation (ttyUSB4) starting connection 'Vodafone' NetworkManager: (ttyUSB4): device state change: 3 -> 4 NetworkManager: Activation (ttyUSB4) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: Activation (ttyUSB4) Stage 1 of 5 (Device Prepare) started... NetworkManager: [1231210578.256890] nm_serial_device_open(): (ttyUSB4) opening device... NetworkManager: Activation (ttyUSB4) Stage 1 of 5 (Device Prepare) complete. NetworkManager: init_done(): Modem initialization failed NetworkManager: (ttyUSB4): device state change: 4 -> 9 NetworkManager: [1231210578.418451] nm_serial_device_close(): Closing device 'ttyUSB4' NetworkManager: Marking connection 'Vodafone' invalid. NetworkManager: Activation (ttyUSB4) failed. NetworkManager: (ttyUSB4): device state change: 9 -> 3 NetworkManager: (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 Change this to 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 > > > > > > Change this to > > > > > > 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 Change this to 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
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 Change this to 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
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
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
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
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
