Unable to chain custom.ipxe using just boot.cfg and custom.ipxe

[netbootxyz]

Unable to chain custom.ipxe using just boot.cfg and custom.ipxe

[antonym]

you need to build your own to use custom as this is disabled by default

@ikkemaniac Is there a specific reason why it is disabled while custom_github_menus is enabled?

I would like to use this tool in a local environment (without permanent available network access) where building images or direct filesystem access is not possible.

custom_github_menus is used when a GitHub user is set from the Utility menu or at local-vars.ipxe so that a menu can be loaded from GitHub directly:

https://github.com/netbootxyz/netboot.xyz/blob/development/roles/netbootxyz/templates/menu/utils-pcbios-64.ipxe.j2#L78

[ikkemaniac]

Just ran into this myself.
On the build flag custom_generate_menus: false, yes you are RIGHT about the workings. But it is explained in the documentation that you need to build your own to use custom as this is disabled by default:
https://github.com/netbootxyz/netboot.xyz/blob/43e2f303def858974f47160e1b657385477e7a9f/etc/netbootxyz/custom/README.md

On the custom/custom.ipxe, you are "wrong", you can set this dir by var custom_templates_dir. The default is xxx/custom, this is explained in the documentation:
https://github.com/netbootxyz/netboot.xyz/blob/43e2f303def858974f47160e1b657385477e7a9f/etc/netbootxyz/custom/README.md

You can set that location to whatever you want. just keep in mind that this is NOT the same as going to the web interface and creating a new ipxe file that you name custom.ipxe

A simple cheat for all this is to set the custom_url var in boot.cfg (note that you need to include the filename if it's not custom.ipxe)
set custom_url http://${boot_domain}
or
set custom_url http://${boot_domain}/fancy_name.ipxe

[Kipjr]

you need to build your own to use custom as this is disabled by default

@ikkemaniac
Is there a specific reason why it is disabled while custom_github_menus is enabled?

I would like to use this tool in a local environment (without permanent available network access) where building images or direct filesystem access is not possible.

[ikkemaniac]

you need to build your own to use custom as this is disabled by default

@ikkemaniac Is there a specific reason why it is disabled while custom_github_menus is enabled?

I would like to use this tool in a local environment (without permanent available network access) where building images or direct filesystem access is not possible.

No freaking clue. Note that i'm not affiliated with this project.

I'd just build a custom ipxe to your liking on your favorite machine and copy that to your environment. Or use the custom_url.