Also, /etc/ethers does not accept IPv6 addresses, and, even when using the hostname instead,
the ether address will not associate with >> an IPv6 address in /etc/hosts. Again,
"dhcp-host=..." still has to be used for DHCPv6.
Oops - I had "bind-interfaces" instead of "bind-dynamic", and
On 5/20/22 04:09, Matus UHLAR - fantomas via Dnsmasq-discuss wrote:
just FYI, I use /etc/ethers for this, as this is unix database for mapping
ethernet numbers to hostnames.
dnsmasq uses this database on my home router
Hmm - this only works if "-Z" or "read-ethers" is explicitly set - as I
dnsmasq 2.86
and
dnsmasq-git 2.87test8.r16.g770bce9-1
Does dnsmasq create dns entries for hosts with dhcp-host= entries?
Or, instead, must all of these dhcp-host= hosts be redundantly listed in
/etc/hosts?
For example,
$ host 172.16.16.2
;; Got bad packet: extra input data
74 bytes
5c c8 85
Should the dhcp-range "constructor" feature work with a prefix length greater
than 64?
The man page says:
For IPv6, the parameters are slightly different: instead of netmask and
broadcast address, there is an optional prefix length which must be equal to or
larger th[a]n the prefix
man 8 dnsmasq:
-F,
--dhcp-range=[tag:[,tag:],][set:,][,|constructor:][,][,][,]
...
For IPv6, the parameters are slightly different: instead of netmask and
broadcast address, there is an optional prefix length which must be equal to
*or larger th[a]n* the prefix length on the local
On 3/17/21 7:19 PM, dnsmasqlist2...@rscubed.com wrote:
>>> I would like to use it with the spamhaus DROP list (A list of bad
>>> network blocks) to make all domains (known and currently unknown) on
>>> those networks disappear.
Hmm - how do you actually configure this? Do you dynamically
On 11/14/19 10:17 PM, Geert Stappers wrote:
> I look forward to the change proposal.
Learn to read English for comprehension, and then refer back to the post you
quoted.
> Zero fuck giving how much disagreement there might be.
> What matters is where we agree.
We may agree that dnsmasq is
Hey Simon
On 11/8/19 4:36 PM, Simon Kelley wrote:
> If there's no name configured in the dnsmasq configuration, then the
> client-provided name will be matched. However if there is a name
> configured in the dnsmasq configuration, selected by MAC address or
> client-id, then that will be used in
Hey Simon
On 10/30/19 3:32 PM, Simon Kelley wrote:
> The question is, [if] the client-provided name and the dhcp-host name
> differ, which one should be matched? Since this is broken, there's no
> pre-existing behaviour to consider. Any configurations relying on one or
> the other are currently
dnsmasq 2.80-4
Arch Linux
/etc/dnsmasq.conf
dhcp-name-match=set:printer,NPI*
$ journalctl -ab
...
client provides name: NPI8C840E.prime
...
tags: known, enp4s0
Uhm - so, did I miss something? Or, is "dhcp-name-match=" broken?
Why is the tag "printer" not been appended to the list of tags?
The
Hey Simon
On 9/8/18 11:17 AM, Simon Kelley wrote:
> The question is, should the above configuration be "baked in" to the code?
As I understand, this vulnerability arises from the Web Proxy Automatic
Discovery (WPAD) protocol, not from dnsmasq itself. And, dnsmasq configuration
provides - or
It seems that, every so often, dnsmasq needs to be restarted - unless we blame
WIDE dhcpv6. Here, dnsmasq has been running for about a week, and a newly
started dhcpv6 client will show things like this in the log:
dhcp6c[412]: dhcp6_get_options: get DHCP option identity association, len 18
Arch Linux
dnsmasq 2.75-1
linux 4.5.2-1
I mentioned about two weeks ago, the dnsmasq dhcpv6 server will just stop
responding after running normally for a while. There have been no comments that
I have seen. Any thoughts? Is there a way to dump the state of the dhcpv6
server? Should I not be
Arch Linux
dnsmasq 2.75-1
linux 4.5-1
After running for about a week, I've just seen dnsmasq get into a mode where the
dhcpv6 server stops responding, while the dhcp server continues to respond and
router advertisements continue normally. It works again after a re-start. Is
this something
14 matches
Mail list logo
