- This topic has 18 replies, 8 voices, and was last updated Dec 14-7:28 pm by Yoghi.
-
Posts
-
blackwood
Sorry anticapitalista but I have no idea, maybe during unbound installation it changed it to 127.0.0.1 and made it unwritable. as soon as i made it writable, it took dns addresses from my router and connected automatically… I don’t know for sure
seaken64
Why was it necessary to uninstall Connman? AntiX has a utility to switch from Connman to Ceni. Would that not suffice? I also use Ceni but I don’t uninstall anything.
Seaken64
I noticed connman stil running in htop even though i was using ceni, thought i’d just uninstall it…
Yoghi
Hello blackwood,
it was enough to kill connman and using sysv-rc-conf avoid its start.
I had the opposite problem, neither ceni nor network manager were able to establish a connection to my phone, a Nokia 2, as hotspot using a D-Link 131 E1 usb dongle on PC.
Connman, tried with a bunch of distros, is the only one able to connect to hotspot and let me surf.
It has only a little trouble, connman listens on port 53 so installing unbound results in a “port already in use” error but a reboot solves the issue automagically.
It makes no sense to repeat what already written if you are interested, hoping that it helps, here’s the link to my post on linuxquestions about unbound + connman
To me connman is the only one working flawlessly with my hardware.
To avoid /etc/resolv.conf changes try with an entering hook creating a script which does nothing when resolvconf try to set /etc/resolv/conf
I called it nodnsupdate with the following content
#!/bin/sh make_resolv_conf(){ : }delete the /etc/resolv.conf present (which should be a link created by resolvconf) and create a new one with only two lines
nameserver 127.0.0.1 nameserver ::1You should have always configured unbound as dns for your machine.
- You must be logged in to reply to this topic.
