Ok … Safeguard added. >From now on, if you reference a transport that’s not listed as supported, the >connection will fail with an exception mentioning this. However there’s now >also a:
allow-unsupported-transport Option, that allows you to disable this safeguard, if it’s required. Chris Von: Sebastian Rühl <[email protected]> Datum: Montag, 22. Juni 2026 um 10:27 An: [email protected] <[email protected]> Betreff: Re: [DISCUSS] Enforcing only use of supported transports? SGTM - Sebastian On 2026/06/20 10:35:34 Christofer Dutz wrote: > Hi all, > > Just tried out something regarding the bug andvasp reported ... and yeah … > this might be worth investigating: > > In the past the S7 driver used tcp as transport, but the new one is using > cotp (which more correctly modells the reality). However, you can still make > PLC4X use the TCP transport. If you do, it's missing the whole ISO on TCP and > TPKT stuff and obviously fails. > In the past we intentionally allowed to use any transport with any driver. > With SPI3 I've made things a bit more explicit. However, we don't prevent > people from using transports a driver was not designed for. > > Now my idea would be that we throw an exception if a user tries to use a > transport that isn't listed in the "supported" transport list. But add a flag > to the connection options to forcefully disable this check if someone was to > explicitly want to use a transport that's not supported. But with this it > would have to be an explicit decision of the user. > > What do you think? > > Chris > > >
