Evgenii
Evgenii
Important! You can't run our netbird test in the environments with subnet 10.0.0.0/8, 192.168.0.0/24, 192.168.1.0/24. Because we use this subnets in test, tests just will failed, so make sure you...
I found a reason of this workaround If remove it `netbird` will create a following route ``` 192.168.91.223 192.168.91.91 UGHS em0 ``` And it means route everything to local IP....
This case broken ``` { name: "Should Not Add Route if overlaps with default gateway", prefix: netip.MustParsePrefix(defaultNexthop.IP.String() + "/31"), shouldAddRoute: false, }, ``` These workaround with returning only interface name...
To be able to properly check `TestAddExistAndRemoveRoute` `shouldAddRoute: false` cases I will try to replace unreliable logs-parsing-based test https://github.com/netbirdio/netbird/blob/4bbedb5193f13f1e033acd4657a9c4f41d048bde/client/internal/routemanager/systemops/systemops_generic_test.go#L256 with OpenTelemetry spans and attributes.
#2386 could also be a blocker. It's better to enable and fix the tests and any potential bugs before allowing people to easily install Netbird on production servers and risk...
I will prepare a PR
Need to test after we release new version.
> Can you please show an example how you use the HTTP client/protocol and the error you're seeing? I quickly went through the code and IMHO the protocol tries to...
Just try this by yourself, here is example of the handler which could demonstrate the problem ``` type processorMock struct { testName string eventDelay time.Duration processedEvents int32 mu sync.Mutex processedIDs...
I use **NATS** protocol. But it does not matter.