From: Daniel Wagner <wagi@monom.org>
To: daniel antoine <univac55@gmail.com>
Cc: connman@lists.linux.dev
Subject: Re: connman issues with enlightenment since last upgrade to version 1.41 Boîte de réception
Date: Mon, 14 Feb 2022 18:45:58 +0100 [thread overview]
Message-ID: <20220214174558.tuvtbfwohy3e63qu@carbon.lan> (raw)
In-Reply-To: <CA+iibzAqa2-xPiddMfjX-EmsvMt7dYV39mW5WBLnUNN=B9gYAA@mail.gmail.com>
On Mon, Feb 14, 2022 at 05:33:25PM +0100, daniel antoine wrote:
> I have seen your answer on lore.kernel.org/connman but not on my
> e-mail. How can I do a log ? by adding /usr/bin/connman -n -d
> /home/user/connmanlog.txt in the connman.service file ? I have tried
> manually, it has functionned but not written the file.
ConnMan writes to stderr for logging, so you need to redirect the stderr
to stdout:
# connmand -n -d 2>&1 > cm-log.txt
> I can reproduce the problem by just removing the main.conf file with
> EnableCheckOnline=true
Alright, sounds something is not getting the default setup correctly.
> in both cases (host wifi interface ready or online) when I start a
> virtual machine and when I do an upgrade in the VM and reach the repo
> server the vnet0 interface on the host get an address 169.254.xxx.xxx
So there is no DHCP server. ConnMan tries on default to get a DHCP lease
if this fails it will setup the interface using IPv4LL (a.k.a IPv4 link
local or bonjour). Anyway you can configure ConnMan not to use
DHCP/IPv4LL.
Daniel
prev parent reply other threads:[~2022-02-14 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 16:33 connman issues with enlightenment since last upgrade to version 1.41 Boîte de réception daniel antoine
2022-02-14 17:45 ` Daniel Wagner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220214174558.tuvtbfwohy3e63qu@carbon.lan \
--to=wagi@monom.org \
--cc=connman@lists.linux.dev \
--cc=univac55@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).