WSL2 mirrored networking fails with Fortinet VPN-V IP-media adapter: ARP unresolved, TCP SYN dropped by Hyper-V (Unauthorized MAC)

Open
#42,013 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, linux
Domain
networking

Research direction

Start by comparing this report with related issue #41443 and trace how WSL mirrored networking handles Windows adapters reported as MediaType: IP. The report provides packet captures showing failed ARP resolution and Hyper-V Unauthorized MAC drops, but does not identify a WSL file, test, or confirmed owner for the fix. Done means establishing whether this adapter type is supported and identifying a safe fix or supported workaround.

Written by the indexing model from the issue text.

Description

emailed-logs network wsl2
Windows Version

Microsoft Windows [Version 10.0.26200.9711]

WSL Version

2.7.13.0

Are you using WSL 1, WSL 2, or WSLC?
  • WSL 2
  • WSL 1
  • WSLC
Kernel Version

6.18.33.2-2

Distro Version

Ubuntu 24.04.4

Other Software

FortiClient 7.4.8.2066

Repro Steps
  1. Configure WSL2 mirrored networking.

  2. Connect a Fortinet VPN on the Windows host.

  3. Confirm that a private HTTPS endpoint is reachable from Windows through the VPN.

  4. Start WSL and identify the mirrored Fortinet interface. Its Linux interface name may change between VPN reconnections or WSL restarts.

  5. Verify the route and neighbor state:

    ip -4 route get <PRIVATE_SERVER_IP>
    ip neigh show
    
  6. Capture traffic on the mirrored VPN interface:

    sudo tcpdump -ni <VPN_INTERFACE> -e \
      'arp or (host <PRIVATE_SERVER_IP> and tcp port 443)'
    
  7. Attempt a TCP connection:

    curl -4 -vk --noproxy '*' \
      --interface <VPN_INTERFACE> \
      --connect-timeout 5 \
      https://<PRIVATE_SERVER_IP>/
    
Expected Behavior

The private HTTPS endpoint should be reachable from WSL through the VPN, just as it is from the Windows host.

Actual Behavior

The connection times out because the VPN gateway cannot be resolved through ARP.

Diagnostic Logs

WSL2 in networkingMode=mirrored cannot access private networks through a Fortinet VPN-V adapter, although the same destinations are reachable from the Windows host.

Packet captures reveal two failure modes:

  1. Normal ARP enabled: WSL repeatedly sends ARP requests for the VPN gateway, but receives no replies. Neighbor resolution fails, preventing TCP SYN transmission.
  2. ARP disabled (NOARP): WSL generates TCP SYN packets, but Windows Packet Monitor records DropReason Unauthorized MAC at a Hyper-V virtual-switch component (VmsVmNic, vmswitch.sys).

The Fortinet VPN adapter is reported as MediaType: IP on Windows but is exposed as an Ethernet (link/ether) interface inside WSL.

WSL NAT networking works with the same VPN. Mirrored networking works when the VPN is disconnected.

1. Windows reports an IP-media VPN adapter

PowerShell:

Get-NetAdapter |
    Where-Object InterfaceDescription -Like '*Fortinet VPN-V*' |
    Format-List InterfaceDescription, MediaType,
                PhysicalMediaType, Status

Output (environment-specific values omitted):

InterfaceDescription : Fortinet VPN-V Network Adapter
MediaType            : IP
PhysicalMediaType    : Unspecified
Status               : Up

The Windows neighbor table shows the VPN gateway with an all-zero link-layer address:

IPAddress          LinkLayerAddress       State
---------          ----------------       ---------
<VPN_GATEWAY_IP>   00-00-00-00-00-00     Reachable

This is consistent with the VPN adapter not using conventional Ethernet gateway resolution.

2. WSL exposes the adapter as Ethernet
ip -d link show dev <VPN_INTERFACE>

Relevant output:

<VPN_INTERFACE>: <BROADCAST,MULTICAST,UP,LOWER_UP>
    mtu 1280
    link/ether <VPN_ADAPTER_MAC>
    parentbus vmbus

The route points to the correct VPN interface:

<PRIVATE_SERVER_IP> via <VPN_GATEWAY_IP>
    dev <VPN_INTERFACE>
    src <VPN_CLIENT_IP>

However, the gateway neighbor entry fails:

<VPN_GATEWAY_IP> FAILED
3. Normal operation fails during ARP resolution

WSL tcpdump output, with addresses redacted:

<VPN_ADAPTER_MAC> > ff:ff:ff:ff:ff:ff, ARP:
Request who-has <VPN_GATEWAY_IP> tell <VPN_CLIENT_IP>

