Open 573 opened 2 years ago
en_US locale for comparison:
Interface vEthernet (WSL) Parameters
----------------------------------------------
IfLuid : ethernet_32775
IfIndex : 44
State : connected
Metric : 5000
Link MTU : 1500 bytes
Reachable Time : 43500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 3
Site Prefix Length : 0
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : dhcp
Managed Address Configuration : enabled
Other Stateful Configuration : enabled
Weak Host Sends : disabled
Weak Host Receives : disabled
Use Automatic Metric : disabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
ECN capability : application
RA Based DNS Config (RFC 6106) : disabled
DHCP/Static IP coexistence : disabled
Impacted commands that are parsed:
netsh interface ipv4 show interfaces "vEthernet (WSL)"
netsh interface ipv4 show config "vEthernet (WSL)"
netsh interface ipv4 show route
Minimal changes needed without refactoring:
network/route_list.go
to remove the header by order instead of content ("Publish") in NewRouteList
network/iface.go
to search for index case-insensitively in retrieveID
network/iface.go
to search for IP address by pattern instead of label in retrieveIP
network/iface.go
to search for subnet prefix by pattern instead of label in retrieveIP
Ideally this would instead interact more directly in a manner similar to the WireGuard for Windows approach.
To run this service on systems where the locale is not en_US, all string occurences regarding
netsh
calls at least would have to be translated.To give an example: