Vulcan22 Posted December 25, 2019 Share Posted December 25, 2019 I am pulling my hair out, i can't seem to connect any Hak5 device to cloud C2. I have tried the Lan Turtle, WiFi Pineapple, Packet Squirrel and Signal Owl and none of them connect. I run... c2-2.1.2_community_amd64_windows -hostname c2 -sshport 80 and have tried many variations of this. At the moment I am running it on windows but I have tried running it on Kali Linux, a Raspberry Pi and a VPS. I download the device.config file and scp it to /etc/ and when I run C2CONNECT this happens... (I am using the Lan turtle in this example, but all the devices are similar). It seems to be connected, but on Cloud C2 it doesn't show up. I tried running it with a domain and in -https mode and that didn't do much. I don't have the slightest idea of what the problem is. I have tried running cloud C2 on different networks and different devices at different places and don't see how this is possible. I am obviously doing something wrong. If anyone can help me or has any advice on how I would go about fixing this it would be greatly appreciated XD. Link to comment Share on other sites More sharing options...
Irukandji Posted December 25, 2019 Share Posted December 25, 2019 They should show up. But I don't know how your network is setup. https://docs.hak5.org/hc/en-us/articles/360014295634-Adding-Devices-to-Cloud-C2 Link to comment Share on other sites More sharing options...
Vulcan22 Posted December 25, 2019 Author Share Posted December 25, 2019 1 hour ago, Jtyle6 said: They should show up. But I don't know how your network is setup. https://docs.hak5.org/hc/en-us/articles/360014295634-Adding-Devices-to-Cloud-C2 There isnt any setting I have to change like port forwarding or anything, is there? (and as far as i know my modem dosnt have a firewall) Link to comment Share on other sites More sharing options...
Void-Byte Posted December 27, 2019 Share Posted December 27, 2019 Hi Treebug, You really shoudn't be using port 80 for SSH as this port is used for HTTP. SSH is normally on port 22 (and for C2 2022). I would remove the "-sshport 80" and rerun your script. Your devices are trying to communicate via port 2022, but you're only listening on port 80, hence why C2 can't communicate and vice versa. Refer to my guide if you need a better understanding. Happy belated X-Mas! Best, VB Link to comment Share on other sites More sharing options...
Vulcan22 Posted December 27, 2019 Author Share Posted December 27, 2019 39 minutes ago, Void-Byte said: Hi Treebug, You really shoudn't be using port 80 for SSH as this port is used for HTTP. SSH is normally on port 22 (and for C2 2022). I would remove the "-sshport 80" and rerun your script. Your devices are trying to communicate via port 2022, but you're only listening on port 80, hence why C2 can't communicate and vice versa. Refer to my guide if you need a better understanding. Happy belated X-Mas! Best, VB Thanks, I ran this... c2-2.1.2_community_amd64_windows -hostname c2 and it was the same thing. I have tried many different commands but the devices just dont connect. I can access cloud C2 and login, but it just says its offline. Link to comment Share on other sites More sharing options...
Void-Byte Posted December 27, 2019 Share Posted December 27, 2019 Have you checked that port 22, 2022, and 80 are all open? If you're using https make sure port 443 is open as well. Link to comment Share on other sites More sharing options...
Irukandji Posted December 27, 2019 Share Posted December 27, 2019 3 hours ago, Void-Byte said: Have you checked that port 22, 2022, and 80 are all open? If you're using https make sure port 443 is open as well. Wait? Do you want him to show up on https://www.shodan.io/ Link to comment Share on other sites More sharing options...
Vulcan22 Posted December 27, 2019 Author Share Posted December 27, 2019 4 hours ago, Void-Byte said: Have you checked that port 22, 2022, and 80 are all open? If you're using https make sure port 443 is open as well. Yes port 2022, 22, 80 and 8080 are open, and I’m not using https Link to comment Share on other sites More sharing options...
Void-Byte Posted December 31, 2019 Share Posted December 31, 2019 Did you ensure that each device has been loaded with the AND updated to the most recent firmware? If so, I think your issue most likely is with how you're hosting, or is being blocked locally. Link to comment Share on other sites More sharing options...
Vulcan22 Posted January 2, 2020 Author Share Posted January 2, 2020 It is finally working, in the end the solution was pretty simple, I ran it on Linux... c2-2.1.2_community_linux_64 -hostname 192.168.48 Link to comment Share on other sites More sharing options...
(1).thumb.jpg.4f81ebabce95b949449cc15ac197722b.jpg)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.