IPv6 VLAN behaves different than IPv4 VLAN

[nachtfuchs]

Hi! I am using VLAN and observe the following:

• If I use IPv4, addresses then service discovery uses the VLAN ID when it sends its message.
• If I use IPv6, addresses then service discovery does NOT use the VLAN ID when it sends its message. This is a bug I guess!
• Why is it a bug? If I use a device that uses a different SOME/IP stack then vsomeip, then no communication between these two devices! Happened for me with a embedded device.
• Note: communication between two nodes with vsomeip stack still works, because they have the "same bug".

My setup:

• I use Wireshark to observe the ethernet communication
• I have two Debian nodes that are connected to each other using a switch.

I tried to upload my wireshark screenshots, but with not success. Sorry about that.

[nachtfuchs]

So I found the "bug", but do not know how to solve it, yet. The problem is that https://github.com/COVESA/vsomeip/blob/3230caf9a1aad7a9d5870e01598aa87c2be782de/implementation/endpoints/src/udp_server_endpoint_impl.cpp#L94C19-L94C20 uses always the default "scope_id", which is zero. So VLAN cannot work for all ethernet configurations. The actual "outbound_interface" of the configured unicast address (in json-file) is NOT used.

Any ideas how to determine the correct outbound_interface respectively scope_id?

[nachtfuchs]

It's a bug! VLAN does NOT work correctly in IPv6 with vsomeip 3.3.8.
Created a pull-request #553

[fcmonteiro]

Please update your PR. Thanks