1:10 p.m.
Hello connman devs,
Last update was wonderful - real support for iwd as a WiFi backend is a
great improvement and as I always say when reporting issues here, it's a
real pleasure using connman.
The reason I'm posting this thread is because connman does weird things
with it's /var/run/connman/resolv.conf (which I linked to
/etc/resolv.conf).
I'm connected both with WiFi and Ethernet to my home network but since
I've set PreferredTechnologies=ethernet,wifi my default route is through
the Ethernet connection - exactly as I want it.
I have a few other settings in my /etc/connman/main.conf so perhaps
they are the reason I'm having trouble with /etc/resolv.conf. Here it
is:
[General]
AutoConnectRoamingServices=true
PersistentTetheringMode=true
SingleConnectedTechnology=true
PreferredTechnologies=ethernet,wifi
AllowDomainnameUpdates=false
AllowHostnameUpdates=false
The problem I'm having is that I get duplicate entries in
/etc/resolv.conf, perhaps because I'm connected to the same network
twice. This is the /etc/resolv.conf connman comes up with whenever I
boot:
search Home Home Home
nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
nameserver 192.168.14.1
Every once in a while (not only after boot), I need to change
/etc/resolv.conf to this when I feel the internet becomes slow:
search Home
nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
nameserver 192.168.14.1
Since the `search` entry seems to be related to my domain, I've added
AllowDomainnameUpdates=false in order to mitigate that but it doesn't
help.
Perhaps I don't understand well the configuration file parameters,
although I've read the manpage thoroughly. Anyway, I think connman
should avoid writing a `resolv.conf` file with duplicate entries like it
does to mine.
Waiting for your reply, Thanks.
Doron.
9:07 a.m.
Hi Doron,
On 4/22/19 1:10 PM, Doron Behar wrote:
Hello connman devs,
Last update was wonderful - real support for iwd as a WiFi backend is a
great improvement and as I always say when reporting issues here, it's a
real pleasure using connman.
The reason I'm posting this thread is because connman does weird things
with it's /var/run/connman/resolv.conf (which I linked to
/etc/resolv.conf).
I'm connected both with WiFi and Ethernet to my home network but since
I've set PreferredTechnologies=ethernet,wifi my default route is through
the Ethernet connection - exactly as I want it.
Good to hear that this works :)
I have a few other settings in my /etc/connman/main.conf so perhaps
they are the reason I'm having trouble with /etc/resolv.conf. Here it
is:
[General]
AutoConnectRoamingServices=true
PersistentTetheringMode=true
SingleConnectedTechnology=true
PreferredTechnologies=ethernet,wifi
AllowDomainnameUpdates=false
AllowHostnameUpdates=false
The problem I'm having is that I get duplicate entries in
/etc/resolv.conf, perhaps because I'm connected to the same network
twice. This is the /etc/resolv.conf connman comes up with whenever I
boot:
search Home Home Home
nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
nameserver 192.168.14.1
That looks wrong indeed.
Every once in a while (not only after boot), I need to change
/etc/resolv.conf to this when I feel the internet becomes slow:
search Home
nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
nameserver 192.168.14.1
Since the `search` entry seems to be related to my domain, I've added
AllowDomainnameUpdates=false in order to mitigate that but it doesn't
help.
Nothing obvious wrong. I'll try to recreate this here.
Perhaps I don't understand well the configuration file
parameters,
although I've read the manpage thoroughly. Anyway, I think connman
should avoid writing a `resolv.conf` file with duplicate entries like it
does to mine.
Waiting for your reply, Thanks.
Thanks for the report. I'll added the task to my todo list.
Thanks,
Daniel
6:12 p.m.
Thanks Daniel,
Indeed this could be very helpful in the next release.
Would it be possible if perhaps you'll kindly post the commit ids that
fixed this when those will be ready? I'd love to build connman with
those patches because this is kind of crucial for me.
Thanks again,
Doron.
On Wed, Apr 24, 2019 at 09:07:13AM +0200, Daniel Wagner wrote:
Hi Doron,
On 4/22/19 1:10 PM, Doron Behar wrote:
> Hello connman devs,
>
> Last update was wonderful - real support for iwd as a WiFi backend is a
> great improvement and as I always say when reporting issues here, it's a
> real pleasure using connman.
>
> The reason I'm posting this thread is because connman does weird things
> with it's /var/run/connman/resolv.conf (which I linked to
> /etc/resolv.conf).
>
> I'm connected both with WiFi and Ethernet to my home network but since
> I've set PreferredTechnologies=ethernet,wifi my default route is through
> the Ethernet connection - exactly as I want it.
Good to hear that this works :)
> I have a few other settings in my /etc/connman/main.conf so perhaps
> they are the reason I'm having trouble with /etc/resolv.conf. Here it
> is:
>
> [General]
> AutoConnectRoamingServices=true
> PersistentTetheringMode=true
> SingleConnectedTechnology=true
> PreferredTechnologies=ethernet,wifi
> AllowDomainnameUpdates=false
> AllowHostnameUpdates=false
>
> The problem I'm having is that I get duplicate entries in
> /etc/resolv.conf, perhaps because I'm connected to the same network
> twice. This is the /etc/resolv.conf connman comes up with whenever I
> boot:
>
> search Home Home Home
> nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
> nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
> nameserver 192.168.14.1
>
That looks wrong indeed.
> Every once in a while (not only after boot), I need to change
> /etc/resolv.conf to this when I feel the internet becomes slow:
>
> search Home
> nameserver fdc9:8a32:cbfb:0:16ae:dbff:fe55:f320
> nameserver 192.168.14.1
>
> Since the `search` entry seems to be related to my domain, I've added
> AllowDomainnameUpdates=false in order to mitigate that but it doesn't
> help.
Nothing obvious wrong. I'll try to recreate this here.
> Perhaps I don't understand well the configuration file parameters,
> although I've read the manpage thoroughly. Anyway, I think connman
> should avoid writing a `resolv.conf` file with duplicate entries like it
> does to mine.
>
> Waiting for your reply, Thanks.
Thanks for the report. I'll added the task to my todo list.
Thanks,
Daniel
11:13 a.m.
HI Doron,
On 28.04.19 18:12, Doron Behar wrote:
Would it be possible if perhaps you'll kindly post the commit ids
that
fixed this when those will be ready? I'd love to build connman with
those patches because this is kind of crucial for me.
Could you test these patches:
[PATCH 0/2] Don't export duplicate entries in resolv.conf
Thanks,
Daniel
3:25 p.m.
I've patched these against the 1.37 tag and everything seems fine.
I've tried to delete the file (/var/run/connman/resolv.conf) and restart
connmand and I didn't see any duplicate entries like before.
I've also inspected the file during disconnections and connections and
everything seems fine.
Thanks a lot! I'll ask the Arch Linux package maintainers to include
thes patches.
Doron.
On Mon, Apr 29, 2019 at 11:13:12AM +0200, Daniel Wagner wrote:
HI Doron,
On 28.04.19 18:12, Doron Behar wrote:
> Would it be possible if perhaps you'll kindly post the commit ids that
> fixed this when those will be ready? I'd love to build connman with
> those patches because this is kind of crucial for me.
Could you test these patches:
[PATCH 0/2] Don't export duplicate entries in resolv.conf
Thanks,
Daniel
626
days inactive
636
days old
5 comments
2 participants
participants (2)
-
Daniel Wagner -
Doron Behar