Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # Set port to 0 so that dnsmasq knows its not being used as a DNS server.
- port=0
- # Configure DHCP-Proxy range
- dhcp-range=192.168.0.255,proxy
- # Log lots of extra information about DHCP transactions.
- log-dhcp
- # For debugging purposes, log each DNS query as it passes through dnsmasq.
- log-queries
- # TFTP support
- enable-tftp
- tftp-root=/tftpboot
- # Booting part
- dhcp-match=gpxe,175 # gPXE sends a 175 option
- dhcp-boot=net:#gpxe,gpxe.kpxe # if the request does not match the gpxe rule (#gpxe) then tell the client (most likely standard PXE client) to boot gPXE
- dhcp-boot=\Boot\pxeboot.n12,freeone,192.168.0.254 # in this case the request was made by gPXE and we tell it to boot win7 pxe image via TFTP (freeone is the host name, and 192.168.0.254 is the IP; in theory these 2 fields should not be necessary if the TFPT server is on the same machine as dnsmasq but...)
- # Force sending of DHCP BOOT Packets
- pxe-service=123456789, "Trigger", triggerfile, 0
- # Not sure why the line above is needed and how it should be used; please see: http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example
- # L.E.: It triggers the sending of dhcp-boot data... actual data is not sent, hence dummy data
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement