On 9/5/2021 16:41, Chris Green wrote:
On Sun, Sep 05, 2021 at 01:51:22PM +0200, Matus UHLAR - fantomas via
Dnsmasq-discuss wrote:
On 03.09.21 17:13, Chris Green wrote:
I know there probably isn't a "right" way to do this but, while I've
been trying to sort out how to make my dns/dhcp more
On 03.09.21 17:13, Chris Green wrote:
I know there probably isn't a "right" way to do this but, while I've
been trying to sort out how to make my dns/dhcp more resilient, I have
looked at my existing dnsmasq running on a Pi and it looks a bit odd
to me.
It's a pretty standard, off the shelf
On Sun, Sep 05, 2021 at 08:30:11PM +0200, Matus UHLAR - fantomas via
Dnsmasq-discuss wrote:
> > > > > > On 03.09.21 17:13, Chris Green wrote:
> > > > > > > I know there probably isn't a "right" way to do this but, while
> > > > > > > I've
> > > > > > > been trying to sort out how to make my
On Sun, Sep 05, 2021 at 10:34:19PM +0200, Geert Stappers via Dnsmasq-discuss
wrote:
> On Sun, Sep 05, 2021 at 01:18:18PM +0100, Chris Green wrote:
> > On Sun, Sep 05, 2021 at 12:51:54PM +0100, Chris Green wrote:
> > [snip]
> > >
> > > It's the calls to systemd-start-resolvconf and
On Sun, Sep 05, 2021 at 01:18:18PM +0100, Chris Green wrote:
> On Sun, Sep 05, 2021 at 12:51:54PM +0100, Chris Green wrote:
> [snip]
> >
> > It's the calls to systemd-start-resolvconf and systemd-stop-resolvconf that
> > are causing
> > the error. For some reason on the Pi it causes this error,
On Sun, Sep 05, 2021 at 01:51:22PM +0200, Matus UHLAR - fantomas via
Dnsmasq-discuss wrote:
> > > On 03.09.21 17:13, Chris Green wrote:
> > > > I know there probably isn't a "right" way to do this but, while I've
> > > > been trying to sort out how to make my dns/dhcp more resilient, I have
> > >
On 03.09.21 17:13, Chris Green wrote:
> I know there probably isn't a "right" way to do this but, while I've
> been trying to sort out how to make my dns/dhcp more resilient, I have
> looked at my existing dnsmasq running on a Pi and it looks a bit odd
> to me.
>
> It's a pretty standard, off the
On 05.09.21 10:14, Chris Green wrote:
I have looked at a new installation of dnsmasq on another Raspberry Pi
and that does exactly the same thing. A ps shows:-
dnsmasq605 1 0 Sep04 ?00:00:17 /usr/sbin/dnsmasq -x
/run/dnsmasq/dnsmasq.pid -u dnsmasq -r
On Sun, Sep 05, 2021 at 10:14:02AM +0100, Chris Green wrote:
[snip]
>
> I'm going to try a dnsmasq installation on a non Raspberry Pi system and
> see what happens.
>
... and after going round lots of circles I think I have found what
causes the problem - it's the systemd configuration for
On Sun, Sep 05, 2021 at 12:51:54PM +0100, Chris Green wrote:
[snip]
>
> It's the calls to systemd-start-resolvconf and systemd-stop-resolvconf that
> are causing
> the error. For some reason on the Pi it causes this error, but not on my
> xubuntu system.
>
> Looking further the
On Sat, Sep 04, 2021 at 09:20:37PM +0100, Simon Kelley wrote:
> On 04/09/2021 17:14, Chris Green wrote:
> > When [re]starting dnsmasq I see the following in syslog:-
> >
> > Sep 4 17:01:08 dns systemd[1]: dnsmasq.service: Succeeded.
> > Sep 4 17:01:08 dns systemd[1]: Stopped dnsmasq - A
On Sat, Sep 04, 2021 at 10:19:09PM +0200, Geert Stappers via Dnsmasq-discuss
wrote:
> On Sat, Sep 04, 2021 at 08:16:44PM +0100, Chris Green wrote:
>
>
>
> > This is with log-queries=extra and log-dhcp set.
>
> And how is dnsmasq started? What is in configuration file?
>
>
> > Is there
On Sat, Sep 04, 2021 at 10:33:23PM +0100, Simon Kelley wrote:
> >
> > Do see already that dnsmasq is started (with some PID)
> > And there is another dnsmasq, probably a dnsmasq script,
> > with another PID.
> >
> > Answering "And how is dnsmasq started? What is in configuration file?"
> >
I have looked at a new installation of dnsmasq on another Raspberry Pi
and that does exactly the same thing. A ps shows:-
dnsmasq605 1 0 Sep04 ?00:00:17 /usr/sbin/dnsmasq -x
/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7
14 matches
Mail list logo
