Hey Treysis,
On Thu, 2021-09-02 at 22:18 +0200, Trey Sis wrote:
> I would really love to have some feedback if you are missing some
> detail.
Your log_queries() call seems incorrect:
> F_CONFIG | F_IPV6 | F_NEG
will lead to
> config is NODATA-IPv6
however, you obviously want
> config is NO
dnsmasq-2.85 (Fedora 33, x86_64)
multiple upstream DNS servers in config file.
No --strict-order, No --all-server setting .
Symptom
Explanation about --all-servers in dnsmasq(8) man page could
be different from actual dnsmasq behavior.
In man page, it is written that
"By default, when dnsmasq has
Two questions really:-
Is the file /var/lib/misc/dnsmasq.leases the only place where
dnsmasq keeps DHCP/IP/Name information across restarts? I.e. if I
delete that file will new DHCP requests get new IPs? (or does the
client have some memory of the last IP it got?)
If a clie
On 03/09/2021 11:31, Chris Green wrote:
> Two questions really:-
>
> Is the file /var/lib/misc/dnsmasq.leases the only place where
> dnsmasq keeps DHCP/IP/Name information across restarts? I.e. if I
> delete that file will new DHCP requests get new IPs? (or does the
> client have
On 02/09/2021 15:30, Chris Green wrote:
> On Thu, Sep 02, 2021 at 02:58:44PM +0100, Kevin Tedder wrote:
>> Personally, I'd rather have two systems fully operational all the time. To
>> discover that the back up solution is not working at the critical moment is
>> the same as not having a backup at
Hi Simon and Geoff,
I would include just small safeguard in the code. It may dereference
negative char index in case of empty string. No empty strings there are
allowed now, but I think failsafe in this place would be worth few cpu
cycles.
Patch attached.
What would you think?
Cheers,
Petr
On
Hey Simon,
this small patch adds the DHCP options "posix-timezone" and "tzdb-
timezone" as defined in RFC 4833, Section 2:
https://datatracker.ietf.org/doc/html/rfc4833#section-2
Examples for valid options are
> dhcp-option = option:posix-timezone,"CEST-
1CET,M3.2.0/2:00:00,M11.1.0/2:00:00"
and
One small issue was detected in 2.85 release Coverity scan and is still
present in current version. It is in unlikely tftp error path, but still
should ensure error is sent in case of interrupt received during sendto().
Patch attached.
On 8/25/21 3:46 PM, Simon Kelley wrote:
> I just pushed a few
On Fri, 3 Sept 2021 at 13:41, Chris Green wrote:
> On Fri, Sep 03, 2021 at 12:08:20PM +0100, Ed W wrote:
> > On 03/09/2021 11:31, Chris Green wrote:
> > > Two questions really:-
> > >
> > > Is the file /var/lib/misc/dnsmasq.leases the only place where
> > > dnsmasq keeps DHCP/IP/Name info
On Fri, Sep 03, 2021 at 12:08:20PM +0100, Ed W wrote:
> On 03/09/2021 11:31, Chris Green wrote:
> > Two questions really:-
> >
> > Is the file /var/lib/misc/dnsmasq.leases the only place where
> > dnsmasq keeps DHCP/IP/Name information across restarts? I.e. if I
> > delete that file wi
On Fri, Sep 03, 2021 at 01:58:54PM +0100, Jesus M Diaz wrote:
> I wasn't considering erasing/deleting the dnsmasq.leases file, I was
> rather thinking of copying it to a non-running backup dnsmasq so
> that
> if/when the running dnsmasq fails I can start the other and it will
>
On 9/3/21 5:58 AM, Jesus M Diaz wrote:
I wasn't considering erasing/deleting the dnsmasq.leases file, I was
rather thinking of copying it to a non-running backup dnsmasq so that
if/when the running dnsmasq fails I can start the other and it will
give out the same IPs.
Do you re
On Fri, 3 Sept 2021 at 15:16, Chris Green wrote:
> On Fri, Sep 03, 2021 at 01:58:54PM +0100, Jesus M Diaz wrote:
> > I wasn't considering erasing/deleting the dnsmasq.leases file, I was
> > rather thinking of copying it to a non-running backup dnsmasq so
> > that
> > if/when t
On 9/3/21 7:02 AM, Chris Green wrote:
I was thinking about the usual "one local server and 1.1.1.1 or
8.8.8.8 as secondary" but now I think about it I suppose there's
nothing difficult about providing two local servers. However will
having one of them non-functional slow things down at all?
S
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 Raspberry Pi installation using
the Lite ver
A DHCP client will try to renew it's lease half way through the time
span of the lease by talking to the DHCP server it got the lease from.
It will continue to use the address for the rest of the lease span if it
doesn't get a reply, and 7/8ths of the time through the lease it will
start to broadca
If I have set dhcp-optsdir in /etc/dnsmasq.conf and add a file to the
directory it points to I assume any extra configuration in the added
file will 'just happen' without any restart or signalling of dnsmasq.
However (like the description for dhcp-hostsdir I presume that an
option I have added as
On 9/3/21 1:23 PM, Chris Green wrote:
If I have set dhcp-optsdir in /etc/dnsmasq.conf and add a file to the
directory it points to I assume any extra configuration in the added
file will 'just happen' without any restart or signalling of dnsmasq.
However (like the description for dhcp-hostsdir I
Hi Simon,
I have prepared a set of patches applied over 2.86rc3 release. They were
made to silent some of reports from Coverity scans we do for our
packages. I did include reported parts in commit messages, so commit
messages are somehow noisy and contain more bytes that the diffs itself.
It shou
19 matches
Mail list logo
