telekom-security / tpotce

🍯 T-Pot - The All In One Multi Honeypot Platform 🐝
GNU General Public License v3.0
6.69k stars 1.07k forks source link

Attack Map Not Showing Attacks #1414

Closed bgao-pangeo closed 12 months ago

bgao-pangeo commented 1 year ago

Hi, we just installed the latest T-POT, we give it a public IP but put the T-POT in a DMZ behind Cisco ASA firewall. Everything works fine however the Attack Map seems to have an issue. it does not show the attack on map or the list, only the counter on the top changes. Every other T-POT function seems to be working fine just fine.

Here is some the standard information that I have gathered:

⚠️ Basic support information (commands are expected to run as root)

htop output: htop

bgao-pangeo commented 1 year ago

Something I forgot to mention just now. Friday of last week for reason that we don't know, the attack map showed attacks real-time. That was the only time that it showed anything for the 2 weeks that we had the system running. We don't believe the "not showing" was because there was no attack, as every T-POT sensor registered a lot of attacks everyday.

t3chn0m4g3 commented 12 months ago

Sorry, but I cannot reproduce that. Please check with Elasticvue or Kibana if all of your indices are in ok. Also check with docker logs <container name> if there are any specific errors that might help identifying the root cause.

bgao-pangeo commented 12 months ago

Hi Marco,

I installed two instances of T-POT, one works without issue; one that is behind a Cisco ASA firewall has this issue.

I've gone through everything and there was no error message.

For the Attack Map to work, is there certain port or filter needs to be turned on/off?

Thank you, Bo


From: Marco Ochse @.> Sent: Thursday, October 5, 2023 5:34 AM To: telekom-security/tpotce @.> Cc: Bo Gao @.>; Author @.> Subject: Re: [telekom-security/tpotce] Attack Map Not Showing Attacks (Issue #1414)

Sorry, but I cannot reproduce that. Please check with Elasticvue or Kibana if all of your indices are in ok. Also check with docker logs if there are any specific errors that might help identifying the root cause.

β€” Reply to this email directly, view it on GitHubhttps://github.com/telekom-security/tpotce/issues/1414#issuecomment-1748486157, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5WY2YUYNPMQZYNRP6N6GTLX5Z5JHAVCNFSM6AAAAAA5IDRG6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYGQ4DMMJVG4. You are receiving this because you authored the thread.Message ID: @.***>