No HNSNetwork created when Wi-Fi is on

No HNSNetwork can be created if Wi-Fi is enabled when trying to add a Windows Node to a K8s cluster.

Expected Behavior

If Wi-Fi is on then a HNSNetwork of type "L2Bridge" gets created.

Current Behavior

If a LAN cable is used and Wi-Fi is off, then a HNSNetwork of type "L2Bridge" can be created by flanneld. But if Wi-Fi is on, then no HNSNetwork of type "L2Bridge" gets created.

Possible Solution

n.a.

Steps to Reproduce (for bugs)

1. Use a single machine having "Windows 10 Enterprise" 20H2, OS Build: 19042.1826 installed.
2. Set up a Linux Virtual Machine (Debian 11) as the K8s cluster control-plane in Hyper-V
3. Add the Windows host as a K8s cluster worker node

Details on the node network:

• Master node (LinuxVM): 172.17.1.100
• Windows host: 172.17.1.1

Details on the IP addresses used by my network adapters:

• Physical ethernet adapter for LAN cable: 192.168.178.59
• Wireless LAN adapter Wi-Fi: 192.168.178.80

Details on the l2bridge configuration: flannel-l2bridge.pdf Note:

• when I use "192.168.178.59" --> it works
• when I use "192.168.178.80" --> it doesn't work
• even when "192.168.178.59" is used and Wireless LAN adapter Wi-Fi is on --> it doesn't work.

Used Flanneld arguments:

• "flanneld.exe --kubeconfig-file=/syngoK8s/config --iface=192.168.178.59 --ip-masq=1 --kube-subnet-mgr=1" --> it works
• "flanneld.exe --kubeconfig-file=/syngoK8s/config --iface=192.168.178.80 --ip-masq=1 --kube-subnet-mgr=1" --> it doesn't work

Context

As a developer I want to have a 2 nodes cluster running on my laptop. The master node is a Linux VM running in Hyper-V. The worker node is my Windows host machine. The Linux VM can also get worker pods scheduled. Having this cluster setup I'll be able to develop and test Linux and Windows containers on my laptop.

Your Environment

• Flannel version: v0.17.0-1-gbf9dbdb0
• Backend used (e.g. vxlan or udp):
• Etcd version:
• Kubernetes version (if used): v1.24.2
• Operating System and version: "Windows 10 Enterprise" 20H2, OS Build: 19042.1826
• Link to your project (optional):

flanneld output - WiFi.pdf

flanneld output - LAN cable.pdf

I checked the logs I am not so in depth with windows. Did you try the first setup that works and then the second setup or it wasn't working from the beginning? The parameters on both seems to be the same but the error seems to be related to them. It's probably related to the hnsCall I don't know if it fails for the wifi driver.

Thank you for your reply! Regarding to your question: it wasn't working from the beginning. I stripped down the implementation to find out the call that is causing the problem. It is indeed the hnsCall that is not working when Wi-Fi is enabled. For this I've also created an issue (https://github.com/microsoft/hcsshim/issues/1477), for which I haven't received any answer until now. If you have time it would be very helpful if you can try the hnsCall in isolation on your machine by following the steps described in the issue mentioned above and provide me feedback.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.