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 string
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
https://lists.thekelleys.org.uk/c
Hi Matthias,
as far as RFCs are concerned, your observation seems valid.
RFC 951 section 3 (Packet Format) requires the boot file name (as
provided by option dhcp-boot) to be a null terminated string.
RFC 2132 section 9.4 ff.(TFTP server name and Bootfile name) define the
respective parameters
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 ca
