[Dnsmasq-discuss] "multiple MAC addresses in a single dhcp-host" vs "multiple dhcp-host lines with the same IP address"

[Jaime]

Hi.

A long time ago [1], Simon wrote to the list saying:

"Be aware that multiple MAC addresses in a single dhcp-host has
different semantics to multiple dhcp-host lines, each with one MAC
address but with the same IP address."

Is this still true i.e. does a single dhcp-line with multiple MAC
addresses still have different semantics to multiple dhcp-host lines
with the same IP address? If so, how do (/does) the semantics differ?

Thank you, Jaime

[1] http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2013q4/007972.html

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Lonnie Abelbeck]

I'm able to reproduce this 2.83 issue, with both errors:
--
Jan 22 09:00:06 gw-lan daemon.err dnsmasq[19230]: failed to send packet: 
Network is unreachable
Jan 22 09:00:06 gw-lan daemon.err dnsmasq[19230]: failed to send packet: 
Network is unreachable
Jan 22 09:00:19 gw-lan daemon.err dnsmasq[19230]: failed to send packet: 
Address family not supported by protocol
Jan 22 09:00:19 gw-lan daemon.err dnsmasq[19230]: failed to send packet: 
Address family not supported by protocol
--
Reverting back to 2.82, the error logs do not appear, no issue.

I normally use "dns-forward-max=512" but tested with "dns-forward-max=2048", no 
effect on the 2.83 issue.

My testing also showed this has nothing to do with proxy-forwarding on 
127.0.0.1#2853 vs. public DNS IPs, same 2.83 issue.


Test method to generate 2.83 issue:

Using an ethernet connected computer to the dnsmasq box, in a browser run Steve 
Gibson's "DNS Nameserver Spoofability Test"...

DNS Nameserver Spoofability Test
https://www.grc.com/dns/dns.htm
(scroll to bottom and click Initiate... button)

This always generates around 40 "failed to send packet" logs with 2.83 in my 
tests.

Interestingly, my WiFi connected MacBook Air over WireGuard does not generate 
any "failed to send packet" logs with the same test. So a direct ethernet 
connection with a non-wimpy computer is required.

Hopefully Simon (et al.) can reproduce this and provide a fix.

This log occurs in send_from() in src/forward.c . Many forward.c changes have 
occurred with 2.82 -> 2.83, but the function send_from() itself is unchanged.

Lonnie



> On Jan 21, 2021, at 8:14 PM, Steve Hirsch  wrote:
> 
> Hi Lonnie, 
>  
> I am also seeing an occasional “failed to send packet: Address family not 
> supported by protocol”.  However, it is mostly “Network Unreachable” and they 
> are pretty continuous (much more than the 10 you have).  Dnscrypt is 
> configured to use DoH to cloudflare servers.  On my side, doesn’t seem to be 
> related to activity level…low levels of activity also generates errors.
>  
> From: Lonnie Abelbeck
> Sent: Thursday, January 21, 2021 6:42 PM
> To: dnsmasq list
> Cc: Steve Hirsch
> Subject: Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is 
> unreachable
>  
> 
> 
> > On Jan 21, 2021, at 5:53 PM, Steve Hirsch  wrote:
> > 
> > After upgrading dnsmasq from version 2.82 to version 2.83 on Arch Linux 
> > (kernel 5.10.9), “failed to send packet: Network is unreachable” errors 
> > continually show up.  However, name resolution still appears to work with 
> > v2.83.  Downgrading back to v2.82, and the error messages go away.  Dnsmasq 
> > is configured to forward requests to dnscrypt-proxy via server=::1#53000 
> > and server=127.0.0.1#53000 lines in  dnsmasq.conf.  Turning on log-queries 
> > and log-dhcp did not show anything unusual in the log.
> >  
> > This configuration has been running fine for over a year now, so I don’t 
> > think it’s a configuration issue.  Dnscrypt-proxy is running version 2.0.45 
> > (updated was on 1/6/2021).
> 
> Hey Steve, I'm seeing something similar "failed to send packet" on my setup 
> that is new with 2.82 -> 2.83 .
> 
> Like you, I am proxying via 127.0.0.1#2853, but with unbound performing 
> DNS-over-TLS.
> 
> This box is my edge device with a fair amount of traffic, so the 10 errors 
> are not a lot in 24 hours, but would like to understand the change with 2.83 .
> 
> # grep dnsmasq /var/log/messages | grep -v dnsmasq-dhcp
> --
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: started, version 2.83 
> cachesize 4096
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: compile time options: IPv6 
> GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP 
> no-conntrack ipset auth no-nettlehash no-DNSSEC loop-detect inotify 
> no-dumpfile
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq-tftp[3300]: TFTP root is /tftpboot 
>  
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: using nameserver 
> 127.0.0.1#2853
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: using only locally-known 
> addresses for domain priv.abelbeck.com
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: read /etc/hosts - 65 
> addresses
> Jan 21 04:27:43 gw-lan daemon.err dnsmasq[3300]: failed to send packet: 
> Address family not supported by protocol
> Jan 21 13:14:00 gw-lan daemon.err dnsmasq[3300]: failed to send packet: 
> Address family not supported by protocol
> Jan 21 13:14:00 gw-lan daemon.err dnsmasq[3300]: failed to send packet: 
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet: 
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet: 
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet: 
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet: 
> Address family not supported by pr

