From: Brad Spencer <bspencer@blackberry.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Wintun NeighborDiscoverySupported
Date: Thu, 9 Sep 2021 11:32:01 -0300 [thread overview]
Message-ID: <00042bf6-4e8c-8638-380d-6774b37f96c2@blackberry.com> (raw)
We have noticed that Windows seems to try to send ARP requests over
Wintun interfaces. In our configurations, these don't go anywhere and
get no responses, but the ARP table fills up with addresses. For example:
$ arp -a -N 10.0.0.100 |wc -l
387
Our Wintun interfaces are created with these properties:
PS C:\> Get-NetIPInterface -InterfaceIndex 69 |Select-Object -Property
AddressFamily,NeighborDiscoverySupported,NeighborUnreachabilityDetection |fl
AddressFamily : IPv6
NeighborDiscoverySupported : Yes
NeighborUnreachabilityDetection : Enabled
AddressFamily : IPv4
NeighborDiscoverySupported : Yes
NeighborUnreachabilityDetection : Enabled
We _think_ that the NeighborDiscoverySupported property being Yes means
that Windows issues ARP requests for addresses on the Wintun interface.
(The second property controls another neighbour behaviour that perhaps
could also be disabled for Wintun interfaces.)
Microsoft's documentation for SetIpInterfaceEntry() claims that these
properties are set "by the network stack", but offers no hint as to what
part of the network stack does this. It does not seem possible to
change these properties on an existing interface.
Are these properties that either the Wintun driver or user-space API is
able to control? Should they be set to No and Disabled? I don't see
any use of the driver variant of SetIpInterfaceEntry() or
MIB_IPINTERFACE_ROW in Wintun's driver or API code, so I'm not sure when
these properties get determined.
--
Brad Spencer
next reply other threads:[~2021-09-09 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 14:32 Brad Spencer [this message]
2021-09-09 17:42 ` Wintun NeighborDiscoverySupported Jason A. Donenfeld
2021-09-09 18:15 ` Brad Spencer
2021-09-09 20:23 ` Alan Graham
2021-09-10 17:19 ` Brad Spencer
2021-09-10 20:56 ` Alan Graham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00042bf6-4e8c-8638-380d-6774b37f96c2@blackberry.com \
--to=bspencer@blackberry.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).