microsoft / SDN

This repo includes PowerShell scripts and VMM service templates for setting up the Microsoft Software Defined Networking (SDN) Stack using Windows Server 2016
Other
487 stars 541 forks source link

new-hsnnetwork / wireguard - An adapter was not found. #532

Open albertkohl-monotek opened 2 years ago

albertkohl-monotek commented 2 years ago

Hello, i'm trying to add a windows node to a working k8s multi-cloud cluster. my current linux nodes all work over a wireguard vpn, on bare-metal ubuntu boxes. while trying to add the windows node my main issue seems to be that i cannot create HnsNetworks on the vpn interface.

the wireguard ip is: 10.0.0.8, the ethernet interface is 192.168.3.122 Invoke-HNSRequest Method[POST] Path[/networks] Data[{ "Subnets": [ { "GatewayAddress": "192.168.255.1", "Policies": [ { "Type": "VSID", "VSID": 9999 } ], "AddressPrefix": "192.168.255.0/30" } ], "NetworkAdapterName": "wg0", "Name": "External", "Type": "Overlay" }]

any pointers would be helpful. Thanks!

virtualmo commented 2 years ago

Facing the same issue when trying to create an overlay network, and the server is using NIC teaming with more than one interface.

PS C:\usr\local\bin> $JsonString='{"Name":"External","Type":"Overlay","Subnets":[{"AddressPrefix":"192.168.255.0/30","GatewayAddress":"192.168.255.1","Policies":[{"Type":"VSID","VSID":9999}]}]}'
PS C:\usr\local\bin> Invoke-HnsRequest -Method POST -Type networks -Data $JsonString
Invoke-HnsRequest : @{Success=False; Error=An adapter was not found. }
At line:1 char:1
+ Invoke-HnsRequest -Method POST -Type networks -Data $JsonString
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-HNSRequest

I face this only when there is more than one interface on the NIC team

PS C:\var> Get-NetLbfoTeam

Name                   : Prod
Members                : {NIC2, NIC1}
TeamNics               : Prod
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : Dynamic
Status                 : Up

With one interface NIC Team, the issue is not seen. Is there any setting for HSN when using NIC teaming?