Re: [Dnsmasq-discuss] "multiple MAC addresses in a single dhcp-host" vs "multiple dhcp-host lines with the same IP address"

[Simon Kelley]

On 22/01/2021 11:22, Jaime wrote:
> Hi.
> 
> A long time ago [1], Simon wrote to the list saying:
> 
> "Be aware that multiple MAC addresses in a single dhcp-host has
> different semantics to multiple dhcp-host lines, each with one MAC
> address but with the same IP address."
> 
> Is this still true i.e. does a single dhcp-line with multiple MAC
> addresses still have different semantics to multiple dhcp-host lines
> with the same IP address? If so, how do (/does) the semantics differ?
> 
> Thank you, Jaime
> 
> [1] 
> http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2013q4/007972.html
> 

Yes. The difference is that in the normal case of multiple lines, once
the IP address is leased to a MAC address, if another MAC address turns
up asking for a lease, it won't be offered that IP address (typically it
will be offered one from the pool) With multiple MAC addresses on a
single line, when the second MAC address turns up, the IP address will
be unceremoniously ripped away from the first MAC address, and given to
the second one. In this case the owners of the two MAC addresses better
1) be the same machine and 2) expect this behaviour. Typically it's a
laptop which downs its wireless interface and brings up the wired
interface when docked.



Cheers,

Simon.

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Simon Kelley]

On 22/01/2021 02:14, Steve Hirsch wrote:
> Hi Lonnie,
> 
>  
> 
> I am also seeing an occasional “failed to send packet: Address family
> not supported by protocol”.  However, it is mostly “Network Unreachable”
> and they are pretty continuous (much more than the 10 you have). 
> Dnscrypt is configured to use DoH to cloudflare servers.  On my side,
> doesn’t seem to be related to activity level…low levels of activity also
> generates errors.
> 
>  
> 
> *From: *Lonnie Abelbeck 
> *Sent: *Thursday, January 21, 2021 6:42 PM
> *To: *dnsmasq list 
> *Cc: *Steve Hirsch 
> *Subject: *Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is
> unreachable
> 
>  
> 
> 
> 
>> On Jan 21, 2021, at 5:53 PM, Steve Hirsch  wrote:
>>
>> After upgrading dnsmasq from version 2.82 to version 2.83 on Arch
> Linux (kernel 5.10.9), “failed to send packet: Network is unreachable”
> errors continually show up.  However, name resolution still appears to
> work with v2.83.  Downgrading back to v2.82, and the error messages go
> away.  Dnsmasq is configured to forward requests to dnscrypt-proxy via
> server=::1#53000 and server=127.0.0.1#53000 lines in  dnsmasq.conf. 
> Turning on log-queries and log-dhcp did not show anything unusual in the
> log.
>> 
>> This configuration has been running fine for over a year now, so I
> don’t think it’s a configuration issue.  Dnscrypt-proxy is running
> version 2.0.45 (updated was on 1/6/2021).
> 
> Hey Steve, I'm seeing something similar "failed to send packet" on my
> setup that is new with 2.82 -> 2.83 .
> 
> Like you, I am proxying via 127.0.0.1#2853, but with unbound performing
> DNS-over-TLS.
> 
> This box is my edge device with a fair amount of traffic, so the 10
> errors are not a lot in 24 hours, but would like to understand the
> change with 2.83 .
> 
> # grep dnsmasq /var/log/messages | grep -v dnsmasq-dhcp
> --
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: started, version 2.83
> cachesize 4096
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: compile time options:
> IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP
> no-conntrack ipset auth no-nettlehash no-DNSSEC loop-detect inotify
> no-dumpfile
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq-tftp[3300]: TFTP root is
> /tftpboot 
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: using nameserver
> 127.0.0.1#2853
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: using only
> locally-known addresses for domain priv.abelbeck.com
> Jan 20 15:52:41 gw-lan daemon.info dnsmasq[3300]: read /etc/hosts - 65
> addresses
> Jan 21 04:27:43 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 13:14:00 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 13:14:00 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 13:14:01 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 14:12:22 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 15:37:30 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> Jan 21 15:37:30 gw-lan daemon.err dnsmasq[3300]: failed to send packet:
> Address family not supported by protocol
> --
> 
> In dnsmasq.conf I set:
> --
> dns-forward-max=512
> --
>
> So far, I'm not able to generate the "failed to send packet" manually by
> flooding DNS requests and such.
> 

