By default interface name is 'tun' with an incrementing number (tun0,
tun1, ...). By specifying 'Interface name' in vpnc config you can change
the name to something more descriptice.
---
properties/nm-vpnc-dialog.ui | 89 +---
properties/nm-vpnc.c |
On Sun, 2014-08-31 at 16:20 +0200, Jérémie Vandeville wrote:
I'm currently testing 802.1x with freeradius and networkmanager. It's
working very well but I've a question : Is it possible to use gnome
credentials (login/password) with eap-ttls or peap (or even with md5)
? For the moment, it
This is how most users are expecting to use it, with (sadly) windoze
being the golden example for seamless integration. Every wireless
vendor just expects there to be integration on the backend with AD/LDAP
or some upstream directory provider if you're doing user/pass-based auth
of some form
On Mon, 2014-09-01 at 10:26 -0400, Gene Czarcinski wrote:
OK, I give up ... what is the magic dance I need to do to restore a
forgotten NIC?
I was playing with gnome's network editor and on the reset page for a
device, I hit the Forget button. Device was removed but now I would
like to
On Mon, 2014-09-22 at 10:02 +0200, Christian Hesse wrote:
By default interface name is 'tun' with an incrementing number (tun0,
tun1, ...). By specifying 'Interface name' in vpnc config you can change
the name to something more descriptice.
So this is great, and ties in with some other stuff
On Fri, 2014-09-19 at 21:21 -0500, Kevin Baker wrote:
Hello all,
I was wondering if there was some justification for the priority
listing in src/nm-device.c: nm_device_get_priority(). Specifically,
that a MODEM connection is higher in the priority than a WIFI
connection.
Note that this
On Thu, 2014-09-04 at 22:04 -0400, Mathieu Trudel-Lapierre wrote:
Signed-off-by: Mathieu Trudel-Lapierre mathieu.trudel-lapie...@canonical.com
---
introspection/nm-access-point.xml | 3 +++
libnm-glib/libnm-glib.ver | 1 +
libnm-glib/nm-access-point.c | 35
