rtl819xx/package/dnsmasq/files, branch master

packages: sort network related packages into package/network/

2012-10-10T12:32:29+00:00

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33688 3c298f89-4303-0410-b956-a3cf2f4a3e73

package/dnsmasq: allow /etc/config/dhcp to specify --address arguments

2012-07-05T17:54:14+00:00

Add a config list to the 'config dnsmasq' section to specify fixed DNS
addresses.

For example:

  config dnsmasq:
	[snip]
	list address '/example.com/192.168.0.1'

will result in the argument '-A /example.com/192.168.0.1' to the dnsmasq
options. This configures dnsmasq to return the specified IP for any
queries to '*.example.com' names.

Useful for overriding lookups to a range of DNS names.

[jow: "append args" -> "xappend", "-A" -> "--address"]

Signed-off-by: Jeremy Kerr 

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32624 3c298f89-4303-0410-b956-a3cf2f4a3e73

Add local TTL option to dnsmasq

2012-07-05T17:46:32+00:00

-T, --local-ttl=
    When replying with information from /etc/hosts or the DHCP leases
file dnsmasq by default sets the time-to-live field to zero, meaning
that the requestor should not itself cache the information. This is
the correct thing to do in almost all situations. This option allows a
time-to-live (in seconds) to be given for these replies. This will
reduce the load on the server at the expense of clients using stale
data under some circumstances.

[jow: change -T to --local--ttl to conform with the other options]

Signed-off-by: Andrew Byrne 

openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32623 3c298f89-4303-0410-b956-a3cf2f4a3e73

[package] dnsmasq: introduce "add_local_hostname" and "add_local_domain" options

2012-07-01T11:32:46+00:00

 - add_local_domain defaults to 1 and controls whether the local domain is written as search directive to the local resolv.conf
 - add_local_hostname defaults to 1 and controls whether A and PTR records are created automatically for the local hostname
These change supersedes http://patchwork.openwrt.org/patch/2207/ and http://patchwork.openwrt.org/patch/2208/

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32570 3c298f89-4303-0410-b956-a3cf2f4a3e73

package/dnsmasq: permit UCI configuration of --dhcp-fqdn option

2012-07-01T11:32:45+00:00

This adds a new boolean option, fqdn, to the "config dnsmasq" section of
/etc/config/dhcp. The default is off. When set on, it enables the dhcp-fqdn
option to dnsmasq. dhcp-fqdn causes dnsmasq's DNS server to not resolve
unqualifed local hostnames. The "domain" option is required when using "fqdn".
Local hostnames will remain available for lookup using fully-qualified names.

Signed-off-by: Mark Mentovai 

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32569 3c298f89-4303-0410-b956-a3cf2f4a3e73

[PATCH 1/4] package/dnsmasq: permit dhcp_option in global dnsmasq config section

2012-07-01T11:32:29+00:00

dnsmasq currently permits dhcp_options to be specified only in "config dhcp"
sections of /etc/config/dhcp. When dnsmasq is providing DHCP service for
multiple subnets and there are multiple "config dhcp" sections without "option
ignore", it makes sense to allow dhcp_options that should apply globally in
the "config dnsmasq" section of /etc/config/dhcp. dhcp_option is a list option.

[jow: rework patch to apply after dhcp-option-force handling got introduced]

Signed-off-by: Mark Mentovai 

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32568 3c298f89-4303-0410-b956-a3cf2f4a3e73

dnsmasq: allow forcing options

2012-05-19T20:17:56+00:00

The option 'force' when set to '1' will transform a dhcp-option to dhcp-option-force instead in the config.

This is useful for forcing options to be sent back to a client (even options it didn't ask for).

Signed-off-by: Philip Prindeville 

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31816 3c298f89-4303-0410-b956-a3cf2f4a3e73

dnsmasq: add support for set: and tag: pairs

2012-05-19T20:17:54+00:00

On my network, I have a variety of machines and appliances, some of which need different configuration issues than the default options.

For example:

config host
	option name 'client'
	option mac '00:01:02:03:04:05'
	option ip '192.168.1.20'
	option tag 'acme'

config tag acme
	option force '1'
	list dhcp_option 'option:router,192.168.1.253'
	list dhcp_option 'option:domain-name,acme.com'
	list dhcp_option 'option:domain-search,acme.com,redfish-solutions.com'

which allows me to override the default router for my client's host, as well as its domain-name, and its domain-search.

this causes the following config lines:

dhcp-host=00:01:02:03:04:05,set:acme,192.168.1.20,client
dhcp-option-force=tag:acme,option:router,192.168.1.253
dhcp-option-force=tag:acme,option:domain-name,acme.com
dhcp-option-force=tag:acme,option:domain-search:acme.com,redfish-solutions.com

This could be useful elsewhere, for instance, if you have an IP CCTV that you don't want to have a default-route, etc.

Signed-off-by: Philip Prindeville 

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31815 3c298f89-4303-0410-b956-a3cf2f4a3e73

[package] dnsmasq: fix parsing of mx record options (#11365)

2012-05-19T20:17:19+00:00

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31814 3c298f89-4303-0410-b956-a3cf2f4a3e73

dnsmasq: configure dnsmasq via flat config file and not command-line args

2012-04-02T22:31:21+00:00

Sometimes it's useful to compare the generated config file from UCI config with a hand-edited dnsmasq config file, especially if you're migrating to an OpenWRT router from something else (such as Astlinux).

Putting the generated config makes it easier to capture and diff, etc.

Signed-off-by: Philip Prindeville 

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31182 3c298f89-4303-0410-b956-a3cf2f4a3e73