<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">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.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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).</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>