Jump to content

denningsrogue

Active Members
  • Content Count

    17
  • Joined

  • Last visited

About denningsrogue

  • Rank
    Hak5 Fan

Recent Profile Visitors

448 profile views
  1. I've updated to 2.0.1 and the problem persists.
  2. Hi all, I can't seem to enable dwall. I've installed and reinstalled the module but when I click the "enable" button nothing happens. Any suggestions appreciated. I am using 2.0 of the firmware.
  3. I am experiencing the exactly the same issue as DigitalData. After a power down, I am unable to "see" the management AP. It occurs wether or not Pine AP is active.
  4. I've had my Tetra for a bit and after a few hiccups (operator error) I have been able to work my way through the set up. I have PineAP harvesting and broadcasting SSIDs but clients can't seem to connect to the Tetra. I've tried Windows 10 and 8, Linux, Android, OS X and iOS clients and while the devices can see the rogue networks they can't connect to them. Any help would be appreciated.
  5. So I have they y USB cable plugged into 2 USB 3.0 ports and I have solid blue light that periodically go out. I also have an ethernet cable plugged into the ethernet port but I can't access the web interface. Missed the earlier post about the battery. When I purchased the battery as part of the kit for the tetra I didn't really expect that it wouldn't have enough juice to run the tetra. My bad.
  6. Tetra arrived today. Anxious to try it out so I plugged in the mini USB USB from the charger to the UART and eventually got a solid blue light. However when I try to navigate to 172.16.42.1:1471 -- nothing. I have an active ethernet link but nothing. When I plug in the barrel cable from the Pineapple Juice 15000 --- nothing -- no lights nothing. Any help appreciated.
  7. I think I have found a work around. Instead of logging in as "ssh root@localhost -p 2222" try this first: "ssh turtle@localhost -p 2222". The login will fail but then when you login with "ssh root@localhost -p 2222" it will work.
  8. Anyone have any other suggestions. Without the autossh, a LanTurtle isn't much use.
  9. I've tried that. What seems to work is to remove the user linked to the Turtle and recreate it but that means copying the keys to the VPS.
  10. I did. I set up autossh with the Turtle attached to my computer's USB port. Confirm that I can connect to the Turtle using my VPS over the LAN. Unplug the Turtle and plug it into a separate power source and I get the connection refused message. I delete the entry for known_hosts on the VPS and sometimes I will then be able to connect but if it is powered down again no way to bring ssh tunnel back to life. I've tried it with 3 different VPSs (Ubuntu, Debian and FreeBSD). Same on all of them. Works briefly but once the Turtle is powered down, I get the connection refused message. Deleting known_hosts may fix it, but only once. Essentially this renders the Turtle unable to be deployed.
  11. So the problem isn't resolved. I got the Lan Turtle stuck when i typed "if config" rather then "ifconfig" to get its IP address. I pulled the power and thereafter the "connection refused" message again. My guess is the that the sudden disappearance of the one end of the tunnel leaves the VPS or the Turtle in a broken state but I don't know how to fix it. I rebooted both the Turtle and the VPS to no effect. I disabled and reenabled autossh on the Turtle also to no effect. I am using a FreeBSD VPS but the expect the problem was the same for the Ubuntu VPS. Somehow after the power loss, the ssh tunnel isn't being properly established. If a guru here could offer a suggestion, I would appreciate it.
  12. I think I resolved the problem. It was a permissions issue. When setting up the sshfs from my home computer to my VPS, I changed the permissions of the home folder that the lan turtle was writing to so that the Lan turtle and my home computer could read from and write to the same folder on the VPS. In that process, I changed the permissions of the home folder of the turtle user which included the hidden .ssh folder and that busted things.
  13. Guys I had auto ssh set up and working reliably using an Ubuntu 14.04 server on digital ocean. Then it stopped working and I got the connection refused message. Set the whole thing up again using a new Ubuntu server on digital ocean and same thing -- worked then stopped. Figured I'd try freeBSD. Same thing. Worked for a while then stopped with a connection refused message. I reinstalled the operating system but now no matter what I do I get the connection refused error. It's strange. SSHFS continues to work, but unless I connect the turtle to my USB port, I can't get in. Any suggestions would be greatly appreciated.
  14. Same issue here. Works under Mavericks; doesn't under El Capitan.
  15. So you can get a connection using the following steps as a stop gap measure 1. ) copy the text from your .ovpn file and paste it into the configuration box in the openvpn module. 2. ) make your way back to the opening page of the turtle gui and exit 3. ) at the command prompt enter the following: /usr/sbin/openvpn --daemon --config /etc/openvpn/my-vpn.conf I have the autossh module configured so if necessary I can rerun that command if openvpn is stopped for some reason.
×
×
  • Create New...