Remove previously created network after creating a new one.
This prevents wpa_supplicant network objects (wpa_cli list_net)
from piling up.
---
gsupplicant/supplicant.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/gsupplicant/supplicant.c b/gsupplicant/supplicant.c
index
Hi,
Over the years operational experience has revealed that the 6to4
protocol suffers from so severe operational problems that it simply
cannot be fixed. Therefore, the IETF recently decided to deprecate 6to4:
http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic
The document is approved
Hi Patrik,
* Patrik Flykt
Here's the leaky point where you have it wrong.
The code does not ever supply DHCP gateways as NTP servers. Or provide
any other options as something they're not for that matter.
The default gateway is added to the list as a possible NTP server in a
completely
From: Pasi Sjöholm pasi.sjoh...@jollamobile.com
Setting up gateway is handled by the kernel
therefore ConnMan does not need to do it
when dhcpv6 is used.
This fixes the issue with IPv6 nameserver host routes
getting added as link-local due the gateway in the
ipconfig was always null.
Reported
Hi Marcel,
I would initially hide it behind a main.conf option, but have it
defaulting to disable to comply with this updated RFC once it has
been accepted.
Ack. I'll send a patch to the list, not sure I'll get around to doing
it before Easter though as I need some time to familiarise myself
On Tue, 2015-03-24 at 13:38 +0200, pasi.sjoh...@jolla.com wrote:
From: Pasi Sjöholm pasi.sjoh...@jollamobile.com
Setting up gateway is handled by the kernel
therefore ConnMan does not need to do it
when dhcpv6 is used.
This fixes the issue with IPv6 nameserver host routes
getting added
Hi Tore,
Over the years operational experience has revealed that the 6to4
protocol suffers from so severe operational problems that it simply
cannot be fixed. Therefore, the IETF recently decided to deprecate 6to4:
http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic
The document
On Tue, 2015-03-24 at 09:32 +0100, Sven Schwedas wrote:
Do you really want to special-case every single broken network setup
under the sun?
As this case is existing behavior, I'm not going to remove it and break
things for users just because.
(And does any networking client apart from connman
Do you really want to special-case every single broken network setup
under the sun?
(And does any networking client apart from connman support this? I think
the usual suspects in corporate networks – namely Windows and maybe RHEL
with NetworkManager – don't.)
On 2015-03-24 04:38, Marcel Holtmann
