-
Notifications
You must be signed in to change notification settings - Fork 24
Agent errors (interface is nil) #6
Comments
I didn't fully implement proper error handling on the Go networking component of the agent yet so it's difficult to tell. However, I suspect this error occurs when the agent was unable to reach the destination IP/URL for the C2 channel. Changing/setting the destination host via the UI is something I have planned for this thursday. You can validate what destination IP is used by the agent by checking the compiler logs. You can view these by using the following process:
The output should show all compilation attempts with the variables. As example:
The last piece specifies the URL the agent will attempt to reach. Does this match with the host your C2 container is running on? :) |
@devnullz The latest commit is still a concept, but you can change the destination at the top right whenever you want. Don't forget to compile the payloads via the UI again :) The adjusted C2 IP still temporary and stored inside your session until I think of a more suitable solution |
Closing the issue for now since the latest release implements payload creation in an updated manner. If the issue still occurs please re-open a ticket ^^ |
I have same issue after payload starting Error in output from compiler log after request from payload:
Reternal ip - 10.0.10.5 (I am running on Ubuntu 18.04, all docker containers are up.) Is there anything incorrect in there? or I failed something? |
@400notOK Hmm I think networking from the reternal-c2 container towards Redis or Mongo DB has a time-out (based on the conrurrent poll() error). Did you run the Ansible install or manual compose? :) |
I ran via docker compose manual. My docker-compose.yml:
|
@400notOK Hmm difficult to tell. I will be pushing an update this evening to (likely) fix most of the issues that I'm currently aware of + implement content encryption with key-exchange between the agent and C2 server. I would also suggest trying the Ansible installer even if its on localhost. Ansible will properly configure networking and provide some easier configuration with relays :) https://github.com/d3vzer0/reternal-quickstart/wiki/1.A-Ansible-Install-Guide |
When I tried ansible way 🙈, I got:
|
Strange, there should be a proper Ubuntu template for the 'generic' Ansible role available. Do you mind running and sharing the following details? :) This should help with finding out whats going on/why it can't find the Ubuntu template:
|
No problem) Ansible version:
Debug output
Contents of the host config:
|
Did you test ansible way behind proxy? |
Nope, but I'm going to test that now :) It seems a deployment with Vagrant is having similar issues. I'll test it out tomorrow and come with a fix ^^ |
Found the issue :) Ansible couldn't find the template file because in some cases the identified distro is seen as Ubuntu (capital U) or ubuntu (small u). In the first case Ansible couldn't find the template file since the file is named ubuntu.yml. Fixed the issue to make all distro versions lowercase and loading the template afterwards. |
agents errors on windows10x64 and windows7x64 OSs is same:
`panic: interface conversion: interface {} is nil, not []interface {}
goroutine 19 [running]:
main.StartPulse()
/reternal-agent/agent/src/corebeacon.go:73 +0x284
created by main.StartBeacon
/reternal-agent/agent/src/corebeacon.go:65 +0x3e`
The text was updated successfully, but these errors were encountered: