Use ipxe + peerdist option (BranchCache) + wimboot? //Andreas
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: den 11 december 2015 14:18 To: [email protected] Subject: Re: [ipxe-devel] [howto] chainload wimboot Hi Robin, currently I'm working on a workflow to automatically detect PXE attacks in an network. Therefore I was writing my own Bootloader which manages to notice this kind of attacks and does some more things. After the bootloader did his job I have to start a WINPE. The reason i have to use wimboot ist that the normal tftp download ist to slow for bigger scaling networks. Lets say i want to start 20000 WINPE at the same time I will get a big problem if i would use TFTP. So i want to use wimboot because its http download has a better performance. It would also help me if you know if i could use ipxe to solve this problem? Thanks for your help Daniel Gesendet: Freitag, 11. Dezember 2015 um 09:16 Uhr Von: "Robin Smidsrød" <[email protected]<mailto:[email protected]>> An: [email protected]<mailto:[email protected]> Betreff: Re: [ipxe-devel] [howto] chainload wimboot On 10.12.2015 15:19, [email protected]<mailto:[email protected]> wrote: > Hello to everyone, > like the subject says I need to know if there is a way to chainload > wimboot within an other bootloader. > The background of this question is that im currently writing my own > bootloader that starts a WINPE over HTTP. In the last weeks I managed to > start a bootmgfw.efi over PXE. And now I want to chainload the wimboot > instead of the bootmgfw.efi and afterwarts let the wimboot start the > WINPE over HTTP. Ist this possible? And what do I have to do? > I have no idea how to start with this and I hope someone of you could > help me. Why are you even doing this, when ipxe+wimboot already does what you want? See ipxe.org/howto/winpe or ipxe.org/howto/sccm and ipxe.org/appnote/wimboot_architecture for details on how they work. Please feel free to elaborate why/if the current ipxe+wimboot doesn't work for you and your situation. -- Robin _______________________________________________ ipxe-devel mailing list [email protected]<mailto:[email protected]> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
