On Wed, 22 Jan 2020 at 21:43, Geert Stappers wrote:
>...
>
> FWIW
> Over here is "PXE service" not used. I have no idea what I might be
> missing. My reason for involvement in this thread is finding what use
> case O.P. has for dnsmasq. Finding out if it can improve my use case,
> finding out if
On Mon, Jan 20, 2020 at 11:34:01PM +0100, Michal Zatloukal wrote:
> On Mon, 20 Jan 2020 at 21:38, Geert Stappers wrote:
> > On Sun, Jan 19, 2020 at 10:40:28PM +0100, Michal Zatloukal wrote:
> > > On Sun, 19 Jan 2020 at 21:45, Geert Stappers wrote:
> > > >
> > > > Please do make the extra mile
> > >
On Mon, 20 Jan 2020 at 21:38, Geert Stappers wrote:
>
> On Sun, Jan 19, 2020 at 10:40:28PM +0100, Michal Zatloukal wrote:
> > On Sun, 19 Jan 2020 at 21:45, Geert Stappers wrote:
> > > On Sun, Jan 19, 2020 at 08:33:54PM +0100, P W wrote:
> > > > On Sun, Jan 19, 2020 at 07:30:44PM +0100, Michal Zatl
On Sun, Jan 19, 2020 at 10:40:28PM +0100, Michal Zatloukal wrote:
> On Sun, 19 Jan 2020 at 21:45, Geert Stappers wrote:
> > On Sun, Jan 19, 2020 at 08:33:54PM +0100, P W wrote:
> > > On Sun, Jan 19, 2020 at 07:30:44PM +0100, Michal Zatloukal wrote:
> > > > On Wed, 8 Jan 2020 at 00:16, Michal Zatlou
Yeah - sorry, I'm not much help when it comes to C code. I was coming
in with assumption my config was somehow incorrect.
What is expected of dnsmasq - a DHCP offer with either a populated
menu, or a populated boot-filename option. As mentioned in the OP,
currently dnsmasq provides broken menu (no
On Sun, Jan 19, 2020 at 08:33:54PM +0100, P W wrote:
> On Sun, Jan 19, 2020 at 07:30:44PM +0100, Michal Zatloukal wrote:
> > On Wed, 8 Jan 2020 at 00:16, Michal Zatloukal wrote:
> > >
> > > In the meantime, I tried a simpler case [1] of UEFI PXE services
> > > config, which I confirmed to work.
>
On Sun, Jan 19, 2020 at 07:30:44PM +0100, Michal Zatloukal wrote:
> On Wed, 8 Jan 2020 at 00:16, Michal Zatloukal wrote:
> >
> > In the meantime, I tried a simpler case [1] of UEFI PXE services
> > config, which I confirmed to work.
> >
> > I intended to replace my config with this and work up tow
Finally got to troubleshoot this today...
The issue arises when there's only a single "proper" pxe-service
configured (one that actually has a boot-filename defined). Is this
expected?
So this works:
pxe-prompt="dnsmasq menu"
pxe-service=7, "Boot UEFI CSA 7", efi64/syslinux.efi
pxe-service=7, "Oth
In the meantime, I tried a simpler case [1] of UEFI PXE services
config, which I confirmed to work.
I intended to replace my config with this and work up towards the
fancier tag-operated version, but made a wrong assumption and _added_
the trivial config to existing set of config files (adding .ba
Hi.
I'm putting together a "booting section" fo my config, where I want to
provide various boot images, according to the machine architecture
provided by the client. As I understand the pxe-service functionality,
there are 2 ways to to netboot:
- either provide bootfile-name (67), which the client
10 matches
Mail list logo
