Recent content by kevindb

The domain that is considered local or perhaps a better way of describing it is managed is specified in the 'Lan -> DHCP server -> Domain name' option. This tells dnsmasq the name of the domain to which it should attach DHCP leases (and is also advertised as the default domain to all DHCP...

Good :-) Do we know what these 2 different devices are? As missus dB returned from shopping with her iThing earlier I saw a dhcpnak as it tried to reuse an IP address from when it was out...a thought occurred that if these devices were mobile phones might they be trying to re-use addressed...

Can we please move on from a default position of 'something is wrong with dnsmasq' to perhaps considering that the DHCP client is buggy. It wouldn't be the first and it most certainly won't be the last.

But may I say how clean & how well documented your git is.....it comes as a shock when something doesn't build out of the box even if it is alpha :-)

I've no idea whether you're agreeing with me or not. Yes you set the local domain name, *but* and this is the thing I don't understand, if you look at /tmp/resolv.dnsmasq you'll find "server=/local/dns.server.ip.address", and 'local' is literally 'local' no matter what you set your local...

That's not quite what its doing. Its set to forward a domain literally called 'local' to WAN DNS servers, which I'll be honest and say I really don't understand the logic! Even if your local domain was called 'local' what would your ISP's DNS know about it - nothing! There may be some clever...

What problem?

It adds '-local' & '-bogus-priv' options to dnsmasq. The intent is that lookups for the local domain, both forward and reverse, are constrained to dnsmasq's knowledge and not forwarded in any way to your ISP's servers. From an IP address perspective, the vast majority of us will be using...

A couple of points here. First, every DNS server is supposed to have a whole view of the domain structure, therefore if an answer doesn't exist it shouldn't exist no matter to which server you send the query. In other words if one server knows about a certain domain and another doesn't then...

I logged a support call with Asus and got a reply from Patrick at Asus UK. The enhancement request has been forwarded to "HQ Wireless department to see if our engineers can implement a fix in the next firmware update." It would be great if Asus can sort this. I'm impressed with the speed and...

Ah, I understand :) By default, dnsmasq sends some standard options to DHCP clients, the netmask and broadcast address are set to the same as the host running dnsmasq, and the DNS server and default route are set to the address of the machine running dnsmasq. So arguably Asus don't actually...

If you empty the 'DNS server' under LAN-> DHCP Server then Asuswrt won't write a 'dhcp-option,lan,6,10.....' line in the dnsmasq.conf, allowing you to simply add the required line in a 'dnsmasq.conf.add' file. The question I have is why you cannot let dnsmasq do it's excellent job of being a...

The active one dnsmasq uses is '/etc/dnsmasq.conf' If you've just 'dnsmasq.conf' in /jffs then that will be completely ignored. You would need to put it in /jffs/configs. But I would recommend instead that you use a '/jffs/configs/dnsmasq.conf.add' file instead which will get appended to the...

add 'log-dhcp' to dnsmasq.conf. This will log dhcp requests and responses to syslog. In that log you'll also see the 'tag/interface' on which the request/response is received/sent. That might give you some extra clues as to what is going on.

What other 'dhcp-option=lan,6' lines are in /etc/dnsmasq.conf? Another thing to do is add 'log-dhcp' to dnsmasq.conf which will enable dhcp logging to syslog. You can then see exactly what dhcp requests are being received *and* how dnsmasq is responding to them.