Darren Shady

NAT/PAT issue. You need to adjust where the device is routing and add masquerade. You know this is needed when you can get to the Internet from the Device, but not from devices attached to it. The WAN port Wiki has the commands, just need to adjust the interfaces to match what your connected with (USB Tether) WAN Port

Beta firmware allows for loading of RTL8187 drivers, however, device reboots when attempting to put in monitor mode using airmon-ng after reboot, no longer have a wifi0, internal has moved to wifi1 Also had a weird occurance when I did a wget for the stable firmware and dropped it into /tmp.....device auto flashed and rebooted? I confirming now. Are you listening for upgrade.bin in the beta build?

And this, sir, is the reason people don't like the *nix community. Forums make people feel stupid for asking questions; They'd rather flame and scold for 5 minutes instead of providing an answer. I can see how some get frustrated, but that's what teaching is. If you don't want to help, don't be here. I wish I could say to my students; "I covered that in a lecture 3 years ago, go look it up" knowing full well they weren't part of that class 3 years ago People forget that when they become proficient at something, they lose patience with others who aren't at their level; you've forgotten what it's like to learn. Digging through threads of forums is overwhelming when really you believe you have a simple question that no one will answer. That sums up most of the security forums. Sorry for the rant; It'll be the only one like it.

Eliminate the OS. Boot to Linux - Ubuntu Live distro or whatever. BT5 Connect to your WiFi network. Download and run the wp4.sh script. (read the script so you know what it does) If still can't connect, make sure your pineapple has a default route (you'll see at the end of the script, there's a section on this. So, if your PC can get out to the Internet, and your Pineapple can, then you have a routing issue.

I have the same issue. Reaver doesn't work on 1.02; have BT5 running it against same targets and works fine.

You at least get the option, you need to update and install the package; I'm getting the same "No chain/target/match by that name" error. To add the extra nat options; opkg update opkg install iptables-mod-nat-extra

It's a routed port, you'll need to NAT. NAT isn't enabled. I've noticed this device takes a while after issuing this command for any "established" traffic to start NATing. root@Pineapple:~# iptables -A FORWARD -i eth1 -o wlan0 -s 172.16.42.0 -m state --state NEW -j ACCEPT root@Pineapple:~# iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT root@Pineapple:~# iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE I'm connected right now in the exact way you described having trouble with, running 1.02 firmware. (Connected to WiFi SSID Pineapple, LAN/POE connected to home Ethernet. iptables aren't persistent across reboots unless saved; issue iptables-save