<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
One option here is to use iPXE ( <a class="moz-txt-link-freetext" href="http://www.ipxe.org/">http://www.ipxe.org/</a> ) to grab the
netboot files via HTTP (or some other protocol) instead of relying
on TFTP. There's some extra configuration work here, but serving up
the 365KB iPXE image to clients via TFTP is a lot less work then
serving up the entire kernel/initrd package.<br>
<br>
<div class="moz-cite-prefix">On 7/23/2014 11:13 PM, Linux Luser
wrote:<br>
</div>
<blockquote
cite="mid:CAPoZCFBKada2jqnqX3FfqvPiue-5bWDMGavQ=KJz4Cr-CwTs1g@mail.gmail.com"
type="cite">
<p dir="ltr">I have a project where I use dnsmasq for netboot
installs. Currently, there can be an unlimited number of
installs happened at once. At what point (number of TFTP
transfers happening in parallel) should I be concerned that I'm
overtaxing dnsmasq's TFTP capabilities? Does dnsmasq use threads
or multiprocessing for TFTP transfers?</p>
<p dir="ltr">Thanks.</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Dnsmasq-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a>
<a class="moz-txt-link-freetext" href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>