<div dir="ltr">Yep, that's what I was doing on my first try. I had dnsmasq installed and used its DHCP capability to assign the IP upon boot, with the tftp capability pointed to the boot files on the /srv/tftp directory. Those files are from Debian's site, the netboot.tar.gz file is extracted into the /srv/tftp directory.<div>
<br></div><div>The client machine would boot fine, get an IP address from the host and start the Debian installation process. The Debian installation process would get to the point of using a mirror to download the remaining packages. </div>
<div><br></div><div>That is where it would fail. I was able to change to a different tty console and see that it was trying to use wget to download files from the mirror and would fail, giving an innocuous error message on tty1 (graphical install screen) saying, basically, it couldn't connect, check your network cable, etc.</div>
<div><br></div><div>So, I assumed ( I know, dangerous term ) that it was not getting internet access beyond the host machine; PXE client connects to host via eth1, host connects to router ( getting its own IP from DHCP on the router ) via eth0, then router to ISP modem to wonder world of interwebs.</div>
<div><br></div><div>One article I read said that having two DHCP services on the network would mess things up. Could that be the culprit as well?</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Mon, Jan 13, 2014 at 11:55 AM, Don Bosman <span dir="ltr"><<a href="mailto:dbosman@msu.edu" target="_blank">dbosman@msu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Normally you need a TFTP server as
well. <br>
I find this site useful. <br>
<a href="http://ltsp.org/" target="_blank">http://ltsp.org/</a><br>
<br>
Don Bosman<div class="im"><br>
<br>
On 1/13/2014 11:27 AM, Adam Kaminski wrote:<br>
</div></div>
<blockquote type="cite"><div class="im">
<div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I was doing
some reading and just realized that in order to PXE boot you'll
need DHCP. I mentioned in my previous reply to statically set
the client to 192.168.2.x. You should be able to use dnsmasq
and have it bind to the eth1 interface. The range would need to
be set to something like 192.168.2.50-192.16.2.151. Apparently
dnsmasq can also act as a a tftp server and the iso just needs
to be set in the conf file.</div>
</div><span>
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div>
<blockquote type="cite">
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote"><span>On Sat,
Jan 11, 2014 at 12:04 AM,
Adam Kaminski <span dir="ltr"><<a href="mailto:adam@adamkaminski.com" target="_blank">adam@adamkaminski.com</a>></span>
wrote:</span><br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
linux-user mailing list<br>
<a href="mailto:linux-user@egr.msu.edu">linux-user@egr.msu.edu</a><br>
<a href="http://mailman.egr.msu.edu/mailman/listinfo/linux-user" target="_blank">http://mailman.egr.msu.edu/mailman/listinfo/linux-user</a><br>
<br></blockquote></div><br></div>