On Thu, 2015-11-05 at 19:15 +0100, Thomas Schäfer wrote:
> Hi,
>
> the last days I tested the NetorkManager with the Huwei E398 with dualstack
> on
> livecd / fresh installed systems. (ISP Deutsche Telekom(t-mobile))
>
> I observed the
>
> Opensuse 42.1
> nm1.0.6/mm1.4.10 --> uses qmi-wwan, c
Hi,
the last days I tested the NetorkManager with the Huwei E398 with dualstack on
livecd / fresh installed systems. (ISP Deutsche Telekom(t-mobile))
I observed the
Opensuse 42.1
nm1.0.6/mm1.4.10 --> uses qmi-wwan, connection editor allows to enable IPv6
and it works
Ubuntu 15.10
nm1.0.4/mm1.
On Wed, 2015-11-04 at 07:53 +0100, Tore Anderson wrote:
> * Lubomir Rintel
>
> > If anyone believes anything important is missing it's a good time to
> > speak up now.
>
> A couple of suggestions:
>
> 1) IPv6 method cleanup:
>* Get rid of «Automatic (DHCP only)»
>* Get rid of «Automatic
Hello,
On 05/11/2015 12:31, Lubomir Rintel wrote:
> Thanks for the patch, Rafaël.
>
> I'm not sure it's correct, though. The VPN plugin probably should
> probably only emit "Config" signal and not "IP4Config" when it has no
> IPv4 configuration.
You tell me :)
I've been looking at this issue fo
On 05/11/2015 12:38, Rafaël Carré wrote:
> Hello,
>
> On 05/11/2015 12:34, Lubomir Rintel wrote:
>> Hello Rafaël,
>>
>> I'm not sure I understand this one either. What do you mean it's fatal
>> now? There's just a g_warning(). Is it that without your other patch
>> this produces invalid IPv4 confi
Hello,
On 05/11/2015 12:34, Lubomir Rintel wrote:
> Hello Rafaël,
>
> I'm not sure I understand this one either. What do you mean it's fatal
> now? There's just a g_warning(). Is it that without your other patch
> this produces invalid IPv4 config and causes the daemon to tear the
> down the conn
Hello Rafaël,
I'm not sure I understand this one either. What do you mean it's fatal
now? There's just a g_warning(). Is it that without your other patch
this produces invalid IPv4 config and causes the daemon to tear the
down the connection?
On Tue, 2015-11-03 at 19:31 +0100, Rafaël Carré wrote:
Thanks for the patch, Rafaël.
I'm not sure it's correct, though. The VPN plugin probably should
probably only emit "Config" signal and not "IP4Config" when it has no
IPv4 configuration.
On Tue, 2015-11-03 at 19:31 +0100, Rafaël Carré wrote:
> IPv4 config can be set manually
> ---
> src/vpn-manag
