Re: [Dnsmasq-discuss] Please consider clarifying the man page about the tftp service
On Mon, Jan 27, 2020 at 06:44:22PM +0100, Olivier Cailloux wrote: > Le lundi 27 janvier 2020 à 15:58 +, Simon Kelley a écrit : > > This is a laudible aim, the problem is that there's no such thing > > as "which option is required exactly". Netboot is gnarly thicket of > > different standards and different ways of doing things, and depending > > on how you want to do things, and which standards the things you > > are trying to boot support, then you need different options. For > > instance in your case you presumably have another DHCP server on > > the network which is dealing with handing out addresses, and you're > > relying on the never-standardised "proxy DHCP" feature of PXE to do > > be able to do netbooting without touching the configuration of that > > other DHCP server. > > In fact if you use just one DHCP server which can be configured, > > especially if it's running dnsmasq, netbooting is much simpler > > than the way you've done it. A primer on netbooting with examples > > of dnsmasq configurations would be a good thing to have, but it's > > place is not in the dnsmasq man page. > > > I understand that it is no simple matter in my situation (and simpler > in others)to clarify the doc and still support every possible use case. > Still, I have a hunch that it is possible to do better (though it might > be because of me not having thought about some use cases). For example, > is there a reason to run the following command? > sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0, proxy" " > --dhcp-boot=pxelinux.0,saucisson" --enable-tftp --log-dhcp > > In my understanding, the --pxe-service switch is required in such a > situation (as you correctly deduced, that is a situation where another > DHCP server is running), or there is some other problem in the command. > If so, dnsmasq should say it. > > But I certainly could be wrong, being no expert in net booting. https://networkboot.org/ > > Cheers > > Thank you for your interest and time. > -- Olivier Groeten Geert Stappers -- Leven en laten leven ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Please consider clarifying the man page about the tftp service
Le lundi 27 janvier 2020 à 15:58 +, Simon Kelley a écrit : > This is a laudible aim, the problem is that there's no such thing as > "which option is required exactly". Netboot is gnarly thicket of > different standards and different ways of doing things, and depending > on > how you want to do things, and which standards the things you are > trying > to boot support, then you need different options. For instance in > your > case you presumably have another DHCP server on the network which is > dealing with handing out addresses, and you're relying on the > never-standardised "proxy DHCP" feature of PXE to do be able to do > netbooting without touching the configuration of that other DHCP > server. > In fact if you use just one DHCP server which can be configured, > especially if it's running dnsmasq, netbooting is much simpler than > the > way you've done it. A primer on netbooting with examples of dnsmasq > configurations would be a good thing to have, but it's place is not > in > the dnsmasq man page. > > I understand that it is no simple matter in my situation (and simpler in others)to clarify the doc and still support every possible use case. Still, I have a hunch that it is possible to do better (though it might be because of me not having thought about some use cases). For example, is there a reason to run the following command? sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0, proxy" " --dhcp-boot=pxelinux.0,saucisson" --enable-tftp --log-dhcp In my understanding, the --pxe-service switch is required in such a situation (as you correctly deduced, that is a situation where another DHCP server is running), or there is some other problem in the command. If so, dnsmasq should say it. But I certainly could be wrong, being no expert in net booting. > > Cheers Thank you for your interest and time. -- Olivier > ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Please consider clarifying the man page about the tftp service
On 24/01/2020 21:49, Olivier Cailloux wrote: > Dear list, > > I have been happy to use dnsmasq to install debian through network > boot. However, it has taken a lot of trials and errors before I found > the correct command line to use. I’d like to report my experience in > hope that the man page be possibly improved, as the developers see fit. > > It was very unclear to me while reading the man page which options > exactly need to be turned on to enable network boot. I tried the > following commands: > sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0, proxy" " > --dhcp-boot=pxelinux.0,saucisson" --enable-tftp --log-dhcp > sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0,proxy" " > --dhcp-boot=pxelinux.0" --enable-tftp --log-dhcp --tftp- > root=/home/olivier/netboot > sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0,proxy" " > --dhcp-boot=/pxelinux.0" --enable-tftp --log-dhcp --tftp- > root=/home/olivier/netboot --dhcp-no-override > > before I finally found a correct one: > sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0,proxy" " > --dhcp-boot=pxelinux.0" --enable-tftp --log-dhcp --tftp- > root=/home/olivier/netboot "--pxe-service=x86PC,Install Linux, > pxelinux" > > (All this took a while because I did not even know the TFTP service was > not activated with my first tries, so I thought the problem lied > somewhere else.) > > The man page says: “If dnsmasq is providing a TFTP service (see -- > enable-tftp ) then only the filename is required here to enable network > booting.” and also reading about the pxe-service option, I thought that > it was unnecessary and was there just to allow for customizing the > string that would display at start (which I thought I do not need). > > Please consider clarifying the man page concerning the relevant options > to state which option is required exactly; and especially, please > consider making dnsmasq tell something in the log file, or (better > IMHO) refuse to start when the options it receives are incoherent. With > the current behavior, it is very hard, when it’s the first time you do > it, to even know that dnsmasq is not configured properly. > This is a laudible aim, the problem is that there's no such thing as "which option is required exactly". Netboot is gnarly thicket of different standards and different ways of doing things, and depending on how you want to do things, and which standards the things you are trying to boot support, then you need different options. For instance in your case you presumably have another DHCP server on the network which is dealing with handing out addresses, and you're relying on the never-standardised "proxy DHCP" feature of PXE to do be able to do netbooting without touching the configuration of that other DHCP server. In fact if you use just one DHCP server which can be configured, especially if it's running dnsmasq, netbooting is much simpler than the way you've done it. A primer on netbooting with examples of dnsmasq configurations would be a good thing to have, but it's place is not in the dnsmasq man page. Cheers Simon ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Please consider clarifying the man page about the tftp service
On Fri, Jan 24, 2020 at 10:49:21PM +0100, Olivier Cailloux wrote: > > I have been happy to use dnsmasq > to install debian through network boot. } before I finally found a correct one for my use case: > sudo /usr/sbin/dnsmasq --port=0 --dhcp-range=192.168.1.0,proxy \ > --dhcp-boot=pxelinux.0 --enable-tftp --log-dhcp \ > --tftp-root=/home/olivier/netboot \ > "--pxe-service=x86PC,Install Linux,pxelinux" > > (All this took a while because I did not even know the TFTP service was > not activated with my first tries, so I thought the problem lied > somewhere else.) > > The man page says: “If dnsmasq is providing a TFTP service (see --enable-tftp > ) > then only the filename is required here to enable network booting.” That line in context | -M, --dhcp-boot=[tag:,],[[,|]] |(IPv4 only) Set BOOTP options to be returned by the DHCP server. |Server name and address are optional: if not provided, the name is |left empty, and the address set to the address of the machine |running dnsmasq. If dnsmasq is providing a TFTP service (see |--enable-tftp ) then only the filename is required here to enable |network booting. If the optional tag(s) are given, they must match |for this configuration to be sent. > and also reading about the pxe-service option, I thought that > it was unnecessary and was there just to allow for customizing the > string that would display at start (which I thought I do not need). > > Please consider clarifying the man page concerning the relevant options > to state which option is required exactly; and especially, please > consider making dnsmasq tell something in the log file, or (better > IMHO) refuse to start when the options it receives are incoherent. With > the current behavior, it is very hard, when it’s the first time you do > it, to even know that dnsmasq is not configured properly. FWIW: I do understand the point of view of Original Poster. Regards Geert Stappers -- Double edge blades are indeed double edge blades. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Please consider clarifying the man page about the tftp service
Dear list, I have been happy to use dnsmasq to install debian through network boot. However, it has taken a lot of trials and errors before I found the correct command line to use. I’d like to report my experience in hope that the man page be possibly improved, as the developers see fit. It was very unclear to me while reading the man page which options exactly need to be turned on to enable network boot. I tried the following commands: sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0, proxy" " --dhcp-boot=pxelinux.0,saucisson" --enable-tftp --log-dhcp sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0,proxy" " --dhcp-boot=pxelinux.0" --enable-tftp --log-dhcp --tftp- root=/home/olivier/netboot sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0,proxy" " --dhcp-boot=/pxelinux.0" --enable-tftp --log-dhcp --tftp- root=/home/olivier/netboot --dhcp-no-override before I finally found a correct one: sudo /usr/sbin/dnsmasq --port=0 "--dhcp-range=192.168.1.0,proxy" " --dhcp-boot=pxelinux.0" --enable-tftp --log-dhcp --tftp- root=/home/olivier/netboot "--pxe-service=x86PC,Install Linux, pxelinux" (All this took a while because I did not even know the TFTP service was not activated with my first tries, so I thought the problem lied somewhere else.) The man page says: “If dnsmasq is providing a TFTP service (see -- enable-tftp ) then only the filename is required here to enable network booting.” and also reading about the pxe-service option, I thought that it was unnecessary and was there just to allow for customizing the string that would display at start (which I thought I do not need). Please consider clarifying the man page concerning the relevant options to state which option is required exactly; and especially, please consider making dnsmasq tell something in the log file, or (better IMHO) refuse to start when the options it receives are incoherent. With the current behavior, it is very hard, when it’s the first time you do it, to even know that dnsmasq is not configured properly. -- Olivier ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
