Jump to content
Hak5 Forums


Active Members
  • Content count

  • Joined

  • Last visited

About Shad

  • Rank

Recent Profile Visitors

751 profile views
  1. [Module] ddnsc - Dynamic Domain Name Service Client

    Yes you can. The only reason you cannot directly ssh into the turtle from the wan side is because the firewall blocks it, but upnp_portfwd also adds a rule to allow access the redirected port. So, as a side effect, after running upnp_portfwd you can also ssh to the now opened port from the WAN.
  2. [Module] ddnsc - Dynamic Domain Name Service Client

    You are welcome. Thank you for letting me know a possible flaw in DDNSC, in next version I will add some extra error-checking for restoring the base config file in case it gets damaged. About the example in using it in conjunction with upnp_portfwd: Supposse you connect the lan turtle to a LAN in which there is a UPNP enabled router that is the gateway to internet. (ie: many telco provided routers, adsl, etc). You set up upnp_portfwd to redirect a port in the router, 20000 for example, to ssh in the turtle. Then you can ssh to the external ip of the router from a remote location and you will ssh into the turtle. BUT, what if you don't know what the external ip is? That's where ddnsc comes to help, as it will also map your no-ip host to the external ip. Then you just ssh to your no-ip hostname port 20000, and voila! direct shell to the turtle from an arbitrary remote location. It's just another way to have a shell into the turtle. It can be used standalone or in conjuction with all the other modules that provide reverse shells.
  3. [Module] ddnsc - Dynamic Domain Name Service Client

    It looks like for some reason your /etc/config/ddns file got messed up or truncated. I think copy and pasting this onto a new /etc/config/ddns file will fix it: config service 'myddns' option interface 'wan' option use_syslog '1' option use_https '0' option force_interval '72' option force_unit 'hours' option check_interval '10' option check_unit 'minutes' option retry_interval '60' option retry_unit 'seconds' option ip_source 'web' option ip_url 'http://checkip.dyndns.com/' option service_name 'no-ip.com' option domain 'yourhost.ddns.net' option username 'youremail@gmail.com' option password 'password' option enabled '0' After that, the configure option of DDNSC should load the values and let you change them. Please let me know if this fixes the problem.
  4. [Module] ddnsc - Dynamic Domain Name Service Client

    no-ip is the same one I am using so that should be no problem. From the error you have posted (etc/init.d/ddns not found) I would say that the needed ddns scripts are not installed on the system. Try this on the shell: opkg update opkg install ddns-scripts It should have been automatically installed when the ddnsc module was first run, but maybe there was some problem during the installation process. Let's see if that solves the problem.
  5. [Module] ddnsc - Dynamic Domain Name Service Client

    Hi Pocket, Which version of ddns are you using?
  6. [Module] TORtle - TORShell + TORGateway

    Thanks Darren! Let's see if anyone tries it AND post some feedback about it. Otherwise I will just leave it as it is, as it currently does everything I needed for my usage case.
  7. SSH: Connection Refused

    If you can't reach your turtle when directly connected to your computer, then yes, you may need to factory reset it following the procedure you mention and is described in the lanturtle.com site. I might add that you can't directly ssh into a vanilla lan turtle from the lan, only from the PC it is plugged into or through some of the reverse/direct shells provided by some additional modules (if you already configured and enabled them on boot)
  8. No SSH when plugged into regular LAN?

    iptables -I INPUT 1 -i eth1 -p tcp --dport 22 -j ACCEPT
  9. MacChanger persistent ?

    Your welcome. Also if you are cloning the MAC of the PC to which the LAN Turtle is connected you could try my clomac module. It does exactly that, plus, if enabled on boot and the PC is not there anymore it will just clone the last "seen" MAC. Ie: you can clone it first using that PC and it will just keep cloning it on every reboot even if it is not present/turned on. Latest version of clomac is not yet directly available from LAN Turtle modules update, and the one that there is doesn't do the clone-last-seen-mac feature. Latest version is on my GIT or directly downloadable from: https://securityfrod4xaa.onion.to/clomac
  10. Hi! This will be the discussion/support thread for TORtle module. I sent the pull request several days ago but as I don't know when it will pushed I decided to open the thread already and attach the file just in case anyone wants to try it. First, what is TORtle? It's bassically a module that combines TOR and LAN Turtle in an automatic convenient way. It does two main things: 1- TORShell: Sets up a hidden service inside TOR network. By default it is a TORShell (SSH within TOR), that is a redirection to local port 22 (ssh)... but you can configure to offer any service you want. This offers another possibility of remote shell WITHOUT requiring any sort of proxy/host pivoting or reverse connection to your machine. LAN Turtle has lots of reverse shell options, which is cool, but having the possibility of direct/arbitrary/anonymous direct shells might be handy in some usage cases. TORShell offers just another one of those options. Also you can use it to host an httpd server (or any other service) inside TOR if you want. For example: My Turtle has a web server at: securityfrod4xaa.onion (or https://securityfrod4xaa.onion.to if connecting from "regular" internet). Of course all of this is provided by the openwrt 'tor' client, TORtle just takes care of automagically setting it all up for you. 2- TORGateway: If enabled, automatically and conveniently forwards all ETH0 traffic through a TOR Transparent Proxy. It's a very simple way make all the connectivity for the USB connected PC go through TOR, simply starting the service with that configuration and not having to do anything else on the PC. TORtle will take care of all the necessary redirections for you. Also, another option is to just run the regular TOR Proxy, for which you can also enable/disable turtle's IP forwarding for added prevention against unintentional leaks. All of this you can choose in the simple configuration screen. I also think that this could be a good place to discuss what are the best/more secure ways to access the TOR network. Ie: The risks of DNS leaking, other spyware inadvertently leaking when forwarding ALL traffic, if it is prefereable to use torified applications with a regular TOR proxy instead a full gateway, etc... And also, any bugs or ideas to improve TORtle are very much welcome. I *really* need your feedback. Thanks! P.D.: I don't see the file I attached to my post... anyway, you can download it from https://securityfrod4xaa.onion.to/tortle Just place it on /etc/turtle/modules and you are all set to use it from 'turtle' menu. - Shad.
  11. MacChanger persistent ?

    I think that there is an issue in the change_mac function of config.menu. The code to set the persistency for the new mac address is certainly there... but never run: macchanger -m $1 eth1 &> /dev/null && { [[ $# > 1 ]] && { uci set network.wan.macaddr="$1" uci commit network In the meantime, a quick workaround would be to manually set the mac address to spoof like this: uci set network.wan.macaddr="XX:XX:XX:XX:XX:XX" uci commit network Now it will keep that setting for subsequent reboots.
  12. [Module] upnp-portfwd - uPnP Port Forwarding

    Yep, I guess there may be a lot of upnp enabled routers out there. In fact it is a convenient feature for most users to just run their torrents or any other p2p software without having to know/care about port forwarding or anything. Security vs usability.. as always. Anyway, once you are inside their network, upnp port forwarding is just another way to open an external "hole". It is just slightly better than reverse shells because you don't even need to pivot on an external proxy or host... but then again there are other ways to provide with a direct/arbitrary/anonymous access, like for example setting up a TOR hidden service (I have just sent a pull for a torshell module). Ironically enough, I have UPnP enabled on my home router :)
  13. Thank you very much Darren! Glad to contribute to this great project :) Clomac (and the other two modules) haven't had much extensive testing as they are almost initial versions I made in the last couple of days. They do work for me as intended in my tests though, but I would appreciate some feedback in possible scenarios where they don't work and/or additional features that would be desired. Also, if they are "just working" for someone I would like to hear about it even if you don't know what else to change/add.
  14. Developing new Lan Turtle modules

    Hi Darren! Thanks for the nice little toy the Lan Turtle is :) I have uploaded my first module. It's a very simple automatic MAC cloner of the client's address into the WAN interface, for added transparency of the bridging and bypass of mac filtering. Is there any way to call a function in the module when it is enabled/disabled in the gui so that as to run some "installation" code? That way the start function doesn't need to also hold the code for persistance after reboot. Also, I am not sure if I sent the pull request correctly, could you confirm? Thanks again!