Hi Julian, Initially I didn't add the replay/passive stuff in the normal driver as this adds dependencies to pcap4j. But thinking about it more recently I noticed, that the only problematic part is the libpcap dependency when using passive mode. When not using that, I think the drivers don't care if that library is installed (we should check this tough). If you can still use the driver without having to install libpcap, I'm fine with that. I was even thinking of adding general support to enable pcap recording via connection string properties so users with problems could simply turn this on and send us the pcap files in jira issues.
Chris Am 07.01.20, 14:37 schrieb "Julian Feinauer" <[email protected]>: Hi Chris, I could (and should, I guess) help you with the integration oft he replay stuff, as I kind of caused it, partly. I would like to have the replay in "regular" mode and ideally also over tcp so that we see the full stack (leak issues) in action. Julian Am 07.01.20, 14:23 schrieb "Christofer Dutz" <[email protected]>: Hi all, I am currently working on ways that I could for example simply replay Cesars pcap files. While with the old drivers this was quite simple, as I simply dind’t create a Driver, but a Connection instead and passed in the transport. Now things have become a little more complicated for me … I think I sort of have to be able to switch on the connection string base. I think we already have this issue with modbus, where there’s a TCP and a Serial transport available. What do you all think ... * if I write "s7://1.2.3.4" it uses TCP ... * if I write "s7:tcp://1.2.3.4" is uses TCP too ... * if I write s7:passive://1.2.3.4" is uses passive mode and listens on the device which would communicate with the host on 1.2.3.4 ... * if I write "s7:pcap:///path/to/pcap/file.pcapng" it simply plays back a pcap file? * If I write “s7:serial:///dev/ttyS0 it would use the serial port ttyS0 (which wouldn’t make sense in a S7 environment but I added it for the sake of completeness) 2:17 PM<https://the-asf.slack.com/archives/CCGG7NTEE/p1578403078003400> So in general a protocol has a default transport which is used if an explicit transport is omitted. If it is provided, that transport is used ... Chris
