Discussion:
NM09 branch
Raymond Wooninck
2011-05-17 11:47:04 UTC
Permalink
Hi,

I have just compiled the latest NM09 branch and things seems to be working.
However I have problems with the Mobile Broadband. Creating a new connection
works, but if I try to edit it, I get the following error:

Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secrets" doesn't exist


It seems that activation of NetworkConnections through the plasmoid is not
working. I can create a new connection, which shows up in the plasmoid, but
upon click it is not being activated. Also clicking on shown wireless networks
does not bring up the "New Connection Dialog" as normal.

But for the rest it seems to be working pretty well with NM09. No more error
messages and connections activated with NM-applet are correctly shown with
PNM.

Please let me know if you need more information.

Regards

Raymond
Raymond Wooninck
2011-05-17 11:56:16 UTC
Permalink
I found out that the plasmoid is currently only working to show information.
None of the functions to activate or de-activate a particular connection is
working.

Raymond
Post by Raymond Wooninck
Hi,
I have just compiled the latest NM09 branch and things seems to be working.
However I have problems with the Mobile Broadband. Creating a new connection
Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secrets" doesn't exist
It seems that activation of NetworkConnections through the plasmoid is not
working. I can create a new connection, which shows up in the plasmoid, but
upon click it is not being activated. Also clicking on shown wireless
networks does not bring up the "New Connection Dialog" as normal.
But for the rest it seems to be working pretty well with NM09. No more error
messages and connections activated with NM-applet are correctly shown with
PNM.
Please let me know if you need more information.
Regards
Raymond
Lamarque Vieira Souza
2011-05-18 01:57:40 UTC
Permalink
This is fixed now. I can create/edit/delete/connect with ethernet, wifi
WPA and Gsm connections.
Post by Raymond Wooninck
I found out that the plasmoid is currently only working to show
information. None of the functions to activate or de-activate a particular
connection is working.
Raymond
Post by Raymond Wooninck
Hi,
I have just compiled the latest NM09 branch and things seems to be
working. However I have problems with the Mobile Broadband. Creating a
new connection works, but if I try to edit it, I get the following
Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secrets" doesn't exist
It seems that activation of NetworkConnections through the plasmoid is
not working. I can create a new connection, which shows up in the
plasmoid, but upon click it is not being activated. Also clicking on
shown wireless networks does not bring up the "New Connection Dialog" as
normal.
But for the rest it seems to be working pretty well with NM09. No more
error messages and connections activated with NM-applet are correctly
shown with PNM.
Please let me know if you need more information.
Regards
Raymond
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110517/2c4b0f61/attachment.htm
Raymond Wooninck
2011-05-18 09:57:18 UTC
Permalink
Dear Lamarque,

I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled this
against the KDE trunk from last night. I removed all the patches for working
with NM 0.9, so that I am sure to use the new networkmanagement functionality.

The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the plasmoid
nor can I connect to any available connection. The only buttons that are
working are to disable networking, disable wireless and the two buttons for
show more/less and to get into the KCM module.

I can create a new connection, which works fine. However trying to edit that
one again gives me the error that I am missing an agent. (I also remember
seeing a commit for Ilia about changing the error and indicating that this is
in preparation of a new securityagent.).

To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.

Please let me know if you need some more information from me.

Regards

Raymond
Post by Lamarque Vieira Souza
This is fixed now. I can create/edit/delete/connect with ethernet, wifi
WPA and Gsm connections.
Post by Raymond Wooninck
I found out that the plasmoid is currently only working to show
information. None of the functions to activate or de-activate a
particular connection is working.
Raymond
Post by Raymond Wooninck
Hi,
I have just compiled the latest NM09 branch and things seems to be
working. However I have problems with the Mobile Broadband. Creating a
new connection works, but if I try to edit it, I get the following
Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secrets" doesn't exist
It seems that activation of NetworkConnections through the plasmoid is
not working. I can create a new connection, which shows up in the
plasmoid, but upon click it is not being activated. Also clicking on
shown wireless networks does not bring up the "New Connection
Dialog" as normal.
But for the rest it seems to be working pretty well with NM09. No more
error messages and connections activated with NM-applet are correctly
shown with PNM.
Please let me know if you need more information.
Regards
Raymond
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
Lamarque Vieira Souza
2011-05-18 13:39:21 UTC
Permalink
Hi,

The old user connections were still listed but they do not work because
NM does not recognise them, I have just commit a change to prevent user
connections from being listed. Creating connection by clicking on the wireless
network works for me. I can cannot usind my etherent, WPA wifi, and 3G/Gsm
connections. I have not tested my bluetooth connections but since bluetooth
and 3G/Gsm are very alike it probably works too. Only VPN is not working
because we need a secrets agent to store the secrets.

Well, I can add/edit/delete any connection here (ethernet, wifi, gsm,
bluetooth, vpn). Maybe that feature depends on which plugin NM is using. I use
ifnet as default in /etc/NetworkManager/nm-system-settings.conf, which one you
use?

I am going to say offline most part of day, only in about 10 hours I will
be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Post by Lamarque Vieira Souza
This is fixed now. I can create/edit/delete/connect with ethernet, wifi
WPA and Gsm connections.
Post by Raymond Wooninck
I found out that the plasmoid is currently only working to show
information. None of the functions to activate or de-activate a
particular connection is working.
Raymond
Post by Raymond Wooninck
Hi,
I have just compiled the latest NM09 branch and things seems to be
working. However I have problems with the Mobile Broadband. Creating a
new connection works, but if I try to edit it, I get the following
Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secrets" doesn't exist
It seems that activation of NetworkConnections through the plasmoid is
not working. I can create a new connection, which shows up in the
plasmoid, but upon click it is not being activated. Also clicking on
shown wireless networks does not bring up the "New Connection
Dialog" as normal.
But for the rest it seems to be working pretty well with NM09. No more
error messages and connections activated with NM-applet are correctly
shown with PNM.
Please let me know if you need more information.
Regards
Raymond
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110518/3cebd039/attachment.htm
Ilia Kats
2011-05-18 14:33:56 UTC
Permalink
Hey,

I am using the ifupdown and keyfile plug-ins, and this works here too. The thing is: In order to work, we must have secrets available. Secrets can either be stored internally by NM or by a user agent. The current implementation is that secrets for system-wide connections (meaning the "System connection" checkbox is checked, so no permissions are set for the connection, meaning NM will let all users connect with it) are stored by NM, all other by the yet-to-be-implemented user agent. If you want this to work _right now_ you have to change libs/internals/connection.cpp lines 210-218 to:

type |= Setting::None;

That way, even for connections restricted to a single user, secrets will be stored by NM internally. (As said in the commit message, this still doesn't work for 802-1x settings. I could not find any errors, but it would be great if someone could double-check the code)

I am going to work on the secrets agent now, but due to the lack of documentation for the to-be-implemented org.freedesktop.NetworkManager.SecretAgent interface and lack of time this could take a while (if someone knows something about the interface, please contact me)

Ilia


-------- Original-Nachricht --------
Betreff: Re: NM09 branch
Datum: 18.05.2011 10:39:21 -0300
Von: Lamarque Vieira Souza <lamarque at gmail.com>
An: kde-networkmanager at kde.org
Hi,
The old user connections were still listed but they do not work because NM does not recognise them, I have just commit a change to prevent user connections from being listed. Creating connection by clicking on the wireless network works for me. I can cannot usind my etherent, WPA wifi, and 3G/Gsm connections. I have not tested my bluetooth connections but since bluetooth and 3G/Gsm are very alike it probably works too. Only VPN is not working because we need a secrets agent to store the secrets.
Well, I can add/edit/delete any connection here (ethernet, wifi, gsm, bluetooth, vpn). Maybe that feature depends on which plugin NM is using. I use ifnet as default in /etc/NetworkManager/nm-system-settings.conf, which one you use?
I am going to say offline most part of day, only in about 10 hours I will be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Post by Lamarque Vieira Souza
This is fixed now. I can create/edit/delete/connect with ethernet, wifi
WPA and Gsm connections.
Post by Raymond Wooninck
I found out that the plasmoid is currently only working to show
information. None of the functions to activate or de-activate a
particular connection is working.
Raymond
Post by Raymond Wooninck
Hi,
I have just compiled the latest NM09 branch and things seems to be
working. However I have problems with the Mobile Broadband. Creating
a
new connection works, but if I try to edit it, I get the following
Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secrets" doesn't
exist
It seems that activation of NetworkConnections through the plasmoid
is
not working. I can create a new connection, which shows up in the
plasmoid, but upon click it is not being activated. Also clicking on
shown wireless networks does not bring up the "New Connection
Dialog" as normal.
But for the rest it seems to be working pretty well with NM09. No
more
error messages and connections activated with NM-applet are
correctly
shown with PNM.
Please let me know if you need more information.
Regards
Raymond
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
Lukáš Tinkl
2011-05-18 15:14:02 UTC
Permalink
Post by Ilia Kats
Hey,
I am using the ifupdown and keyfile plug-ins, and this works here too. The
thing is: In order to work, we must have secrets available. Secrets can
either be stored internally by NM or by a user agent. The current
implementation is that secrets for system-wide connections (meaning the
"System connection" checkbox is checked, so no permissions are set for the
connection, meaning NM will let all users connect with it) are stored by
NM, all other by the yet-to-be-implemented user agent. If you want this to
work _right now_ you have to change libs/internals/connection.cpp lines
type |= Setting::None;
That way, even for connections restricted to a single user, secrets will be
stored by NM internally. (As said in the commit message, this still
doesn't work for 802-1x settings. I could not find any errors, but it
would be great if someone could double-check the code)
I am going to work on the secrets agent now, but due to the lack of
documentation for the to-be-implemented
org.freedesktop.NetworkManager.SecretAgent interface and lack of time this
could take a while (if someone knows something about the interface, please
contact me)
Ilia
-------- Original-Nachricht --------
Betreff: Re: NM09 branch
Datum: 18.05.2011 10:39:21 -0300
Von: Lamarque Vieira Souza <lamarque at gmail.com>
An: kde-networkmanager at kde.org
Post by Lamarque Vieira Souza
Hi,
The old user connections were still listed but they do not work because
NM does not recognise them, I have just commit a change to prevent user
connections from being listed. Creating connection by clicking on the
wireless network works for me. I can cannot usind my etherent, WPA wifi,
and 3G/Gsm connections. I have not tested my bluetooth connections but
since bluetooth and 3G/Gsm are very alike it probably works too. Only
VPN is not working because we need a secrets agent to store the secrets.
Well, I can add/edit/delete any connection here (ethernet, wifi, gsm,
bluetooth, vpn). Maybe that feature depends on which plugin NM is using.
I use ifnet as default in /etc/NetworkManager/nm-system-settings.conf,
which one you use?
I am going to say offline most part of day, only in about 10 hours I will
be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Hi,
you can have a look at my proof-of-concept code here:
https://bitbucket.org/caybro/knm9

The interesting parts are in:
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.cpp
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.h
(just a very simple implementation of the agent, the real stuff should use
KWallet as the backend for storing the secrets)

and the most tricky part, the creation of the agent:
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/gui/mainwindow.cpp#cl-100
(lines 100 - 105)

HTH,
--
Luk?? Tinkl <ltinkl at redhat.com>
Software Engineer - Base Operating Systems Brno
KDE developer <lukas at kde.org>
Red Hat Inc. http://cz.redhat.com
Ilia Kats
2011-05-19 21:55:33 UTC
Permalink
Hey,

thanks a lot for this. Just one question: could you get it to save secrets (I haven't compiled your source, just used it as reference)? Somehow I get the feeling that the SaveSecrets method isn't called at all when the connection is created. All kDebug which is in this method and also other methods from different classes that are called by SaveSecrets doesn't produce output at all. Also, I had a crash when calling methods from another class, which is used by both GetSecrets and SaveSecrets (the crash is fixed now), and kded crashed only when trying to edit the connection (GetSecrets got called), but not when the connection was created.

Or am I misunderstanding something? My understanding is that we pass the complete connection with secrets and secret flags to NM when creating the connection, and NM will then call SaveSecrets on the secret agent. Or do we have to call it ourselves?

Ilia

-------- Original Message --------
Subject: Re: NM09 branch
Date: 18.05.2011 17:14:02 +0200
From: Luk?? Tinkl <ltinkl at redhat.com>
To: ilia-kats at gmx.net, kde-networkmanager at kde.org
Post by Lukáš Tinkl
Post by Ilia Kats
Hey,
I am using the ifupdown and keyfile plug-ins, and this works here too. The
thing is: In order to work, we must have secrets available. Secrets can
either be stored internally by NM or by a user agent. The current
implementation is that secrets for system-wide connections (meaning the
"System connection" checkbox is checked, so no permissions are set for the
connection, meaning NM will let all users connect with it) are stored by
NM, all other by the yet-to-be-implemented user agent. If you want this to
work _right now_ you have to change libs/internals/connection.cpp lines
type |= Setting::None;
That way, even for connections restricted to a single user, secrets will be
stored by NM internally. (As said in the commit message, this still
doesn't work for 802-1x settings. I could not find any errors, but it
would be great if someone could double-check the code)
I am going to work on the secrets agent now, but due to the lack of
documentation for the to-be-implemented
org.freedesktop.NetworkManager.SecretAgent interface and lack of time this
could take a while (if someone knows something about the interface, please
contact me)
Ilia
-------- Original-Nachricht --------
Betreff: Re: NM09 branch
Datum: 18.05.2011 10:39:21 -0300
Von: Lamarque Vieira Souza <lamarque at gmail.com>
An: kde-networkmanager at kde.org
Post by Lamarque Vieira Souza
Hi,
The old user connections were still listed but they do not work because
NM does not recognise them, I have just commit a change to prevent user
connections from being listed. Creating connection by clicking on the
wireless network works for me. I can cannot usind my etherent, WPA wifi,
and 3G/Gsm connections. I have not tested my bluetooth connections but
since bluetooth and 3G/Gsm are very alike it probably works too. Only
VPN is not working because we need a secrets agent to store the secrets.
Well, I can add/edit/delete any connection here (ethernet, wifi, gsm,
bluetooth, vpn). Maybe that feature depends on which plugin NM is using.
I use ifnet as default in /etc/NetworkManager/nm-system-settings.conf,
which one you use?
I am going to say offline most part of day, only in about 10 hours I will
be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Hi,
https://bitbucket.org/caybro/knm9
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.cpp
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.h
(just a very simple implementation of the agent, the real stuff should use
KWallet as the backend for storing the secrets)
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/gui/mainwindow.cpp#cl-100
(lines 100 - 105)
HTH,
Lamarque Vieira Souza
2011-05-24 05:03:08 UTC
Permalink
Post by Ilia Kats
Hey,
thanks a lot for this. Just one question: could you get it to save secrets
(I haven't compiled your source, just used it as reference)? Somehow I get
the feeling that the SaveSecrets method isn't called at all when the
connection is created. All kDebug which is in this method and also other
methods from different classes that are called by SaveSecrets doesn't
produce output at all. Also, I had a crash when calling methods from
another class, which is used by both GetSecrets and SaveSecrets (the crash
is fixed now), and kded crashed only when trying to edit the connection
(GetSecrets got called), but not when the connection was created.
Or am I misunderstanding something? My understanding is that we pass the
complete connection with secrets and secret flags to NM when creating the
connection, and NM will then call SaveSecrets on the secret agent. Or do
we have to call it ourselves?
Ilia
-------- Original Message --------
Subject: Re: NM09 branch
Date: 18.05.2011 17:14:02 +0200
From: Luk?? Tinkl <ltinkl at redhat.com>
To: ilia-kats at gmx.net, kde-networkmanager at kde.org
Post by Lukáš Tinkl
Post by Ilia Kats
Hey,
I am using the ifupdown and keyfile plug-ins, and this works here too.
The thing is: In order to work, we must have secrets available. Secrets
can either be stored internally by NM or by a user agent. The current
implementation is that secrets for system-wide connections (meaning the
"System connection" checkbox is checked, so no permissions are set for
the connection, meaning NM will let all users connect with it) are
stored by NM, all other by the yet-to-be-implemented user agent. If you
want this to work _right now_ you have to change
type |= Setting::None;
That way, even for connections restricted to a single user, secrets will
be stored by NM internally. (As said in the commit message, this still
doesn't work for 802-1x settings. I could not find any errors, but it
would be great if someone could double-check the code)
I am going to work on the secrets agent now, but due to the lack of
documentation for the to-be-implemented
org.freedesktop.NetworkManager.SecretAgent interface and lack of time
this could take a while (if someone knows something about the
interface, please contact me)
Ilia
-------- Original-Nachricht --------
Betreff: Re: NM09 branch
Datum: 18.05.2011 10:39:21 -0300
Von: Lamarque Vieira Souza <lamarque at gmail.com>
An: kde-networkmanager at kde.org
Post by Lamarque Vieira Souza
Hi,
The old user connections were still listed but they do not work because
NM does not recognise them, I have just commit a change to prevent user
connections from being listed. Creating connection by clicking on the
wireless network works for me. I can cannot usind my etherent, WPA
wifi, and 3G/Gsm connections. I have not tested my bluetooth
connections but since bluetooth and 3G/Gsm are very alike it probably
works too. Only VPN is not working because we need a secrets agent to
store the secrets.
Well, I can add/edit/delete any connection here (ethernet, wifi, gsm,
bluetooth, vpn). Maybe that feature depends on which plugin NM is
using. I use ifnet as default in
/etc/NetworkManager/nm-system-settings.conf, which one you use?
I am going to say offline most part of day, only in about 10 hours I
will be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new
networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Hi,
https://bitbucket.org/caybro/knm9
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.
cpp
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent
.h (just a very simple implementation of the agent, the real stuff should
use KWallet as the backend for storing the secrets)
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/gui/mainwindow.cpp#cl-
100 (lines 100 - 105)
HTH,
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
This also explains some things, like wifi keys being stored in plain text
by NM:

http://mail.gnome.org/archives/networkmanager-list/2011-March/msg00122.html

I think we should change Plasma NM to always change secrets to agent-
owned when creating a connection to prevent NM storing secrets in plain text.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110524/8e475d5a/attachment-0001.htm
Lamarque Vieira Souza
2011-05-25 00:29:40 UTC
Permalink
Post by Lamarque Vieira Souza
Post by Ilia Kats
Hey,
thanks a lot for this. Just one question: could you get it to save
secrets (I haven't compiled your source, just used it as reference)?
Somehow I get the feeling that the SaveSecrets method isn't called at
all when the connection is created. All kDebug which is in this method
and also other methods from different classes that are called by
SaveSecrets doesn't produce output at all. Also, I had a crash when
calling methods from another class, which is used by both GetSecrets and
SaveSecrets (the crash is fixed now), and kded crashed only when trying
to edit the connection (GetSecrets got called), but not when the
connection was created.
Or am I misunderstanding something? My understanding is that we pass the
complete connection with secrets and secret flags to NM when creating the
connection, and NM will then call SaveSecrets on the secret agent. Or do
we have to call it ourselves?
I think we should call SaveSecret when creating a connection, but then we
have a problem: Plasma NM is divided into four process: the kded module, the
plasmoid (in plasma-desktop process), the kcm module and
networkmanagement_configshell. Connections are created in the last two, but
the agent run on behalf of the kded module. The kcm module and
networkmanagementconfig_shell must call the kded module to save secrets. To
make things worse NM guys deciced that the agent should not have a name on the
bus, so we cannot call it directly. We can add another DBus interface in the
kded module just to call the agent. This way we can avoid the secrets double
saving problem in kcm module.

What seems to be happening is that after creating the connection the
secrets are not being saved in the kwallet by us and neither by NM (by calling
SaveSecrets). When activating the connection NM calls GetSecrets and that
failed because the agent does not have the secrets. When we update the
connection in kcm module NM finally calls SaveSecrets passing the secrets as
parameters and the kded module saves them. We could also call updateConnection
after creating it :-) That works, I have just tested it.
Post by Lamarque Vieira Souza
Post by Ilia Kats
Ilia
-------- Original Message --------
Subject: Re: NM09 branch
Date: 18.05.2011 17:14:02 +0200
From: Luk?? Tinkl <ltinkl at redhat.com>
To: ilia-kats at gmx.net, kde-networkmanager at kde.org
Post by Lukáš Tinkl
Post by Ilia Kats
Hey,
I am using the ifupdown and keyfile plug-ins, and this works here too.
The thing is: In order to work, we must have secrets available.
Secrets can either be stored internally by NM or by a user agent. The
current implementation is that secrets for system-wide connections
(meaning the "System connection" checkbox is checked, so no
permissions are set for the connection, meaning NM will let all users
connect with it) are stored by NM, all other by the
yet-to-be-implemented user agent. If you want this to work _right
now_ you have to change
type |= Setting::None;
That way, even for connections restricted to a single user, secrets
will be stored by NM internally. (As said in the commit message, this
still doesn't work for 802-1x settings. I could not find any errors,
but it would be great if someone could double-check the code)
I am going to work on the secrets agent now, but due to the lack of
documentation for the to-be-implemented
org.freedesktop.NetworkManager.SecretAgent interface and lack of time
this could take a while (if someone knows something about the
interface, please contact me)
Ilia
-------- Original-Nachricht --------
Betreff: Re: NM09 branch
Datum: 18.05.2011 10:39:21 -0300
Von: Lamarque Vieira Souza <lamarque at gmail.com>
An: kde-networkmanager at kde.org
Post by Lamarque Vieira Souza
Hi,
The old user connections were still listed but they do not work
because NM does not recognise them, I have just commit a change to
prevent user connections from being listed. Creating connection by
clicking on the wireless network works for me. I can cannot usind my
etherent, WPA wifi, and 3G/Gsm connections. I have not tested my
bluetooth connections but since bluetooth and 3G/Gsm are very alike
it probably works too. Only VPN is not working because we need a
secrets agent to store the secrets.
Well, I can add/edit/delete any connection here (ethernet, wifi, gsm,
bluetooth, vpn). Maybe that feature depends on which plugin NM is
using. I use ifnet as default in
/etc/NetworkManager/nm-system-settings.conf, which one you use?
I am going to say offline most part of day, only in about 10 hours I
will be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new
networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Hi,
https://bitbucket.org/caybro/knm9
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgen
t. cpp
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgen
t .h (just a very simple implementation of the agent, the real stuff
should use KWallet as the backend for storing the secrets)
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/gui/mainwindow.cpp#c
l- 100 (lines 100 - 105)
HTH,
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
This also explains some things, like wifi keys being stored in plain text
http://mail.gnome.org/archives/networkmanager-list/2011-March/msg00122.html
I think we should change Plasma NM to always change secrets to agent-
owned when creating a connection to prevent NM storing secrets in plain text.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110524/ae847cc6/attachment-0001.htm
Lukáš Tinkl
2011-05-25 11:02:00 UTC
Permalink
Dne St 25. kv?tna 2011 02:29:40 jste napsal(a): > Em Tuesday 24 May 2011,
Post by Lamarque Vieira Souza
Post by Ilia Kats
Hey,
thanks a lot for this. Just one question: could you get it to save
secrets (I haven't compiled your source, just used it as reference)?
Somehow I get the feeling that the SaveSecrets method isn't called at
all when the connection is created. All kDebug which is in this method
and also other methods from different classes that are called by
SaveSecrets doesn't produce output at all. Also, I had a crash when
calling methods from another class, which is used by both GetSecrets
and SaveSecrets (the crash is fixed now), and kded crashed only when
trying to edit the connection (GetSecrets got called), but not when
the connection was created.
Or am I misunderstanding something? My understanding is that we pass
the complete connection with secrets and secret flags to NM when
creating the connection, and NM will then call SaveSecrets on the
secret agent. Or do we have to call it ourselves?
I think we should call SaveSecret when creating a connection, but then we
have a problem: Plasma NM is divided into four process: the kded module,
the plasmoid (in plasma-desktop process), the kcm module and
networkmanagement_configshell. Connections are created in the last two, but
the agent run on behalf of the kded module. The kcm module and
networkmanagementconfig_shell must call the kded module to save secrets. To
make things worse NM guys deciced that the agent should not have a name on
the bus, so we cannot call it directly. We can add another DBus interface
in the kded module just to call the agent. This way we can avoid the
secrets double saving problem in kcm module.
What seems to be happening is that after creating the connection the
secrets are not being saved in the kwallet by us and neither by NM (by
calling SaveSecrets). When activating the connection NM calls GetSecrets
and that failed because the agent does not have the secrets. When we
update the connection in kcm module NM finally calls SaveSecrets passing
the secrets as parameters and the kded module saves them. We could also
call updateConnection after creating it :-) That works, I have just tested
it.
I just tested it, everything works fine, except activating a VPN connection.
Furthermore, I'm getting a "No agent..." error message when trying to edit any
connection. Strange thing is that those connections that contain a password
display it correctly; I think that's because NM itself saves the pass.

In the VPN case, my guess is that we are not using the correct data type
consistently for the data/secrets maps. They both have to be QStringMap, not
QVariantMap/Map; in fact the whole connection is a QVariantMapMap but the last
level is a QVariant of type QStringMap :) Tricky stuff, see:
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.cpp
and
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/authdialogs/vpncauthdlg.cpp

Anyway thanks for all the hard work.
--
Luk?? Tinkl <ltinkl at redhat.com>
Software Engineer - Base Operating Systems Brno
KDE developer <lukas at kde.org>
Red Hat Inc. http://cz.redhat.com
Lamarque Vieira Souza
2011-05-26 19:46:21 UTC
Permalink
Post by Lukáš Tinkl
I just tested it, everything works fine, except activating a VPN
connection. Furthermore, I'm getting a "No agent..." error message when
trying to edit any connection. Strange thing is that those connections
that contain a password display it correctly; I think that's because NM
itself saves the pass.
VPN is working now. As far as I can tell everything that work with master
(NM-0.8) work in nm09 branch now. I use kwallet, I have not tested the plain
text saving.
Post by Lukáš Tinkl
In the VPN case, my guess is that we are not using the correct data type
consistently for the data/secrets maps. They both have to be QStringMap,
not QVariantMap/Map; in fact the whole connection is a QVariantMapMap but
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.cp
p and
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/authdialogs/vpnc
authdlg.cpp
The problem was that we had not implemented the VpnSecrets object and
then the GetSecrets call did not even try to open kwallet to read the secrets.
Post by Lukáš Tinkl
Anyway thanks for all the hard work.
Thanks :-)
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110526/5a6bba54/attachment-0001.htm
Lamarque Vieira Souza
2011-05-26 19:51:27 UTC
Permalink
Post by Lamarque Vieira Souza
Post by Lukáš Tinkl
I just tested it, everything works fine, except activating a VPN
connection. Furthermore, I'm getting a "No agent..." error message when
trying to edit any connection. Strange thing is that those connections
that contain a password display it correctly; I think that's because NM
itself saves the pass.
VPN is working now. As far as I can tell everything that work with master
(NM-0.8) work in nm09 branch now. I use kwallet, I have not tested the
plain text saving.
Hmmm there is still one problem. The secrets do not appear in the edit
dialog, but the connection works.
Post by Lamarque Vieira Souza
Post by Lukáš Tinkl
In the VPN case, my guess is that we are not using the correct data type
consistently for the data/secrets maps. They both have to be QStringMap,
not QVariantMap/Map; in fact the whole connection is a QVariantMapMap but
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/NMSecretAgent.
cp p and
https://bitbucket.org/caybro/knm9/src/ac430c8136dd/backend/authdialogs/vp
nc authdlg.cpp
The problem was that we had not implemented the VpnSecrets object and
then the GetSecrets call did not even try to open kwallet to read the secrets.
Post by Lukáš Tinkl
Anyway thanks for all the hard work.
Thanks :-)
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110526/23632d1b/attachment.htm
Lamarque Vieira Souza
2011-05-27 17:12:44 UTC
Permalink
Dne ?t 26. kv?tna 2011 21:51:27 jste napsal(a): > Em Thursday 26 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Post by Lukáš Tinkl
I just tested it, everything works fine, except activating a VPN
connection. Furthermore, I'm getting a "No agent..." error message
when trying to edit any connection. Strange thing is that those
connections that contain a password display it correctly; I think
that's because NM itself saves the pass.
VPN is working now. As far as I can tell everything that work with master
(NM-0.8) work in nm09 branch now. I use kwallet, I have not tested the
plain text saving.
Hmmm there is still one problem. The secrets do not appear in the edit
dialog, but the connection works.
Hmm I spoke too soon, the VPN doesn't work here (vpnc), it tries to
activate it but it fails immediately, not asking for any secrets (I have
one saved and one being asked for). If I activate it in nm-applet, it
can't be deactivated by our applet either (clicking that red cross button)
Sometimes my VPN also failed, if I try to connect one or two more times
it connects. All my secrets are set to "always save" and it works, if I set
one to "always ask" it does not connect nor ask for the secret. As for the
deactivating problem Plasma NM saves the ObjectPath of the VPN connection when
activating and uses it to deactivate the connection, which means Plasma NM is
only able to deactivate the connections it activated itself.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110527/1438fa81/attachment.htm
Lamarque Vieira Souza
2011-05-29 09:22:22 UTC
Permalink
Post by Lamarque Vieira Souza
Dne ?t 26. kv?tna 2011 21:51:27 jste napsal(a): > Em Thursday 26 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Post by Lukáš Tinkl
I just tested it, everything works fine, except activating a VPN
connection. Furthermore, I'm getting a "No agent..." error message
when trying to edit any connection. Strange thing is that those
connections that contain a password display it correctly; I think
that's because NM itself saves the pass.
VPN is working now. As far as I can tell everything that work with master
(NM-0.8) work in nm09 branch now. I use kwallet, I have not tested
the plain text saving.
Hmmm there is still one problem. The secrets do not appear in the edit
dialog, but the connection works.
Hmm I spoke too soon, the VPN doesn't work here (vpnc), it tries to
activate it but it fails immediately, not asking for any secrets (I have
one saved and one being asked for). If I activate it in nm-applet, it
can't be deactivated by our applet either (clicking that red cross button)
Sometimes my VPN also failed, if I try to connect one or two more times
it connects. All my secrets are set to "always save" and it works, if I set
one to "always ask" it does not connect nor ask for the secret. As for the
deactivating problem Plasma NM saves the ObjectPath of the VPN connection
when activating and uses it to deactivate the connection, which means
Plasma NM is only able to deactivate the connections it activated itself.
I have just fixed the not asking problem, please test. Edit dialog also
shows secrets now.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110529/f74d39fe/attachment.htm
Lamarque Vieira Souza
2011-05-30 16:29:52 UTC
Permalink
Dne Ne 29. kv?tna 2011 11:22:22 jste napsal(a): > Em Friday 27 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Dne ?t 26. kv?tna 2011 21:51:27 jste napsal(a): > Em Thursday 26 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Post by Lukáš Tinkl
I just tested it, everything works fine, except activating a
VPN connection. Furthermore, I'm getting a "No agent..." error
message when trying to edit any connection. Strange thing is
that those connections that contain a password display it
correctly; I think that's because NM itself saves the pass.
VPN is working now. As far as I can tell everything that work
with master
(NM-0.8) work in nm09 branch now. I use kwallet, I have not
tested the plain text saving.
Hmmm there is still one problem. The secrets do not appear in
the
Post by Lamarque Vieira Souza
edit
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
dialog, but the connection works.
Hmm I spoke too soon, the VPN doesn't work here (vpnc), it tries to
activate it but it fails immediately, not asking for any secrets (I
have one saved and one being asked for). If I activate it in
nm-applet, it can't be deactivated by our applet either (clicking
that red cross button)
Sometimes my VPN also failed, if I try to connect one or two more
times
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
it connects. All my secrets are set to "always save" and it works, if I
set one to "always ask" it does not connect nor ask for the secret. As
for the deactivating problem Plasma NM saves the ObjectPath of the VPN
connection when activating and uses it to deactivate the connection,
which means Plasma NM is only able to deactivate the connections it
activated itself.
I have just fixed the not asking problem, please test. Edit dialog also
shows secrets now.
Sry, doesn't work at all :/ I just created a new VPN(c) connection and
although it shows in the config dialog, it doesn't in the GUI. Furthermore,
it doesn't save the password I had typed and still displays an error
message (No agents were available for this request.) when I try to edit
the connection.
Honestly I do not know why it does not work for you. What you described
is the behaviour of an old snapshot of Plasma NM. Please, send me your
.xsession-errors and the output of the attached script.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110530/7535dff9/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: connection.sh
Type: application/x-shellscript
Size: 1125 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110530/7535dff9/attachment.sh
Lukáš Tinkl
2011-05-30 16:49:17 UTC
Permalink
Post by Lamarque Vieira Souza
Dne Ne 29. kv?tna 2011 11:22:22 jste napsal(a): > Em Friday 27 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Dne ?t 26. kv?tna 2011 21:51:27 jste napsal(a): > Em Thursday 26 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Post by Lukáš Tinkl
I just tested it, everything works fine, except activating a
VPN connection. Furthermore, I'm getting a "No agent..."
error message when trying to edit any connection. Strange
thing is that those connections that contain a password
display it correctly; I think that's because NM itself saves
the pass.
VPN is working now. As far as I can tell everything that work
with master
(NM-0.8) work in nm09 branch now. I use kwallet, I have not
tested the plain text saving.
Hmmm there is still one problem. The secrets do not appear in
the
Post by Lamarque Vieira Souza
edit
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
dialog, but the connection works.
Hmm I spoke too soon, the VPN doesn't work here (vpnc), it tries to
activate it but it fails immediately, not asking for any secrets (I
have one saved and one being asked for). If I activate it in
nm-applet, it can't be deactivated by our applet either (clicking
that red cross button)
Sometimes my VPN also failed, if I try to connect one or two more
times
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
it connects. All my secrets are set to "always save" and it works, if
I set one to "always ask" it does not connect nor ask for the
secret. As for the deactivating problem Plasma NM saves the
ObjectPath of the VPN connection when activating and uses it to
deactivate the connection, which means Plasma NM is only able to
deactivate the connections it activated itself.
I have just fixed the not asking problem, please test. Edit dialog also
shows secrets now.
Sry, doesn't work at all :/ I just created a new VPN(c) connection and
although it shows in the config dialog, it doesn't in the GUI.
Furthermore, it doesn't save the password I had typed and still displays
an error message (No agents were available for this request.) when I try
to edit the connection.
Honestly I do not know why it does not work for you. What you described
is the behaviour of an old snapshot of Plasma NM. Please, send me your
.xsession-errors and the output of the attached script.
Hmm, after a relogout (killing the kded module was not enough it seems), I do
get the password displayed correctly in the config dialog, but now activating
the VPN is asking for *both* passwords :) See this screenshot:

Loading Image...

Here's the connection as it appears on DBUS:

{u'connection': {u'autoconnect': 0,
u'id': u'Redhat',
u'type': u'vpn',
u'uuid': u'bb331947-3333-4572-9715-5b99ea800dee'},
u'ipv4': {u'addresses': [],
u'dns': [],
u'method': u'auto',
u'never-default': 1,
u'routes': []},
u'ipv6': {u'addresses': [],
u'dns': [],
u'may-fail': 1,
u'method': u'ignore',
u'routes': []},
u'vpn': {u'data': {u'IPSec ID': u'RH-standard',
u'IPSec gateway': u'xx.xxx.xxx.xx',
u'IPSec secret-flags': u'0',
u'NAT Traversal Mode': u'natt',
u'Xauth password-flags': u'2',
u'Xauth username': u'ltinkl',
u'ipsec-secret-type': u'save',
u'xauth-password-type': u'ask'},
u'service-type': u'org.freedesktop.NetworkManager.vpnc'}}
--
Luk?? Tinkl <ltinkl at redhat.com>
Software Engineer - Base Operating Systems Brno
KDE developer <lukas at kde.org>
Red Hat Inc. http://cz.redhat.com
Lamarque Vieira Souza
2011-05-31 07:16:08 UTC
Permalink
Post by Lukáš Tinkl
Hmm, after a relogout (killing the kded module was not enough it seems), I
do get the password displayed correctly in the config dialog, but now
Plasma NM also asks me for both secrets, although filling only the one
marked as "always ask" and leaving the other empty allows me to connect. I
think the auth dialog was created that way and I am quite sure Plasma NM for
NM-0.8 also works that way, so it is not a regression.
Post by Lukáš Tinkl
{u'connection': {u'autoconnect': 0,
u'id': u'Redhat',
u'type': u'vpn',
u'uuid': u'bb331947-3333-4572-9715-5b99ea800dee'},
u'ipv4': {u'addresses': [],
u'dns': [],
u'method': u'auto',
u'never-default': 1,
u'routes': []},
u'ipv6': {u'addresses': [],
u'dns': [],
u'may-fail': 1,
u'method': u'ignore',
u'routes': []},
u'vpn': {u'data': {u'IPSec ID': u'RH-standard',
u'IPSec gateway': u'xx.xxx.xxx.xx',
u'IPSec secret-flags': u'0',
u'NAT Traversal Mode': u'natt',
u'Xauth password-flags': u'2',
u'Xauth username': u'ltinkl',
u'ipsec-secret-type': u'save',
u'xauth-password-type': u'ask'},
u'service-type': u'org.freedesktop.NetworkManager.vpnc'}}
Everything seems ok here.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110531/388a0228/attachment.htm
Lukáš Tinkl
2011-05-30 15:12:44 UTC
Permalink
Dne Ne 29. kv?tna 2011 11:22:22 jste napsal(a): > Em Friday 27 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Dne ?t 26. kv?tna 2011 21:51:27 jste napsal(a): > Em Thursday 26 May 2011,
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
Post by Lukáš Tinkl
I just tested it, everything works fine, except activating a VPN
connection. Furthermore, I'm getting a "No agent..." error
message when trying to edit any connection. Strange thing is
that those connections that contain a password display it
correctly; I think that's because NM itself saves the pass.
VPN is working now. As far as I can tell everything that work with master
(NM-0.8) work in nm09 branch now. I use kwallet, I have not tested
the plain text saving.
Hmmm there is still one problem. The secrets do not appear in the
edit
Post by Lamarque Vieira Souza
Post by Lamarque Vieira Souza
dialog, but the connection works.
Hmm I spoke too soon, the VPN doesn't work here (vpnc), it tries to
activate it but it fails immediately, not asking for any secrets (I
have one saved and one being asked for). If I activate it in
nm-applet, it can't be deactivated by our applet either (clicking that
red cross button)
Sometimes my VPN also failed, if I try to connect one or two more times
it connects. All my secrets are set to "always save" and it works, if I
set one to "always ask" it does not connect nor ask for the secret. As
for the deactivating problem Plasma NM saves the ObjectPath of the VPN
connection when activating and uses it to deactivate the connection,
which means Plasma NM is only able to deactivate the connections it
activated itself.
I have just fixed the not asking problem, please test. Edit dialog also
shows secrets now.
Sry, doesn't work at all :/ I just created a new VPN(c) connection and
although it shows in the config dialog, it doesn't in the GUI. Furthermore, it
doesn't save the password I had typed and still displays an error message (No
agents were available for this request.) when I try to edit the connection.
--
Luk?? Tinkl <ltinkl at redhat.com>
Software Engineer - Base Operating Systems Brno
KDE developer <lukas at kde.org>
Red Hat Inc. http://cz.redhat.com
Raymond Wooninck
2011-05-18 17:27:28 UTC
Permalink
Hi,

As that I am the only user on my laptop, I do not really care how the secrets
are being stored. :-)

My home wireless does not have any WEP or WPA and strangely enough I can't
edit this connection. The error message shows :

nm-settings-connection.c.690 - Connection didn't have requested setting
'802-11-wireless-security'.

However my biggest issue is that I can not activate connections shown by the
Plasmoid. I even tried to have a new one created by deleting the old
connection, but it just simple doesn't work. Only those connections that will
automatically become active, are working.

I don't know what version of NM you all are running, however the openSUSE NM
0.8.999 (RC2) is showing this behaviour.

I have already updated to the latest version and I know 100% for sure that all
connections are system-based ones.

Please let me know what kind of information is required, but at this moment
Fedora's solution with their compatibility libs for NM0.9 worked better than
this one.

Please do not get me wrong. I think you all are doing a terrific job and I
wish that I could help out with coding. Unfortunately I am not a coder, but I
hope that I can contribute with test results, etc.

Raymond
Post by Ilia Kats
Hey,
I am using the ifupdown and keyfile plug-ins, and this works here too. The
thing is: In order to work, we must have secrets available. Secrets can
either be stored internally by NM or by a user agent. The current
implementation is that secrets for system-wide connections (meaning the
"System connection" checkbox is checked, so no permissions are set for the
connection, meaning NM will let all users connect with it) are stored by
NM, all other by the yet-to-be-implemented user agent. If you want this to
work _right now_ you have to change libs/internals/connection.cpp lines
type |= Setting::None;
That way, even for connections restricted to a single user, secrets will be
stored by NM internally. (As said in the commit message, this still doesn't
work for 802-1x settings. I could not find any errors, but it would be
great if someone could double-check the code)
I am going to work on the secrets agent now, but due to the lack of
documentation for the to-be-implemented
org.freedesktop.NetworkManager.SecretAgent interface and lack of time this
could take a while (if someone knows something about the interface, please
contact me)
Ilia
-------- Original-Nachricht --------
Betreff: Re: NM09 branch
Datum: 18.05.2011 10:39:21 -0300
Von: Lamarque Vieira Souza <lamarque at gmail.com>
An: kde-networkmanager at kde.org
Post by Lamarque Vieira Souza
Hi,
The old user connections were still listed but they do not work because
NM does not recognise them, I have just commit a change to prevent user
connections from being listed. Creating connection by clicking on the
wireless network works for me. I can cannot usind my etherent, WPA
wifi, and 3G/Gsm connections. I have not tested my bluetooth
connections but since bluetooth and 3G/Gsm are very alike it probably
works too. Only VPN is not working because we need a secrets agent to
store the secrets.
Well, I can add/edit/delete any connection here (ethernet, wifi, gsm,
bluetooth, vpn). Maybe that feature depends on which plugin NM is
using. I use ifnet as default in
/etc/NetworkManager/nm-system-settings.conf, which one you use?
I am going to say offline most part of day, only in about 10 hours I
will be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new
networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Post by Lamarque Vieira Souza
This is fixed now. I can create/edit/delete/connect with
ethernet, wifi
WPA and Gsm connections.
Post by Raymond Wooninck
I found out that the plasmoid is currently only working to show
information. None of the functions to activate or
de-activate a
particular connection is working.
Raymond
Post by Raymond Wooninck
Hi,
I have just compiled the latest NM09 branch and things seems to be
working. However I have problems with the Mobile
Broadband. Creating
a
new connection works, but if I try to edit it, I get the following
Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secr
ets" doesn't
exist
It seems that activation of NetworkConnections through the plasmoid
is
not working. I can create a new connection, which shows up in the
plasmoid, but upon click it is not being activated. Also clicking on
shown wireless networks does not bring up the "New
Connection
Dialog" as normal.
But for the rest it seems to be working pretty well with NM09. No
more
error messages and connections activated with NM-applet are
correctly
shown with PNM.
Please let me know if you need more information.
Regards
Raymond
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
Raymond Wooninck
2011-05-18 17:33:10 UTC
Permalink
Hi Lamarque,

The question is more that if you see a network connection in the plasmoid
(which is set not to connect automatically), can you activate that connection
by clicking on it in the plasmoid ??

The latest snapshot shows me that I can create a new connection based on
detected networks, however if I do not set that connection to automatically
connect, then I have no opportunity to activate it.

I have in the office the situation that we have a wired and wireless
connection. Normally the wired is used and only if we want to move around we
are utilizing the wireless. So I have a connection defined that does not
connect automatically. It shows in the recognized connections in the plasmoid,
but I can click and click and click, but no result and definitely no
connectivity.

I have recreated this connection today with the latest snapshot, I also
created the connection with the NM-Applet (gnome), but both give exactly the
same result. Connections somehow can not be activated nor deactivated through
the plasmoid !!

Raymond
Post by Lamarque Vieira Souza
Hi,
The old user connections were still listed but they do not work because
NM does not recognise them, I have just commit a change to prevent user
connections from being listed. Creating connection by clicking on the
wireless network works for me. I can cannot usind my etherent, WPA wifi,
and 3G/Gsm connections. I have not tested my bluetooth connections but
since bluetooth and 3G/Gsm are very alike it probably works too. Only VPN
is not working because we need a secrets agent to store the secrets.
Well, I can add/edit/delete any connection here (ethernet, wifi, gsm,
bluetooth, vpn). Maybe that feature depends on which plugin NM is using. I
use ifnet as default in /etc/NetworkManager/nm-system-settings.conf, which
one you use?
I am going to say offline most part of day, only in about 10 hours I will
be back online.
Post by Raymond Wooninck
Dear Lamarque,
I am very sorry, but this issue is not fixed in the NM09 branch of
networkmanagement. I took a new snapshot from this morning and compiled
this against the KDE trunk from last night. I removed all the patches for
working with NM 0.9, so that I am sure to use the new networkmanagement
functionality.
The plasmoid shows the connections, etc. However I can can click on any
connection I see, but nothing happens. I can't disconnect through the
plasmoid nor can I connect to any available connection. The only buttons
that are working are to disable networking, disable wireless and the two
buttons for show more/less and to get into the KCM module.
I can create a new connection, which works fine. However trying to edit
that one again gives me the error that I am missing an agent. (I also
remember seeing a commit for Ilia about changing the error and indicating
that this is in preparation of a new securityagent.).
To me it seems that either networkmanagement is currently depending on
kSecretService or that certain things have not been commited yet.
Please let me know if you need some more information from me.
Regards
Raymond
Post by Lamarque Vieira Souza
This is fixed now. I can create/edit/delete/connect with ethernet, wifi
WPA and Gsm connections.
Post by Raymond Wooninck
I found out that the plasmoid is currently only working to show
information. None of the functions to activate or de-activate a
particular connection is working.
Raymond
Post by Raymond Wooninck
Hi,
I have just compiled the latest NM09 branch and things seems to be
working. However I have problems with the Mobile Broadband. Creating a
new connection works, but if I try to edit it, I get the following
Method "GetSecrets" with signature "s" on interface
"org.freedesktop.NetworkManager.Settings.Connection.Secrets" doesn't exist
It seems that activation of NetworkConnections through the
plasmoid
is
not working. I can create a new connection, which shows up in the
plasmoid, but upon click it is not being activated. Also
clicking on shown wireless networks does not bring up the
"New Connection Dialog" as normal.
But for the rest it seems to be working pretty well with
NM09. No
more
error messages and connections activated with NM-applet are correctly
shown with PNM.
Please let me know if you need more information.
Regards
Raymond
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
_______________________________________________
kde-networkmanager mailing list
kde-networkmanager at kde.org
https://mail.kde.org/mailman/listinfo/kde-networkmanager
Lamarque Vieira Souza
2011-05-18 21:51:19 UTC
Permalink
Post by Raymond Wooninck
Hi Lamarque,
Hi,
Post by Raymond Wooninck
The question is more that if you see a network connection in the plasmoid
(which is set not to connect automatically), can you activate that
connection by clicking on it in the plasmoid ??
I have just reverted my commit that caused the problem. It should work
now.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110518/74c36615/attachment.htm
Michael Biebl
2011-05-18 22:44:00 UTC
Permalink
Hi
Post by Lamarque Vieira Souza
Post by Raymond Wooninck
Hi Lamarque,
Hi,
Post by Raymond Wooninck
The question is more that if you see a network connection in the plasmoid
(which is set not to connect automatically), can you activate that
connection by clicking on it in the plasmoid ??
I have just reverted my commit that caused the problem. It should work
now.
I can reproduce the issue here. Unfortunately, the latest revert doesn't resolve it.
(Existing) connections still can't be activated in the plasma widget.

