Skip to content

Connecting problems #17

Open
Open

Description

@Deb-kal

Hi,
I have installed Loki, everything work great but I have a problem with connecting clients to Loki.
As I want .exe files for Windows, I used to build the client on Windows, cause i'm on Kali.
When I click on the exe file (Generated on Win10 64bits Virtualbox) nothing goes wrong it seems the exe is perfectly executed but I got not clients on Loki.

Configured my private and public IP in const.py correctly.

I was wondering if it was beacause I start Loki using "python3 Loki.py", I've tried to launch loki with "python loki.py" but it throw an error.

What am I doing wrong ?

Activity

  1. Bitwise-01 commented on Sep 21, 2019

    @Bitwise-01
    Owner

    Make sure you have set your public ip as ip when you’re generating the payload

  2. Deb-kal commented on Sep 21, 2019

    @Deb-kal
    Author

    So,

    I redid everything and it still not work.
    What I do:

    Change Private and Public IP in const.py with :

    PRIVATE_IP = '192.168.1.X'
    PUBLIC_IP = 'My_Public_IP'

    ports
    FTP_PORT = 128
    SSH_PORT = 256

    Then I start Loki, go to server settings and start server on

    192.168.1.X : 8080

    Next, on Windows10 x64 VM, I build the client with :

    python builder.py -i MY_PUBLIC_IP -p 8080 -n Test -t exe -ic \myicon.ico -hd -ap

    Still can't connect to Loki.

    Note: I've already opened my router ports see :
    Capture-dcran-de-2019-09-21-17-54-43-ConvertImage

    Ftp server open on port 128 (UDP + TCP)
    SSH server open on port 256 (UDP + TCP)
    Http port open on 8080 (UDP + TCP )

    Got this "Warning" launching loki too:

    • Serving Flask app "loki" (lazy loading)
    • Environment: production
      WARNING: Do not use the development server in a production environment.
      Use a production WSGI server instead.
    • Debug mode: off
    • Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
  3. Bitwise-01 commented on Sep 21, 2019

    @Bitwise-01
    Owner

    Just ignore that warning. As long as you're running Loki locally you don't need to worry about it. Btw 8080 is not the web server, the web server runs on port 5000. 8080 is the TCP port Loki server runs on; it's the port that allows Loki to communicate with infected machines

  4. Deb-kal commented on Sep 21, 2019

    @Deb-kal
    Author

    So now, with your help I have changed ports on my router.
    I finally succeeded to connect the client to Loki, but only one time..., and doing what I always did, I think.... After client connect I’ve uninstalled the client on the VM machine to try to connect another time. Reinstalled the VM to be sure and now it’s the same : impossible to connect clients and Loki.
    I really don’t know what I’m doing wrong, launching Loki with python 3.7, starting server on my private IP port 8080, installing python 3.7 on Windows VM and building the server with my public IP port 8080 ...

    EDIT :
    Sometimes I get this error after clicking on the builder output client :
    44836767-52F7-4FF4-B09B-E74CD8C40F87

  5. Bitwise-01 commented on Sep 23, 2019

    @Bitwise-01
    Owner

    Join my Discord server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions