Seite 1 von 2
PXE boot
Verfasst: 25 Mär 2024, 13:05
von emlegend0
Hallo zusammen
Wenn ich über PXE ein Netboot Produkt installieren will kommt beim Boot die Fehlermeldung
kann mir da jemand weiterhelfen?
Re: PXE boot
Verfasst: 26 Mär 2024, 07:16
von j.schneider
Hallo,
was für ein DHCP-Server ist im Einsatz und wie ist der konfiguriert?
Ist die Option 67 gesetzt?
https://docs.opsi.org/opsi-docs-de/4.3/ ... erver.html
Grüße
Jan Schneider
Re: PXE boot
Verfasst: 26 Mär 2024, 07:34
von m.radtke
Moin,
kommen die TFTP Anfragen am Server an?
Gruß
Mathias
Re: PXE boot
Verfasst: 26 Mär 2024, 09:16
von emlegend0
Der DHCP server ist auf dem OPSI server wie in der Anleitung beschrieben mit der Automatischen Konfiguration installiert
Re: PXE boot
Verfasst: 26 Mär 2024, 09:59
von ThomasT
Kannst du deine /etc/dhcp/dhcpd.conf hier posten? Und um welche MAC Adresse es sich handelt.
Re: PXE boot
Verfasst: 26 Mär 2024, 10:54
von emlegend0
Code: Alles auswählen
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
Das wäre die dhcpd.conf
00:50:56:91:93:8 die MAC Adresse des clients
Re: PXE boot
Verfasst: 26 Mär 2024, 16:01
von ThomasT
Äh...in deiner dhcpd.conf steht gar nichts sinnvolles drin.
Woher bekommen die Clients dann ihre IP? Der OPSI-Server macht da in meinen Augen auf jedenfall erstmal nichts...
Auf nem laufenden Windows bekommst du das per ipconfig /all raus, da gibt es dann eine Zeile bei deinem aktiven Interface "DHCP-Server "
Re: PXE boot
Verfasst: 27 Mär 2024, 13:30
von emlegend0
[/code]
Re: PXE boot
Verfasst: 27 Mär 2024, 13:42
von emlegend0
entschuldigung ich habe nicht das ganze file gesendet :
hier wäre das ganze file
Code: Alles auswählen
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
#log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option subnet-mask 255.255.255.224;
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.example.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.example.com;
#}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}
use-host-decl-names on;
subnet 192.168.120.0 netmask 255.255.255.0 {
group {
next-server 192.168.120.100;
if substring (option vendor-class-identifier, 19, 1) = "0" {
filename "opsi/opsi-linux-bootimage/loader/opsi-netboot.bios";
}
else if substring (option vendor-class-identifier, 19, 1) = "7" {
filename "opsi/opsi-linux-bootimage/loader/shimx64.efi.signed";
}
}
host emuvm01 {
fixed-address emuvm01.labor.local;
hardware ethernet 00:50:56:91:93:8e;
next-server 10.11.12.13;
}
}
und der client hat als dhcp nicht den opsi server hinterlegt
Re: PXE boot
Verfasst: 28 Mär 2024, 08:52
von ThomasT
hmm, kann es sein, dass du deine /etc/opsi/backends/dhcpd.conf aus diesem Doku Eintrag kopiert hast:
https://docs.opsi.org/opsi-docs-de/4.3/ ... r-autoconf
Wenn ja, kommentier mal bitte die "default Client Parameters" Zeile aus und starte den OPSI-Server neu.