Repository navigation
Connecting via Gateway does not work due to Address Validation #75
Description
When not directly connecting to an ECU but going through a gateway, the check introduced in #68 now fails. For example, I connect to IP 192.168.1.1 and its routing activation response contains diagnostic address 0x10. However, I want to connect to an ECU behind this gateway, let's say with diagnostic address 0x40. In the past I simply use 0x40 in the DoIPClient but this obviously now fails. What is the intention here? I think it is a valid use-case we should support?
Activity
jacobschaer commentedon Aug 9, 2026
@1ozZ - ideas? If you have something you think will help for this use case drop an MR.
1ozZ commentedon Aug 10, 2026
@christophruethingbmw You are absolutely right. The check introduced in #68 is indeed too strict for real-vehicle or gateway scenarios, where accessing a non-edge ECU will fail due to the logical address mismatch.
@jacobschaer Apologies for the broken code in my previous PR. I will submit a fix PR later today to address this issue.
christophruethingbmw commentedon Aug 10, 2026
@1ozZ , thank you very much for the quick fix :)