DNP3 support about conpot HOT 19 OPEN

Six years on, we're still in demand for DNP3, and the old branch is no longer usable.

from conpot.

I made some successful tests with the proxy module: https://github.com/glastopf/conpot/tree/dnp3_proxy

from conpot.

How can I help here? Is this doc up to date? https://github.com/glastopf/conpot/blob/dnp3_proxy/docs/source/components/protocols/dnp3.rst

from conpot.

The documentation should be up to date. Have a look at the decoder and how to extend it.

from conpot.

Let me know if you run into any problems or need some help.

from conpot.

I've just built and installed cverges' DNP3 fork successfully.

Is this right or do I need to install automatak's one?

Now I'll read something about DNP3 and then I'll have a look at the decoder in the dnp3_proxy branch.

from conpot.

I went straight to the automatak code and installed the samples, some instructions can be found here: https://github.com/mushorg/conpot/blob/dnp3_proxy/docs/source/components/protocols/dnp3.rst

from conpot.

Ok thanks I'll do.

from conpot.

Done, outstationdemo and masterdemo samples are running fine.

from conpot.

I have changed the outstations listening port to +=1 so conpot can listen on the default port and I didn't had to change the client. Let me know if you run into trouble merging master into the branch. And feel free to continue using that branch.

from conpot.

Just as a reminder to myself, I patched the source file /cpp/examples/outstation/DemoMain.cpp and changed 20000 to 20001.

from conpot.

This is helpful during development: http://www.automatak.com/opendnp3/decoder/

from conpot.

@adepasquale have you looked more into this?

from conpot.

Even if this might overlap with the DNP3 proxy branch, I'd like to code wireshark dissectors first. Then implement DNP3 only after I have better understood the protocol.

from conpot.

Sounds good to me. I might have a student interested in working on this after all. I still think writing a proper wrapper around automataks opendnp3 library would be pretty awesome...

from conpot.

Although my experience with swig is limited, I think auto generated python API is a little hackish - and may lead to unexpected behavior. I would instead suggest using Boost.python to write the wrapper for the handler.
This way the python API would be seamless to work with, since we know what we are getting into 😉
We can use automak's lib for writing the handler.

from conpot.

There has been promising updates on this 🙂 pydnp3

from conpot.

Any progress?
I am also planning to add dnp3 support in conpot.

from conpot.

Six years on, we're still in demand for DNP3, and the old branch is no longer usable.

You think you can help in any way?

from conpot.