Jump to content

zoro25

Active Members
  • Content Count

    81
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by zoro25

  1. I'm logged into a domain and nothing for me, 

    I have a both Darren's light script and also the needed  /etc/init.d/dnsmasq stop
    /usr/sbin/screen -dmS responder bash -c 'cd /overlay/etc/turtle/Responder; python Responder.py -I br-lan -f -w -r -d -F'  

    in my rc.local file and nothing is logged from locked devices (also domain joined). 

    For people who can get it to work can you please give more info on your set up or even a walk through if possible. 

  2. Use Br-Lan (can also be seen in the screenshot - posted by Whistle Master above)

    I have used this with my mobile device acting as clientmode (meaning the tetra/nano got outside internet access via mobile device tethered),

    I rarely use any of the Tetra/Nano radios as client mode. that way I can use PineAp and also all of the modules without losing any functionality.

    • Upvote 1
  3. Okay so still looking for some kind of support on this.

    When I run tick the 3 options for logging at the top of PineAP I receive nothing logged.

    Only time anything is logged is if the phone connected to the device connects via wifi (then it picks up a couple of SSIDS) ,

    However it has never detected external SSIDs or clients.

    I've sent emails to support@hak5.org and also Darren, however after about 7 emails sent no reply, except to provide output of log file which I have done over a week ago, I also raised a bug. = https://www.wifipineapple.com/?portal&bugs&action=view&id=378

    A little bit of support back from the Hak5 guys would be welcome , seeing as I have supported your guys over the years and have purchased a Tetra (obviously also a nano) and also long time Mk5 owner/user. .

    I just need to know from the team if I have a hardware issue needing a new device or a software issue which means I can wait for a new firmware.

  4. Yes testing on my own devices.

    I have tried all PineAp combinations and still nothing, also I shouldn't have to deauth as I purposely have my devices not connected to my main protected AP so they should be looking for any open AP they have saved.

    But the Nano never sees anything in PineAp mode.

    I did a great on my mk5 this morning and on that device PineAp works fine, just the Nano giving issues.

    I've also made sure that all filters are clear so I'm not just looking for a certain ssid or client but still no go.

    I'm looking for a list of commands that I would need to replicate the behavior of PineAp as my guess is that the ui is doing something strange or there is some type of race condition happening when scripted commands are sent.

  5. HI guys

    I have a Nano that has never "fully" worked, previously I put this down to the firmware not being fully functional , however after 1.04 release I figured that it must be my device.

    I'll explain my issue.

    Its PineAP , I can never get SSIDs to show (unless I manually connect to an accesspoint) , it should be picking up AP's which are being broadcasted by clients looking for connections, If I do a recon I can see about 20 SSID's and clients , but nothing is logged in PineAP (nothing at all)

    And as it can't get SSID's it never broadcasts any and as it never broadcasts any I can never get connections , unless I manually connect to the AP which I have set on the Nano.

    My Recon mode works really well. No issues there

    However under PineAP I want to just scan all devices close by, and log SSID's and then broadcast.

    Are there any commands that I can run once I SSH into the Nano to check all is functioning okay.

    Also I should note that I pressed the button to change Wlan1 to a random Mac address (not sure if this broke the Nano PineAP functionality)

    I've done about 4 factory resets and all still not working as it should, PS I have a MK5 so I know the basics of how PineAP mode should work and what to expect is returned.

    Thanks in advance

  6. TL;DR: The NANO isn't txpower locked -- they're capped the chips maximum which is what we've implemented. No magic command is going to push the silicon past its spec. The easy way to increase total output power is with a higher gain antenna. If you want to take it a step further, I recommend using a low noise amplifier like the USB powered ALFA booster in the hakshop.

    EDITED FOR SPACE

    Hi Darren,

    I saw in the latest video the nice setup with the amps,

    I have a couple of questions,

    1. Do they require separate USB power (meaning 2 PineApple Juices) one for the Nano and another for the Amps or is the power from the Nano enough to power 2 Amps and the Nano?

    2. Can you do a screen grab of the extra AccessPoints and also TX if possible with and without those installed.

    3. Lastly do you have 8Dbi antenna for sale?, I can see any if you do

  7. +1 exact same issue, I choose Wlan2 from the drop down and type in password for AP and it connects , once I refresh the page it's connected using WLAN1 , and on reset it auto connects using WLAN1 even if Wlan2 is available,

    Also disconnect doesn't work as it disconnects and just auto reconnects before I can ever get Wlan2 to connect, WLan1 reconnects too quick.

    I've had to change AP password to prevent it auto connecting.

    Is there ever a case when a user would want client mode in Wlan1?,

  8. I've noticed a trend where residences are now more secure than a lot of corps. (small businesses I should state and not large ones).

    Residences will leave the default WIFI password that came on the router, alot of the time this is on a sticker on the bottom of the device and will be 10+ chars in mix of upper lower and numbers,

    Small Corps will change this default WIFI password for ease of use for their staff, so something like businessname+random number (or even just businessname) also the buinessname is usually also the SSID name :-)

    However on the counter side the admin account to access the router settings once on network is usually left as default on residences while it is changed on Corps.

    So Corp easier to crack WIFI password , and Residences easier to get access to admin panel of Wifi Access point.

×
×
  • Create New...