On Friday 25 of November 2011 21:25:18 Ajay Garg wrote:
Thanks Jirka,
I understood, that there needed a set of key-value pairs, to be added under
the heading-setting '802-1x'.
It is working now - I am able to connect to the WPA2-Enterprise network.
Thanks a ton !!
You're welcome. It's
On Monday 28 of November 2011 02:14:07 Adam Tauno Williams wrote:
I'm attempting to interrogate the state of the network condition via
Network Manager's D-Bus service. I can reliably get a value, but the
value seems incorrect.
According to
On Mon, 2011-11-28 at 15:44 +0100, Jirka Klimes wrote:
On Monday 28 of November 2011 02:14:07 Adam Tauno Williams wrote:
I'm attempting to interrogate the state of the network condition via
Network Manager's D-Bus service. I can reliably get a value, but the
value seems incorrect.
Hey,
According to the DBus specs [1], no element within a DBus interface can
start with a digit... so org.freedesktop.ModemManager1.Modem.3gpp is a
bad name. :-/
I will temporarily fallback to use:
org.freedesktop.ModemManager1.Modem.Modem3gpp (along with
Hi Thomas,
However if your long term goal is WISPr support, then you have to look
at the whole page anyway. There is no guarantee that the WISPr XML is at
the beginning. Some providers actually just attach it to the end.
personally i don't care about WISPr. I just want to know if i have
This is a followup to my previous change here; the port-not-open
situation is better treated as a manageable error condition rather
than a programming error.
- Nathan
From cec1bb628cd736fd0ac251e77e87f970cd78a4fb Mon Sep 17 00:00:00 2001
From: Nathan Williams n...@chromium.org
Date: Wed, 23
Quoting Marcel Holtmann mar...@holtmann.org:
I personally
would go straight for handling WISPr support and then the rest falls out
of it for free.
I must confess, that I didn't know about WISPr before you mentioned
it earlier in this thread. The Wikipedia article[1] suggests, that
it has
