by aka » Sun Mar 26, 2017 1:15 pm
radicspeter wrote:Okay, if i choose network boot option, my config files transfer only by TFTP...
If you choose network boot option, this means that you have TFTP server (because Raspberry firmware can
boot by network only using TFTP, it's Raspberry firmware limitation. Raspberry firmware can't download files by HTTP) nearby. Raspberry firmware loads WTware binary files by TFTP. After WTware binary files loaded and WTware started, we can add HTTP config downloading, but I don't understand the reason. Why do you want to download small configs over HTTP if you have TFTP server nearby?
radicspeter wrote:And if i choose local boot option, there is an option to use HTTP server to transfer my config files...
1.) if i use network boot in Raspberry Pi 2, it can only use TFTP server?
When you use local boot, you do not need to have TFTP nearby. Raspberry firmware, that doesn't handle HTTP, boots WTware from SD card. WTware handles HTTP and WTware can download configs from everywhere.
[quote="radicspeter"]Okay, if i choose network boot option, my config files transfer only by TFTP...[/quote]
If you choose network boot option, this means that you have TFTP server (because Raspberry firmware can [b]boot by network[/b] only using TFTP, it's Raspberry firmware limitation. Raspberry firmware can't download files by HTTP) nearby. Raspberry firmware loads WTware binary files by TFTP. After WTware binary files loaded and WTware started, we can add HTTP config downloading, but I don't understand the reason. Why do you want to download small configs over HTTP if you have TFTP server nearby?
[quote="radicspeter"]And if i choose local boot option, there is an option to use HTTP server to transfer my config files...
1.) if i use network boot in Raspberry Pi 2, it can only use TFTP server?[/quote]
When you use local boot, you do not need to have TFTP nearby. Raspberry firmware, that doesn't handle HTTP, boots WTware from SD card. WTware handles HTTP and WTware can download configs from everywhere.