forum.opsi.org

Hii,


I need configuration of opsi dhcp with windows dhcp, how can i configure opsi dhcp for external windows dhcp.

Please help....


Regards,
Vivek

Hi,

here you have an example for a windows 2023 r2 dhcp ricght under the linux example

https://download.uib.de/4.2/documentati ... uefi-dhcpd

remember that you need an additional policy for UEFI clients.

Regards

Mathias

Thanks for your reply , can you let me know , where can i configure DHCP policy , is it in /etc/dhcp/dhcpd.conf or any other conf file is there for dhcp policy?

DHCP conf file ..

#
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#

# 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;

# option definitions common to all supported networks...
option domain-name "fgn.local";
option domain-name-servers 192.168.1.10;
option netbios-name-servers 192.168.1.124;
option netbios-node-type 8;

default-lease-time 600;
max-lease-time 7200;

# 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 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.fugue.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.fugue.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;
# }
#}

# This will tell the box its hostname while booting:
use-host-decl-names on;

subnet 192.168.80.0 netmask 255.255.255.0 {
option routers 192.168.80.1;

#Group the PXE bootable hosts together
group {
# PXE-specific configuration directives...
#option dhcp-class-identifier "PXEClient";
# You need an entry like this for every host
# unless you are using dynamic addresses
# next-server 192.168.80.124;
# filename "linux/pxelinux.0";
066 Host name of the start server: 192.168.80.10
067 Name of the start file: linux/pxelinux.cfg/shimx64.efi.signed
# Das ist die UEFI Detection:
if substring (option vendor-class-identifier , 19,1 ) = "0" {
log (info, "pxe client");
filename "linux/pxelinux.0";
}
else if substring (option vendor-class-identifier , 19,1 ) = "6" {
log (info, "efi32 client");
filename "linux/pxelinux.cfg/elilo-x86.efi";
}
else if substring (option vendor-class-identifier , 19,1 ) = "7" {
log (info, "efi64 client");
filename "linux/pxelinux.cfg/shimx64.efi.signed";
}
else {
log (info, concat ( "Unhandled vendor class Arch: ", substring (option vendor-class-identifier , 19,1 )));
}
# test-client
# host test-client {
# hardware ethernet 00:00:cb:62:e9:24;
# fixed-address test-client;
# }
host fgn-dockerservices-iv {
fixed-address 192.168.1a.29;
hardware ethernet 00:50:56:9d:30:a7;
}
}
}

Define manufacturer class
Add new manufacturer class
Edit class
Display name: Legacy BIOS
Asci: PXEClient:Arch:00000:UNDI:002001

Set predefined options
Options
Option class: Legacy BIOS
Add
Adjust the option type
Name: Legacy BIOS
Data Type: String
Code: 60
Description: PXEClient Class Legacy BIOS
Predefined options and values
String: PXEClient

New policy
Policy Name: PXE BootFile Legacy BIOS
continue
Add conditions
Criteria: Manufacturer class
Operator: equals
Value: Legacy BIOS
add
Would you like to configure an IP address range for the following policy: No
Manufacturer class: DHCP Standard Options
067 Name of the start file
file input
String value: linux/pxelinux.0

067 Name of the Start file: linux/pxelinux.cfg/shimx64.efi.signed Policy: None
067 Name of the Start file: linux/pxelinux.0 Policy: PXE BootFile Legacy BIOS

Hello Vivek,

ootb the dhcp-backend of opsi only works with the isc-dhcp-server Installation on a Linux System.
There is no trivial method to configure the windows dhcp-server with opsi.
It should be possible to use the directory-connector opsi extension so your clients are synced with the AD. From there your DHCP could get it's raw data, but this is not within our scope tbh.