On Mon, 2014-09-29 at 10:27 +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.
Pushed this, thanks! After some consideration thou
Dan Williams on Tue, 2014/09/30 12:33:
> On Mon, 2014-09-29 at 10:27 +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.
>
>
Christian Hesse on Mon, 2014/09/29 14:46:
> By default interface name is 'tun' or 'tap' with an incrementing number
> (tun0, tun1, ... or tap0, tap1, ...). By specifying 'Interface name' in
> vpnc config you can change the name to something more descriptice.
The vpnc part has been merge with some
Hi,
I am testing a little bit ipv6 (v6 only and v4/v6-dualstack) mobile
connections via UMTS and LTE.
While modemmamanger
mmcli -m 0 --simple-connect="apn=internet,ip-type=ipv4v6"
mmcli -m 0 --simple-connect="apn=internet,ip-type=ipv6"
works. (using qmi, mbim and/or at+cgdcont ) I want to go u
On Tue, 2014-09-30 at 21:52 +0200, Thomas Schäfer wrote:
> Hi,
>
> I am testing a little bit ipv6 (v6 only and v4/v6-dualstack) mobile
> connections via UMTS and LTE.
>
> While modemmamanger
>
> mmcli -m 0 --simple-connect="apn=internet,ip-type=ipv4v6"
> mmcli -m 0 --simple-connect="apn=interne