When using ipv6 and lokal link addresses, a mismatch due to the network devices inside the address object causes a mismatch in the connections map object. This causes:
`2024-03-26 17:31:56.700105 [info] Didn't find TCP connection: Subscription rejected for: fe80::5054:ff:fe12:3402:34049
2024-03-26 17:31:56.700360 [error] TCP connection to target1: [fe80::5054:ff:fe12:3402:34049] not established for subscription to: [012c.0004.0001]
Reproduction Steps
Use ipv6 with local link addresses and a someip service using reliable: true
vSomeip Version
v3.4.10
Boost Version
1.78
Environment
Embedded
Describe the bug
When using ipv6 and lokal link addresses, a mismatch due to the network devices inside the address object causes a mismatch in the connections map object. This causes: `2024-03-26 17:31:56.700105 [info] Didn't find TCP connection: Subscription rejected for: fe80::5054:ff:fe12:3402:34049 2024-03-26 17:31:56.700360 [error] TCP connection to target1: [fe80::5054:ff:fe12:3402:34049] not established for subscription to: [012c.0004.0001]
Reproduction Steps
Use ipv6 with local link addresses and a someip service using reliable: true
Expected behaviour
No connections issues.
Logs and Screenshots
No response