Difference between revisions of "Pxe"
m (→Configuration) |
m (→Description) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 29: | Line 29: | ||
Assumes sme server is acting as dhcp server. | Assumes sme server is acting as dhcp server. | ||
| + | This contrib supplies the basic parameters for dhcpd to allow pxe booting on your network. | ||
| + | |||
| + | It is ONLY config db parameters and /etc/dhcpd.conf template fragments. No panels or scripts. | ||
| + | |||
| + | Just restart dhcpd to get updated parameters added into /etc/dhcpd.conf<syntaxhighlight lang="bash"> | ||
| + | service dhcpd restart | ||
| + | </syntaxhighlight>This will update your /etc/dhcpd.conf file to include<syntaxhighlight lang="perl"> | ||
| + | option client-architecture code 93 = unsigned integer 16; | ||
| + | |||
| + | <and within the subnet scope> | ||
| + | |||
| + | if option client-architecture = 00:07 { | ||
| + | filename "/bootx64.efi"; | ||
| + | } | ||
| + | elsif option client-architecture = 00:06 { | ||
| + | filename "/bootia32.efi"; | ||
| + | } | ||
| + | else { | ||
| + | filename "/pxelinux.0"; | ||
| + | } | ||
| + | |||
| + | </syntaxhighlight> | ||
=== Installation === | === Installation === | ||
| − | <tabs container><tab name="For SME 10"> | + | <tabs container=""><tab name="For SME 10"> |
yum --enablerepo=smecontribs install {{#var:smecontribname}} | yum --enablerepo=smecontribs install {{#var:smecontribname}} | ||
</tab></tabs> | </tab></tabs> | ||
| Line 55: | Line 77: | ||
|- | |- | ||
|00:06 | |00:06 | ||
| − | |bootia32. | + | |bootia32.efi |
|pxe boot executable for this boot architecture (32 bit EFI) | |pxe boot executable for this boot architecture (32 bit EFI) | ||
| | | | ||
|- | |- | ||
|00:07 | |00:07 | ||
| − | |bootx64. | + | |bootx64.efi |
|pxe boot executable for this boot architecture (64 bit EFI) | |pxe boot executable for this boot architecture (64 bit EFI) | ||
| | | | ||
| Line 78: | Line 100: | ||
|<boot executable> | |<boot executable> | ||
|boot architecture and associated boot executable | |boot architecture and associated boot executable | ||
| − | e.g. 00:09 syslinux. | + | e.g. 00:09 syslinux.efi |
|optional | |optional | ||
| − | |} | + | |}Additional boot architectures (as per https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#processor-architecture) can be supported by adding them to pxe as <arch> <executable> e.g. <syntaxhighlight lang="bash"> |
| − | + | config set-prop pxe 00:09 syslinux.efi | |
| − | + | </syntaxhighlight> | |
=== Uninstall === | === Uninstall === | ||
Latest revision as of 06:08, 22 June 2022
 | |
| pxe logo | |
| Maintainer | TrevorB |
|---|---|
| Url | https://wiki.koozali.org |
| Category | |
| Tags | network, pxe boot, tftp, thinclient |
Maintainer
Version
Description
Global settings for dhcp to allow clients to network boot. Assumes sme server is acting as dhcp server.
This contrib supplies the basic parameters for dhcpd to allow pxe booting on your network.
It is ONLY config db parameters and /etc/dhcpd.conf template fragments. No panels or scripts.
Just restart dhcpd to get updated parameters added into /etc/dhcpd.conf
service dhcpd restart
This will update your /etc/dhcpd.conf file to include
option client-architecture code 93 = unsigned integer 16;
<and within the subnet scope>
if option client-architecture = 00:07 {
filename "/bootx64.efi";
}
elsif option client-architecture = 00:06 {
filename "/bootia32.efi";
}
else {
filename "/pxelinux.0";
}
Installation
yum --enablerepo=smecontribs install smeserver-pxe
Configuration
you can list the available configuration with the following command :
config show pxe
Some of the properties are not shown, but are defaulted in a template or a script. Here a more comprehensive list with default and expected values :
| property | default | values | |
|---|---|---|---|
| status | enabled | enabled, disabled | |
| default | pxelinux.0 | any name of executable | |
| 00:06 | bootia32.efi | pxe boot executable for this boot architecture (32 bit EFI) | |
| 00:07 | bootx64.efi | pxe boot executable for this boot architecture (64 bit EFI) | |
| dir | <directory> | subdirectory of /tftpboot in which to find executable
e.g. EFI |
optional |
| nextserver | <IP address> | IP address of tftp server in your network | optional |
| <arch> | <boot executable> | boot architecture and associated boot executable
e.g. 00:09 syslinux.efi |
optional |
Additional boot architectures (as per https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#processor-architecture) can be supported by adding them to pxe as <arch> <executable> e.g.
config set-prop pxe 00:09 syslinux.efi
Uninstall
yum remove smeserver-pxe
Bugs
Please raise bugs under the SME-Contribs section in bugzilla
and select the smeserver-pxe component or use this link
Below is an overview of the current issues for this contrib:
Changelog
Only released version in smecontrib are listed here.
- add event smeserver-pxe-update to trigger dhcpd restart via creatlinks [12087]
- Remove incorrect = sign from nextserver parameter and enclsing "'s
- Set default architecture executables to Centos 7 defaults [SME 11969]
2022/04/28 Trevor Batley 0.1-1.sme
- Initial release [SME 10821]
- Split of PXE Global parameters out of smeserver-thinclient
