Smart-Aswood

datahead: I've gotten as high as 9mbps but it was on a single test with an ethernet connection to a laptop with ICS. Otherwise I'm the same as you. I live in a pretty unpopulated area, so that's probably sufficient for the putzing around I do. If I have 2 clients onboard at the same time I hoop and holler. Client mode just isn't stable enough to use, at all. If someone wants to give me a step by step or point to one, I'll be happy to eat my words if it works. In client mode, after about 15 minutes, clients get like .9 and .7 mbps. (point nine and point seven). Any slower than that, which is regular, and the speed test just times out. I've tried it with AWUS036Hs and AWUS036NEHs too. I have two of each. All 4 are great radios in Wireshark. Just not in MK5 client mode.

I figured this out too. "Nov 26 22:14:49 Pineapple daemon.warn dnsmasq-dhcp[1962]: no address range available for DHCP request via wlan2" That occurred because in client mode, I was using a hotel wifi for internet access AND that hotel had a system with a gateway of 172.16.0.1 From what I understand of TCP/IP (almost nothing) 172.16.x.x itself shouldn't cause those errors. It's the implementation in the hotel router's DHCP that does it. Didn't have those errors when I configured my own wireless router (using my Mifi 5510L for WAN) with those same IPs and gateway. So interesting (not a whole lot) but not in any way a problem.

Okay. I did it. Both onboard radios were off and I was running on two external USB Alfas. Didn't try PineAP or anything because I just did this to see if it woulkd increase the speed clients would experience. It did not. So there's no need to do it, far as I can see, beyond saying you did it.

Absolutely right. Just because something is n-capable doesn't mean it's using n. All these units will fall back to g at the least sign of a problem, even when both cards are n-capable. Think about it from a design engineering perspective. G is monstrously stable. So are you going to get more complaints and products returned to the store if your design sticks steadfastly to n, or if it immediately negotiates for g at the first sign of trouble? How many customers are even going to notice they're on g instead of n? Answer: not many. I've streamed HD movies from Amazon on both g and n without a hitch. Only problem I had in that experiment was making sure I and the wireless router stayed on n - which isn't easy. Same thing goes for 3g and 4g, by the way. I've got six 4g devices that I use for telemetry every day. Even line-of-sight with a known 4g Verizon antenna these things regularly fall back to 3g. Why? See above. They still work fine. So I'm not busy obtaining RMA tickets to return them. In each case, their designers have kept their jobs BECAUSE they made that fallback the norm rather than the exception.

This looks like a fitting place to bring this up. We have some troubles connecting victims to Jasagers these days. I remember Vivek-Ramachandran on SecurityTube showing how easy it was to fool his iPhone into logging in to a Mitm attack. That was a couple of years ago. Bet he can't do that with the phone he has now. Tablet either. Laptops are still fair game, for now. This all happened because devices like the Pineapple did their job. Good old honey pot still works though. Give it a good name and a certain percentage of people will log in. Free Fast and Private Wireless.

Might be able to do something with WiFi Manager. Probably not assign each to a different application though. (I think) that would require two radios to be on the same channel. Can't do that. Tomorrow I'm going to try using two external Alfas in place of wlan0 and wlan1. Just want to see if having the radios further apart will add some stability. It won't. But I'm going to try it. In that case though, I'll have the two onboard radios either off or at least dormant. You're supposed to be able to have two (wifi) radios as close together as you want as long as they're on different channels. Not sure I buy that. That assumes there's no out-of-channel noise, even right next to the antenna. With a good radio and low power, there shouldn't be much -- but none? Wifi channels are pretty close together in the same band. Like I said, I doubt it makes any difference. Gonna find out.

Okay I'll be darned. That worked. Also, configuring the Pineapple AP through PineAP and leaving it alone in the Network configuration. So I learned something ---> where there are more than one place to configure something, don't. Just configure it with one tool.

Okay, considering what you said about leaving both radios free, I tried using an Ethernet connection to a Windows 7 laptop as was evidently done in previous versions befor MkV. Laptop is getting great internet via the hotel wifi. Broke the Pineapple access point. Pretty sure a big part of how I got this so fussed is that I downloaded Wireless Manager and was making changes with it and the Network infusion. I got rid of all infusions besides the factory setup and I'll try again.

Great answer. I knew it was something. I'll still keep doing the client thing because the Mifi 5510L isn't workable yet AND I'm staying at hotels with free wifi. I was using a AWUS036NEH in the with wlan1 turned off USB slot (seemed much more stable) until I kept getting this filliing up my syslog Nov 26 22:14:49 Pineapple daemon.warn dnsmasq-dhcp[1962]: no address range available for DHCP request via wlan2 Nov 26 22:14:46 Pineapple daemon.warn dnsmasq-dhcp[1962]: no address range available for DHCP request via wlan2 It was like 6 times a minute. Can you point me to a fix for that?

Hello. New here. Just fired up a new Pineapple yesterday. First, let me say that the support I see for these $99 appliances is better than I recall getting from Cisco and other companies selling $3000 appliances back in the 90s. Perfect? No. Running network appliances is frustrating. The more an appliance does and the more options it has, the more versatile it is, the more the potential conflicts and support headaches it will have. The Pineapple does a lot! Very versatile! Lots and lots of options! The support I see on these pages is top notch, considering all that. No, Pineapple support does not now owe me $5. Okay, here's my question: Why tether? Why connect to a device like my Verizon Mifi 5510L managed modem via usb instead of wirelessly? Is it just so you won't have to power the modem separately? Has to be more than that. I tried and tried to tether my 5510L until I asked myself that question. Just used it wirelessly -----> no problemo. It's still doing all it's own management and works perfectly. Apologies if this has been covered before, but I can't find this specific question asked via searches.

Same problem here, still. Using the Pineapple as an AP hasn't been stable. Started new unit yesterday and brought everything up to date before using. Nov 26 14:34:10 Pineapple daemon.info hostapd: wlan0: STA bla bla bla IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Nov 26 14:34:09 Pineapple daemon.info hostapd: wlan0: STA bla bla bla IEEE 802.11: disassociated due to inactivity Firmware Version: 2.0.4