<VPN_ADAPTER_MAC> > ff:ff:ff:ff:ff:ff, ARP:
Request who-has <VPN_GATEWAY_IP> tell <VPN_CLIENT_IP>

<VPN_ADAPTER_MAC> > ff:ff:ff:ff:ff:ff, ARP:
Request who-has <VPN_GATEWAY_IP> tell <VPN_CLIENT_IP>

No ARP reply is observed. The neighbor state becomes FAILED, and no TCP SYN is transmitted.

4. Disabling ARP allows TCP SYN transmission, but Hyper-V drops the frames

As a temporary diagnostic experiment, ARP was disabled on the mirrored VPN interface:

sudo ip link set dev <VPN_INTERFACE> arp off

The interface then reports:

<BROADCAST,MULTICAST,NOARP,UP,LOWER_UP>

WSL generates TCP SYN packets, but the Ethernet source and destination MAC addresses are identical:

<VPN_ADAPTER_MAC> > <VPN_ADAPTER_MAC>
<VPN_CLIENT_IP>.<EPHEMERAL_PORT> >
    <PRIVATE_SERVER_IP>.443: Flags [S]

The connection still times out.

Windows Packet Monitor was used to trace these packets:

pktmon filter remove

pktmon filter add WSLCorporate `
    -i <PRIVATE_SERVER_IP> -t TCP -p 443

pktmon start --capture --pkt-size 0 `
    --file-name C:\Temp\NoArp.etl

# Reproduce the TCP connection timeout inside WSL.

pktmon stop

pktmon format C:\Temp\NoArp.etl `
    -o C:\Temp\NoArp.txt

Relevant Packet Monitor output, with network identifiers redacted:

Drop:
  Direction Ingress
  Type Ethernet
  Component 680
  DropReason Unauthorized MAC
  DropLocation 0xE0002019
  OriginalSize 74
  LoggedSize 74

<VPN_ADAPTER_MAC> > <VPN_ADAPTER_MAC>
<VPN_CLIENT_IP>.<EPHEMERAL_PORT> >
    <PRIVATE_SERVER_IP>.443: Flags [S]

The same drop repeats for subsequent TCP SYN retransmissions.

The component was identified in the trace as:

Component 680
Type VmsVmNic
Name vmswitch.sys
VmsExtIfIndex = 72
VMSwitchName = <VIRTUAL_SWITCH_NAME>

This confirms that the TCP SYN packets produced under NOARP reach the Hyper-V virtual-switch path and are rejected with Unauthorized MAC.

A separate diagnostic experiment using a static neighbor entry pointing to the VPN adapter's own MAC produced the same drop reason. That MAC was not verified as a valid gateway MAC, so the static-neighbor result should not be interpreted as evidence that an ordinary, correctly addressed Ethernet frame would also be rejected.

The original failure occurs earlier, during gateway ARP resolution. The NOARP test demonstrates what happens when that stage is bypassed.

ARP was restored after testing:

sudo ip link set dev <VPN_INTERFACE> arp on
sudo ip neigh flush dev <VPN_INTERFACE>

Suspected cause

There appears to be a compatibility issue between WSL mirrored networking and Windows VPN adapters that use MediaType: IP rather than conventional Ethernet link semantics.

Windows handles the Fortinet VPN adapter as an IP-media interface, while WSL mirrors it as an Ethernet interface requiring neighbor resolution.

Under normal operation, ARP resolution fails. Disabling ARP allows Linux to generate TCP SYN packets, but the resulting Ethernet frames are rejected by the Hyper-V virtual-switch path.

The evidence establishes these failure points, but does not conclusively identify whether the required fix belongs in WSL, Hyper-V, or Fortinet's adapter implementation.

Questions for maintainers

  1. Is mirroring Windows MediaType: IP VPN adapters as Linux Ethernet interfaces supported?
  2. Should WSL provide special neighbor-resolution handling for IP-only or point-to-point VPN adapters?
  3. Is vmswitch.sys rejecting these NOARP-generated frames with Unauthorized MAC expected behavior?
  4. Is there a supported workaround that preserves mirrored networking without disabling virtual-switch security protections?

Workaround

Switching WSL to NAT networking restores access to private destinations through the Fortinet VPN.

Possibly related issue

  • #41443 — Mirrored networking: reply from TUN-based VPN adapter dropped before reaching WSL vNIC

That issue involves a different VPN client and packet direction, but may be related to how mirrored networking handles non-Ethernet VPN adapters.

Dominant language
C++
Stars
34.4k
Forks
1.9k
Avg merge
1d 23h
Merged PRs (30d)
166

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/WSL

All issues in microsoft/WSL

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.