jdoe

Yeah, no worries here either. Given another update is coming so soon, I'm just going to hold off until the 1.0.2 release and then I'll let ya know if I'm still having an issue.

Yeah, I am having the same issue, and posted it a few hours ago in the 1.0.1 firmware thread. Actually, the issue may have gottem worse for me after the firmware bump. Before I would get the radio0-wlan1/radio1-wlan0 issue only after a reset, and as soon as I fixed it, it wouldn't reappear until another reset. Now I have the same issue, only it seems to reoccur once and awhile, even without a reset. Moreover, on occasion, eth0 shows up as radio0 as well.

Just wondering if anyone is still having the radio0/radio1 swapping issue? I know 1.0.1 was suppose to fix it, but it seems after every factory reset, as soon as I connect to an AP in client mode, wlan1 becomes radio0 and wlan0 becomes radio1 (and on occasion, even eth0 gets in on the radio action)...

Hah! You guys suck! I've spent the last thirty minutes trying to find out where you guys were seeing this stuff on: http://www.fleabay.net/ Turns out, Fleabay is a real site - but only has about 36 items total on it. I'm a huge ebay user, but here I was thinking maybe this is some underground electronics marketplace you guys had found...

I don't know about others, but I have this Anker: http://amzn.com/B005NGKR54 And it came with the appropriate adapter for the V. That said, it's not getting anywhere near the advertised uptime that the juicepack has, so I'm eagerly awaiting my elite upgrade kit.

There is a bug that should be fixed with the first firmware update. After a factory reset you need to SSH in and run: rm /etc/config/wireless && wifi detect > /etc/config/wireless && reboot

Yeah, that thing is awesome, and it's a fluke! Now if I can just find 2 grand laying around somewhere...

Yeah, I've got three or four different boxes out in the field, and I just start at port 20,000 and work my way backwards on the server. So, if I ssh localhost -p 20000 -> RPi ssh localhost -p 19999 -> Beagle Black ssh localhost -p 19998 -> MK5 I can't access all of them at once, but as long as the keys are set up in both directions, you can script it. Each access just happens sequentially.

AutoSSH isn't working for me either, but as a temporary fix, I wrote this script: #!/bin/bash TEST=`ps -ea | grep " ssh [-]fnNT"` if [ "$TEST" = "" ]; then ssh -fnNT -R PORT:localhost:LISTENPORT USER@SERVER fi It's real dumb, but its been working flawlessly. It checks to see if a reverse shell is up (that's the grep line), if it is, it does nothing. If it's not up, it restarts it. I used the same names above as they did in the AutoSSH infusion (LISTENPORT is the port you'll forward, likely 22, and PORT is the port you'll use to connect to it on the remote server). Of course all the same stuff as AutoSSH applies (i.e. you have to have ssh keys set up, etc) I call this via a Cron Job once a minute. * * * * * /sd/static/keepUp.sh > /dev/null 2>&1 I've actually used this for a RPi I have deployed behind a firewall for months, and it hasn't let me down yet.

Yeah, I would like to second the Anker battery. I still ordered the kit from hak5 since it's been custom tested for the pineapple by the crew (and because of how excited Darren was about it during the launch vid, heh), but for the Pi and a few robotics projects I work on, I'm using this: http://amzn.com/B005NGKR54 It's 10,000 mAh, very nice quality, beautiful polished look, LED remaining charge indictors, variable USB, 9V, 12V outputs, and enough adapters to connect it to anything on earth. If you don't need the extra options or for it to look sexier than your phone, I'm sure you can find a similar one from Anker a bit cheaper.

Yeah, I too would be interested in any antenna recommendations. I've always used the 7dBi alpha panels in the past, but I'll be purchasing something new for the MK5. Thanks in advance!

If the radio issue is the one you're referring to, SSHing and typing this: rm /etc/config/wireless && wifi detect > /etc/config/wireless && reboot Has always worked for me.

Yeah, I would like to second xrad's comments. I've never worked with any of the previous Pineapples, but I watched every video made by Hak5 on the release, technical details, etc waiting for it to arrive. I've also read most of the forums posts. Moverover I've been doing this kind of stuff for most of my life, as well as my career, and I'm still running into some issues. Of course I don't blame this on the dev team, it's an extremely versatile product that was just launched, so I anticipated having issues. And from what I've seen so far, the support team is great! At the same time, reading through the forums, I must say - the community around the product is somewhat sad. I'm seeing lots of people genuinely asking for help, and lots of really condescending responses from users far from having enough knowledge/skill to pull it off. If we could provide new users a sticky with the current quick-fixes to problems that every one who uses the product is going to run into, it would save a ton of wasted man hours both for the users needing help, as well as those who feel they need to provide snarky responses. A problem with simply going through the threads as-is, is that some of the issues have been resolved, and thus some of the fixes that worked previously either aren't needed, or need to be solved in a different way. Moreover, reading through the forums, there are not-so-good fixes being thrown around and recommended. How is a 'newb' suppose to discriminate between them? A sticky that's updated would solve all of these issues. Please note, I'm not implying that there aren't many very good threads as well - that's clear. Sebkinne and a bunch of others are the reason I've got it as functional as I do. I'm just commenting on the overall feel of many of the threads (here and in particular in the usb rubber ducky forum).