Re: How to stop MM from configuring a specific modem?

[Jason Glasgow]

This can be done via udev rules.


   - Use lsusb to find the vendor id and product id of your modem.
   - Write a new udev rules file, similar to
   
http://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/77-mm-usb-device-blacklist.rules
   - Have your rules file set ENV{ID_MM_DEVICE_IGNORE}="1"
   - Put your udev file in /etc/udev/rules.d/ (or similar directory for you
   distribution).

-Jason

On Wed, Oct 13, 2010 at 11:16 PM, Msquared  wrote:

> Hi!
>
> How do I configure ModemManager to ignore a specific USB 3G modem?
>
> I have a 3G USB modem that I'm using with gnokii to reprogram phonebooks
> on SIM cards.
>
> Since I do not use the device as a modem, ModemManager interferes with
> gnokii when the modem is first plugged in.
>
>
> So far I've only been able to completely disable MM or uninstall it, to
> stop it from interfering with the modem.
>
> I tried adding the device to NetworkManager's unmanaged-devices list, but
> of course that just stops NM from using the modem; it doesn't stop MM from
> configuring the modem.
>
> Is there a way to stop MM from messing with a specific modem?
>
> Regards, Msquared...
> ___
> 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

How to stop MM from configuring a specific modem?

[Msquared]

Hi!

How do I configure ModemManager to ignore a specific USB 3G modem?

I have a 3G USB modem that I'm using with gnokii to reprogram phonebooks
on SIM cards.

Since I do not use the device as a modem, ModemManager interferes with
gnokii when the modem is first plugged in.


So far I've only been able to completely disable MM or uninstall it, to
stop it from interfering with the modem.

I tried adding the device to NetworkManager's unmanaged-devices list, but
of course that just stops NM from using the modem; it doesn't stop MM from
configuring the modem.

Is there a way to stop MM from messing with a specific modem?

Regards, Msquared...
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: auto reconnect issue

[rain blue]

2010/10/13 Bin Li 

> On Tue, Oct 5, 2010 at 1:44 PM, rain blue  wrote:
> > Dear,
> >I have some issues about reconnect.
> > ex: a. I have /etc/NetworkManager/system-connection/Wired static ip
> >   b.connecting Wired static ip
> >   c.rm /etc/NetworkManager/system-connection/Wired static ip
> >   d.disconnected
> >   e.create /etc/NetworkManager/system-connection/Wired static ip2
> > then nm-applet can't auto reconnect Wired static ip2 configure.
> > what can i do that let nm-applet auto reconnect?
> Do you add below line in [connection] section?
> autoconnect=true

Yes, I have add this line.
maybe it is wifi module issue?
because sometimes i use nm-tool that can't scan AP.
Only the interface be waked up

Thanks Bin reply
blue


> > Networkmanager-applet 0.8 version
> > ( I close all about nm-applet GUI , just want to use command or c code to
> > control )
> > BTW, I write to use AddConnection DBUS by c code. Add 3.5G Wired Wifi
> static
> > IP setting.
> > (reference: Jirka sampler & nm-keyfile-connection.c)
> > Maybe it will help beginner to study NM. Like me...
> > Thanks everyone
> > blue
> >
> >
> > ___
> > 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: NM can't save password of VPN connection in system scope

[cee1]

The second version of patch for nm-openvpn: filter out empty secrets before
saving to system scope.


-- 
Regards,

- cee1


nm-openvpn_Store-password-in-system-scope V2.patch
Description: Binary data
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Unable to connect to mobile broadband: +CME ERROR:30

[van Schelve]

Am Mittwoch, den 13.10.2010, 12:49 +0200 schrieb Dan Williams
:
> On Mon, 2010-10-11 at 10:43 +0200, van Schelve wrote:
>> Hi,
>>
>> I found a different problem where I get reports from our users in the
>> field. They tell us that they are not able to connect to mobile
>> network.
>>
>> In the logs I captured I found a cme error 30 which means "No network
>> service". I tried it two or three times with still the same problem.
>> Then I tested with a second identical laptop with an identical setup
>> and I was able to bring up the mobile connection on this system without
>> any problem.
>>
>> So I decided to use the rfkill switch on the laptop where I found the
>> problem with the result that dialin was possible after doing th rfkill
>> cycle.
> 
> Interesting; your module seems to have firmware 1.1.8.3, while I have 3
> different modules with 1.1.8.15, 1.1.9.3, and 2.0.8.19.  I think
> 2.0.8.19 screwed my device though, so don't try it.  I've noticed odd
> problems like this on other Sierra devices in the past that were solved
> by firmware updates (AC875 and AC881), but it's pretty hard to find
> firmware upgrades for their  embedded modules.  Do you know offhand if
> any of the devices in the field has other firmware than 1.1.8.3?

We have completely identical hardware in the field. All the systems are
Lenovo Thinkpad T61 with identical BIOS 2.10 version and the same
firmware
on the embedded sierra device : 1.1.8.3. I think changing the firmware
to
a different version woud be a really bad option. Our systems are spread
all over germany and I don't think the firmware update would be
possible
under linux.

On the other hand it was good luck that I was able to see this issue on
my system. I'm thinking about enabling debug on all our systems this
way:

cat
/usr/share/dbus-1/system-services/org.freedesktop.ModemManager.service
[D-BUS Service]
Name=org.freedesktop.ModemManager
Exec=/usr/sbin/modem-manager --debug >>
/var/log/modem-manager-debug.log
User=root

and starting NetworkManager --log-level=debug in the upstart initscript

What do you mean? Would this be ok?

> 
> In any case, I'll add some code to ModemManager to get better Sierra
> device status for GSM devices to help debug this issue.  If you run into
> this problem yourself, we want the output of AT!GSTATUS? to get more
> info if you can.
> 

But this means I need to disable mobile broadband temporary because
otherwise
the serial port is blocked by modem-manager and I cannot get the
information at
the same time. Having more debug in sierraplugin would be very helpful
because 
I have seen other issues that I have not reported yet (for example SIM
Busy)

HG

> Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Unable to connect to mobile broadband: +CME ERROR:30

[Dan Williams]

On Mon, 2010-10-11 at 10:43 +0200, van Schelve wrote:
> Hi,
> 
> I found a different problem where I get reports from our users in the 
> field. They tell us that they are not able to connect to mobile 
> network.
> 
> In the logs I captured I found a cme error 30 which means "No network 
> service". I tried it two or three times with still the same problem.
> Then I tested with a second identical laptop with an identical setup 
> and I was able to bring up the mobile connection on this system without
> any problem.
> 
> So I decided to use the rfkill switch on the laptop where I found the 
> problem with the result that dialin was possible after doing th rfkill 
> cycle.

Interesting; your module seems to have firmware 1.1.8.3, while I have 3
different modules with 1.1.8.15, 1.1.9.3, and 2.0.8.19.  I think
2.0.8.19 screwed my device though, so don't try it.  I've noticed odd
problems like this on other Sierra devices in the past that were solved
by firmware updates (AC875 and AC881), but it's pretty hard to find
firmware upgrades for their  embedded modules.  Do you know offhand if
any of the devices in the field has other firmware than 1.1.8.3?

In any case, I'll add some code to ModemManager to get better Sierra
device status for GSM devices to help debug this issue.  If you run into
this problem yourself, we want the output of AT!GSTATUS? to get more
info if you can.

Dan


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: ANN: NetworkManager 0.8.2-beta1

[Dan Williams]

On Mon, 2010-10-11 at 21:08 +0800, cee1 wrote:
> 2010/10/11 cee1 
> Hi Dan,
> 
> 
> I tried to run nm-connect-editor(of 0.8.2-beta1), it aborted
> with "WARNING **: Icon nm-device-wwan missing". (gtk+ 2.18.3)
> 
> 
> I copy and rename an arbitrary icon
> in /usr/share/icons/hicolor/48x48/apps to
> "nm-device-wwan.png", the UI initializes normally.
> 
> 
> Does the source misses this icon for all sizes except 22x22?
> 
> 
> According to the Icon Theme Specification, gtk should load
> nm-device-wwan.png of size 22x22 automatically. I removed the manually
> copied icon in 48x48, nm-connection-editor also pops up its window
> normally, curious, maybe the side effect of the cache ?

Yeah, after install you'd normally have to run:

gtk-update-icon-cache -f /usr/share/icons/hicolor

or wherever the icons are installed.

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Wireless driver is being recognized as wired driver

[Dan Williams]

On Tue, 2010-10-12 at 09:58 +0200, Jirka Klimes wrote:
> On Tuesday 12 of October 2010 09:04:25 panduranga wrote:
> > Hi all,
> > 
> > We are integrating Wireless LAN driver with Ubuntu GNOME on a customer
> > proprietary board.
> > 
> > The issue we are facing is that our network interface (WLAN) is being
> > recognized as wired interface by GNOME network-manager. We are using Ubuntu
> > 10.10.
> > 
> > But iwconfig is recognising xxxwlan0 interface as wireless.
> > iwlist scan is scanning the AP's.
> > 
> > If i stop network-manager and wpa_supplicant and load the drivers and then
> > start them, then it is being listed as wireless interface.
> > 
> > Please find the log below:
> > ===
> > 
> > Oct  7 18:48:55 ubuntu-desktop modem-manager: (net/xxxwlan0): port's parent
> > platform driver is not whitelisted
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:SCPlugin-Ifupdown:
> > devices added (path: /sys/devices/platform/device_wifi.1/net/xxxwlan0,
> > iface: xxxwlan0)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:SCPlugin-Ifupdown:
> > device added (path: /sys/devices/platform/device_wifi.1/net/xxxwlan0,
> > iface: xxxwlan0): no ifupdown configuration found.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]: 
> > [1286457535.687011] [nm-device-ethernet.c:729]
> > real_update_permanent_hw_address(): (xxxwlan0): unable to read permanent
> > MAC address (error 95)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > driver 'device_wifi' does not support carrier detection.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0): new
> > Ethernet device (driver: 'device_wifi' ifindex: 3)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > exported as /org/freedesktop/NetworkManager/Devices/1
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0): now
> > managed
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > device state change: 1 -> 2 (reason 2)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > bringing up device.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > deactivating device (reason: 2).
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Added default
> > wired connection 'Auto xxxwlan0' for
> > /sys/devices/platform/device_wifi.1/net/xxxwlan0
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > device state change: 2 -> 3 (reason 0)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) starting connection 'Auto xxxwlan0'
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > device state change: 3 -> 4 (reason 0)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) Stage 1 of 5 (Device Prepare) scheduled...
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) Stage 1 of 5 (Device Prepare) started...
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) Stage 2 of 5 (Device Configure) scheduled...
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) Stage 1 of 5 (Device Prepare) complete.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) Stage 2 of 5 (Device Configure) starting...
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > device state change: 4 -> 5 (reason 0)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > bringing up device.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > device state change: 5 -> 9 (reason 4)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Marking
> > connection 'Auto xxxwlan0' invalid.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) failed.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  Activation
> > (xxxwlan0) Stage 2 of 5 (Device Configure) complete.
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > device state change: 9 -> 3 (reason 0)
> > Oct  7 18:48:55 ubuntu-desktop NetworkManager[1634]:  (xxxwlan0):
> > deactivating device (reason: 0).
> > 
> > We want to know if we are missing some thing in the wlan driver.If anybody
> > has worked on the GNOME-Network Manager earlier or has a clue about this,
> > kindly share with us.
> > 
> > Please let us know if you need more details.
> > 
> > thanks,
> > Pandu.
> 
> It's probably a bug of device_wifi driver. What's the driver anyway?
> 
> What's the output of 
> 
> tree /sys/class/net/xxxwlan0
> and
> cat /sys/class/net/xxxwlan0/type

Right, this is almost always a driver bug.  It's usually one of two
things:

1) the driver does not respond to the SIOCGIWNAME WEXT ioctl
2) there is no /sys/class/net//phy80211 directory (only relevant
for mac80211-based drivers)

