Dhcp fixes may be too nitpicky

I have a system her which gets no DHCP lease now:

	10:05:36.952520 IP (tos 0x0, ttl 255, id 929, offset 0, flags [none], proto UDP (17), length 338)
	    10.1.18.8.67 > 10.1.18.223.68: BOOTP/DHCP, Reply, length 310, xid 0xc096f202, Flags [none]
		  Your-IP 10.1.18.223
		  Server-IP 172.30.11.200
		  Gateway-IP 10.1.18.8
		  Client-Ethernet-Address 10:98:36:a6:23:fc
		  file "\Boot\x64\wdsmgfw.efi"
		  Vendor-rfc1048 Extensions
		    Magic Cookie 0x63825363
		    DHCP-Message (53), length 1: Offer
		    Subnet-Mask (1), length 4: 255.255.254.0
		    RN (58), length 4: 1800
		    RB (59), length 4: 3150
		    Lease-Time (51), length 4: 3600
		    Server-ID (54), length 4: 172.30.11.200
		    Default-Gateway (3), length 4: 10.1.18.1
		    Domain-Name (15), length 9: "HTKNT.dk^@"
		    Domain-Name-Server (6), length 8: 172.30.27.4,172.30.27.5
		    Vendor-Option (43), length 7: 243.5.10.50.56.82.2

	DHCPOFFER from 10.1.18.11
	dhcpoffer: filename contains invalid characters.
	packet_to_lease failed.

I dont know if it is the backslash in "file" or the NUL in Domain-Name

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[email protected]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.