why E2E Profile 4 and Profile 5 can only be used for instances [1-255]"

COVESA / vsomeip

An implementation of Scalable service-Oriented MiddlewarE over IP

Mozilla Public License 2.0

1.12k stars 697 forks source link

why E2E Profile 4 and Profile 5 can only be used for instances [1-255]" #805

Open GHARBIAchref opened 5 days ago

GHARBIAchref commented 5 days ago

vSomeip Version

v3.4.10

Boost Version

1.83

Environment

windows 10

Describe the bug

why E2E Profile 4 and Profile 5 can only be used for instances ### [1-255]" VSOMEIP_ERROR << "E2E Profile 4 can only be used for instances [1-255]";

Reproduction Steps

No response

Expected behaviour

No response

Logs and Screenshots

No response

duartenfonseca commented 5 days ago

do you have reproduction steps for the error?

GHARBIAchref commented 5 days ago

Hello, @duartenfonseca e2e_instance When I try to apply the protection mechanism of profile 04 to a service that has an instance >255 , this error message appears, and the protection Profile 04 does not apply.

duartenfonseca commented 4 days ago

do you have an instance value bigger than 255? vsomeip-lib/implementation/e2e_protection/src/e2e/profile/profile04/checker.cpp::24

GHARBIAchref commented 4 days ago

@duartenfonseca
Hello , yes, my application has an instance value greater than 255. Is it possible to apply the E2E P04 fetcher in this application?

duartenfonseca commented 4 days ago

i don't think it is possible. this was the way it was implemented. maybe you can try to use profile 7 or profile 1 which do not have that check.