I've so far failed to generate a hypothesis as to what's causing this,
given the set of changes 2.82->2.83

This error message is in the code path when a DNS query over UDP has
been answered and the answer is being sent back over UDP to the original
requestor. The obvious new code here is that multiple instances
_of_the_same_query_ are now combined together, and when the answer
appears, it's sent to all the requestors one after another. It may
therefore be worth trying a flood of the _same_ query repeated.


Cheers,

Simon.
Simon.



___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Hannu Nyman]

I bisected the dnsmasq commits, and looks like it is caused by this:

15b60ddf935a531269bb8c68198de012a4967156  FAIL
824461192ca5098043f9ca4ddeba7df1f65b30ba  Ok ?

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=15b60ddf935a531269bb8c68198de012a4967156

"Handle multiple identical near simultaneous DNS queries better."'

Dnsmasq built from earlier commits seem to avoid the error/warning messages, 
while builds after 15b60ddf cause log spam.



This bug is seen by lots of OpenWrt users, based on OpenWrt forum 
discussion.  E.g. onward from

https://forum.openwrt.org/t/security-advisory-2021-01-19-1-dnsmasq-multiple-vulnerabilities/85903/22

One observation in the forum discussion is that this is only/mainly seen when 
then are Windows PCs or Macs active in LAN. IPv6 RA/DHCPv6 may also play a role.




___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Simon Kelley]

On 22/01/2021 16:08, Hannu Nyman wrote:
> I bisected the dnsmasq commits, and looks like it is caused by this:
> 
> 15b60ddf935a531269bb8c68198de012a4967156  FAIL
> 824461192ca5098043f9ca4ddeba7df1f65b30ba  Ok ?
> 
> http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=15b60ddf935a531269bb8c68198de012a4967156
> 
> 
> "Handle multiple identical near simultaneous DNS queries better."'
> 
> Dnsmasq built from earlier commits seem to avoid the error/warning
> messages, while builds after 15b60ddf cause log spam.
> 
> 
> This bug is seen by lots of OpenWrt users, based on OpenWrt forum
> discussion.  E.g. onward from
> https://forum.openwrt.org/t/security-advisory-2021-01-19-1-dnsmasq-multiple-vulnerabilities/85903/22
> 
> 
> One observation in the forum discussion is that this is only/mainly seen
> when then are Windows PCs or Macs active in LAN. IPv6 RA/DHCPv6 may also
> play a role.
> 
> 

I think this is the solution.

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=04490bf622ac84891aad6f2dd2edf83725decdee


You've found the right commit, and it looks like if two queries are
combined (because they ask the same question) then dnsmasq can get
confused when it comes to return the answer, the reply to the second
query can be sent via the socket that the first one arrived on. That's
normally OK, but if the first query arrives via IPv4 and the second via
IPv6, for instance, then the bug is triggered. Hence the mentions of
IPv6 in this thread.

This is an example of the risk of doing security fixes in secret before
public disclosure, I'm sure a beta release would have found this.

Thanks for the effort taken chasing this. Please apply the patch above
and see if it fixes it.


Cheers,

Simon.





> 
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Simon Kelley]

Update: I missed a case.


Simon.




thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=12af2b171de0d678d98583e2190789e50e02

On 22/01/2021 17:47, Simon Kelley wrote:
> On 22/01/2021 16:08, Hannu Nyman wrote:
>> I bisected the dnsmasq commits, and looks like it is caused by this:
>>
>> 15b60ddf935a531269bb8c68198de012a4967156  FAIL
>> 824461192ca5098043f9ca4ddeba7df1f65b30ba  Ok ?
>>
>> http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=15b60ddf935a531269bb8c68198de012a4967156
>>
>>
>> "Handle multiple identical near simultaneous DNS queries better."'
>>
>> Dnsmasq built from earlier commits seem to avoid the error/warning
>> messages, while builds after 15b60ddf cause log spam.
>>
>>
>> This bug is seen by lots of OpenWrt users, based on OpenWrt forum
>> discussion.  E.g. onward from
>> https://forum.openwrt.org/t/security-advisory-2021-01-19-1-dnsmasq-multiple-vulnerabilities/85903/22
>>
>>
>> One observation in the forum discussion is that this is only/mainly seen
>> when then are Windows PCs or Macs active in LAN. IPv6 RA/DHCPv6 may also
>> play a role.
>>
>>
> 
> I think this is the solution.
> 
> http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=04490bf622ac84891aad6f2dd2edf83725decdee
> 
> 
> You've found the right commit, and it looks like if two queries are
> combined (because they ask the same question) then dnsmasq can get
> confused when it comes to return the answer, the reply to the second
> query can be sent via the socket that the first one arrived on. That's
> normally OK, but if the first query arrives via IPv4 and the second via
> IPv6, for instance, then the bug is triggered. Hence the mentions of
> IPv6 in this thread.
> 
> This is an example of the risk of doing security fixes in secret before
> public disclosure, I'm sure a beta release would have found this.
> 
> Thanks for the effort taken chasing this. Please apply the patch above
> and see if it fixes it.
> 
> 
> Cheers,
> 
> Simon.
> 
> 
> 
> 
> 
>>
>> ___
>> Dnsmasq-discuss mailing list
>> Dnsmasq-discuss@lists.thekelleys.org.uk
>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Hannu Nyman]

Please apply the patch above and see if it fixes it.


Sorry, but no.

There is a new error: "failed to send packet: Not a socket"


Fri Jan 22 19:54:33 2021 daemon.info dnsmasq[11495]: started, version 2.84test1 
cachesize 1000
Fri Jan 22 19:54:33 2021 daemon.info dnsmasq[11495]: DNS service limited to 
local subnets
Fri Jan 22 19:54:33 2021 daemon.info dnsmasq[11495]: compile time options: IPv6 
GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack 
no-ipset no-auth no-nettlehash no-DNSSEC no-ID loop-detect inotify dumpfile
...
Fri Jan 22 19:54:33 2021 daemon.info dnsmasq-dhcp[11495]: read /etc/ethers - 0 
addresses
Fri Jan 22 19:54:34 2021 daemon.err dnsmasq[11495]: failed to send packet: Not 
a socket
Fri Jan 22 19:54:53 2021 daemon.err dnsmasq[11495]: failed to send packet: Not 
a socket
Fri Jan 22 19:54:53 2021 daemon.err dnsmasq[11495]: failed to send packet: Not 
a socket


I think that Kevin D-B has also reported the same finding to you, in parallel.


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Hannu Nyman]

> Update: I missed a case.


Possibly also something else.

With 2.84test2, there are now three different errors:


Fri Jan 22 20:32:49 2021 daemon.info dnsmasq[12040]: started, version 
2.84test2 cachesize 1000

