PXE-provided images not showing on remote PC on boot?

Cubytus · 2. Januar 2016

Hi all,

I used the PXE plugin to provide a GParted boot image over the network. I used the standard settings with the older version pre-configured by OMV, and activated the TFTP server on OMV.

The first problem is the PXE > Images > Update button doesn't seem to work: It still allows me to choose between outdated images of GParted

And the second issue: on booting the other computer, after a long time, it gives the PXE-E53 error "no boot filename received".

Where should I begin to address the source of the issue?

ryecoaaron · 2. Januar 2016

How do you know it isn't updating? What are the Gparted versions? The list is maintained by us so it may not be a current Gparted version.

Is your dhcp server pointing clients to the PXE server and telling it what the default filename to look for?

Cubytus · 3. Januar 2016

Usually there's a message indicating that an update is in progress. The latest version of GParted is 0.24, but the one shown is 0.21. It was not clear if this was an automatically-updated list, or manually updated, therefore I thought it wasn't updating.

How do I know if the DHCP server (router) is pointing the client to the PXE server?

subzero79 · 3. Januar 2016

Zitat von Cubytus

How do I know if the DHCP server (router) is pointing the client to the PXE server?

in 99% of the cases an ISP home gateway/router won't give you an option to pass dhcp option for pxe. If you have pfsense, openwrt or tomato router you can pass the option in dnsmasq.

What you do in this cases is you disable dhcp server in the router an use dnsmasq in OMV. Now the dhcp server runs in your NAS, there you can put the option to pass the option as dhcp to clients to boot pxe. I believe @davidh2k put in the pxe plugin tab information about that.

Cubytus · 3. Januar 2016

Hmm, maybe this router does? I don't know if these screen captures would show anything of use regarding the DHCP function that would have to be modified.

The other screen capture shows that, even though PXE is active, it's not enabled (How?).

As a test, I disconnected the modem /router after configuring OMV as the DHCP server. However, it fails to assign a DHCP address to this computer, and on the other I am trying to boot, I got a different error:

PXE-E51 No DHCP or proxy DHCP offers were received

subzero79 · 3. Januar 2016

In the first screenshot

try add code option

67 with value pxelinux.0
68 with value any name, say PXE

150 with value ip address of OMV

I am based on this http://www.iana.org/assignment…otp-dhcp-parameters.xhtml

Using dnsmasq is easier is just one line like this

dhcp-boot=pxelinux.0,PXE,10.10.10.12

Cubytus · 3. Januar 2016

Well the dnsmasq test I tried didn't work out.

I now have the settings as presented in the first screenshot.

Is the Option 68 supposed to look like the 8.13 section in this RFC document? In which case "PXE" doesn't match the expected format.

And the computer I want to boot off the PXE server now gives a different error:

Code

PXE-T00 Get not supported
PXE-E36 Error received from TFTP server

Which is a good sign because it means it was able to find the server (I guess).

I tried to check the system logs in OMV, but it fails to load with a "Communication failure" error. I then connected to the shell, and ran

Code

tail -f /var/log/messages

hoping to find something as the other computer boots, but nothing appeared.

And, as the last screenshot in the previous post, the Diagnostics > Services > overview shows PXE is running, but not enabled. Is that even normal?

subzero79 · 3. Januar 2016

Could be that the codes are different,with tcpdump you can capture a full dhcp request and offer in omv to see what the router is sending

tcpdump -nni any -vvvv 'port 67 or 68'

Then in another ssh session renew dhcp with

dhclient eth0

subzero79 · 3. Januar 2016

I think i posted the wrong codes try this ones

66 ip address of OMV
67 value pxelinux.0

maybe delete value 150

Cubytus · 3. Januar 2016

I corrected the settings as per your post, removing option 150. Then I installed tcpdump on OMV.

On renewing DHCP in OMV, I get

Code

tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
00:41:31.538321 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 400)
    192.168.1.1.67 > 192.168.1.12.68: [udp sum ok] BOOTP/DHCP, Reply, length 372, xid 0xd8e06760, Flags [none] (0x0000)
      Your-IP 192.168.1.12
      Client-Ethernet-Address b8:27:eb:XX:YY:ZZ
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Offer
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 86400
        Subnet-Mask Option 1, length 4: 255.255.255.0
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name-Server Option 6, length 8: 206.248.154.170,206.248.154.22
        Domain-Name Option 15, length 4: "Home"
        Netbios-Name-Server Option 44, length 8: 192.168.1.1,192.168.1.1
        TFTP Option 66, length 24: "192.168.1.12M-}M-}M-}M-}M-}M-}M-}M-}M-^?M-^?M-^?M-u"
        BF Option 67, length 10: "pxelinux.0"
        MH Option 68, length 12: 80.88.69.253,253.253.253.253,253.253.253.253
        T150 Option 150, length 24: 825831982,825636910,825110834,4261281277,4261281277,4294967285
        END Option 255, length 0
00:41:31.544650 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 400)
    192.168.1.1.67 > 192.168.1.12.68: [udp sum ok] BOOTP/DHCP, Reply, length 372, xid 0xd8e06760, Flags [none] (0x0000)
      Your-IP 192.168.1.12
      Client-Ethernet-Address b8:27:eb:XX:YY:ZZ
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: ACK
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 86400
        Subnet-Mask Option 1, length 4: 255.255.255.0
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name-Server Option 6, length 8: 206.248.154.170,206.248.154.22
        Domain-Name Option 15, length 4: "Home"
        Netbios-Name-Server Option 44, length 8: 192.168.1.1,192.168.1.1
        TFTP Option 66, length 24: "192.168.1.12M-}M-}M-}M-}M-}M-}M-}M-}M-^?M-^?M-^?M-u"
        BF Option 67, length 10: "pxelinux.0"
        MH Option 68, length 12: 80.88.69.253,253.253.253.253,253.253.253.253
        T150 Option 150, length 24: 825831982,825636910,825110834,4261281277,4261281277,4294967285
        END Option 255, length 0

Alles anzeigen

What should I be paying attention to?

Computer still doesn't boot off PXE

subzero79 · 3. Januar 2016

Then i don't know, do you know the brand/model for the router?

Guess you have to try dnsmasq, this how a dnsmasq response looks like, is quite different from your router

Code

15:53:02.064095 IP (tos 0xc0, ttl 64, id 60308, offset 0, flags [none], proto UDP (17), length 328)
10.10.10.1.67 > 10.10.10.23.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x706e23df, secs 2, Flags [none] (0x0000)
Your-IP 10.10.10.23
Server-IP 10.10.10.12
Client-Ethernet-Address 7c:d2:c3:9c:64:44
sname "PXE"
file "pxelinux.0"
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: ACK
Server-ID Option 54, length 4: 10.10.10.1
Lease-Time Option 51, length 4: 43200
RN Option 58, length 4: 21600
RB Option 59, length 4: 37800
Subnet-Mask Option 1, length 4: 255.255.255.0
BR Option 28, length 4: 10.10.10.255
Default-Gateway Option 3, length 4: 10.10.10.1
Domain-Name-Server Option 6, length 4: 10.10.10.1
Domain-Name Option 15, length 3: "lan"
END Option 255, length 0
PAD Option 0, length 0, occurs 3

Alles anzeigen

Server-IP is the tftp omv server, are you sure you're running the tftp server?

subzero79 · 3. Januar 2016

Try adding code 52 with value 3, to see if passes the file and sname parameters to the header like the packet i just showed.

http://tools.ietf.org/html/rfc2132 Overload option section 9.3

Cubytus · 3. Januar 2016

The modem is a Zhone 6718-W1. There's no documentation in the user manual about the DHCP options.
The capture when the computer tries to boot when option 52 is added shows:

Code

tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
01:56:10.771518 IP (tos 0x0, ttl 20, id 0, offset 0, flags [none], proto UDP (17), length 576)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 00:23:8b:XX:YY:ZZ, length 548, xid 0x8cxxyyzz, secs 4, Flags [Broadcast] (0x8000)
      Client-Ethernet-Address 00:23:8b:XX:YY:ZZ
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Discover
        Parameter-Request Option 55, length 24: 
          Subnet-Mask, Time-Zone, Default-Gateway, IEN-Name-Server
          Domain-Name-Server, RL, Hostname, BS
          Domain-Name, SS, RP, EP
          Vendor-Option, Server-ID, Vendor-Class, BF
          Option 128, Option 129, Option 130, Option 131
          Option 132, Option 133, Option 134, Option 135
        MSZ Option 57, length 2: 1260
        GUID Option 97, length 17: 0.237.34.214.20.82.169.123.86.40.158.30.197.126.102.234.140
        ARCH Option 93, length 2: 0
        NDI Option 94, length 3: 1.2.1
        Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
        END Option 255, length 0
        PAD Option 0, length 0, occurs 212
01:56:10.773466 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 408)
    192.168.1.1.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length 380, xid 0x8cxxyyzz, Flags [Broadcast] (0x8000)
      Your-IP 192.168.1.22
      Client-Ethernet-Address 00:23:8b:XX:YY:ZZ
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Offer
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 86400
        Subnet-Mask Option 1, length 4: 255.255.255.0
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name-Server Option 6, length 8: 206.248.154.170,206.248.154.22
        Domain-Name Option 15, length 4: "Home"
        Netbios-Name-Server Option 44, length 8: 192.168.1.1,192.168.1.1
        OO Option 52, length 1: #51
        TFTP Option 66, length 24: "192.168.1.12M-}M-}M-}M-}M-}M-}M-}M-}trin"
        BF Option 67, length 10: "pxelinux.0"
        MH Option 68, length 16: 80.88.69.253,253.253.253.253,253.253.253.253,255.255.255.246
        T150 Option 150, length 24: 825831982,825636910,825110834,4261281277,4261281277,1953655150
        END Option 255, length 0
        PAD Option 0, length 0
