When proto://path format is used to specify bootfile, the latter is transformed to work as an input argument to either wget or tftp, loosing the protocol information in the process.
Thus, if the first netboot fails for some reason (e.g. the HTTP server is not running on the other end), then ixprepdhcp.sh will default to using TFTP on the next attempt.
Expected Behavior
The same protcol and path should be used on repeated netboot attempts.
Steps To Reproduce
(ixboot) setenv ipaddr 169.254.0.1
(ixboot) setenv netmask 255.255.255.252
(ixboot) setenv serverip 169.254.0.2
(ixboot) setenv bootfile http://169.254.0.2/rootfs.itb
(ixboot) run boot_net
net: Preparing...
proto=http
bootfile=169.254.0.2:/rootfs.itb
net: ERROR: Unable to use slot
(ixboot) run boot_net
net: Preparing...
169.254.0.2:/rootfs.itb: No match
Using mvpp2-2 device
TFTP from server 169.254.0.2; our IP address is 169.254.0.1
Filename '/rootfs.itb'.
Load address: 0xa000000
Loading: *
TFTP server died; starting again
net: ERROR: Unable to use slot
(ixboot)
Current Behavior
When
proto://pathformat is used to specifybootfile, the latter is transformed to work as an input argument to eitherwgetortftp, loosing the protocol information in the process.Thus, if the first netboot fails for some reason (e.g. the HTTP server is not running on the other end), then
ixprepdhcp.shwill default to using TFTP on the next attempt.Expected Behavior
The same protcol and path should be used on repeated netboot attempts.
Steps To Reproduce
Additional information
No response