...
Fri Jan 22 20:32:49 2021 daemon.info dnsmasq[12040]: read 
/tmp/hosts/dhcp.cfg01411c - 2 addresses
Fri Jan 22 20:32:49 2021 daemon.info dnsmasq-dhcp[12040]: read /etc/ethers - 
0 addresses
Fri Jan 22 20:32:50 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Address family not supported by protocol
Fri Jan 22 20:32:50 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Not a socket
Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Address family not supported by protocol
Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Not a socket
Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Address family not supported by protocol
Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Not a socket
Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Address family not supported by protocol
Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Not a socket
Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send packet: 
Network unreachable




___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Simon Kelley]

Apolgies about your wasted time. Once more with 2.84test3 ?


Cheers,

Simon

On 22/01/2021 18:37, Hannu Nyman wrote:
>> Update: I missed a case.
> 
> 
> Possibly also something else.
> 
> With 2.84test2, there are now three different errors:
> 
> 
> Fri Jan 22 20:32:49 2021 daemon.info dnsmasq[12040]: started, version
> 2.84test2 cachesize 1000
> ...
> Fri Jan 22 20:32:49 2021 daemon.info dnsmasq[12040]: read
> /tmp/hosts/dhcp.cfg01411c - 2 addresses
> Fri Jan 22 20:32:49 2021 daemon.info dnsmasq-dhcp[12040]: read
> /etc/ethers - 0 addresses
> Fri Jan 22 20:32:50 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:32:50 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Network unreachable
> 
> 
> 
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] "multiple MAC addresses in a single dhcp-host" vs "multiple dhcp-host lines with the same IP address"

[Jaime]

On Fri, 22 Jan 2021 at 16:38, Simon Kelley  wrote:
> Typically it's a
> laptop which downs its wireless interface and brings up the wired
> interface when docked.

That's exactly my use-case. Thank you very much for the explanation -
it's very much appreciated.

Best wishes, Jaime

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Steve Hirsch]

I’ve applied test1, test2, and test3 patches.  So far, no “failed to send” log 
messages and everything appears to be working normally on Arch Linux (kernel 
5.10.9). Thanks, Simon!

P.S.  Thanks for all of your work on this software!

From: Simon Kelley
Sent: Friday, January 22, 2021 3:48 PM
To: 
dnsmasq-discuss@lists.thekelleys.org.uk
Subject: Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is 
unreachable

Apolgies about your wasted time. Once more with 2.84test3 ?


Cheers,

Simon

On 22/01/2021 18:37, Hannu Nyman wrote:
>> Update: I missed a case.
>
>
> Possibly also something else.
>
> With 2.84test2, there are now three different errors:
>
>
> Fri Jan 22 20:32:49 2021 daemon.info dnsmasq[12040]: started, version
> 2.84test2 cachesize 1000
> ...
> Fri Jan 22 20:32:49 2021 daemon.info dnsmasq[12040]: read
> /tmp/hosts/dhcp.cfg01411c - 2 addresses
> Fri Jan 22 20:32:49 2021 daemon.info dnsmasq-dhcp[12040]: read
> /etc/ethers - 0 addresses
> Fri Jan 22 20:32:50 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:32:50 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Address family not supported by protocol
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Not a socket
> Fri Jan 22 20:33:08 2021 daemon.err dnsmasq[12040]: failed to send
> packet: Network unreachable
>
>
>
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.83 failed to send packet: Network is unreachable

[Lonnie Abelbeck]

> On Jan 22, 2021, at 4:33 PM, Simon Kelley  wrote:
> 
> Apolgies about your wasted time. Once more with 2.84test3 ?

Thanks Simon, 2.84test3 solves all "failed to send packet" logs in my testing 
...
--
Jan 22 18:44:22 gw-lan daemon.info dnsmasq[3297]: started, version 2.84test3 
cachesize 4096
Jan 22 18:44:22 gw-lan daemon.info dnsmasq[3297]: compile time options: IPv6 
GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack 
ipset auth no-nettlehash no-DNSSEC loop-detect inotify no-dumpfile
--

Thanks for the prompt fix!

Lonnie


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss