RussDR
-
Posts
22 -
Joined
-
Last visited
-
Days Won
2
Posts posted by RussDR
-
-
This is now resolved. Go to etc/config/network and change the config for 'lan' to:
config interface 'lan'option ifname 'eth0 eth1'option type 'bridge'option proto 'dhcp'Both interfaces are assigned an ip by DHCP.I did this and got everything working on my end as well. However, our printer (on the same network) has gone haywire. It just keeps restarting. The turtle has no physical connection to the printer, just that they are on the same network.
I thought maybe it was an IP conflict or something, but no. I can't figure it out.
-
Awesome RussDR - thanks for checking this out. Unfortunately I wasn't able to repeat your success. I changed the /etc/config/nmap file like you suggested, as seen below:
config 192.168.1.1 'target'
config 7 'profile'
config 'log'
Saved it and went back to the turtle gui - when I try to configure the log location, I get the same slight screen refresh, and no entry to the menu. Can you share what your /etc/config/nmap file looks like after you've configured it within the module? Maybe I can just manually enter it and it will work then? I tried:
config /sshfs 'log'
but to no avail. Any additional help would be much appreciated!
telot
I'm glad it worked out for you!
-
If you go into the CLI and head into the /etc/config directory, you'll find the nmap config file. You can edit it and add a line, "config 'log' " (no quotations) into the file and save it. That allowed me to set the log directory within the Turtle Shell GUI.
-
2
-
-
What happened? The update process shouldn't take but 5 minutes - if that. When you check for updates, it'll give you 30 seconds to back out (CTRL+C) before downloading the turtle-2.bin file and issuing the sysupgrade command. It'll also kill SSH connection so PuTTY or OpenSSH will drop. You'll know it has finished flashing and started it reboot cycle when the amber LED starts blinking.
If you want to manually update the firmware you can download turtle-2.bin from http://downloads.lanturtle.com/turtle-2.bin then SCP it over to /tmp/ on the Turtle and issue "sysupgrade -v -n /tmp/turtle-2.bin"
I'm not entirely sure. I started the update process and the PuTTY session dropped. I waited about 5 minutes and didn't see any activity from the amber light. I figured it may have been a fluke install and just let it go while I was going about my business. I came back an hour later and still no amber. I tried to SSH back in but no good. I pulled the device out of the USB and it sure enough it wouldn't boot back up or respond to SSH connections.
I'm not entirely sure if it's related, but my router was acting up. I was getting internet to wireless devices, but pages weren't loading completely.
Regardless, I found the firmware download link by poking around on Github and used the recovery function to upload and flash the firmware. All is in working order now!
Thanks for the response! Great device!
-
1
-
-
Nevermind. I found the firmware link by scouring the Lanturtle-wiki Github page. If anyone runs into the same issue as I did, the v2 update firmware can be found at "http://downloads.lanturtle.com/turtle-2.bin".
-
Is the firmware available for download? I let the Turtle do it's initial update and about an hour went by before I decided to pull the power. Sure enough upon rebooting, I cannot SSH into the unit.
I've deduced through browsing the site that recovery mode is available by holding the button down on the board, but I've been prompted with an upload page with no firmware to load.
-
This same thing literally just happened to me just now. I'm in the midst of trying a couple of things but so far the MKV's format utility didn't work and neither did Windows. The only thing I've done in the past 24 hours is add another adapter to the USB port and update a couple of infusions. Strange coincidence. I'll factory reset it and report back.
-
Well, it's quite simple. It happens on every AP I have access to - they all use WPA2 and don't have any login pages. And since it happens right after a factory reset, there are absolutely no infusions, scripts and whatnot running other than what comes with the factory settings. There is also no additional hardware connected (other than my laptop via the eth0 interface, of course). So here is what I do in simple steps:
1) factory reset
2) set root password and reboot
3) log in
4) go to network settings in the web interface
5) go to client mode
6) select appropriate AP and enter PSK (connection quality up to 70/70)
7) click connect
8) wait if something happens - in about 20% of the cases I will get a connection
9) if connection works: reboot
10) wifi client connection won't work at all anymore, so
11) factory reset
Hmm. Did you try re-flashing the Mark V? Not factory reset, but re-flash.
-
I've honestly never had this issue before. Not exactly at least. I found I had a similar issue if I used wlan1 to access an AP with a login splash page. I use my Android phone as the interface when I'm mobile and it was getting the AP's login request. I was attempting to login and the Mark V hung then rebooted. I never got a chance to see if Wifi Manager showed additional interfaces but.. After reboot, the Mark V would connect to the same AP and the process would begin again. I would have about 30 seconds or so in the interface or in an SSH and then it would reboot. I found that the only way to make that quit was if I actually logged into the splash page.
What I'd say is to try and give us as many variables as possible for how you arrived at your issue and maybe we can recreate it? What type of AP is it? What infusions/scripts/whatever are you running? Any additional peripherals attached to the Mark V?
Another thing to keep in mind is not to run too many things at once. I've had my Mark V reboot on me due to that as well.
-
I just got these same antennas today along with the proper adapters. They were worse than stock. A lot worse. Let me know how your experience is.I dont mind waiting, for now ill play with these 9dbi antennas on my alfa wifi card lol
I'm almost tempted to think my Mark V has signal issues. My Mark V can just about see my router on the other side of the house let alone actually being able to perform any successful attacks on it while my old laptop with a broadcom b/g mini pci-e card and standard on board antenna can attack it with ease.
-
I get this every time that I try to install with your steps.What was your command? It looks like you have one too many forward slashes for the install directory.
-
I've been trying to run this Infusion and while it certainly deAuth's clients in every variation that I've ran it in, the Mark V eventually hangs and then reboots. It happens every single time anywhere from 30 seconds in to 3-4 minutes in. Is this occurring for anyone else?
-
He's got a paypal link in his signature block... :)
Doh! On mobile! Should have known better! Thanks!
-
Awesome. You're dedication should be rewarded... Have you ever looked into something like a bitcoin tipping address or anything?
-
Some of the info in this thread helped: http://www.backtrack-linux.org/forums/showthread.php?t=52539
my mon0 interface having a different MAC was giving me the problem on a laptop w/Kali.
This morning I sat down with my laptop/Kali and used Reaver on an AP I setup that's worked before. Change the MAC of mon0, problems. Don't change the MAC, no problems. I haven't tried changing the mac of both the wlan and mon interfaces to be the same.
I tried using reaver via the command line on the Kali Pi and Pineapple with two different radios on the same AP. Not much luck. Mostly the failure to associate. I'm going to keep playing with it.
Thanks for the reply. I didn't research too hard into it but I can tell you I made sure the MAC addresses had matched so I think it has something to do with Reaver and WFP bumping heads somewhere. I had stumbled across an OpenWRT version of Bully that someone ported to the MKV. It's running circles around reaver ATM.
Either way, thank you Whistle Master, for all of your effort with the Infusion.
-
I'm thinking it has to do with Reaver running on this platform, but I couldn't get Reaver to stop hanging at the start. I even SSH'ed into the WFP and gave it a try but couldn't associate with the target AP (or any surrounding AP's for that matter) on either of the radios. I had to use aireplay to associate and then it worked. Has anyone else ran into this?
Client Mode
in WiFi Pineapple NANO
Posted · Edited by RussDR
words...
The Nano doesn't see 5GHz networks. Is it possible your router is only outputting a 5GHz signal from your router (as opposed to both 5GHZ and 2.4GHz)?