Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
albertkohl-monotek opened this issue Aug 25, 2022 · 1 comment
Open

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

albertkohl-monotek opened this issue Aug 25, 2022 · 1 comment

Comments

@albertkohl-monotek
Copy link

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
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants