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 provision telephones. It appears that version 1.5 only allows the first part (i.e. “pbx.XXXXXXX.com”). This creates an issue where the application (in this case a telephone server) needs the complete path to provision.
I can confirm that this bug exist.
vyos@alpha# set service dhcp-server shared-network-name subnet tftp-server-name ftp://user:[email protected]
Error: ftp://user:[email protected] 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:
So in short “pbx.example.com” is valid and so is “192.0.2.1” but not “http://pbx.example.com/path/configfile”.
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):
https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml