Joseph Oravec

Based on my testing, it looks like vsomeip is vulnerable to a sequence: - TCP socket is open and operational - connection is severed == cable is cut, cable is...

I've opened draft pull request: - https://github.com/COVESA/vsomeip/pull/681 with the code-changes that I've applied locally to address this issue. Although sockets still "leak" the TCP keepalive with detect and close within...

> @joeyoravec is this ready to review or are you still working on this? I've left this in draft so it's clear that this is not ready for merge. Yes...

> @joeyoravec is this ready to review or are you still working on this? I've left this in draft so it's clear that this is not ready for merge. Yes...

We came up with 3 possible solutions; 1. eliminate the tce `restart()` call from `service_discovery_impl::handle_eventgroup_subscription_nack()`. It's not clear why this is required or how it would help 2. modify tce...

> @joeyoravec is this ready to review or are you still working on this? I've left this in draft so it's clear that this is not ready for merge. Yes...

I've opened draft pull requests: - #671 - #670 with the code-changes that I've applied locally to address this issue. I would appreciate any feedback on the approach.

I've updated the pull request for 3.4.x (but not 3.1.x) with an additional commit for a problem discovered in testing. I was getting this warning: ``` Received an unreliable vSomeIP...

See linked pull request with a proposed solution. After adding some debug prints, I concluded that it's possible for `is_sending_` to be true across `restart()` of a TCP client endpoint:...

I'm not too familiar with this example code, but I see it's registering for SAMPLE_EVENT_ID == 0x8778 which we can see in your log: ``` 1970-01-01 00:06:24.842109 [info] REGISTER EVENT(1277):...