Jump to content

r6uur6nr6u5ur56

Active Members
  • Posts

    37
  • Joined

  • Last visited

Everything posted by r6uur6nr6u5ur56

  1. When looking through dmesg I notice this not sure if the "not supported" is the problem because I can open "cat /dev/rfcomm0" just fine, not sure how gpsd thinks about it [ 70.176926] Bluetooth: RFCOMM TTY layer initialized [ 70.176966] Bluetooth: RFCOMM socket layer initialized [ 70.176987] Bluetooth: RFCOMM ver 1.11 [ 77.927678] Bluetooth: TIOCGSERIAL is not supported [ 87.020196] Bluetooth: TIOCGSERIAL is not supported [ 87.021156] Bluetooth: TIOCGSERIAL is not supported [ 93.020151] Bluetooth: TIOCGSERIAL is not supported [ 401.665876] Bluetooth: TIOCGSERIAL is not supported [ 401.670516] Bluetooth: TIOCGSERIAL is not supported [ 411.021010] Bluetooth: TIOCGSERIAL is not supported [ 411.021251] Bluetooth: TIOCGSERIAL is not supported [ 411.022220] Bluetooth: TIOCGSERIAL is not supported [ 411.022454] Bluetooth: TIOCGSERIAL is not supported [ 417.020636] Bluetooth: TIOCGSERIAL is not supported [ 417.020832] Bluetooth: TIOCGSERIAL is not supported [
  2. Thanks for the tip, I already tried "chmod 777 /dev/rfcomm0" for fun earlier but no luck, same error
  3. rfcomm 9730 root 5r CHR 216,0 0t0 49166 /dev/rfcomm0 I should note that I'm using a raspberry pi 3, don't know if it makes a difference I'm guessing the "rfcomm" from above is the rfcomm process it self hosting the /dev/rfcomm0
  4. Yes I have that tried that, but it instantly closes the gpsd process with no log/error message
  5. For the life of me I can't figure this out, at the moment I have my phone sharing the GPS over bluetooth using the app (Share GPS) I have the phone paired and using "rfcomm connect rfcomm0 xx:xx:xx:xx..." to create a serial rfcomm0 connection When I use "cat /dev/rfcomm0" I see all the nmea output constantly flowing but when check the status of gpsd (systemctl status gpsd) I get the following output ● gpsd.service - GPS (Global Positioning System) Daemon Loaded: loaded (/lib/systemd/system/gpsd.service; static) Active: active (running) since Fri 2017-12-01 12:12:03 CET; 23min ago Main PID: 9645 (gpsd) CGroup: /system.slice/gpsd.service └─9645 /usr/sbin/gpsd -N /dev/rfcomm0 /dev/rfcomm0 Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed. Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: device open failed: Device or resource busy - retrying read-only Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: read-only device open failed: Device or resource busy Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed. Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: device open failed: Device or resource busy - retrying read-only Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: read-only device open failed: Device or resource busy Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed. Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: device open failed: Device or resource busy - retrying read-only Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: read-only device open failed: Device or resource busy Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed. but (cat \dev\rfcomm0) works fine, when I look in kismet I get the following message ERROR: No update from GPSD in 15 seconds or more, attempting to reconnect INFO: Connected to a JSON-enabled GPSD version 3.11, turning on JSON mode
  6. Nice idea, could be done I guess in the good old PHP, there is already a project going for some time tho, u can check it out here, http://www.fruitywifi.com
  7. I tried it on my 3DS, but I was not able to login into the pineapple, it simply redirected back to the login page
  8. Are there any europe shops open for the turtle ? if so, link :)
  9. Thanks, I aswell had to put the ethernet into Classic mode, it's working
  10. I'm curious if it's possible to put a ethernet cable between the raspberry pi 2 and the pineapple and access the Pi2 through the pineapple's wifi I've seen others been able todo so but I've seen no other thread how they got it working, anyone know ?
  11. Yoo, is there a nice way to setup a boot script written in bash/sh I'm trying to enable wlan0, wlan1 and wlan2 and after that enable airodump Currently I'm trying todo it through init.d but no luck really and the dip switches are funky in version 2.3.0 Any help is appreciated :)
  12. I'm curious about this aswell, can it be done together with a Raspberry PI ?
  13. Anyone tried to pwn some consoles which are having wifi ? I know most of you are probably targetting devices like laptops, phones and such but what about gaming consoles ? Tried it earlier with my WII U and it was really easy with the pineapple
  14. Did anyone got a Raspberry PI working with BeEF together with the Pineapple ? I'm curious how this can be done
  15. Got it working, simply re-flashed the sdcard for the raspberry, thanks for the help
  16. Through the web interface... ? I've tried classic and client mode but both didn't really worked, I putted a static ip on the pi 172.16.42.2, couldn't ping it from pineapple over ssh
  17. It's rather simple really, I have pi plugged in the pineapple and have the pineapple create a hotspot And with phone or laptop I connect to the hotspot and can nmap etc But atm I can't seem to find the pi when using nmap or I ping to the wrong ip/subnet
  18. I want the setup to be done over the cable, I can't seem to ping the pi when it's plugged in SSH etc is enabled
  19. I was wondering... is there a way to let's say plugin a ethernet cable in the PineApple to the Raspberry PI And then connect to the Raspberry PI over the Pineapple's hotspot ? This should be possible in theory, just wondering how it should be done with the pineapple :)
  20. Change the channel to 6, this 1 is more common
  21. Winscp did even a worser job, couldn't even reach 1%, it nearly instantly gave a "Host is not communicating for more than 15 seconds. Still waiting" And this is over ethernet, it did aswell the same result over wireless Putty, SSH all works fine... but transfering files ? oh noo The file I'm trying to transfer is 36,288 KB Edit: woow I disabled the infusion "RandomRoll" and all the sudden it started transfering the file Even did a reboot just to be sure... first it didn't download the file at all just 0%, disabled RandomRoll infusion, boom transfering and completed it Somebody should look into that infusion to see wth is going on
  22. Just like the title says, I keep getting disconnected when having a connection to the pineapple over Ethernet or Wireless Every 1-3MB orso it will disconnect and everytime I had to keep hitting resume for a 30MB file it's a pain Anyone else having this problem aswell ?
  23. Thanks GPS could be fun for kismet etc, which I don't use currently will maybe in the future A real time clock would be the best fix there is Wireshark finds the time weird in the column... lol In the actual packets it's showing the correct time
  24. I will probably get a GPS stick eventually, but atm I found a even better solution So, here is my solution, we let the pineapple SSH into a android device, grab the phone's time and voila pineapple is having the time without internet Stuff I did to get it all working: 1. SSH into the pineapple 2. Go into /root/.ssh 3. ssh-keygen -t dsa (do not fillin a password) 3. cat id_dsa.pub >> ~/.ssh/authorized_keys 4. now copy that id_dsa.pub from your pineapple to the Phone (or laptop whatever) I simply used FileZilla 5. Copy that id_dsa.pub to /<YourHomeFolder>/.ssh 6. cat id_dsa.pub >> ~/.ssh/authorized_keys 7. Create a set_date.sh on your Pineapple in /root/set_date.sh #!/bin/sh date `ssh USER@HOST date "+%y%m%d%H%M.%S"` 8. chmod +x set_date.sh Set the Cron job on your pineapple, I setted mine to 5 minutes, could even do 1 minute tbh */05 * * * * /root/set_date.sh This should do the job This method might even be quicker then using a GPS stick since you'd probably have to wait for a lock or something Don't forget to use a static ip at your own device (not the pineapple) incase ip changes and script no longer works...
×
×
  • Create New...