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 <jk@ozlabs.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32624 3c298f89-4303-0410-b956-a3cf2f4a3e73
-T, --local-ttl=<time>
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@andy.id.au>
openwrt-devel mailing list
openwrt-devel@lists.openwrt.orghttps://lists.openwrt.org/mailman/listinfo/openwrt-devel
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32623 3c298f89-4303-0410-b956-a3cf2f4a3e73
Set PATH in non-interactive logins to include /sbin paths,
so to be consistent with what is currently set in /etc/profile
for interactive shells.
[jow: reapply with current patch level, fix inner patch, refresh]
Signed-off-by: Gui Iribarren <gui@altermundi.net>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32620 3c298f89-4303-0410-b956-a3cf2f4a3e73
Set PATH in non-interactive logins to include /sbin paths,
so to be consistent with what is currently set in /etc/profile
for interactive shells.
Signed-off-by: Gui Iribarren <gui@altermundi.net>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32618 3c298f89-4303-0410-b956-a3cf2f4a3e73
This ensures that the resulting firmware can
be flashed from the latest (v3.13.17) offical
firmware.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32617 3c298f89-4303-0410-b956-a3cf2f4a3e73
Because ath9k does not supports separate LEDs for
different bands yet, the 2.4GHz LED will show the
activity, even if the 5GHz band is selected.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32615 3c298f89-4303-0410-b956-a3cf2f4a3e73
When mtd alters the fis partition table it assumes that the first partition
table entry also is the first logical parition table entry. For instance our
table could look like this (irrelevant partitions put aside):
* vmlinux.bin.l7 0xA8710000
* rootfs 0xA8030000
Here mtd would assume vmlinux.bin.l7 being the first partition and use its
address to calculate the size and offset which ultimately leads to a broken
partition table.
This patch alters the behavior by checking what partition has the smaller
address to do the calculations based on that address.
Signed-off-by: Marek Lindner <lindner_marek@yahoo.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32601 3c298f89-4303-0410-b956-a3cf2f4a3e73
The offset parameter can be used to write the data at the offset
instead of writing it to the beginning of the partition.
Signed-off-by: Marek Linder <lindner_marek@yahoo.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32600 3c298f89-4303-0410-b956-a3cf2f4a3e73
Pass the mtd_layout via the kernel command line instead.
Also increase the kernel partition size to 1024k, so current kernel can fit in.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32585 3c298f89-4303-0410-b956-a3cf2f4a3e73
Busybox udhcpc dropped support for the -c option, instead it can be emulated by using -x 0x3d:id,
change the dhcp protocol script accordingly and filter all colons from the id while we're at it.
This change supersedes http://patchwork.openwrt.org/patch/1810/
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32573 3c298f89-4303-0410-b956-a3cf2f4a3e73
On the off chance that the root filesystem's /tmp is used directly as a
temporary directory instead of having a tmpfs mounted over it, it should have
the sticky bit set.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32572 3c298f89-4303-0410-b956-a3cf2f4a3e73
- 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
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 <mark@moxienet.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32569 3c298f89-4303-0410-b956-a3cf2f4a3e73
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 <mark@moxienet.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32568 3c298f89-4303-0410-b956-a3cf2f4a3e73
