Dnsmasq - Revision history

Leo at 04:04, 21 June 2020

2020-06-21T04:04:28Z

← Older revision		Revision as of 04:04, 21 June 2020
Line 163:		Line 163:
	tftp-root=/tftpboot		tftp-root=/tftpboot
	}}		}}

			== Other Notes ==
			Use <code>-x pidfile</code> to specify a PID file and <code>-k</code> to run in the foreground.

	==See Also==		==See Also==

Leo: /* Quick Usage */

2020-06-21T04:02:00Z

Quick Usage

← Older revision		Revision as of 04:02, 21 June 2020
Line 5:		Line 5:
	==Quick Usage==		==Quick Usage==

	dnsmasq can take its configuration entirely from a configuration file or command arguments. On embedded systems with no writable filesystem, it is possible to configure and run dnsmasq solely by command arguments which will be used in the examples below~~. Converting command arguments into a configuration file is as simple as taking out the leading <code>--</code> and putting them into a file~~.		dnsmasq can take its configuration entirely from a configuration file or command arguments. On embedded systems with no writable filesystem, it is possible to configure and run dnsmasq solely by command arguments which will be used in the examples below.

			Converting the command arguments into a configuration file is as simple as taking out the leading double dashes <code>--</code> from every argument, saving each argument as its own line in a file, and specifying the configuration file with <code>-C configfile</code>.

			By default, dnsmasq will read <code>/etc/dnsmasq.conf</code> first. On a clean install, this file typically specifies the user and group the process should run as only.

			===As a DHCP server===
	Refer to the DHCP options section to understand the DHCP option numbers used in the examples below. You can always mix different options together to enable any of the following examples together.		Refer to the DHCP options section to understand the DHCP option numbers used in the examples below. You can always mix different options together to enable any of the following examples together.

	~~=== As a DHCP server ===~~
	To run dnsmasq as a DHCP server with a lease pool between 192.168.192.11 through 192.168.192.250 with a 1 hour lease time and 192.168.192.10 as the DNS server and gateway:		To run dnsmasq as a DHCP server with a lease pool between 192.168.192.11 through 192.168.192.250 with a 1 hour lease time and 192.168.192.10 as the DNS server and gateway:
	{{Highlight		{{Highlight
Line 22:		Line 26:
	Lease time must be given as seconds (no unit), minutes (m), or hours (h). You must convert days or weeks into hours. 1 day as 24h, or 1 week as 168h.		Lease time must be given as seconds (no unit), minutes (m), or hours (h). You must convert days or weeks into hours. 1 day as 24h, or 1 week as 168h.

	=== As a DNS relay server ===		===As a DNS relay server===
	To run dnsmasq as a DNS relay on port 5353:		To run dnsmasq as a DNS relay on port 5353:
	{{Highlight		{{Highlight
Line 29:		Line 33:
	}}		}}

	=== As a TFTP server ===		===As a TFTP server===
	To run dnsmasq as a standalone TFTP server:		To run dnsmasq as a standalone TFTP server:
	{{Highlight		{{Highlight
Line 39:		Line 43:
	}}		}}

	=== As a DHCP, DNS, and TFTP server ===		===As a DHCP, DNS, and TFTP server===
	Run dnsmasq with all the options listed in the examples above together.		Run dnsmasq with all the options listed in the examples above together.
	{{Highlight		{{Highlight
Line 160:		Line 164:
	}}		}}

	== See Also ==		==See Also==

	* Project website: http://www.thekelleys.org.uk/dnsmasq/doc.html<br />		*Project website: http://www.thekelleys.org.uk/dnsmasq/doc.html<br />
	{{Navbox Linux}}		{{Navbox Linux}}
	[[Category:Linux]]		[[Category:Linux]]

	{{Navbox Services}}		{{Navbox Services}}

Leo: Rewrote a bunch of content and made quick usage examples

2020-06-21T03:56:58Z

Rewrote a bunch of content and made quick usage examples

Show changes

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T06:22:24Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

← Older revision		Revision as of 06:22, 1 September 2019
Line 109:		Line 109:


	[[Category:Linux]]~~{{Navbox Linux}}~~		{{Navbox Linux}}[[Category:Linux]]

	{{Navbox Services}}		{{Navbox Services}}

Leo: Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

2019-09-01T05:10:22Z

Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

← Older revision		Revision as of 05:10, 1 September 2019
Line 109:		Line 109:


	[[Category:Linux]]~~{{Navbox Linux}}~~{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}

	{{Navbox Services}}		{{Navbox Services}}

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

2019-09-01T05:09:13Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:09, 1 September 2019
Line 109:		Line 109:


	[[Category:Linux]]{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}{{Navbox Linux}}

	{{Navbox Services}}		{{Navbox Services}}

Leo: Text replacement - "Category:Linux " to "Category:Linux{{Navbox Linux}} "

2019-09-01T03:44:36Z

Text replacement - "Category:Linux " to "Category:Linux{{Navbox Linux}} "

← Older revision		Revision as of 03:44, 1 September 2019
Line 109:		Line 109:


	[[Category:Linux]]		[[Category:Linux]]{{Navbox Linux}}

	{{Navbox Services}}		{{Navbox Services}}

Leo: /* PXE Boot */

2017-05-23T18:07:07Z

PXE Boot

← Older revision		Revision as of 18:07, 23 May 2017
Line 82:		Line 82:

	=== PXE Boot ===		=== PXE Boot ===
	The next-server is defined using the {{code\|dhcp-option-force=66,xx.xx.xx.xx}} option. The boot filename can be defined using the {{code\|dhcp-boot=xxxx}} option.		The next-server is defined using the {{code\|1=dhcp-option-force=66,xx.xx.xx.xx}} option. The boot filename can be defined using the {{code\|1=dhcp-boot=xxxx}} option.

	Alternatively, these two options can be passed as a command line option using the {{code\|-M}} flag, followed by the filename, next-server hostname, and IP. Eg. {{code\|-M pxelinux.0,,10.130.4.254}}. The hostname can be left blank.		Alternatively, these two options can be passed as a command line option using the {{code\|-M}} flag, followed by the filename, next-server hostname, and IP. Eg. {{code\|-M pxelinux.0,,10.130.4.254}}. The hostname can be left blank.

Leo: /* PXE Boot */

2017-05-23T18:06:45Z

PXE Boot

← Older revision		Revision as of 18:06, 23 May 2017
Line 82:		Line 82:

	=== PXE Boot ===		=== PXE Boot ===
	The next-server is defined using the {{code-option-force=66}} option.		The next-server is defined using the {{code\|dhcp-option-force=66,xx.xx.xx.xx}} option. The boot filename can be defined using the {{code\|dhcp-boot=xxxx}} option.
	The boot filename can be defined using the {{code\|dhcp-boot}} option.

	Alternatively, these two options can be passed as a command line option using the {{code\|-M}} flag, followed by the filename, next-server hostname, and IP. Eg. {{code\|-M pxelinux.0,,10.130.4.254}}. The hostname can be left blank.		Alternatively, these two options can be passed as a command line option using the {{code\|-M}} flag, followed by the filename, next-server hostname, and IP. Eg. {{code\|-M pxelinux.0,,10.130.4.254}}. The hostname can be left blank.

Leo: /* PXE Boot */

2017-05-23T18:05:40Z

PXE Boot

← Older revision		Revision as of 18:05, 23 May 2017
Line 82:		Line 82:

	=== PXE Boot ===		=== PXE Boot ===
	~~To define the~~ next-server ~~and boot filename (like you would in dhcpd for instance), edit~~ the ~~dnsmasq configuration file with the following line, or append it to the dnsmasq options (with~~ {{code\|--~~dhcp~~-~~boot~~}} or {{code\|-M}}).		The next-server is defined using the {{code-option-force=66}} option.
			The boot filename can be defined using the {{code\|dhcp-boot}} option.

	{{~~highlight~~\|~~lang=text~~\|~~code=~~		Alternatively, these two options can be passed as a command line option using the {{code\|-M}} flag, followed by the filename, next-server hostname, and IP. Eg. {{code\|-M pxelinux.0,,10.130.4.254}}. The hostname can be left blank.
	~~dhcp~~-~~boot=~~pxelinux.0,,~~172~~.20.1.10
	}}

	The ~~options passed to dhcp-boot are:~~
	~~# pxelinux.0 is the filename to boot~~
	~~# (empty) is the servername that is looked up in the local hosts file~~.
	~~# 172.20.1.10 is the next-server (ie. the PXE TFTP server)~~

	==== Example ====		==== Example ====
	Here is a working example of a PXE boot config that I've used on a RaspberryPi.		Here is a working example of a PXE boot config that I've used on a RaspberryPi. Dnsmasq here also acts as the TFTP server serving from {{code\|/tftpboot}}.

	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
Line 101:		Line 95:
	bind-interfaces		bind-interfaces
	dhcp-range=10.130.4.110,10.130.4.169,24h		dhcp-range=10.130.4.110,10.130.4.169,24h

	dhcp-boot=/pxelinux.0		dhcp-boot=/pxelinux.0

	dhcp-option-force=66,10.130.4.254		dhcp-option-force=66,10.130.4.254