At least I can create new connections now by clicking on the wireless network in
the network list. IIRC this didn't work before and I had to use the kcm module.

I hope you keep up your good work on the 0.9 branch. All major distros will use
NM 0.9 in their next release, so a fully working KDE solution is very important.
Imho more important than polishing the 0.8 branch.


Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110519/5f482e4d/attachment.sig
Michael Biebl
2011-05-18 22:49:13 UTC
Permalink
Post by Michael Biebl
I hope you keep up your good work on the 0.9 branch. All major distros will use
NM 0.9 in their next release, so a fully working KDE solution is very important.
Imho more important than polishing the 0.8 branch.
I wanted to add here, that as soon as pnm provides basic, working functionality
for NM 0.9, I'll upload NM 0.9 packages to Debian sid and wheezy, our next release.

I think Matthieu is planning to do the same for Ubuntu Oneiric.

F15, as you probably know, has already made the switch.

Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110519/4dfd24f1/attachment.sig
Lamarque Vieira Souza
2011-05-18 23:16:30 UTC
Permalink
Post by Michael Biebl
Hi
Post by Lamarque Vieira Souza
Post by Raymond Wooninck
Hi Lamarque,
Hi,
Post by Raymond Wooninck
The question is more that if you see a network connection in the
plasmoid (which is set not to connect automatically), can you activate
that connection by clicking on it in the plasmoid ??
I have just reverted my commit that caused the problem. It should work
now.
I can reproduce the issue here. Unfortunately, the latest revert doesn't
resolve it. (Existing) connections still can't be activated in the plasma
widget.
User connections created using master branch does not work in nm09, only
the ones created as system connection works in nm09 branch. That is why I did
the first commit (to prevent user connections from being displayed in Plasma
NM/nm09).
Post by Michael Biebl
At least I can create new connections now by clicking on the wireless
network in the network list. IIRC this didn't work before and I had to use
the kcm module.
Yes, I fixed that last night.
Post by Michael Biebl
I hope you keep up your good work on the 0.9 branch. All major distros will
use NM 0.9 in their next release, so a fully working KDE solution is very
important. Imho more important than polishing the 0.8 branch.
Again: ALL "polishings" from 0.8 branch have been applied to nm09 branch
too. They are enhancements to BOTH 0.8 and 0.9 branches and by the list of
bugs they fix you can see users wanted those "polishings":

http://lamarque-lvs.blogspot.com/2011/04/plasma-nm-bugs-fixed-after-462.html
http://lamarque-lvs.blogspot.com/2011/03/plasma-nm-bugs-fixed.html

I also have another list of bugs fixed after 4.6.3 release date that I
have not published yet.
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110518/249987ee/attachment-0001.htm
Michael Biebl
2011-05-18 23:30:49 UTC
Permalink
Post by Lamarque Vieira Souza
Post by Michael Biebl
I can reproduce the issue here. Unfortunately, the latest revert doesn't
resolve it. (Existing) connections still can't be activated in the plasma
widget.
User connections created using master branch does not work in nm09, only
the ones created as system connection works in nm09 branch. That is why I did
the first commit (to prevent user connections from being displayed in Plasma
NM/nm09).
It is a system connection afaics.
The "System connection" check box was checked when I created the connection and
the psk is stored in the keyfile in /etc/NetworkManager/system-connections/

The problem is, that after creating the connection, I can not activate it by
clicking on it in the "Connections" list.

Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110519/89903c95/attachment.sig
Loading...