It looks like between version 1.3 and 1.5 you changed the dhcp-server “tftp-server-name” parameter as to not allow complete url paths. In version 1.2 we could add “tftp-server-name http://pbx.XXXXXX.com/app/provision/ ” (or even “tftp-server-name http://pbx.XXXXXX.com/app/provision/$ma=XXXX ” to auto…

I can confirm that this bug exist. vyos@alpha# set service dhcp-server shared-network-name subnet tftp-server-name ftp://user:pass@serv01.nowhere.tld Error: ftp://user:pass@serv01.nowhere.tld is not a valid IPv4 address

Both standards regarding tftp-server-name says its the name of the server and not a URI which is the expected value: [image] RFC 2132: DHCP Options and BOOTP Vendor Extensions This document specifies the current set of DHCP options. Future options will be specified in separate RFCs. The…

DHCP_SERVER tftp-server-name

Bugs

Apachez October 28, 2024, 5:39am 5

You are expected to use DHCP option 209 aka configuration-file and DHCP option 210 aka path-prefix to get the URI your client can request from the server (along with the tftp-server-name):