On Sat, 8 Apr 2017 at 00:21, Simon Kelley wrote:
> I understand the desire to be able to specify resolvers dynamically with
> the full set of source-address and routing options; that's actually
> already available, and has been for a long time, using the DBus
The latest firmware for the printer is from 2015. This is one of those
shared Epson/Fuji/Xerox models which I believe is entering EOL, since there
is already another printer
called M200 (Ecotank). Anyway, I'll report it.
Should the the implementation be correct in dnsmasq, then there will be
I am currently using addn-hosts for DNS blacklisting. All of the dhcp
client machines on my network use static assignment via dhcp-host entries
in the config file. Running dnsmasq version 2.48 on Centos 6 (yes, I'm
aware its old but that seems to be the most recent version in the Centos 6
On 06/04/17 14:01, Pedro MG Palmeiro wrote:
> Dnsmasq trunk replies are being ignored by some devices, in my case, two
> epson printers (AL-M200).
> Dnsmasq 2.76 works fine.
> This could be related with
On 30/03/17 12:38, Floris Bos wrote:
> Adds option to delay replying to DHCP packets by one or more seconds.
> This provides a workaround for a PXE boot firmware implementation
> that has a bug causing it to fail if it receives a (proxy) DHCP
> reply instantly.
> On Linux it looks up the exact
The overriding objection to this is that it adds to the syntax and
semantics of the resolv-file format, but dnsmasq doesn't "own" that
format: it's actually a libc configuration file, and dnsmasq takes
advantage of the fact that the format is "well known" to extract useful
information from it. If