Re: permissions and connection editor
On Tue, 2011-10-25 at 17:46 +0200, Ramon Diaz-Uriarte wrote: > Dear All, > > Since my troubles with nm-connection-editor continued, I decided to remove > and install again all of gnome, consolekit, keyring, and > policykit. However, the problems remain. > > > 1. I cannot add wireless connections, as non-root, if they have any kind > of security. The "Save" box is greyed, and I get repeated messages saying > > ** (nm-connection-editor:22077): WARNING **: Invalid setting Wireless > Security: Invalid wireless security You may get this periodically; but this warning means that there is some piece of the wifi security tab that isn't yet valid. What security are you using? WPA PSK? WPA Enterprise? WEP? > > 2. If I try to access one of the available wireless networks, and enter > the authentication info (e.g., CA certificate, password, etc) then I get a > box asking for the root password. > > However, when I enter the root password, it stays there for a long time, > and eventually I get a message saying "You are not allowed to modify the > system configuration" and "An error occurred while checking for > authorizations: Did not receive a reply. Possible causes include: the > remote application did not send a reply, the message bus security policy > blocked the reply, the reply timeout expired, or the network connection > was broken. You may report this as a bug." This seems like a PolicyKit bug or some misconfiguration thereof. NM's usage of PolicyKit is pretty simple: it just asks polkitd if the user is authorized. Then PolicyKit takes over. Can you perhaps paste some logs of NetworkManager (/var/log/messages, or /var/log/daemon.log, of /var/log/NetworkManager.log) that show what's going on when this error happens? > > > Error 2. also happens if I try to, say, access any system-wide > configuration that require root access (e.g., services). > > > So I am not sure where the error is, nor what can I do, since I have > reinstalled everything (after purging configuration files). I am using > Debian, and here are some of the relevant packages. (Note, though, that > gnome-keyring seems to work, at least with other programs). > > > network-manager 0.9.0-2 > network-manager-gnome 0.9.0-4 > policykit-1 0.102-1 > policykit-1-gnome 0.104-1 > consolekit0.4.5-1 > gnome-keyring 3.0.3-2 > libgnome-keyring0 3.2.0-3 > libpam-gnome-keyring3.0.3-2 > python-gnomekeyring 2.32.0-4 Definitely sounds like a PolicyKit problem. There are some things you can do, like using pkcheck to test this stuff out, but you might get better debugging help by asking PolicyKit people too. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Make modemmanager select data port instead of control port on Sierra MC8700/8790
On Wed, 2011-10-26 at 11:06 +0200, Davy Herben wrote:
> Hi all,
>
> I'm working on a system which provides internet access in mobile
> environments through multiple connections (cellular, satellite,
> wifi...). We use NetworkManager to manage the wifi and cell connections,
> and our own software to monitor and log the connection statistics
> (signal strength, SSID, cell id...).
>
> All this runs on an ubuntu machine. We're in the process of upgrading
> from an old 8.04 to 10.04. This bumps the NetworkManager from the 7.x
> range to 8.0 (or 8.4 via a PPA).
>
> The sierra cards expose a number of ttyUSB ports: a few app ports, a
> control port (responds with useful data to AT commands), and a data port
> (can be used to open a connection, but answers only OK/ERROR to AT
> commands).
>
> In 7.x, I used udev rules to force NM to connect using the data port,
> like this:
>
> KERNELS=="ttyUSB7", DRIVERS=="sierra", ENV{ID_NM_MODEM_GSM}="1"
>
> My software then connects to the control port to monitor the status,
> also when the data connection is open.
>
> With NM 8.0 / 8.4, the modemmanager detects the sierra modems, but
> selects the control port instead of the data port. The connection is
> successfully established, but I get no monitoring data as the control
> port is locked.
I've been tracking this for about 2 years so far, specifically with the
8775. I do have code to allow using the APP1 or APP2 port for PPP
instead of the port that has the full parser, but I've never ever been
able to get any of the 8775 modems I've tried to work correctly in this
configuration: PPP never successfully completes. I'm not 100% sure if
it's the command sequence we're using or what. Basically, with my
patches, MM sets up the connection on the main data port all the way up
to (but not including) the ATDT. Then, it sends the ATD#99***x* on the
APP1/APP2 port.
I've tried *5* different 8775 cards, each with different firmware from
1.8, two versions of 1.9, one version of 2.0, and another of 2.1
something and they all respond the same way. I'm beginning to think
that the 8775 simply doesn't support this. I do have an 8780 that I
haven't yet tried with these patches.
> I also considered reading the data I need from udev in my application,
> but it looks like the data like signal strength are not reported for
> these cards.
>
> How would you guys handle this? Is there a way to force the ModemManager
> to connect to the data port? Or (less ideally) to get the data I need
> some other way?
I guess I'd need a bit of guidance or testing after adding this
functionality; other modems can use it too. So I suppose I'll just
polish it up, push it, and only enable it when some special option gets
set. That way you can test it without us breaking everyone else's
Sierra modems.
Dan
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH 5/8] bonding: Implement bonding slaves
On Tue, 2011-10-18 at 13:48 +0200, Thomas Graf wrote:
> Adds a MASTER= directive to ifcfg-rh allowing a connection to define
> itself as bonding slave.
>
> Adds a connection property "master" which contains the in-kernel device
> name or UUID of the master connection.
>
> Adds a connection property "slave-type" which defines the type of slave
> this connection represents. Currently this is only set by bonding but
> eventually this will be used by VLAN and bridging.
Could we drop this property and just use the 'type' setting of the
connection to determine what type of slave this is? ie, if 'master' is
set and 'type == 'bond'' then this is a bond slave, no? It seems like
most of the time the 'slave-type' value will correspond to the same
value as 'type'. Thoughts?
Dan
> Enforces that no bonding slave connection has any IPv4 or IPv6
> configuration set.
>
> Changes make_ip4_setting() to take a universal flag indicating whether
> to allow disabling ip4 config or not and use it for both, ip6 and
> bonding special case.
>
> Signed-off-by: Thomas Graf
> ---
> libnm-util/libnm-util.ver |3 +
> libnm-util/nm-setting-connection.c | 140
>
> libnm-util/nm-setting-connection.h | 11 +++-
> src/settings/plugins/ifcfg-rh/reader.c | 38 +++--
> 4 files changed, 185 insertions(+), 7 deletions(-)
>
> diff --git a/libnm-util/libnm-util.ver b/libnm-util/libnm-util.ver
> index 0ee5917..b4d6912 100644
> --- a/libnm-util/libnm-util.ver
> +++ b/libnm-util/libnm-util.ver
> @@ -197,11 +197,14 @@ global:
> nm_setting_connection_get_connection_type;
> nm_setting_connection_get_id;
> nm_setting_connection_get_num_permissions;
> + nm_setting_connection_get_master;
> nm_setting_connection_get_permission;
> + nm_setting_connection_get_slave_type;
> nm_setting_connection_get_read_only;
> nm_setting_connection_get_timestamp;
> nm_setting_connection_get_type;
> nm_setting_connection_get_uuid;
> + nm_setting_connection_is_slave_type;
> nm_setting_connection_new;
> nm_setting_connection_permissions_user_allowed;
> nm_setting_connection_remove_permission;
> diff --git a/libnm-util/nm-setting-connection.c
> b/libnm-util/nm-setting-connection.c
> index e9030b1..ede63fb 100644
> --- a/libnm-util/nm-setting-connection.c
> +++ b/libnm-util/nm-setting-connection.c
> @@ -72,6 +72,7 @@ nm_setting_connection_error_get_type (void)
> ENUM_ENTRY
> (NM_SETTING_CONNECTION_ERROR_INVALID_PROPERTY, "InvalidProperty"),
> ENUM_ENTRY
> (NM_SETTING_CONNECTION_ERROR_MISSING_PROPERTY, "MissingProperty"),
> ENUM_ENTRY
> (NM_SETTING_CONNECTION_ERROR_TYPE_SETTING_NOT_FOUND, "TypeSettingNotFound"),
> + ENUM_ENTRY
> (NM_SETTING_CONNECTION_ERROR_IP_CONFIG_FOUND, "IpConfigFound"),
> { 0, 0, 0 }
> };
> etype = g_enum_register_static ("NMSettingConnectionError",
> values);
> @@ -97,6 +98,8 @@ typedef struct {
> char *id;
> char *uuid;
> char *type;
> + char *master;
> + char *slave_type;
> GSList *permissions; /* list of Permission structs */
> gboolean autoconnect;
> guint64 timestamp;
> @@ -112,6 +115,8 @@ enum {
> PROP_AUTOCONNECT,
> PROP_TIMESTAMP,
> PROP_READ_ONLY,
> + PROP_MASTER,
> + PROP_SLAVE_TYPE,
>
> LAST_PROP
> };
> @@ -478,6 +483,59 @@ nm_setting_connection_get_read_only (NMSettingConnection
> *setting)
> return NM_SETTING_CONNECTION_GET_PRIVATE (setting)->read_only;
> }
>
> +/**
> + * nm_setting_connection_get_master:
> + * @setting: the #NMSettingConnection
> + *
> + * Returns the #NMSettingConnection:master property of the connection.
> + *
> + * Returns: Name of the master device
> + */
> +const char *
> +nm_setting_connection_get_master (NMSettingConnection *setting)
> +{
> + g_return_val_if_fail (NM_IS_SETTING_CONNECTION (setting), NULL);
> +
> + return NM_SETTING_CONNECTION_GET_PRIVATE (setting)->master;
> +}
> +
> +/**
> + * nm_setting_connection_get_slave_type:
> + * @setting: the #NMSettingConnection
> + *
> + * Returns the #NMSettingConnection:slave-type property of the connection.
> + *
> + * Returns: Type of the slave device
> + */
> +const char *
> +nm_setting_connection_get_slave_type (NMSettingConnection *setting)
> +{
> + g_return_val_if_fail (NM_IS_SETTING_CONNECTION (setting), NULL);
> +
> + return NM_SETTING_CONNECTION_GET_PRIVATE (setting)->slave_type;
> +}
> +
> +/**
> + * nm_setting_connection_is_slave_type:
> + * @setting: the #NMSettingConnection
> + * @type: the name of the slave type
> + *
> + * Returns: TRUE if connection is of specified slave type
> + */
> +gboolean
> +nm_setting_connection_is_slave_type (NMSettingConnection *setting,
> + const char *type)
> +{
> + NMSettingConnectionPrivate *priv
Re: [PATCH 4/8] bonding: Detect virtual bonding devices and create an ethernet device
On Tue, 2011-10-18 at 13:48 +0200, Thomas Graf wrote:
> A bonding device is like a virtual ethernet device. We therefore reuse
> nm-device-ethernet and add some special handling to detect bonding
> connections.
Does rtnl_link_get_type() really return a "char *"? Any reason that's
'const char *'? I'd expect callers not to be able to modify the
returned string, and the code you've got here dupes it before returning.
Especially when constants are assigned to io_name in say
bonding.c/vlan.c/dummy.c too...
Just something to think about for libnl4 I guess, since the libnl3 API
probably can't be changed now. I've caught quite a few errors and
memory leaks over the years by making sure accessors return 'const'
stuff.
Dan
> Changes v2:
> - Fixed memory leak
>
> Signed-off-by: Thomas Graf
> ---
> src/nm-device-ethernet.c | 35 ---
> src/nm-device-ethernet.h |2 ++
> src/nm-device.c|1 -
> src/nm-system.c| 32
> src/nm-system.h|2 ++
> src/nm-udev-manager.c | 14 --
> src/settings/nm-settings.c | 13 +++--
> 7 files changed, 91 insertions(+), 8 deletions(-)
>
> diff --git a/src/nm-device-ethernet.c b/src/nm-device-ethernet.c
> index 8556c5b..6e1471f 100644
> --- a/src/nm-device-ethernet.c
> +++ b/src/nm-device-ethernet.c
> @@ -55,6 +55,7 @@
> #include "nm-setting-wired.h"
> #include "nm-setting-8021x.h"
> #include "nm-setting-pppoe.h"
> +#include "nm-setting-bond.h"
> #include "ppp-manager/nm-ppp-manager.h"
> #include "nm-logging.h"
> #include "nm-properties-changed-signal.h"
> @@ -599,6 +600,22 @@ nm_device_ethernet_get_address (NMDeviceEthernet *self,
> struct ether_addr *addr)
> memcpy (addr, &priv->hw_addr, sizeof (priv->hw_addr));
> }
>
> +gboolean
> +nm_device_bond_connection_matches(NMDevice *device, NMConnection *connection)
> +{
> + NMSettingBond *s_bond;
> + const char *devname;
> +
> + devname = nm_device_get_iface (device);
> + g_assert(devname);
> +
> + s_bond = nm_connection_get_setting_bond (connection);
> + if (s_bond && !strcmp (devname, nm_setting_bond_get_interface_name
> (s_bond)))
> + return TRUE;
> +
> + return FALSE;
> +}
> +
> /* Returns speed in Mb/s */
> static guint32
> nm_device_ethernet_get_speed (NMDeviceEthernet *self)
> @@ -890,6 +907,14 @@ real_get_best_auto_connection (NMDevice *dev,
> g_assert (s_con);
>
> connection_type = nm_setting_connection_get_connection_type
> (s_con);
> +
> + if (!strcmp (connection_type, NM_SETTING_BOND_SETTING_NAME)) {
> + if (nm_device_bond_connection_matches (dev, connection))
> + return connection;
> +
> + continue;
> + }
> +
> if (!strcmp (connection_type, NM_SETTING_PPPOE_SETTING_NAME))
> is_pppoe = TRUE;
>
> @@ -1625,7 +1650,7 @@ real_check_connection_compatible (NMDevice *device,
> NMSettingConnection *s_con;
> NMSettingWired *s_wired;
> const char *connection_type;
> - gboolean is_pppoe = FALSE;
> + gboolean is_pppoe = FALSE, is_bond = FALSE;
> const GByteArray *mac;
> gboolean try_mac = TRUE;
> const GSList *mac_blacklist, *mac_blacklist_iter;
> @@ -1635,19 +1660,23 @@ real_check_connection_compatible (NMDevice *device,
>
> connection_type = nm_setting_connection_get_connection_type (s_con);
> if ( strcmp (connection_type, NM_SETTING_WIRED_SETTING_NAME)
> + && strcmp (connection_type, NM_SETTING_BOND_SETTING_NAME)
> && strcmp (connection_type, NM_SETTING_PPPOE_SETTING_NAME)) {
> g_set_error (error,
>NM_ETHERNET_ERROR,
> NM_ETHERNET_ERROR_CONNECTION_NOT_WIRED,
> - "The connection was not a wired or PPPoE
> connection.");
> + "The connection was not a wired, bond, or PPPoE
> connection.");
> return FALSE;
> }
>
> if (!strcmp (connection_type, NM_SETTING_PPPOE_SETTING_NAME))
> is_pppoe = TRUE;
>
> + if (!strcmp (connection_type, NM_SETTING_BOND_SETTING_NAME))
> + is_bond = TRUE;
> +
> s_wired = (NMSettingWired *) nm_connection_get_setting (connection,
> NM_TYPE_SETTING_WIRED);
> /* Wired setting is optional for PPPoE */
> - if (!is_pppoe && !s_wired) {
> + if (!is_pppoe && !s_wired && !is_bond) {
> g_set_error (error,
>NM_ETHERNET_ERROR,
> NM_ETHERNET_ERROR_CONNECTION_INVALID,
>"The connection was not a valid wired
> connection.");
> diff --git a/src/nm-device-ethernet.h b/src/nm-device-ethernet.h
> index b9e2afd..46db79e 100644
> --- a/src/nm-device-ethernet.h
> +++ b/src/nm-device-ethernet.h
> @@ -63,6 +63,8 @@ NMDevice *nm_device_ethernet_new (con
Re: ModemManager: [PATCH 1/2] Improvements to SIM PIN handling
OK, that explanation makes sense to me. I guess I wasn't quite getting your point previously. Part of my reluctance to implement the array of retry counts was, as you point out, the lack of clarity in 27.007 (and the related specs) about how subsidy and facility locks work. The fact that it talks about PUKs for all of the locks implies that you get a certain number of tries to enter a PIN correctly. But I haven't come across a modem yet that reports retries for anything besides SIM-PIN/PUK and SIM-PIN2/PUK2. So the array most likely will never have more than two elements. Or four, if we want to show PIN retries as 0 when a PUK is in effect. So here's what I think the new behavior will be: - If UnlockRequired has a non-empty value, then UnlockRetries will indicate the number of tries remaining for the lock that it specifies - If UnlockRequired is empty, then the value of UnlockRetries is not meaningful (but should probably be set to some fixed value, or should just be unset). - A new array-valued property, yet to be named, will always indicate the number of tries remaining for all lock types for which the information is available. When UnlockRequired has a non-empty value, the item in the array for that lock will be the same as the value of UnlockRetries. I'm not sure whether this will actually make things easier for the developer, but at least it allows for a simple explanation of the purpose of each property. Eric On Fri, Nov 4, 2011 at 1:11 PM, Dan Williams wrote: > On Tue, 2011-11-01 at 14:45 -0400, Eric Shienbrood wrote: > > Back from vacation, catching up... > > > > On Wed, Oct 26, 2011 at 8:44 PM, Dan Williams wrote: > > On Wed, 2011-10-19 at 15:42 -0400, Eric Shienbrood wrote: > > > > > > I wonder if we shouldn't keep the change/disable retries > > separate from > > the unlock retries though. I'm not 100% comfortable with > > having a > > situation where UnlockRetries means one thing if > > UnlockRequired is this, > > and another thing if it's this other thing. These two > > operations > > (change/disable) don't block the modem from operating, so they > > are in a > > second class. Which probably merit their own properties > > instead? > > > > > > I don't see in what way UnlockRetries means two different things. I > > thought it just meant the number of retries before the next level of > > security kicks in. If you enter the SIM PIN incorrectly three times, > > whether it's for unlock, change, or enable/disable, then the SIM > > becomes locked and requires the PUK to be entered to unlock it. As far > > as I can tell from the modems I've tested on, there's no concept of > > ChangeRetries vs. UnlockRetries, there's just Retries. In other words, > > the effect of entering the PIN incorrectly three times is the same in > > all cases - the modem won't operate until the PUK is entered. This may > > make the rest of the following discussion moot, but here goes anyway: > > Ok, fair enough. It's a bit confusing when some modems like Huawei > allow you to get the # retries for the current unlock (^CARDLOCK) *and* > the # retries for multiple operations at the same time (^CPIN returns > tries for PUK, PIN, PUK2, and PIN2 in the same command). There's also > the subsidy lock for the device, and facility locks. It's unclear to me > from 27.007 whether the they talk about is one set explicitly > with CLCK when the facility is locked, or whether it's the > PIN/PUK/PIN2/PUK2 or what. So there's a lot of locks running around > here, and it was somewhat unclear what UnlockRetries was really supposed > to be talking about. Initially it was supposed to be only the # retries > allowed for the current unlock request specified in UnlockRequired, and > when UnlockRequired was NULL, UnlockRetries would also be NULL, since > otherwise there's no way to know what UnlockRetries specifies the number > of retries for (given all the different locks and their retries). > > Which spawned the discussion of "how can we keep the required code > (pin/puk/facility/whatever) together with the # of retries for that > specific item". > > When you want to change your PIN code, the modem is already unlocked, > and thus UnlockRequired would be NULL/"". So when you try to change the > PIN and enter the PIN wrong, it wouldn't make a ton of sense to change > UnlockRetries to some value and keep UnlockRequired NULL/"" since that > breaks the contract between them. > > Which is why (if I remember last week correctly) I was trying to add > another property which contained all the unlocks and their respective > retries, regardless of what state the modem was in at that point in > time. My thought was that UnlockRequired/UnlockRetries would be what > was needed to make the modem function *now*, but other stuff could be > punted to the Big Unlock Array that also contained the # retries for > each item.
Re: personalize network manager
On Fri, 2011-11-04 at 11:53 -0500, Dan Williams wrote: > On Fri, 2011-11-04 at 13:39 +0100, Diana de Lara del Rey wrote: > > I've trying to personalize my network manager. In the code of network > > manager applet, I want to have a configuration that anyone can't > > modify, otherwise I like that when any of my users try to connect to > > mi wireless, the network interface shows all the fields with a > > configuration that they can't change, similar to the attached image. > > In NetworkManager this is handled by PolicyKit permissions. You > basically don't give users the permission to modify the connection at > all, and you make the connection a "system connection". In NM 0.9, you > can also make this connection visible only to the user in question. An > overview of how all this works is here: > > http://live.gnome.org/NetworkManager/ApiSimplify > > So for NM 0.9 you'd either require the user to authenticate themselves > with the root password, or you'd just deny them the ability to edit > system connections at all by changing the > org.freedesktop.NetworkManager.settings.modify.system and > org.freedesktop.NetworkManager.settings.modify.own permissions to "no" > or "auth_admin_keep". > > But the screenshot you've attached shows that you're using > NetworkManager 0.8.x, where the permissions model isn't quite as > flexible. There, you'd need to create a "system wide" connection (check > "Available to all users" in nm-connection-editor) and change the > org.freedesktop.network-manager-settings.system.modify permission to > "no" or "auth_admin_keep". This does mean that this connection will be > available to all users, of course, including the password. NM 0.9 fixes > this and allows it to be available only to one or more users which you > as the sysadmin specify. More on PolicyKit here: http://hal.freedesktop.org/docs/polkit/pklocalauthority.8.html Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ModemManager: [PATCH 1/2] Improvements to SIM PIN handling
On Tue, 2011-11-01 at 14:45 -0400, Eric Shienbrood wrote:
> Back from vacation, catching up...
>
> On Wed, Oct 26, 2011 at 8:44 PM, Dan Williams wrote:
> On Wed, 2011-10-19 at 15:42 -0400, Eric Shienbrood wrote:
>
>
> I wonder if we shouldn't keep the change/disable retries
> separate from
> the unlock retries though. I'm not 100% comfortable with
> having a
> situation where UnlockRetries means one thing if
> UnlockRequired is this,
> and another thing if it's this other thing. These two
> operations
> (change/disable) don't block the modem from operating, so they
> are in a
> second class. Which probably merit their own properties
> instead?
>
>
> I don't see in what way UnlockRetries means two different things. I
> thought it just meant the number of retries before the next level of
> security kicks in. If you enter the SIM PIN incorrectly three times,
> whether it's for unlock, change, or enable/disable, then the SIM
> becomes locked and requires the PUK to be entered to unlock it. As far
> as I can tell from the modems I've tested on, there's no concept of
> ChangeRetries vs. UnlockRetries, there's just Retries. In other words,
> the effect of entering the PIN incorrectly three times is the same in
> all cases - the modem won't operate until the PUK is entered. This may
> make the rest of the following discussion moot, but here goes anyway:
Ok, fair enough. It's a bit confusing when some modems like Huawei
allow you to get the # retries for the current unlock (^CARDLOCK) *and*
the # retries for multiple operations at the same time (^CPIN returns
tries for PUK, PIN, PUK2, and PIN2 in the same command). There's also
the subsidy lock for the device, and facility locks. It's unclear to me
from 27.007 whether the they talk about is one set explicitly
with CLCK when the facility is locked, or whether it's the
PIN/PUK/PIN2/PUK2 or what. So there's a lot of locks running around
here, and it was somewhat unclear what UnlockRetries was really supposed
to be talking about. Initially it was supposed to be only the # retries
allowed for the current unlock request specified in UnlockRequired, and
when UnlockRequired was NULL, UnlockRetries would also be NULL, since
otherwise there's no way to know what UnlockRetries specifies the number
of retries for (given all the different locks and their retries).
Which spawned the discussion of "how can we keep the required code
(pin/puk/facility/whatever) together with the # of retries for that
specific item".
When you want to change your PIN code, the modem is already unlocked,
and thus UnlockRequired would be NULL/"". So when you try to change the
PIN and enter the PIN wrong, it wouldn't make a ton of sense to change
UnlockRetries to some value and keep UnlockRequired NULL/"" since that
breaks the contract between them.
Which is why (if I remember last week correctly) I was trying to add
another property which contained all the unlocks and their respective
retries, regardless of what state the modem was in at that point in
time. My thought was that UnlockRequired/UnlockRetries would be what
was needed to make the modem function *now*, but other stuff could be
punted to the Big Unlock Array that also contained the # retries for
each item. That way we keep a simpler, more understandable interface,
and provide the ability for retries for actions that don't prevent the
modem from working at the time they are performed.
Dan
>
> So the question becomes, as a user, are there any PINs other
> than SIM-PIN
> which the user themselves can change?
>
>
> The call barring services allow the user to change passwords, but call
> barring only applies in the CS domain, so does ModemManager care about
> it? The other category of locks is the personalization locks, but my
> reading of 3gpp TS 22.022 is that the passwords can't be changed by
> the user. So that just leaves SIM PIN and SIM PIN2 as changeable. On
> the other hand, the AT+CPWD command takes a facility name as the first
> argument, implying changeability for all locks. Which one should be
> believed?
>
>
> If not, then a single u32
> property for ChangeRetries would be good. I know there are
> other PINs
> that can be disabled (SIM-PIN, network block/simlock, etc) so
> that one
> might warrant a dict or an array of { "sim-pin": 4, "ph-net
> pin": 10 }
> etc. All on the Gsm.Card interface (for 0.5...).
>
>
> The SIM locks can both be disabled/enabled and unlocked. As far as I
> can tell, the personalization locks can only be enabled/disabled. And
> I think the user can only disable, not enable. But in any case, I'll
> go back to my original argument that you only really care about the
> retry count for the PIN currently being asked for, and that it's not
> worth the complexity needed to maintain
Re: [PATCH 2/2] MM: internal_queue_command(): Reject new commands when the port is closed.
On Thu, 2011-11-03 at 17:37 -0400, Nathan Williams wrote: > This is the actual crasher. Pushed, thanks. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mobile-broadband-provider-info: Request for msisdn-query tag to be added
On Fri, 2011-11-04 at 09:35 +0200, Graham Inggs wrote: > There is often a need to query the MSISDN (mobile telephone number) > associated with a GSM SIM card, for example when doing a pre-paid > top-up over the internet or when calling the network operator's > technical support. Because this number can change, the only reliable > way of obtaining it is directly from the network operator. > > Most Vodafone network operators and all of the network operators in > South Africa support querying the MSISDN by USSD, for example sending > '*111*501#' for Vodacom South Africa. > > Would it be possible to extend the mobile-broadband-provider-info > database to include a msisdn-query tag please? Sure, care to post patches for it? Seems useful. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: personalize network manager
On Fri, 2011-11-04 at 13:39 +0100, Diana de Lara del Rey wrote: > I've trying to personalize my network manager. In the code of network > manager applet, I want to have a configuration that anyone can't > modify, otherwise I like that when any of my users try to connect to > mi wireless, the network interface shows all the fields with a > configuration that they can't change, similar to the attached image. In NetworkManager this is handled by PolicyKit permissions. You basically don't give users the permission to modify the connection at all, and you make the connection a "system connection". In NM 0.9, you can also make this connection visible only to the user in question. An overview of how all this works is here: http://live.gnome.org/NetworkManager/ApiSimplify So for NM 0.9 you'd either require the user to authenticate themselves with the root password, or you'd just deny them the ability to edit system connections at all by changing the org.freedesktop.NetworkManager.settings.modify.system and org.freedesktop.NetworkManager.settings.modify.own permissions to "no" or "auth_admin_keep". But the screenshot you've attached shows that you're using NetworkManager 0.8.x, where the permissions model isn't quite as flexible. There, you'd need to create a "system wide" connection (check "Available to all users" in nm-connection-editor) and change the org.freedesktop.network-manager-settings.system.modify permission to "no" or "auth_admin_keep". This does mean that this connection will be available to all users, of course, including the password. NM 0.9 fixes this and allows it to be available only to one or more users which you as the sysadmin specify. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: SMS receiving question
On Fri, 2011-11-04 at 11:36 -0500, Dan Williams wrote: > On Fri, 2011-11-04 at 17:20 +0100, Jean Parpaillon wrote: > > Hi, > > > > Le vendredi 04 novembre 2011 à 11:14 -0500, Dan Williams a écrit : > > > On Fri, 2011-11-04 at 09:20 -0400, Nathan Williams wrote: > > > > Do you have logs from ModemManager? If you run with --log-level=DEBUG, > > > > you should see the +CMTI notification when the SMS arrives, and we can > > > > see what MM does from that point forward. > > > > > > Via IRC yesterday, > > > > You may be confusing, I am not on the chan. But I should, and I will :) > > Sorry! Somebody else was, and had the exact same question, so I just > assumed it was you :) So to debug, grab ModemManager debug output like it says here: http://live.gnome.org/NetworkManager/Debugging and see what MM says when it sends the CNMI command. If it errors out, try using screen or minicom and asking the modem what values it supports using: AT+CNMI=? like is shown below. Also, what modem? Dan > Dan > > > > he said that he's got a Huawei E1550 ( I think I have > > > one too) and that it responded with CMS ERROR: 303 to the AT > > > +CNMI=2,1,2,1,0 request that MM sends. Which is odd, because those > > > appear to be legal values: > > > > > > AT+CNMI=? > > > +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1) > > > > > > so obviously something isn't quite working with this device and the SIM > > > card, and because we can't set the message storage the CMTI > > > notification isn't happening. > > > > > > Dan > > > > > > > - Nathan > > > > > > > > On Fri, Nov 4, 2011 at 6:12 AM, Jean Parpaillon > > > > wrote: > > > > > Hi all, > > > > > I am using ModemManager to receive SMS with a Huawei E1752 USB modem. > > > > > I am plugged on signal SmsReceived but I receive nothing. I used ofono > > > > > stack to do the same things and it worked, but I can not run both > > > > > ofono > > > > > and ModemManager at the same time. > > > > > > > > > > Do you know if my issue comes from this particular modem or is a > > > > > known > > > > > ModemManager issue ? > > > > > > > > > > Best regards, > > > > > -- > > > > > Jean Parpaillon > > > > > Pulse2 project leader > > > > > > > > > > Mandriva SA - http://mandriva.com > > > > > Rennes - FR > > > > > Phone: +33 6 30 10 92 86 > > > > > email: jparpail...@mandriva.com > > > > > jabber: jean.parpail...@gmail.com > > > > > skype: jean.parpaillon > > > > > > > > > > ___ > > > > > 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 ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: SMS receiving question
On Fri, 2011-11-04 at 17:20 +0100, Jean Parpaillon wrote: > Hi, > > Le vendredi 04 novembre 2011 à 11:14 -0500, Dan Williams a écrit : > > On Fri, 2011-11-04 at 09:20 -0400, Nathan Williams wrote: > > > Do you have logs from ModemManager? If you run with --log-level=DEBUG, > > > you should see the +CMTI notification when the SMS arrives, and we can > > > see what MM does from that point forward. > > > > Via IRC yesterday, > > You may be confusing, I am not on the chan. But I should, and I will :) Sorry! Somebody else was, and had the exact same question, so I just assumed it was you :) Dan > > he said that he's got a Huawei E1550 ( I think I have > > one too) and that it responded with CMS ERROR: 303 to the AT > > +CNMI=2,1,2,1,0 request that MM sends. Which is odd, because those > > appear to be legal values: > > > > AT+CNMI=? > > +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1) > > > > so obviously something isn't quite working with this device and the SIM > > card, and because we can't set the message storage the CMTI > > notification isn't happening. > > > > Dan > > > > > - Nathan > > > > > > On Fri, Nov 4, 2011 at 6:12 AM, Jean Parpaillon > > > wrote: > > > > Hi all, > > > > I am using ModemManager to receive SMS with a Huawei E1752 USB modem. > > > > I am plugged on signal SmsReceived but I receive nothing. I used ofono > > > > stack to do the same things and it worked, but I can not run both ofono > > > > and ModemManager at the same time. > > > > > > > > Do you know if my issue comes from this particular modem or is a known > > > > ModemManager issue ? > > > > > > > > Best regards, > > > > -- > > > > Jean Parpaillon > > > > Pulse2 project leader > > > > > > > > Mandriva SA - http://mandriva.com > > > > Rennes - FR > > > > Phone: +33 6 30 10 92 86 > > > > email: jparpail...@mandriva.com > > > > jabber: jean.parpail...@gmail.com > > > > skype: jean.parpaillon > > > > > > > > ___ > > > > 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: SMS receiving question
Hi, Le vendredi 04 novembre 2011 à 11:14 -0500, Dan Williams a écrit : > On Fri, 2011-11-04 at 09:20 -0400, Nathan Williams wrote: > > Do you have logs from ModemManager? If you run with --log-level=DEBUG, > > you should see the +CMTI notification when the SMS arrives, and we can > > see what MM does from that point forward. > > Via IRC yesterday, You may be confusing, I am not on the chan. But I should, and I will :) > he said that he's got a Huawei E1550 ( I think I have > one too) and that it responded with CMS ERROR: 303 to the AT > +CNMI=2,1,2,1,0 request that MM sends. Which is odd, because those > appear to be legal values: > > AT+CNMI=? > +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1) > > so obviously something isn't quite working with this device and the SIM > card, and because we can't set the message storage the CMTI > notification isn't happening. > > Dan > > > - Nathan > > > > On Fri, Nov 4, 2011 at 6:12 AM, Jean Parpaillon > > wrote: > > > Hi all, > > > I am using ModemManager to receive SMS with a Huawei E1752 USB modem. > > > I am plugged on signal SmsReceived but I receive nothing. I used ofono > > > stack to do the same things and it worked, but I can not run both ofono > > > and ModemManager at the same time. > > > > > > Do you know if my issue comes from this particular modem or is a known > > > ModemManager issue ? > > > > > > Best regards, > > > -- > > > Jean Parpaillon > > > Pulse2 project leader > > > > > > Mandriva SA - http://mandriva.com > > > Rennes - FR > > > Phone: +33 6 30 10 92 86 > > > email: jparpail...@mandriva.com > > > jabber: jean.parpail...@gmail.com > > > skype: jean.parpaillon > > > > > > ___ > > > 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 > > > -- Jean Parpaillon Pulse2 project leader Mandriva SA - http://mandriva.com Rennes - FR Phone: +33 6 30 10 92 86 email: jparpail...@mandriva.com jabber: jean.parpail...@gmail.com skype: jean.parpaillon 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: SMS receiving question
On Fri, 2011-11-04 at 09:20 -0400, Nathan Williams wrote: > Do you have logs from ModemManager? If you run with --log-level=DEBUG, > you should see the +CMTI notification when the SMS arrives, and we can > see what MM does from that point forward. Via IRC yesterday, he said that he's got a Huawei E1550 ( I think I have one too) and that it responded with CMS ERROR: 303 to the AT +CNMI=2,1,2,1,0 request that MM sends. Which is odd, because those appear to be legal values: AT+CNMI=? +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1) so obviously something isn't quite working with this device and the SIM card, and because we can't set the message storage the CMTI notification isn't happening. Dan > - Nathan > > On Fri, Nov 4, 2011 at 6:12 AM, Jean Parpaillon > wrote: > > Hi all, > > I am using ModemManager to receive SMS with a Huawei E1752 USB modem. > > I am plugged on signal SmsReceived but I receive nothing. I used ofono > > stack to do the same things and it worked, but I can not run both ofono > > and ModemManager at the same time. > > > > Do you know if my issue comes from this particular modem or is a known > > ModemManager issue ? > > > > Best regards, > > -- > > Jean Parpaillon > > Pulse2 project leader > > > > Mandriva SA - http://mandriva.com > > Rennes - FR > > Phone: +33 6 30 10 92 86 > > email: jparpail...@mandriva.com > > jabber: jean.parpail...@gmail.com > > skype: jean.parpaillon > > > > ___ > > 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: nm-connection-editor working only as root
On Fri, 2011-11-04 at 11:48 +0100, Ramon Diaz-Uriarte wrote: > > > On Wed, 02 Nov 2011 20:31:41 -0500,Dan Williams wrote: > > On Mon, 2011-10-24 at 11:48 +0200, Ramon Diaz-Uriarte wrote: > > > Actually, three problems remain ;-). > > > > > > > > > 1. I've rebooted and reloged in several times, but I cannot save a > > > connection because it complaints about insufficient privileges. (I get a > > > pop-up message that says "Connection add failed", "Insufficient > > > privileges"). > > > > > > > > > I have logged with kdm (or gdm) and have a local session: > > > > > > ramon@Bufo:~$ ck-list-sessions > > > Session1: > > > unix-user = '1000' > > > realname = 'ramon diaz-uriarte' > > > seat = 'Seat1' > > > session-type = '' > > > active = TRUE > > > x11-display = ':0' > > > x11-display-device = '/dev/tty7' > > > display-device = '' > > > remote-host-name = '' > > > is-local = TRUE > > > on-since = '2011-10-23T16:29:00.632372Z' > > > login-session-id = '4294967295' > > > Is this an update or a new connection? This error is coming from > > PolicyKit, so does this work if you edit the file: > > > /usr/share/polkit-1/actions/org.freedesktop.network-manager-settings.system.policy > > > and change the following hunk to: > > > > > <_description>Modify system connections > > <_message>System policy prevents modification of system > > settings > > > > yes > > auth_admin_keep > > > > > > > then try. If that doesn't work, change it to: > > > > > <_description>Modify system connections > > <_message>System policy prevents modification of system > > settings > > > > yes > > yes > > > > > > > no reboot or anything is necessary, the changes take effect immediately. > > > I tried both (note: there were minor differences in syntax, like mine is > called NetworkManager, not network-manager, etc). > > The first one did not work, but the second did. Thanks a lot. Ok, this is good to know. We now know that your user was marked as 'active' via ConsoleKit (which PolicyKit talks to) but for some reason PolicyKit wasn't able to show the authentication dialog. If you're using a GNOME desktop, do you have the "polkit-gnome-authentication-agent-1" program anywhere in /usr/libexec or /usr/lib or /usr/lib64 or /usr/bin ? If you're not on a GNOME desktop, do you ever see PolicyKit authentication dialogs? > Best, > > > R. > > > > > Dan > > > > > > > 2. There is the problem of not being able to access my previously defined > > > connections (versions 0.8.1). They must be somewhere, but the new versions > > > do not seem to be able to find them. > > > > > > > > > > > > 3. Finally, connections saved using, say, gksudo nm-connection-editor are > > > stored under > > > /etc/NetworkManager/system-connections > > > > > > with passwords, etc, as plain text. Sure, they are only readable to root, > > > but ssn't this a potential problem? If I remember correctly, with previous > > > versions, you could only access connections (and their passwords) after > > > entering your password via keyring. > > > > > > > > > Best, > > > > > > R. > > > > > > > > > > > > On Fri, 21 Oct 2011 22:17:01 +0200,Ramon Diaz-Uriarte > > > wrote: > > > > > > > > > > > > > On Fri, 21 Oct 2011 21:16:25 +0200,Michael Biebl > > > > wrote: > > > > > [1 ] > > > > > Am 21.10.2011 21:14, schrieb Ramon Diaz-Uriarte: > > > > > > > > > > > > > > > > > > On Fri, 21 Oct 2011 16:42:52 +0200,Michael Biebl > > > > > > wrote: > > > > > >> Am 21.10.2011 13:44, schrieb Ramon Diaz-Uriarte: > > > > > > > > > > > >> What's the output of ck-list-sessions? > > > > > > > > > > > > > > > > > > Session5: > > > > > > active = FALSE > > > > > > is-local = FALSE > > > > > > > > That's your problem. Use a login manager, like gdm or kdm, which > > > > > properly registers a ConsoleKit session. > > > > > Otherwise the PolicyKit rules used by NM won't work. > > > > > > > Login with gdm does work, but only partially. I can now add and edit > > > > connections as non-root (ck-list-sessions now lists two local > > > > sessions). But the long list of wireless connections I had defined > > > > (prior > > > > to 0.9) is not there. Is there anyway to get those back? > > > > > > > > > > As well, can I get the PolicyKit rules to work with other login > > > > managers? > > > > I use wdm, but the trick of adding > > > > > > > exec ck-launch-session xmonad > > > > > > > at the end of my .xinitrc does not seem to work. > > > > > > > > > > Thanks, > > > > > > > > > > R. > > > > > > > > > > > > > > > > > Michael > > > > > > > > -- > > > > > Why is it that all of the instruments seeking intelligent life in the > > > > > universe are pointed away from Earth? > > > > > > > > [2 OpenPGP digital signature ] > > > > > > > -- > > > > Ramon Diaz-Uriarte > > > > Department of Bioch
Re: nm-connection-editor working only as root
Em 24/10/2011 07:48, "Ramon Diaz-Uriarte" escreveu: > > > Actually, three problems remain ;-). > > > 1. I've rebooted and reloged in several times, but I cannot save a > connection because it complaints about insufficient privileges. (I get a > pop-up message that says "Connection add failed", "Insufficient > privileges"). Seems that you've left files owned by root in your profile. Try to chmod all your home directory back to your user. > > > I have logged with kdm (or gdm) and have a local session: > > ramon@Bufo:~$ ck-list-sessions > Session1: >unix-user = '1000' >realname = 'ramon diaz-uriarte' >seat = 'Seat1' >session-type = '' >active = TRUE >x11-display = ':0' >x11-display-device = '/dev/tty7' >display-device = '' >remote-host-name = '' >is-local = TRUE >on-since = '2011-10-23T16:29:00.632372Z' >login-session-id = '4294967295' > > > 2. There is the problem of not being able to access my previously defined > connections (versions 0.8.1). They must be somewhere, but the new versions > do not seem to be able to find them. > > > > 3. Finally, connections saved using, say, gksudo nm-connection-editor are > stored under > /etc/NetworkManager/system-connections > > with passwords, etc, as plain text. Sure, they are only readable to root, > but ssn't this a potential problem? If I remember correctly, with previous > versions, you could only access connections (and their passwords) after > entering your password via keyring. > > > Best, > > R. > > > > On Fri, 21 Oct 2011 22:17:01 +0200,Ramon Diaz-Uriarte wrote: > > > > > On Fri, 21 Oct 2011 21:16:25 +0200,Michael Biebl wrote: > > > [1 ] > > > Am 21.10.2011 21:14, schrieb Ramon Diaz-Uriarte: > > > > > > > > > > > > On Fri, 21 Oct 2011 16:42:52 +0200,Michael Biebl wrote: > > > >> Am 21.10.2011 13:44, schrieb Ramon Diaz-Uriarte: > > > > > > > >> What's the output of ck-list-sessions? > > > > > > > > > > > > Session5: > > > > active = FALSE > > > > is-local = FALSE > > > > That's your problem. Use a login manager, like gdm or kdm, which > > > properly registers a ConsoleKit session. > > > Otherwise the PolicyKit rules used by NM won't work. > > > Login with gdm does work, but only partially. I can now add and edit > > connections as non-root (ck-list-sessions now lists two local > > sessions). But the long list of wireless connections I had defined (prior > > to 0.9) is not there. Is there anyway to get those back? > > > > As well, can I get the PolicyKit rules to work with other login managers? > > I use wdm, but the trick of adding > > > exec ck-launch-session xmonad > > > at the end of my .xinitrc does not seem to work. > > > > Thanks, > > > > R. > > > > > > > Michael > > > > -- > > > Why is it that all of the instruments seeking intelligent life in the > > > universe are pointed away from Earth? > > > > [2 OpenPGP digital signature ] > > > -- > > Ramon Diaz-Uriarte > > Department of Biochemistry > > Universidad Autónoma de Madrid > > Spain > > > http://ligarto.org/rdiaz > > > Temporarily at: > > Structural Biology and Biocomputing Programme > > Spanish National Cancer Centre (CNIO) > > > Phone: +34-91-732-8000 ext. 3019 > > Fax: +-34-91-224-6972 > -- > Ramon Diaz-Uriarte > Department of Biochemistry > Universidad Autónoma de Madrid > Spain > > http://ligarto.org/rdiaz > > Temporarily at: > Structural Biology and Biocomputing Programme > Spanish National Cancer Centre (CNIO) > > Phone: +34-91-732-8000 ext. 3019 > Fax: +-34-91-224-6972 > ___ > 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: SMS receiving question
Do you have logs from ModemManager? If you run with --log-level=DEBUG, you should see the +CMTI notification when the SMS arrives, and we can see what MM does from that point forward. - Nathan On Fri, Nov 4, 2011 at 6:12 AM, Jean Parpaillon wrote: > Hi all, > I am using ModemManager to receive SMS with a Huawei E1752 USB modem. > I am plugged on signal SmsReceived but I receive nothing. I used ofono > stack to do the same things and it worked, but I can not run both ofono > and ModemManager at the same time. > > Do you know if my issue comes from this particular modem or is a known > ModemManager issue ? > > Best regards, > -- > Jean Parpaillon > Pulse2 project leader > > Mandriva SA - http://mandriva.com > Rennes - FR > Phone: +33 6 30 10 92 86 > email: jparpail...@mandriva.com > jabber: jean.parpail...@gmail.com > skype: jean.parpaillon > > ___ > 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-connection-editor working only as root
On Wed, 02 Nov 2011 20:31:41 -0500,Dan Williams wrote: > On Mon, 2011-10-24 at 11:48 +0200, Ramon Diaz-Uriarte wrote: > > Actually, three problems remain ;-). > > > > > > 1. I've rebooted and reloged in several times, but I cannot save a > > connection because it complaints about insufficient privileges. (I get a > > pop-up message that says "Connection add failed", "Insufficient > > privileges"). > > > > > > I have logged with kdm (or gdm) and have a local session: > > > > ramon@Bufo:~$ ck-list-sessions > > Session1: > > unix-user = '1000' > > realname = 'ramon diaz-uriarte' > > seat = 'Seat1' > > session-type = '' > > active = TRUE > > x11-display = ':0' > > x11-display-device = '/dev/tty7' > > display-device = '' > > remote-host-name = '' > > is-local = TRUE > > on-since = '2011-10-23T16:29:00.632372Z' > > login-session-id = '4294967295' > Is this an update or a new connection? This error is coming from > PolicyKit, so does this work if you edit the file: > /usr/share/polkit-1/actions/org.freedesktop.network-manager-settings.system.policy > and change the following hunk to: > > <_description>Modify system connections > <_message>System policy prevents modification of system > settings > > yes > auth_admin_keep > > > then try. If that doesn't work, change it to: > > <_description>Modify system connections > <_message>System policy prevents modification of system > settings > > yes > yes > > > no reboot or anything is necessary, the changes take effect immediately. I tried both (note: there were minor differences in syntax, like mine is called NetworkManager, not network-manager, etc). The first one did not work, but the second did. Thanks a lot. Best, R. > Dan > > > > 2. There is the problem of not being able to access my previously defined > > connections (versions 0.8.1). They must be somewhere, but the new versions > > do not seem to be able to find them. > > > > > > > > 3. Finally, connections saved using, say, gksudo nm-connection-editor are > > stored under > > /etc/NetworkManager/system-connections > > > > with passwords, etc, as plain text. Sure, they are only readable to root, > > but ssn't this a potential problem? If I remember correctly, with previous > > versions, you could only access connections (and their passwords) after > > entering your password via keyring. > > > > > > Best, > > > > R. > > > > > > > > On Fri, 21 Oct 2011 22:17:01 +0200,Ramon Diaz-Uriarte > > wrote: > > > > > > > > > On Fri, 21 Oct 2011 21:16:25 +0200,Michael Biebl wrote: > > > > [1 ] > > > > Am 21.10.2011 21:14, schrieb Ramon Diaz-Uriarte: > > > > > > > > > > > > > > > On Fri, 21 Oct 2011 16:42:52 +0200,Michael Biebl > > > > > wrote: > > > > >> Am 21.10.2011 13:44, schrieb Ramon Diaz-Uriarte: > > > > > > > > > >> What's the output of ck-list-sessions? > > > > > > > > > > > > > > > Session5: > > > > > active = FALSE > > > > > is-local = FALSE > > > > > > That's your problem. Use a login manager, like gdm or kdm, which > > > > properly registers a ConsoleKit session. > > > > Otherwise the PolicyKit rules used by NM won't work. > > > > > Login with gdm does work, but only partially. I can now add and edit > > > connections as non-root (ck-list-sessions now lists two local > > > sessions). But the long list of wireless connections I had defined (prior > > > to 0.9) is not there. Is there anyway to get those back? > > > > > > > As well, can I get the PolicyKit rules to work with other login managers? > > > I use wdm, but the trick of adding > > > > > exec ck-launch-session xmonad > > > > > at the end of my .xinitrc does not seem to work. > > > > > > > Thanks, > > > > > > > R. > > > > > > > > > > > > Michael > > > > > > -- > > > > Why is it that all of the instruments seeking intelligent life in the > > > > universe are pointed away from Earth? > > > > > > [2 OpenPGP digital signature ] > > > > > -- > > > Ramon Diaz-Uriarte > > > Department of Biochemistry > > > Universidad Autónoma de Madrid > > > Spain > > > > > http://ligarto.org/rdiaz > > > > > Temporarily at: > > > Structural Biology and Biocomputing Programme > > > Spanish National Cancer Centre (CNIO) > > > > > Phone: +34-91-732-8000 ext. 3019 > > > Fax: +-34-91-224-6972 -- Ramon Diaz-Uriarte Department of Biochemistry, Lab B-25. Facultad de Medicina (UAM) Arzobispo Morcillo, 2 28029 Madrid Spain Phone: +34-91-497-2412 Email: rdia...@gmail.com ramon.d...@iib.uam.es http://ligarto.org/rdiaz ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
SMS receiving question
Hi all, I am using ModemManager to receive SMS with a Huawei E1752 USB modem. I am plugged on signal SmsReceived but I receive nothing. I used ofono stack to do the same things and it worked, but I can not run both ofono and ModemManager at the same time. Do you know if my issue comes from this particular modem or is a known ModemManager issue ? Best regards, -- Jean Parpaillon Pulse2 project leader Mandriva SA - http://mandriva.com Rennes - FR Phone: +33 6 30 10 92 86 email: jparpail...@mandriva.com jabber: jean.parpail...@gmail.com skype: jean.parpaillon 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: OpenVpn plugin NeedSecret
[SOLVED]
I've solved the problem. Thanks a lot to Dan for his support.
I've added all secrets into
/etc/NetworkManager/system-connection/VPNconn...below the correct structure:
[connection]
id=VPNconn
uuid=355653c0-34d3-4777-ad25-f9a498b7ef8e
type=vpn
autoconnect=FALSE
[ipv4]
method=auto
[vpn]
name=openvpn
service-type=org.freedesktop.NetworkManager.openvpn
connection-type=tls
remote=xx..xx.it
proto-tcp=no
reneg-seconds=0
port=1194
ca=/etc/openvpn/certs/cacert.crt
cert=/etc/openvpn/certs/x.pem
key=/etc/openvpn/certs/xx-key.pem
comp-lzo=yes
[ipv6]
method=ignore
Reagards
On Thu, Nov 3, 2011 at 4:43 PM, Dan Williams wrote:
> On Thu, 2011-11-03 at 16:03 +0100, Francesco Andrisani wrote:
> > Thanks a lot. But i'm not able to know all parameter to intert into
> > my /etc/NetworkManager/system-connections/VPNconnection.
> >
> > For example keyfile, certficate, ecc
> >
> > Please can you tell me how to find these informations (all
> > parameters)?
>
> At the moment the best way to do this is to edit the connection with
> nm-connection-editor; otherwise it's a bit byzantine but the list of
> acceptable parameters is here:
>
>
> http://git.gnome.org/browse/network-manager-openvpn/tree/src/nm-openvpn-service.h
>
> and the values that these keys can contain are in the code, but it's
> probably non-trivial to pull them out. I can see where documenting the
> acceptable values in the header there would be a nice thing to do.
> Otherwise, if you have a config file you're importing from that would
> work, or I can help you figure out what to use if you can describe your
> VPN setup more. Or nm-connection-editor.
>
> Dan
>
>
> > Thanks and regards
> >
> > On Thu, Nov 3, 2011 at 3:51 PM, Dan Williams wrote:
> > On Thu, 2011-11-03 at 10:26 +0100, Francesco Andrisani wrote:
> > > Anothe DEBUG info:
> > >
> > > debian:/etc/NetworkManager# /usr/libexec/nm-openvpn-service
> > --debug
> > > ** Message: nm-openvpn-service (version 0.9.0) starting...
> > > ** Message: real_need_secrets: connection
> > > -
> > > connection
> > > name : "connection"
> > > id : "VPNconnection" (s)
> > > uuid : "355653c0-34d3-4777-ad25-f9a498b7ef8e" (s)
> > > type : "vpn" (s)
> > > permissions : [] (sd)
> > > autoconnect : FALSE (s)
> > > timestamp : 0 (sd)
> > > read-only : FALSE (sd)
> > >
> > >
> > > ipv4
> > > name : "ipv4"
> > > method : "auto" (s)
> > > dns : [] (s)
> > > dns-search : [] (sd)
> > > addresses : [] (s)
> > > routes : [] (s)
> > > ignore-auto-routes : FALSE (sd)
> > > ignore-auto-dns : FALSE (sd)
> > > dhcp-client-id : NULL (sd)
> > > dhcp-send-hostname : TRUE (sd)
> > > dhcp-hostname : NULL (sd)
> > > never-default : FALSE (sd)
> > > may-fail : FALSE (sd)
> > >
> > >
> > > ipv6
> > > name : "ipv6"
> > > method : "ignore" (s)
> > > dns : [] (s)
> > > dns-search : [] (sd)
> > > addresses : [] (s)
> > > routes : [] (s)
> > > ignore-auto-routes : FALSE (sd)
> > > ignore-auto-dns : FALSE (sd)
> > > never-default : FALSE (sd)
> > > may-fail : TRUE (sd)
> > >
> > >
> > > vpn
> > > name : "vpn"
> > > service-type :
> > "org.freedesktop.NetworkManager.openvpn" (s)
> > > user-name : NULL (sd)
> > > data : [ { 'name': openvpn }, ] (s)
> > > secrets : [ ] (s)
> >
> >
> > So here's the problem; the [vpn] setting isn't completely
> > specified.
> > Did you import this connection from an openvpn config file?
> > Unless this
> > was changed at some point (or there's a bug in the editor)
> > this
> > connection was never valid since it doesn't have the required
> > connection
> > type field and a few other things. Here's what it *should*
> > look like:
> >
> > [vpn]
> > service-type=org.freedesktop.NetworkManager.openvpn
> > connection-type=password
> > password-flags=3
> > remote=ovpn.mycompany.com
> > cipher=AES-256-CBC
> > proto-tcp=yes
> > reneg-seconds=0
> > port=443
> > username=dcbw
> > ca=/home/dcbw/MyCA.pem
> >
> > or something along those lines. If you imported it from a
> > config file,
> > can you try doing that again? If it still looks like this,
> > can you send
> > me the config file so I can see what's going wrong?
> >
> > Dan
> >
> > > Regards
> > >
>
mobile-broadband-provider-info: Request for msisdn-query tag to be added
There is often a need to query the MSISDN (mobile telephone number) associated with a GSM SIM card, for example when doing a pre-paid top-up over the internet or when calling the network operator's technical support. Because this number can change, the only reliable way of obtaining it is directly from the network operator. Most Vodafone network operators and all of the network operators in South Africa support querying the MSISDN by USSD, for example sending '*111*501#' for Vodacom South Africa. Would it be possible to extend the mobile-broadband-provider-info database to include a msisdn-query tag please? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
ModemManager: USSD not working on Huawei modems that don't support PDU encoding
When attempting to send the USSD command '*101#' on a Huawei E220, ModemManager sends AT+CUSD=1,"AA182C3602",15 Which eventually times out, Instead of sending AT+CUSD=1,"*101#",15 >From what I can tell, some Huawei modems only support PDU encoded USSD and others only support plain text USSD. Some plain text USSD models: E620, E220, and the Vodafone branded E272, K4505, K4605. Some PDU USSD models: E160, E1752, E1820. I do not know of an AT command to determine whether modem supports PDU or plain text USSD, and maintaining a list of models would be tedious. The following procedure has worked for me in another project: Send the USSD command in plain text. If the modem responds with "ERROR", send the USSD command PDU encoded. If successful, set a flag that signifies that for the remainder of this session, all further USSD commands need to be PDU encoded and all USSD responses need to be PDU decoded. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
