Re: PXE boot debian-installer
Steven Demetrius wrote: there's a pretty good howto on tldp.org, that I've followed and it work perfectly. there are other howto's on the net and I read once one describing setup for the goal described here. I.e. download debian iso image, configure pxe boot, setup dhcp, nfs server etc If you're interested write me an e-mail and I'll look for the link regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: PXE boot debian-installer
[Emanoil, sorry for the duplication] Hi, just quick-read this thread. I did this recently on my home lan, following this article[1]. A few notes: - tftpd runs through inetd, good to know when troubleshooting (i ran mine standalone); - it's obvious, but open port 69 on your firewall; - you can unzip one single image instead of editing text-files [2], what i did. On my home net i just disconneted my host computer from my router and conneted it to the pxe-client; then configured the dhcp server. This was easier for me since my router is not that flexible on dhcp and pxe. HTH, Nuno Magalhães [1] http://www.debian-administration.org/articles/478 [2] http://www.debian-administration.org/articles/478#comment_23 -- () ascii ribbon campaign - against html e-mail /\ ascii-rubanda kampajno - kontraŭ html-a retpoŝto -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: PXE boot debian-installer
Thanks for all the helpful links and advice. I finally just made the router relay DHCP requests and setup a dhcp3 server which allows me to do everything. -- Alok -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: PXE boot debian-installer
Alok G. Singh wrote:
What I want to do is to deploy a dhcp+tftp server in the network that
people can boot into debian-installer via PXE. The idea is to have an
easy way to install Debian/Ubuntu without having to cart DVDs
around.
The DHCP server running on the router assigns addresses in the
192.168.1.0/24 subnet. I have setup another DHCP server to respond to
PXE in the same subnet. Now, how do I make sure the two DHCP servers
play nice together ? That is, the router's DHCP server should be used
unless DHCPREQUEST is from a PXE client.
The specifics are: dhcp3-server and tftp-hpa from Debian Lenny.
Alok:
On both DHCP servers set up different ranges that do *not* over lap.
This will only work if you can set the router to ignore bootp requests
and the Lenny DHCP to accept only bootp request (ignore booting
requests) or visa versa.
From the documentation (man dhcpd.conf) the default Debian DHCP server
will by default ignore bootp requests. This can be changed by using
the dynamic-bootp flag. With this flag set it will accept both
booting and bootp requests. There is no flag or command that I can
find to ignore booting requests.
So if the router can be set to accept bootp and ignore booting then
this should work.
Example:
Router bootp only - range 192.168.1.50 192.168.1.100
Lenny DHCP booting only - range 192.168.1.101 192.168.1.200
Another solution to this and the one that I use is to use only the
default Lenny (Debian) DHCP server and enable dynamic-bootp.
With this solution both booting and bootp clients will share the
same range/pool of IP addresses. Since the bootp clients will become
booting clients after OS installation then sharing IP addresses in the
same range/pool is not an issue.
Here is and example:
# DHCP booting and tftpd bootp for Debian and other OS install
#Declare the subnet
subnet 192.168.1.0 netmask 255.255.255.0
{
# Declare the range/pool for DHCP and set the dynamic-bootp
# flag to boot bootp/netboot clients as well as booting clients
range dynamic-bootp 192.168.20.40 192.168.20.200;
# DHCP broadcast
option broadcast-address 192.168.1.255;
# Name of the DHCP server
server-name netbootp;
# IP address of the tftpboot server
next-server 192.168.1.10;
# Name of the boot file.
filename pxelinux.0;
}
Steven.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: PXE boot debian-installer
In 871vrtasei@klein.localdomain, Alok G. Singh wrote: The DHCP server running on the router assigns addresses in the 192.168.1.0/24 subnet. I have setup another DHCP server to respond to PXE in the same subnet. Now, how do I make sure the two DHCP servers play nice together ? That is, the router's DHCP server should be used unless DHCPREQUEST is from a PXE client. I'm not sure you can. The first step would be to figure out what, if anything, is in the DHCPREQUEST packet that would indicate the sender is a PXE client. Then, configure one server to not respond to those requests and one to only respond to those requests. I don't think there is, strictly speaking, a difference. But, a DHCP client on a booted system will just ignore all the netboot information in the response. So, generally you just run one DHCP server that gives everyone the netboot information and there's little downside. You also might be able to come up with a heuristic for your network. Here PXE requests don't request a hostname, but normal requests do. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: PXE boot debian-installer
On Thu, Apr 16, 2009 at 08:39:01AM -0500, Boyd Stephen Smith Jr. wrote: In 871vrtasei@klein.localdomain, Alok G. Singh wrote: The DHCP server running on the router assigns addresses in the 192.168.1.0/24 subnet. I have setup another DHCP server to respond to PXE in the same subnet. Now, how do I make sure the two DHCP servers play nice together ? That is, the router's DHCP server should be used unless DHCPREQUEST is from a PXE client. I'm not sure you can. The first step would be to figure out what, if anything, is in the DHCPREQUEST packet that would indicate the sender is a PXE client. Then, configure one server to not respond to those requests and one to only respond to those requests. Just to confirm, I know that you *can* do this, i.e. a PXE client sends out different information than a regular DHCP client... I just can't recall what the difference is off-hand. I don't think there is, strictly speaking, a difference. But, a DHCP client on a booted system will just ignore all the netboot information in the response. So, generally you just run one DHCP server that gives everyone the netboot information and there's little downside. This is probably the best way. Cheers, -- Eric Gerlach, Network Administrator Federation of Students University of Waterloo p: (519) 888-4567 x36329 e: egerl...@feds.uwaterloo.ca -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: PXE boot debian-installer
Eric Gerlach wrote: I don't think there is, strictly speaking, a difference. But, a DHCP client on a booted system will just ignore all the netboot information in the response. So, generally you just run one DHCP server that gives everyone the netboot information and there's little downside. This is probably the best way. The problem was that the router is pretty dumb and can't do much. I've made it relay and setup a real DHCP server on the network. -- Alok If this is a service economy, why is the service so bad? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: PXE boot debian-installer
Hi, Alok: On Thursday 16 April 2009 10:56:21 Alok G. Singh wrote: What I want to do is to deploy a dhcp+tftp server in the network that people can boot into debian-installer via PXE. The idea is to have an easy way to install Debian/Ubuntu without having to cart DVDs around. The DHCP server running on the router assigns addresses in the 192.168.1.0/24 subnet. I have setup another DHCP server to respond to PXE in the same subnet. Now, how do I make sure the two DHCP servers play nice together ? That is, the router's DHCP server should be used unless DHCPREQUEST is from a PXE client. Don't do that. While it *might* be technically possible to make them both coexist*1 (you don't tell us if the router is another Debian box or it is a magic box) it will be real pita. Since you told your router is dumb, just configure your Debian system with all the needed stuff (DHCP and TFTP) and turn off the router's DHCP server. *1 I'm aware you can have more than one DHCP server to provide avaliability if you can control them both, but that's a different issue. -- SALUD, Jesús *** jesus.nava...@undominio.net *** -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
