On 02/15/2013 06:26 PM, Ben Chan wrote:
I was also wondering if that's needed. I guess soft-resetting the modem
helps clear any unknown settings on the modem before ModemManager starts
managing it. For a hotplugged modem, I'd assume it is managed by
ModemManager from the beginning and have the
Hi Dan,
Plus, as I stated earlier, libxml will be required to handle Wispr
responses (and hotspot 2.0), which are legitimate XML trees. So, why not
just add it as a dependency right now?
that is a funny comment since within ConnMan, we are using GMarkup to
handle the WISPr login.
One note: The original patch was supposed to handle 511 http status code,
not wispr. see http://tools.ietf.org/html/rfc6585
2013/2/19 Marcel Holtmann mar...@holtmann.org
Hi Dan,
Plus, as I stated earlier, libxml will be required to handle Wispr
responses (and hotspot 2.0), which are
Hi Jonh,
One note: The original patch was supposed to handle 511 http status code,
not wispr. see http://tools.ietf.org/html/rfc6585
I do not remember any portal using 511 status. At least the ones we
tested have not used it. However we have seen hotspots that are using
200 success status code
Hello,
I have downloaded and installed the last ModemManager version from the Git
repository. I also have installed the NetworkManager packages by Aleksander to
integrate MM with gnome3 in fedora18:
http://sigquit.wordpress.com/2012/11/13/integrating-the-new-modemmanager-in-gnome3/
Everything
On 02/18/2013 11:34 PM, Dan Williams wrote:
On Mon, 2013-02-18 at 22:53 -0500, Hans-Christoph Steiner wrote:
On 02/18/2013 10:44 PM, Dan Williams wrote:
On Mon, 2013-02-18 at 22:27 -0500, Hans-Christoph Steiner wrote:
I have a hard-coded adhoc network setup with a fixed ssid, channel, bssid,
Hoola Jose MarĂa :)
I have downloaded and installed the last ModemManager version from the
Git repository. I also have installed the NetworkManager packages by
Aleksander to integrate MM with gnome3 in fedora18:
http://sigquit.wordpress.com/2012/11/13/integrating-the-new-modemmanager-in-gnome3/
/aleksander/public_html/fedora-packages/20130219
--
Aleksander
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
in the Bearer interface.
Try with these ones here:
/home/aleksander/public_html/fedora-packages/20130219
Oops, here better:
http://www.lanedo.com/~aleksander/fedora-packages/20130219/
--
Aleksander
___
networkmanager-list mailing list
networkmanager-list
On Tue, 2013-02-19 at 09:53 -0500, Hans-Christoph Steiner wrote:
On 02/18/2013 11:34 PM, Dan Williams wrote:
On Mon, 2013-02-18 at 22:53 -0500, Hans-Christoph Steiner wrote:
On 02/18/2013 10:44 PM, Dan Williams wrote:
On Mon, 2013-02-18 at 22:27 -0500, Hans-Christoph Steiner wrote:
I
On 02/19/2013 11:23 AM, Dan Williams wrote:
On Tue, 2013-02-19 at 09:53 -0500, Hans-Christoph Steiner wrote:
On 02/18/2013 11:34 PM, Dan Williams wrote:
On Mon, 2013-02-18 at 22:53 -0500, Hans-Christoph Steiner wrote:
On 02/18/2013 10:44 PM, Dan Williams wrote:
On Mon, 2013-02-18 at 22:27
On Tue, 2013-02-19 at 11:57 -0500, Hans-Christoph Steiner wrote:
On 02/19/2013 11:23 AM, Dan Williams wrote:
On Tue, 2013-02-19 at 09:53 -0500, Hans-Christoph Steiner wrote:
On 02/18/2013 11:34 PM, Dan Williams wrote:
On Mon, 2013-02-18 at 22:53 -0500, Hans-Christoph Steiner wrote:
On
Hi, that sounds interesting. Step by the #nm freenode channel sometimes.
Pavel
- Original Message -
From: Dan Fruehauf malko...@gmail.com
To: networkmanager-list@gnome.org
Sent: Sunday, February 17, 2013 3:19:44 AM
Subject: NetworkManager-ssh
Hi list,
I've recently started
Hello,
I have two nm_client applications running simultaneously: 1) nm_applet, and
2) my_app.
Initially both programs agree on the state of the wifi device i.e.
nm_device_get_state (device):
1 )
nm-applet: W: notify_active_ap_changed_cb Device State = 100
nm-applet: W: Device Product = BCM4312
Patch iface-modem: fix invalid modem state consolidation (commit
69aff6183a9e6532b4074c89831d6dcfa81ddcce) incorrectly consolidates the
modem state upon the disconnection of a bearer. The modem state remains
'connected' after the last bearer is disconnected. This patch fixes
that.
---
I've found a bug in this patch and submitted a fix. Upon the disconnection
of bearers, the consolidation of modem state shouldn't take the curent
state into account, but simply goes through all subsystems.
Thanks,
Ben
On Thu, Jan 24, 2013 at 12:12 AM, Aleksander Morgado
16 matches
Mail list logo