On Wed, Dec 08, 2021 at 01:18:42AM +0100, Petr Menšík wrote:
> Hi Simon and others,
>
> I am debugging strange issue, which happens inside OpenStack in certain
> situations. It seems under not precisely defined conditions dnsmasq
> returns "no address available" error even in situation, when not
On Thu, Dec 09, 2021 at 03:28:40AM +0100, Petr Menšík wrote:
> On 12/5/21 19:44, Fabian Druschke wrote:
> > Hey friends, i hope you all are doing fine.
> >
> > Currently i'm facing a little challenge. I have a large network with
> > more or less 30k clients, and i need a router for NAT from the
Hi,
yes, there were some fixes related to bind to device option. I would
suggest looking at CentOS 8/RHEL 8 patches of 2.79 [1], which hopefully
fixed also regressions caused by the CVE fixes. Description of the
problem matches something I had to fix later, it should be some of
recent patches.
I
I am afraid there are some implementation problems found in IPv4 DHCP
allocations. If multiple machines start at the same time (I have script
to launch 16), especially with dhcp-sequential-ip it is problematic. ISC
dhclient can cope with it somehow well, but some PXE booting firmware is
less
Interesting, I am just debugging situation when multiple instances start
and request DHCP at similar time. Without no-ping option, it works quite
bad. Even starting 16 instances at the same time does not work reliably
to us with ping enabled. It seems our 2.79 version is broken, 2.81 were
fixed.
On 18/11/2021 18:21, Sung Pae wrote:
> Hello list,
>
> The --rebind-domain-ok option is broken in v2.86 and on master in the
> following ways:
>
> * In v2.85, --stop-dns-rebind --rebind-domain-ok=test.me would only allow
> "test.me" and subdomains of "test.me" to return private addresses to
