Hi,
On Wed, 2015-03-04 at 12:47 +0200, Mihai Neagu wrote:
> So the presence of the carrier (cable plugged in) to all ethernet
> interfaces should trigger auto-connect.
Autoconnect is already triggered when carrier is present. Autoconnect
considers everything to be fine when at least on
Patrik,
So the presence of the carrier (cable plugged in) to all ethernet
interfaces should trigger auto-connect.
Is there a tracker where I can create an entry for this issue (like
bugzilla)?
Will the fix also include auto-connect to gadget interfaces which have
the cable plugged in to a
Hi,
On Tue, 2015-02-24 at 17:59 +0200, Mihai Neagu wrote:
> >> If you are using Ethernet, then both interfaces should be configured.
> >> In general, the plugged in cable aka carrier for Ethernet was support
> >> to indicate that it gets used. Of course only one can have the default
> >>
Marcel, Patrik,
Yes. I'm thinking about two new values for "IPv4.method", called
"dhcp-only" and "linklocal-only". Using main.conf would not be the
appropriate place because we are interested in interface specific
settings where, for instance, one interface can be dhcp-only and
another linklocal
Hi Mihai,
> > Yes. I'm thinking about two new values for "IPv4.method", called
> > "dhcp-only" and "linklocal-only". Using main.conf would not be the
> > appropriate place because we are interested in interface specific
> > settings where, for instance, one interface can be dhcp-only and
Hi Mihai,
> We're looking into using connman as the network manager for our programmable
> embedded systems.
>
> It currently has most of the desired features, but we would still need the
> following functionality:
>
> 1. DHCP-only method - to not fall back to link-local if no DHCP lease is
>
Hi guys,
We're looking into using connman as the network manager for our
programmable embedded systems.
It currently has most of the desired features, but we would still need
the following functionality:
1. DHCP-only method - to not fall back to link-local if no DHCP lease is
issued
2. Se