-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LLM-based Honeypots issues #1729
Comments
Please check your Ollama setup / settings, i.e.: It seems there is a communication issue between the containers and your Ollama installation, otherwise our installations work perfectly fine. Also I recommend using the default models from the |
Thanks for this Beelzebub settings typo. What is your Ollama setup for your tests ? Ok for testing default .env before. |
On the testing environment we are using the Ollama docker image with GPU support, running on a separate instance with a FQDN and on port |
Just noticed, you cannot use |
Thanks that work. I'm going to try ollama on another instance instead of tpot itself etc. Thanks for your quick responses. |
Introduction
Hello, I encounter issues with Beelzebub and Galah.
I don't know yet if they are mistakes on my side, Tpot bug or both.
root
)We happily take the time to improve T-Pot and take care of things, but we need you to take the time to create an issue that provides us with all the information we need.
Ubuntu Server
lsb_release -a
anduname -a
?Linux host 6.8.0-51-generic 52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
24.04.1
Virtualbox
Yes, let's start with the setup :
Env
Ollama
Running with llama3.2 model at the moment. Here is the classic docker-compose I use :
Tpot Docker-compose
Except the comments on read-only for debug purposes. I have the default config :
Galah
Beelzebub
Issues
Beelzebub
Steps to reproduce
Ollama Docker logs
Questions
I don't understand why this log line :
{"level":"error","msg":"Error ExecuteModel: ls, Post \"http://localhost:11434/api/chat\": dial tcp [::1]:11434: connect: connection refused","timestamp":"2025-01-07T09:10:11Z"}
I can reach the ollama endpoint like show in the steps to reproduce part. And I can ssh / interact with beelzebub.
Galah
Steps to reproduce
Galah Docker debug
Galah Docker network
Questions
I don't understand the reverse DNS lookup fail with Docker internal DNS. Here :
time="2025-01-07T09:51:26Z" level=error msg="error getting enrichment info for \"192.168.80.1\": lookup 1.80.168.192.in-addr.arpa. on 127.0.0.11:53: no such host"
By the way, we can spot a TLS handshake error :
2025/01/07 09:51:31 http: TLS handshake error from 192.168.80.1:53132: local error: tls: bad record MAC
Since is recent from the lastc45cda4f7091b84170319feb6d54a787dcd9a182
commit, I don't dig on it yet.Conclusion
Thanks for your work.
Feel free to ask if you need more informations.
Cheers.
The text was updated successfully, but these errors were encountered: