Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE
values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes are supported by the
On Wed, 2011-10-12 at 13:51 -0500, Dan Williams wrote:
I'd rather enforce connection validity with verify() and warn the user
if any IP config was found in the file in the ifcfg plugin.
I'm not sure why we need a dummy config; we'd only need one check for
it, and that's in stage3 when we
I maintain a persistent 3G connection on a remote device using network
manager. However, every so often, the link fails and then does not restart
itself. I managed to identify an occurrence of this in my syslog, but
honestly I'm not really sure what I'm looking at. It seems that the machine
thinks
On Friday, 14. October 2011 17:50:14 Dan Williams wrote:
Good catch, I missed the memset() call.
And if readlink() doesn't fill the buffer,
the remaining bytes will already be set to 0 by the memset, AFAICT.
Are you seeing a crash here or was this from visual inspection?
Pure
I don't see how this would prevent autoconnect if secured with a PIN?
That case would specifically be served by the other entry point:
When modem is unlocked {
If (autoconnect == true) {
Enable_and_autoconnect()
}
}
Note that I am assuming a version of NM where autoconnect has
(Typo. I meant: a version where auto/-unlock/ has been fixed.)
On 17-10-2011 18:50, Anders Feder wrote:
I don't see how this would prevent autoconnect if secured with a PIN?
That case would specifically be served by the other entry point:
When modem is unlocked {
If (autoconnect == true)
Excerpts from Anders Feder's message of 2011-10-17 18:50:08 +0200:
I don't see how this would prevent autoconnect if secured with a PIN?
That case would specifically be served by the other entry point:
When modem is unlocked {
If (autoconnect == true) {
The modem is automatically unlocked when discovered by nm-applet. When
that happens is outside the scope of this fix, but I assume it happens
in both cases you describe.
Anders Feder
On 17-10-2011 23:48, Sascha Silbe wrote:
Excerpts from Anders Feder's message of 2011-10-17 18:50:08 +0200:
