Quoting Steve Litt (sl...@troubleshooters.com):
> Yes, and I think that's outdated.
You can configure your DHCP client software to _not_ use nameserver IPs
sent by the DHCPd and instead use locally defined ones. If using
ISC's dhclient, set
supersede domain-name-servers ip-address [,
On Thu, 11 Jul 2019 20:07:05 -0700
Rick Moen wrote:
> http://connectman.sourceforge.net/
CLI connection manager looks pretty cool, especially if I can team it
up with UMENU. I might try it out as a substitute for using wpa_gui and
wpa_password.
SteveT
Steve Litt
July 2019 featured book:
On Thu, 11 Jul 2019 22:14:45 -0400
Hendrik Boom wrote:
> On Thu, Jul 11, 2019 at 08:34:59PM -0400, Steve Litt wrote:
> > Hi Hendrik,
> >
> > It isn't just conman: It's all these silly "we do it all for you"
> > networking helpers. I just do this:
> >
> > chattr +i /etc/resolv.conf
> >
> >
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> Does conman, the connection manager, originate from Helpful Lennart?
Nei.
http://connectman.sourceforge.net/
> And doesn't the DNS IP number on a mobile device like a laptop normally
> come from the DHCP protocol?
Pretty nearly universally,
On Thu, Jul 11, 2019 at 08:34:59PM -0400, Steve Litt wrote:
> On Wed, 10 Jul 2019 11:31:31 -0400
> Hendrik Boom wrote:
>
> > This morning DNS wasn't working on my laptop, though it worked
> > perfectly well on the server it wifi-ed to.
> > After some pinging and checking connections, I found
On Wed, 10 Jul 2019 11:31:31 -0400
Hendrik Boom wrote:
> This morning DNS wasn't working on my laptop, though it worked
> perfectly well on the server it wifi-ed to.
> After some pinging and checking connections, I found this on my
> laptop.
>
> The file /etc/resolv.conf:
>
> # Generated by
Quoting Dimitris via Dng (dng@lists.dyne.org):
> maybe it expects you to run a local caching dns resolver :D
The best (IMO) term for what you're describing is 'recursive server',
though there's a lot of variant word usage.
I'm using connman too! :(
I just updated mine /etc/resolv to
nameserver 8.8.8.8
nameserver 8.8.4.4
and it was instantly changed to
nameserver 209.222.18.222
nameserver 209.222.18.218
Ozi
On Thu, Jul 11, 2019 at 1:31 AM Hendrik Boom wrote:
> This morning DNS wasn't working on my laptop,
On 7/10/19 6:31 PM, Hendrik Boom wrote:
> Now why would the connection manager (conman) suddenly be setting my
> nameserver to localhost?
maybe it expects you to run a local caching dns resolver :D
it might actually provide a faster experience... using
unbound/dnsmasq/others. wiki.archlinux.org
https://manpages.debian.org/stretch/connman/connman.8.en.html
Look at the -r option. Maybe that lets you disable the built-in DNS proxy. Was
that previously set somewhere?
> On 11 Jul 2019, at 01:31, Hendrik Boom wrote:
>
> This morning DNS wasn't working on my laptop, though it worked
This morning DNS wasn't working on my laptop, though it worked perfectly
well on the server it wifi-ed to.
After some pinging and checking connections, I found this on my
laptop.
The file /etc/resolv.conf:
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1
Now why would the
11 matches
Mail list logo
