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 <philipp@redfish-solutions.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31815 3c298f89-4303-0410-b956-a3cf2f4a3e73
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 <philipp@redfish-solutions.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31182 3c298f89-4303-0410-b956-a3cf2f4a3e73
Adding the following syntax support:
config mxhost
option domain mydomain.com
option relay svr10.ironport.com
option pref 50
and this will generate an MX record for mydomain.com pointing at the relay with a given preference.
Redux: default the preference to 0 if absent.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31057 3c298f89-4303-0410-b956-a3cf2f4a3e73
The SRV record also requires the class and weight fields... Currently you can overload the "port" keyword as:
option port xxxx,class,weight
but this is counter-intuitive. Here we fix this.
Redux: make the port required.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31056 3c298f89-4303-0410-b956-a3cf2f4a3e73
The attached patch for dnsmasq.init allows to assign a hostname to a
particular mac-address. It's useful to override the client supplied
hostname, especially if the client does not supply a hostname at all.
It corresponds to the following example in dnsmasq.conf.example:
# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"
#dhcp-host=11:22:33:44:55:66,fred
Regards
Mathias
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26983 3c298f89-4303-0410-b956-a3cf2f4a3e73
'limit' is actually the number of IP addresses to serve. See the use of ipcalc.sh.
For getting the expected number of IP addresses served, we have to decrement
limit by one.
Patch from: kentarou matsuyama <matsuyama@thinktube.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25100 3c298f89-4303-0410-b956-a3cf2f4a3e73
If an already running DHCP-server is found on
the configured interface, the init-script refuses
to start, but does not give a hint why. It took us
some days to track down this behavior in our MANET,
where every wifi/adhoc-node runs it own DHCP-server.
Now syslog is more verbose on this.
Signed-off-by: Bastian Bittorf <bittorf@bluebottle.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@24051 3c298f89-4303-0410-b956-a3cf2f4a3e73
- when processing domain entries, append searchdomain to host entries if they are not fully qualified
- create only one reverse record for address entries with multiple names
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@21109 3c298f89-4303-0410-b956-a3cf2f4a3e73
This renames name to networkid where applicable, and re-adds the name option for hosts.
Signed-off-by: Stefan Bethke <stb@lassitu.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@19069 3c298f89-4303-0410-b956-a3cf2f4a3e73
While trying to document the dhcp UCI config, I noticed that the name config option is applied wrongly when adding static addresses. Cf. the dnsmasq man page.
Signed-off-by: Stefan Bethke <stb@lassitu.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@18934 3c298f89-4303-0410-b956-a3cf2f4a3e73
e.g.
list 'addnhosts' '/var/etc/hosts.olsr'
list 'addnhosts' '/var/etc/hosts.olsrv6'
hosts.olsr for ipv4 and hosts.olsrv6 for ipv6 addresses.
Signed-off-by: Patrick Grimm <patrick@lunatiki.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@18470 3c298f89-4303-0410-b956-a3cf2f4a3e73
- make "name" option in "host" sections optional and append it to -G if set,
allows specifying hostnames for static leases without resorting to /etc/hosts
- implement "domain" sections, allows defining arbitary host names and associated
ptr records from uci
- bump package revision
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@17897 3c298f89-4303-0410-b956-a3cf2f4a3e73
dnsmasq allows adding of arbitrary SRV/PTR/TXT/CNAME records.
However, those options sometimes can not be passed as
command-line arguments due to excess length. This patch tries to
solve this problem:
1. Provide /etc/dnsmasq.conf file with comments about adding
SRV/PTR/TXT/CNAME records.
2. Add this file to conffiles list so it is preserver during
backup/restore or system upgrade.
If someone needs a lot of custom records, default configuration
file can be edited. Since manual pages and documentation is not
installed, provided comments should be enough to figure out
option syntax.
Signed-off-by: Alexey I. Froloff <raorn@altlinux.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@17663 3c298f89-4303-0410-b956-a3cf2f4a3e73
This tiny patch makes the dnsmasq init.d script listen to a parameter called "notinterface", which tells dnsmasq to not listen on a defined set of interfaces.
By default dnsmasq *always* listens on the loopback interface, even if you tell it to specifically listen on a certain other interface. Sometimes this is not desirable behaviour, so you might want to turn it off. This is useful when, for example, you want to have your own DNS server listening on the loopback interface.
Signed-off-by: Johnny Halfmoon <jhalfmoon at milksnot.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@17599 3c298f89-4303-0410-b956-a3cf2f4a3e73
dnsmasq.init tried to set range options even when ignore was
set to "1". Now the functions stops processing after evaluating
the "ignore" option when the result is > 0
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@15618 3c298f89-4303-0410-b956-a3cf2f4a3e73
