Artem Glazychev

Thanks for the detailed information! Most likely yes, it is related to OPA for monitoring. But it is not actually an error if you are not using init-container (cmd-nsc-init). We...

@edwarnicke [cmd-nsc](https://github.com/networkservicemesh/cmd-nsc) does [Monitor connections](https://github.com/networkservicemesh/cmd-nsc/blob/main/main.go#L253) before the Request. This is necessary to take the connection if there was cmd-nsc-init container before. But as you know, you've implemented an open-policy for...

@bilgehan-erman Sorry to keep you waiting I looked at your setup and logs, and I think I understand what's going on. The main reason is that the NSC is trying...

For `sdk` `sandbox` tests we can iterate over all combinations. But for `integration tests` it would be too wasteful. I would suggest using some of the most illustrative ones. **Integration...

@edwarnicke What do you think about this list? https://github.com/networkservicemesh/sdk/issues/1196#issuecomment-993238554

@edwarnicke @denis-tingaikin Any thoughts?

@edwarnicke Yes, the first way is correct. And also the fact that Request.Connection.ConnectionContext.IPContext.DstIP also contains two addresses - 172.16.1.0 (before healing) and 172.16.1.2 (after healing). But 172.16.1.0 is already wrong...

@edwarnicke You are right. Maybe we should at least **_try_** to recover the addresses? The logic could be like this: **1**. NSE has a couple of IPAMs: ``` ipv4IPAM -...

@edwarnicke Additional question: Do we understand correctly that the IP addresses for the client and endpoint **_should not_** change? What if, for example, healing with `reselect`?

@edwarnicke > I suspect the best answer for our current point2pointipam would be to simply compare any existing IP in the chain to the prefixes from which its issuing IPs....