01:56:12.831304 IP (tos 0x0, ttl 20, id 1, offset 0, flags [none], proto UDP (17), length 576)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 00:23:8b:XX:YY:ZZ, length 548, xid 0x8cxxyyzz, secs 4, Flags [Broadcast] (0x8000)
      Client-Ethernet-Address 00:23:8b:XX:YY:ZZ
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Request
        Requested-IP Option 50, length 4: 192.168.1.22
        Parameter-Request Option 55, length 24: 
          Subnet-Mask, Time-Zone, Default-Gateway, IEN-Name-Server
          Domain-Name-Server, RL, Hostname, BS
          Domain-Name, SS, RP, EP
          Vendor-Option, Server-ID, Vendor-Class, BF
          Option 128, Option 129, Option 130, Option 131
          Option 132, Option 133, Option 134, Option 135
        MSZ Option 57, length 2: 1260
        Server-ID Option 54, length 4: 192.168.1.1
        GUID Option 97, length 17: 0.237.34.214.20.82.169.123.86.40.158.30.197.126.102.234.140
        ARCH Option 93, length 2: 0
        NDI Option 94, length 3: 1.2.1
        Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
        END Option 255, length 0
        PAD Option 0, length 0, occurs 200
01:56:12.831912 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 408)
    192.168.1.1.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length 380, xid 0x8cxxyyzz, Flags [Broadcast] (0x8000)
      Your-IP 192.168.1.22
      Client-Ethernet-Address 00:23:8b:XX:YY:ZZ
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: ACK
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 86400
        Subnet-Mask Option 1, length 4: 255.255.255.0
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name-Server Option 6, length 8: 206.248.154.170,206.248.154.22
        Domain-Name Option 15, length 4: "Home"
        Netbios-Name-Server Option 44, length 8: 192.168.1.1,192.168.1.1
        OO Option 52, length 1: #51
        TFTP Option 66, length 24: "192.168.1.12M-}M-}M-}M-}M-}M-}M-}M-}trin"
        BF Option 67, length 10: "pxelinux.0"
        MH Option 68, length 16: 80.88.69.253,253.253.253.253,253.253.253.253,255.255.255.246
        T150 Option 150, length 24: 825831982,825636910,825110834,4261281277,4261281277,1953655150
        END Option 255, length 0
        PAD Option 0, length 0
^C
4 packets captured

Alles anzeigen

The previous attempt to use dnsmasq failed: the local computer didn't receive an IP, and the computer trying to boot off PXE failed to get one as well with error:
PXE-E51 No DHCP or proxy DHCP offers were received

Zitat

Server-IP is the tftp omv server, are you sure you're running the tftp server?

TFTP is enabled and running, but PXE is running but not enabled. Is that normal?

subzero79 · 3. Januar 2016

Zitat von Cubytus

PXE-E51 No DHCP or proxy DHCP offers were received

Then dnsmasq is not configured properly or not running. What settings did you put in the panel ? can you put a screenshot here

Also if you're gonna use dnsmasq in OMV, give the server static ip, otherwise you might loose access in case is headless, and then have to connect the monitor.

Zitat von Cubytus

but PXE is running but not enabled. Is that normal?

Yes, the pxe is just a configuration not a service or daemon

Cubytus · 3. Januar 2016

Here is the configuration:

anything wrong?

subzero79 · 3. Januar 2016

Everything is wrong, your network is not 192.168.178.0 is 192.168.1.0 seems obvious, look at the dhcp range

Also select lease network from the menu.

The extra options correct them again number 178 present there is 192.168.1.0, though the extra options are unnecessary IMO, at least in my setup they work without it.

Look at my screenshot

Of course don't copy the values from mine is different network

Cubytus · 3. Januar 2016

To be clear, is the 10.10.x.y range you're using also part of the local IPs of your modem? Or a completely different range?

subzero79 · 3. Januar 2016

yes of course, just one subnet. The router has a static ip of 10.10.10.1, dhcp disabled. OMV has a static ip of 10.10.10.12 same subnet.

davidh2k · 3. Januar 2016

Thats how it's supposed to look like. Don't fill first and last IP.

Be aware that this configuration still breaks internet connection, as you need to manually edit resolv.conf or the resolvconf footer file to have your DNS Server in it.

Greetings
David

Cubytus · 3. Januar 2016

I tried both davidh2k and subzero79's configurations, which are slightly different. Both give the same error:

PXE-E52: proxyDHCP offers were received. No DHCP offers were received

In both cases, I adapted the IPs to match the one normally covered by the router, ans I added a static entry for OMV, as shown.
In the case of subzero79's config, my OMV doesn't show anything when I click the arrow for "Lease network", which isn't used in davidh2k's config.

I also wanted to maintain a SSH connection to OMV, but it failed to resolve either the raw IP (same as when assigned by the modem) or its hostname.

What would be the meaning of this PXE-E52 error?

PXE-provided images not showing on remote PC on boot?

Jetzt mitmachen!

Tags