On 30.11.23 00:09, Chris Friesen via Dnsmasq-discuss wrote:
I was just wondering whether the --interface and --except-interface
options to dnsmasq would also apply to messages like DHCPDISCOVER and
DHCPREQUEST
Yes.
You may also want to further tune usage via '--no-dhcp-interface' (or
maybe '-
On 29/11/2023 23:09, Chris Friesen via Dnsmasq-discuss wrote:
Hi,
I was just wondering whether the --interface and --except-interface
options to dnsmasq would also apply to messages like DHCPDISCOVER and
DHCPREQUEST which are broadcast to 255.255.255.255.
In my particular case I have an ex
On 11/30/2023 6:13 AM, Simon Kelley wrote:
As you've surmised, making more than one dnsmasq/DHCP instance on a
server work is tricky.
It can be done, but only in a very specific way.
Each dnsmasq instance must be configured to serve exactly one interface,
using the --interface config option.
Looks good. Patch applied.
Cheers,
Simon.
On 24/11/2023 11:13, Damian Sawicki via Dnsmasq-discuss wrote:
Hello dnsmasq experts,
Following up on the recent addition of the flag --max-tcp-connections, I'd like
to propose a patch with monitoring of the number of TCP connections. This way,
a
Hello!
I have sent similar proposal already in year 2021 [1]. But I have
reworked that a bit to reuse existing --local-service option and just
add new parameter to it. If --local-service=host is used, dnsmasq will
bind to addresses on lo interface only. It will not even open port on
other int
On 11/30/2023 6:13 AM, Simon Kelley wrote:
As you've surmised, making more than one dnsmasq/DHCP instance on a
server work is tricky.
It can be done, but only in a very specific way.
Each dnsmasq instance must be configured to serve exactly one interface,
using the --interface config option.
U
