Activating conpot_default on NextGen installation

[UncleRaymondo]

M,

Just rebuilt the box here with your latest and greatest 😄

Used the NextGen install. Is there anyway we can get conpot_default to turn on with it as well, as I don't see S7Comm, Modbus, or Bacnet ports appearing in dps.sh

I've got a client presentation next week and wouldn't mind showing them the dashboard with an attack or two on those protocols (alongside all the others!)

Cheers,
R

[t3chn0m4g3]

Yes, if you take care of the port conflicts for the other services you just need to copy and paste from industrial.yml.
You can test with docker-compose -f nextgen.yml up to see if any port conflicts are present.

Hope that helps 😄

Cheers,
M.

[UncleRaymondo]

Cool - I've copied the Conpot Default from /opt/tpot/etc/compose/industrial.yml to /opt/tpot/etc/compose/nextgen.yml and commented out any conflicting ports (so that only s7comm, modbus and bacnet are running on this service)

If I try docker-compose -f nextgen.yml up I now get this error

Running docker network ls shows the following

Not sure why these ones are appearing as compose_* and the original ones are etc_* - am I modifying an incorrect file?

Any ideas what I'm doing wrong?

Cheers,
R

[UncleRaymondo]

Never mind M.... it would help if I actually stopped and restarted the tpot service before and after the changes facepalm

Going to try and split up that default one into 3 different services so it shows conpot_s7comm, conpot_modbus, conput_bacnet...

Cheers,
R

[UncleRaymondo]

Ok the split worked :)

now to try and attack the protocols and see what appears on the dashboard

Cheers,
R

[t3chn0m4g3]

Perfect, great it is working!

Cheers,
M.