You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm observing a strange behavior with Conpot. I'm using docker compose with the below yml file. Everything works fine for the first 4 or 5 scans but i noticed after that, conpot logs become unresponsive and nmap scans fail to retrieve any data. Host is running 4 cpus with 16 gig of ram.
Also, I tried to set the timezone within the yml file to have the logs reflect the timezone of the host machine but it's not working.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I'm observing a strange behavior with Conpot. I'm using docker compose with the below yml file. Everything works fine for the first 4 or 5 scans but i noticed after that, conpot logs become unresponsive and nmap scans fail to retrieve any data. Host is running 4 cpus with 16 gig of ram.
Also, I tried to set the timezone within the yml file to have the logs reflect the timezone of the host machine but it's not working.
Any advices on these observations mentioned?
==========================
version: "3"
services:
conpot:
image: honeynet/conpot:latest
container_name: conpot_default
ports:
- 80:8800 #SCADA UI, http
- 102:10201 #S7Comm
- 502:5020 #Modbus
- 161:16100/udp #SNMP
- 47808:47808/udp #Bacnet
- 623:6230/udp #IPMI
- 21:2121 #FTP
- 69:6969/udp #TFTP
- 44818:44818 #EN/IP
network_mode: bridge
environment:
- PATH=$HOME/.local/bin:$PATH
- TZ=America/Toronto
- env TZ=America/Toronto
command: sh -c "/home/conpot/.local/bin/conpot -f --template default"
restart: always
networks: {}
Beta Was this translation helpful? Give feedback.
All reactions