holgerr

Sorry for the delay - other, more urgent work got in the way. Anyway, here's everything but the syslog contents, since I couldn't find anything useful in /var/log (from what I've seen it looks like there should be a /var/log/messages file, but there isn't...). By the way, this is after I reinstalled the stager, the reflashed the 1.0.4 firmware and then connected to the AP (looks like I connected to the repeater instead of the main access point, but the results are the same with both):

I did - same result as a factory reset. I even reinstalled the stager.

Yes, will do that later today when I'm done working on something else.

1.0.4

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

Hi, I'm going insane trying to get my Mark V to work properly. There are a number of annoying problems that really prevent it from being useful at the moment. I can only get the second WLAN interface (client mode) to work exactly once after a factory reset. Even then it doesn't work all the time, but at least I usually get it to connect at some point. But as soon as I have to reboot, not only does it not reconnect to the network it was on, but it also doesn't allow me to manually reconnect anymore. It will try, but always fail for no apparent reason and the red light never comes on. If I have the wifimanager infusion installed by that point, it strangely shows me an additional radio interface (radio2) that doesn't have a MAC address and neither does radio1. If I go in through ssh and run the wifi command, it throws an error about a missing hardware interface. If I delete /etc/config/network and recreate it with the wifi command, that still doesn't help. So basically, whenever I need to reboot or move my Pineapple to a different power outlet, I need to start completely from scratch with everything I was doing - makes it pretty useless. I've had a ticket open in the bug tracker about this for almost as long as I've had the device - nobody has even touched it. At the moment it looks as if this device is in an alpha stage of development at best and should not have been sold in the state it's in (not to mention that my firmware SD card was empty, which caused another bit of hassle). Am I the only one who is having these problems - so in other words, does my device maybe have a hardware fault? Or am I the only one who is trying to use both WLAN interfaces the way they are intended to be used and everyone else happily creates an uplink via the ethernet interface? I specifically bought this thing as a lightweight solution for (authorized) penetration testing in circumstances where I need to be able to drop the device and leave it, but with the wifi not reconnecting and reverse-ssh not automatically working either (which doesn't matter since the network connection issue prevents it from being useful), it really feels like I've been sold a lemon instead of a pineapple...