![]() Here is you can find my default network configuration. Jun 19 03:27:58 lubuton systemd: Started LSB: HPA's tftp server.Ĭlient side: PXE-E53: No bootfilename recieved Jun 19 03:27:58 lubuton tftpd-hpa: * Starting HPA's tftpd in.tftpd Jun 19 03:27:58 lubuton systemd: Starting LSB: HPA's tftp server. Loaded: loaded (/etc/init.d/tftpd-hpa generated)Īctive: active (running) since Sun 03:27:58 CEST 6h ago Jun 19 09:30:18 lubuton systemd: Started dnsmasq - A lightweight DHCP and caching DNS server. Jun 19 09:30:18 lubuton dnsmasq: read /etc/hosts - 7 addresses Jun 19 09:30:18 lubuton dnsmasq: reading /etc/nf Jun 19 09:30:18 lubuton dnsmasq-tftp: TFTP root is /srv/tftp Jun 19 09:30:18 lubuton dnsmasq-dhcp: DHCP, sockets bound exclusively to interface enp5s0 ![]() Process: 75270 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS) Process: 75261 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 75253 ExecStartPre=/etc/init.d/dnsmasq checkconfig (code=exited, status=0/SUCCESS) Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Sun 09:30:18 CEST 8s ago rvice - dnsmasq - A lightweight DHCP and caching DNS server.Here you'll find my current network settings and the other details: service dnsmasq service dnsmasq status I've been testing to make this configuration work with dnsmasq instead. If it's on, it should get one for the PXE boot configuration only and release after it's done. If network boot is disabled on client it should get an IP from the general network range to get file sharing and other LAN services. I presumed it should give priority to the same range. It's narrow, because my router is set on 192.168.1.1. Even then, it gets the same IP back sometimes. I've to manually reset the network on client. ![]() Although, it lease it and doesn't release it, even after reboot. ![]() The point would be, that only computers that request boot should have one of those 2 IP's. 2 computers using PXE boot together) # cat /etc/network/interfaces The server has therefor a second IP 192.168.0.19 broadcast on /24 for only 2 IP range. Therefor I've configured my network adapter with 2 IP addresses on a different range.ġ92.168.1.19 is the general network that broadcast on /24įor the PXE server boot I'm trying to use another set of IP's to separate it from the rest of the network configuration. I would like to setup my PXE server to attribute a correct IP-address, only for clients requesting network boot. ![]()
0 Comments
Leave a Reply. |