| 1 |
On Thu, 2009-11-19 at 15:55 +0100, SpaceCake wrote: |
| 2 |
> yes, but as I told earlier in nm-applet this section is grey, so I |
| 3 |
> cannot |
| 4 |
> add vpn configs. when I start vpnc with the correct config from root's |
| 5 |
> shell, it is working perfectly and connect me to the vpn gw I use, so |
| 6 |
> this |
| 7 |
> is why I said the problem maybe in the deep somewhere around dbus |
| 8 |
> communication, but I'm not sure |
| 9 |
|
| 10 |
I don't know why these options would be greyed out. Unless.. do you |
| 11 |
actually have the plugins installed? |
| 12 |
|
| 13 |
$ equery l networkmanager* |
| 14 |
* Searching for networkmanager* ... |
| 15 |
[IP-] [ ~] net-misc/networkmanager-0.7.1_p20090824 (0) |
| 16 |
[IP-] [ ~] net-misc/networkmanager-openvpn-0.7.1-r1 (0) |
| 17 |
[IP-] [ ~] net-misc/networkmanager-vpnc-0.7.1 (0) |
| 18 |
|
| 19 |
Does it even show up in nm-connection-editor? |
| 20 |
|
| 21 |
AFAIK the UI just uses these plugins to create a vpn configuration. This |
| 22 |
is long before actually talking to the nm daemon. So the UI just |
| 23 |
creates a config and stores it (in GNOME the non-system configs are |
| 24 |
stored in gconf at /system/networking/connections. Then when you want |
| 25 |
to connect, the UI grabs whatever config and passes it to the nm daemon |
| 26 |
(via dbus?). Your issue seems to be with the first part of this process |
| 27 |
(the UI), not the second. |
| 28 |
|
| 29 |
-a |
Archives