On 11/04/2023 14:04, Ben Hendin wrote:
" looks like we need
--no-dhcpv4-interface and --no-dhcpv6-interface. That would certainly
solve your problem."
Just to clarify - you are stating that these options don't currently
exist and would need to be implemented in a future version?
I think every incoming device tags dhcp requests with tag of that
interface name.
Therefore it should be possible:
dhcp-range=tag:eth1,192.168.1.50-192.168.1.100
dhcp-range=tag:eth2,10.0.0.100-10.0.0.150
If you enable --log-dhcp for extra details logged, it should log for
each query all tags
" looks like we need
--no-dhcpv4-interface and --no-dhcpv6-interface. That would certainly
solve your problem."
Just to clarify - you are stating that these options don't currently exist
and would need to be implemented in a future version?
I have blocked the request via ebtables on my device for
On 05/04/2023 19:04, Ben Hendin wrote:
Thanks Simon (apologies - my first reply went to your direct email
instead of back to the list which was not my intent!)
There are dhcp4 ranges defined, but none with ranges for those interface.
For example, the interface which should give out the RAs
Thanks Simon (apologies - my first reply went to your direct email instead
of back to the list which was not my intent!)
There are dhcp4 ranges defined, but none with ranges for those interface.
For example, the interface which should give out the RAs is br0, and the
relevant lines are:
On 03/04/2023 16:54, Ben Hendin wrote:
I'm running Dnsmasq version 2.85-openssl-5-g989ee98 on an embedded
device (Entware installation)
I am seeing log entries that state the following when clients come onto
the network to request IP addresses via DHCP:
"no address range available for
I'm running Dnsmasq version 2.85-openssl-5-g989ee98 on an embedded device
(Entware installation)
I am seeing log entries that state the following when clients come onto the
network to request IP addresses via DHCP:
"no address range available for DHCP request via br0"
br0 is a bridged interface
