thx for the hints. got the rfc
Options containing NVT ASCII data SHOULD
NOT include a trailing NULL; however, the receiver of such options
MUST be prepared to delete trailing nulls if they exist. The
receiver MUST NOT require that a trailing null be included in the
data. In the
Am Tue, 11 Jun 2024 12:46:40 +0200
schrieb Matthias Lay :
> dhcp-option=tag:2,option:66,"fake2quoted"
sorry. typo
dhcp-option=66,"fake2quoted"
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
Hi,
I noticed there is a ending zero in dhcp options replys. Just wanted to
check if this is intended.
my test was
dhcp-option=tag:2,option:66,"fake2quoted"
the reply to a request looks like that in tcpdump
TFTP (66), length 12: "fake2quoted^@"
it includes an \x00 at the end of the
Am Sat, 17 Feb 2024 22:36:04 +
schrieb Simon Kelley :
> On 16/02/2024 13:24, Matthias Lay via Dnsmasq-discuss wrote:
> >
> > Hi List,
> >
> > I am trying to set the *dhcp-ignore* option for a single dhcp-range
> > only. after reading the manpage my setup
Hi List,
I am trying to set the *dhcp-ignore* option for a single dhcp-range
only. after reading the manpage my setup is like this:
dhcp-range=set:8,22.22.22.1,22.22.22.100
dhcp-ignore=tag:8,tag:!known
this doesnt seem to work. the tags are there and logged, but the
request is not ignored. it
