starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-25 23:25:54 +03:00

[GH-ISSUE #338] Name resolution issue #138

New issue

Closed

opened 2026-02-27 14:50:32 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 14:50:32 +03:00

Owner

Originally created by @aqwserf on GitHub (Jun 24, 2019).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/338

Hi,
after struggling with my OpenWRT to have pxe running, I now have a issue with the netboot.xyz UEFI. Everytime I try to boot with the UEFI version (netboot.xyz.efi), it fails with the following error when it tries to retrieve the squashfs file:

(initramfs) IP-Config
......
......
Creating /etc/resolv.conf
Begin: Trying wget http://cdimage.debian.org/cdimage/archive/8.11.0-live/amd64/webboot/debian-live-8.11.0-amd64-lxde-desktop.squashfs -O /live/medium/live/debian-live-8.11.0-amd64-lxde-desktop.squashfs ... wget: bad address 'cdimage.debian.org'
Unable to find a live file system on the network
(initramfs)

I've tried to debug the situation by wgetting myself and the same error appears.
The problem apparently lies in the name resolution:

(initramfs) nslookup cdimage.debian.org
Server:       192.168.1.1
Address:    192.168.1.1

nslookup: can't resolv 'cdimage.debian.org'
(initramfs) cat /etc/resolv.conf
domain local.lan
search local.lan
nameserver 192.168.1.1

The /etc/resolv.conf file is ok and when I try the same command on my laptop, eveything works fine.
I've tried with the netboot.xyz.kpxe and it works fine and I've just tried with another boot install this time (Kali) and the installer starts.
Does anyone has a clue ? Is it related to the debian initrd ?

Otherwise, I have several problems with other boot image (systemrescuecd, ubcd...), same as the issue #214 :

..... Exec format error

Could it be related ?

Thank you !

Originally created by @aqwserf on GitHub (Jun 24, 2019). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/338 Hi, after struggling with my OpenWRT to have pxe running, I now have a issue with the netboot.xyz UEFI. Everytime I try to boot with the UEFI version (netboot.xyz.efi), it fails with the following error when it tries to retrieve the squashfs file: ```bash (initramfs) IP-Config ...... ...... Creating /etc/resolv.conf Begin: Trying wget http://cdimage.debian.org/cdimage/archive/8.11.0-live/amd64/webboot/debian-live-8.11.0-amd64-lxde-desktop.squashfs -O /live/medium/live/debian-live-8.11.0-amd64-lxde-desktop.squashfs ... wget: bad address 'cdimage.debian.org' Unable to find a live file system on the network (initramfs) ``` I've tried to debug the situation by wgetting myself and the same error appears. The problem apparently lies in the name resolution: ``` (initramfs) nslookup cdimage.debian.org Server: 192.168.1.1 Address: 192.168.1.1 nslookup: can't resolv 'cdimage.debian.org' (initramfs) cat /etc/resolv.conf domain local.lan search local.lan nameserver 192.168.1.1 ``` The `/etc/resolv.conf` file is ok and when I try the same command on my laptop, eveything works fine. I've tried with the `netboot.xyz.kpxe` and it works fine and I've just tried with another boot install this time (Kali) and the installer starts. Does anyone has a clue ? Is it related to the debian initrd ? Otherwise, I have several problems with other boot image (systemrescuecd, ubcd...), same as the issue #214 : ``` ..... Exec format error ``` Could it be related ? Thank you !

kerem closed this issue

2026-02-27 14:50:32 +03:00

kerem commented

2026-02-27 14:50:32 +03:00

Author

Owner

@NiKiZe commented on GitHub (Jun 25, 2019):

many initrds with busybox does not support name resolution,
I guess you have tried wget in a fully booted linux env, but if you enter the limited initrd environment my guess is that you will see the same thing, you can confirm with ping or some other tool if name resolution works at all or not in that case.

"Exec format error (http://ipxe.org/2e008081)"
If you get it when booting in efi mode, is most likely due to the fact that you are trying to boot a non efi compliant binary (in the case of linux kernel, it wasn't compiled with CONFIG_EFI_STUB=y)
Which you can read more about on the ipxe,org error page (the url is helpful, and always good to include)

@NiKiZe commented on GitHub (Jun 25, 2019): many initrds with busybox does not support name resolution, I guess you have tried wget in a fully booted linux env, but if you enter the limited initrd environment my guess is that you will see the same thing, you can confirm with ping or some other tool if name resolution works at all or not in that case. "Exec format error (http://ipxe.org/2e008081)" If you get it when booting in efi mode, is most likely due to the fact that you are trying to boot a non efi compliant binary (in the case of linux kernel, it wasn't compiled with CONFIG_EFI_STUB=y) Which you can read more about on the ipxe,org error page (the url is helpful, and always good to include)

kerem commented

2026-02-27 14:50:32 +03:00

Author

Owner

@aqwserf commented on GitHub (Jun 27, 2019):

many initrds with busybox does not support name resolution,
I guess you have tried wget in a fully booted linux env, but if you enter the limited initrd environment my guess is that you will see the same thing, you can confirm with ping or some other tool if name resolution works at all or not in that case.

That's right, I tried on an full Linux env. I've also tried with a ping and that's right too, it doesn't works...
But what I don't understand is that it works with kali boot install and not with a debian live. Does that means that the initrd is different ?

"Exec format error (http://ipxe.org/2e008081)"
If you get it when booting in efi mode, is most likely due to the fact that you are trying to boot a non efi compliant binary (in the case of linux kernel, it wasn't compiled with CONFIG_EFI_STUB=y)
Which you can read more about on the ipxe,org error page (the url is helpful, and always good to include)

Ok, thank you for the explanation. So if I understand well, netboot.xyz propose an efi binary that can't load non-efi binary ? If so, can't they propose efi binary ?

@aqwserf commented on GitHub (Jun 27, 2019): > many initrds with busybox does not support name resolution, > I guess you have tried wget in a fully booted linux env, but if you enter the limited initrd environment my guess is that you will see the same thing, you can confirm with ping or some other tool if name resolution works at all or not in that case. That's right, I tried on an full Linux env. I've also tried with a ping and that's right too, it doesn't works... But what I don't understand is that it works with kali boot install and not with a debian live. Does that means that the initrd is different ? > "Exec format error (http://ipxe.org/2e008081)" > If you get it when booting in efi mode, is most likely due to the fact that you are trying to boot a non efi compliant binary (in the case of linux kernel, it wasn't compiled with CONFIG_EFI_STUB=y) > Which you can read more about on the ipxe,org error page (the url is helpful, and always good to include) Ok, thank you for the explanation. So if I understand well, netboot.xyz propose an efi binary that can't load non-efi binary ? If so, can't they propose efi binary ?

kerem commented

2026-02-27 14:50:32 +03:00

Author

Owner

@NiKiZe commented on GitHub (Jun 27, 2019):

different distros of course have their own intrds, but it boils down to "buggy" busybox. you should ask for an update on the specific distro (they seem unlikely to fix it tho, as far as i have seen)

the simple answer is that there is no efi binary that can boot a non efi binary or wise versa.
The way that these tools are setup relies on legacy technices that shouldn't be used, but it takes loots more work to solve "correctly" and it requires EFI compatible kernels.

@NiKiZe commented on GitHub (Jun 27, 2019): different distros of course have their own intrds, but it boils down to "buggy" busybox. you should ask for an update on the specific distro (they seem unlikely to fix it tho, as far as i have seen) the simple answer is that there is no efi binary that can boot a non efi binary or wise versa. The way that these tools are setup relies on legacy technices that shouldn't be used, but it takes loots more work to solve "correctly" and it requires EFI compatible kernels.

kerem commented

2026-02-27 14:50:32 +03:00

Author

Owner

@aqwserf commented on GitHub (Jun 27, 2019):

Ok, thank you for your answers. I close the issue as it doesn't seem to be solvable easily :)

@aqwserf commented on GitHub (Jun 27, 2019): Ok, thank you for your answers. I close the issue as it doesn't seem to be solvable easily :)

kerem referenced this issue

2026-02-27 14:52:48 +03:00

[PR #138] [MERGED] Add ALT Linux Rescue #670

kerem referenced this issue

2026-03-01 18:39:10 +03:00

[PR #138] [MERGED] Add ALT Linux Rescue #2206

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#138

No description provided.

Rows
Columns