see is_wireless() in src/nm-udev-manager.c.

Dan


___

Re: Patch for nm-openvpn: fix incompatible change of NMVpnPluginUiInterface

[cee1]

Found the same problem for nm-pptp, attachment is the patch.

2010/10/12 cee1 

> Hi Dan,
>
> From NM0.8.1 to 0.8.2, two members of "NMVpnPluginUiInterface" renamed.
> File 
> properties/nm-openvpn.c
>  of
> nm-openvpn should upgrade for this.
>


-- 
Regards,

- cee1


0001-nm-pptp.c-fix-for-new-NMVpnPluginUiInterface.patch
Description: Binary data
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NM can't save password of VPN connection in system scope

[cee1]

2010/2/27 Dan Williams 

> On Fri, 2010-02-26 at 21:17 +0800, cee1 wrote:
> > The connection editor should support this as long as a system
> > settings
> > plugin is enabled that supports writing out VPN connections.
> >  At the
> > moment the only plugin that does support this is the 'keyfile'
> > plugin.
> > Look in /etc/NetworkManager/nm-system-settings.conf to see if
> > it's
> > enabled.
> >
> > The keyfile plugin is enabled.
> >
> >
> > It seems connection editor doesn't support this:
> > For nm-connect-editor, only the function
> > "save_secrets" (network-manager-pptp-0.7.2/properties/nm-pptp.c) will
> > read user-entered password, and this function is only called for user
> > scope setting.
>
> Looks like you're right for NM-pptp; though for NM-vpnc this is
> correctly handled in update_connection().  We'll have to fix that.

Patch for nm-pptp
(nm-pptp_Store-password-in-update_connection-for-global-setti.patch)

BTW, for nm-openvpn, code of saving secret in system scope seems with the
same problem, another patch is given.
(nm-openvpn_Store-password-in-update_connection-for-global-setti.patch)
Note:

   - Unlike patch for nm-pptp, this patch is only compiling pass, not tested
   in practice currently.
   - The original code will call "nm_setting_vpn_add_secret" in
   
hash_copy_advanced,
   seems nonsense (if in user scope, not needed, otherwise, the patch will call
   it later) and removes.



-- 
Regards,

- cee1


nm-pptp_Store-password-in-update_connection-for-global-setti.patch
Description: Binary data


nm-openvpn_Store-password-in-update_connection-for-global-setti.patch
Description: Binary data
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Let NM support the dial-up modem

[Bin Li]

Dan,

 Could we have any plan to support the dial-up modem in NM and MM? I'm
try to add it in MM and NM, and still some issue.

 1) Is it better that make a single dialup plugin for MM? Or just put
it in generic plugin?
 2) When I use the dialup plugin, my Huawei 3G modem, was processed by
dialup plugins, cause it load before the huawei plugins, how to
recognize modem correctly? I prepare put the dialup plugins to the
last like generic plugin to resolve my current issue.
 3) In nm-connection-editor, is it better to separate a single tab for modem?

 Any idea?

Sincerely Yours,

Bin Li

http://cn.opensuse.org
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: auto reconnect issue

[Bin Li]

On Tue, Oct 5, 2010 at 1:44 PM, rain blue  wrote:
> Dear,
>        I have some issues about reconnect.
> ex: a. I have /etc/NetworkManager/system-connection/Wired static ip
>       b.connecting Wired static ip
>       c.rm /etc/NetworkManager/system-connection/Wired static ip
>       d.disconnected
>       e.create /etc/NetworkManager/system-connection/Wired static ip2
> then nm-applet can't auto reconnect Wired static ip2 configure.
> what can i do that let nm-applet auto reconnect?
Do you add below line in [connection] section?
autoconnect=true

> Networkmanager-applet 0.8 version
> ( I close all about nm-applet GUI , just want to use command or c code to
> control )
> BTW, I write to use AddConnection DBUS by c code. Add 3.5G Wired Wifi static
> IP setting.
> (reference: Jirka sampler & nm-keyfile-connection.c)
> Maybe it will help beginner to study NM. Like me...
> Thanks everyone
> blue
>
>
> ___
> 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