On 17/03/2023 17:54, Simon Kelley wrote:
> On 16/03/2023 16:04, Petr Menšík wrote:
>> I think it should be fixed on the side of clients instead. If they ask for
>> all addresses, just
>> give them when they do exist. If the network is very expensive (can you be
>> more concrete about
>> type of
Ooh. I am a very specialist use case here, but if you were interested to
develop this a little, I
have a related use case I would like to solve!
I kind of want the reverse. I have (very) expensive bandwidth and want to block
queries because
I know that none of my links will support ipv6 in
On 05/04/2023 14:32, Ed W wrote:
On 17/03/2023 17:54, Simon Kelley wrote:
On 16/03/2023 16:04, Petr Menšík wrote:
I think it should be fixed on the side of clients instead. If they ask for all
addresses, just
give them when they do exist. If the network is very expensive (can you be more
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 DHCP
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:
ra-param=
On Wed, Apr 5, 2023 at 7:00 AM Ed W wrote:
>
> I have customers on Iridium satellite links. So basic system is 2.4kbit
> (300 bytes/sec) and it costs
> around $100/MB
>
Completely off-topic, but can you tell us where the customers reside? My
wild guess is Antarctica. Seems like the only place