kpoeticg

deathdealerxx, you know there's a way around having *.com/*.htm show in the browser right?

If you're unable to connect your Pineapple to the internet through your Alfa card without tango mode then it has nothing to do with tango. It's the driver issue. If that's the case then 2.7.7 should work for you because it works for me =]

I don't have a second Pineapple so I can't help you with tango mode, but currently 2.8.0 has a driver issue with internet connections through the external Alfa. You should check if you can connect to your router using just the first Pineapple and your Alfa. With mine i can connect to my router through internal and broadcast my AP through my Alfa but using the Alfa to connect to my router doesn't authenticate no matter what i do. Just my two cents...

I just flashed the firmware about 2 minutes ago. I haven't started testing yet, I came here to check for any bricking issues first since i don't have a serial cable either. If you can give details about what caused your brick it could help prevent other testers like myself from doing the same thing. Thanks in advance...

I see. If you're using BackTrack 5 r2 I'm guessing you're using wicd for your network manager. I have the same issue with wicd, I couldn't get it to maintain both connections at the same time either. Since you're using a dated version of BackTrack I recommend upgrading to Kali which uses a different network manager instead of wicd which is able to maintain a wired and wireless connection at the same time. If there's some specific reason that you prefer to stay on r2 you should either find a different network manager compatible with it or figure out if there's a way to configure it in wicd.. Either way, it has nothing to do with the Pineapple. It's an issue with BackTrack. Edit: If you have access to a Windows install it wouldn't be a bad idea to set it up through Windows, connect to it, downoad the Network Manager infusion, get your Alfa connected to your network, and setup ipforwarding. That way once it's connected to your network u can connect to it in your BackTrack browser without an ethernet cable. Just use the ip you're router gives it instead of 172.16.42.1

How are you trying to connect to the internet specifically? Are you using an ethernet cable to your pc/laptop, or your router, or wifi? Either way the links in deathdealerxx's response should get you up and running.

Awesome Sebkinne, can't wait. Thank's SymPak, now I can finally use my Pineapple without flashing 5 times a day!! q=]

Ah so that's the catch. Yeah wlan0 will work for you. It's pointless though if Karma doesn't work. It feels like some kind of driver issue even though wlan1 works fine as an AP. I'm pretty positive it has nothing to do with any network settings because I have tried EVERYTHING! I just got my pineapple 2 weeks ago with no prior OpenWRT experience and now I can setup my wireless connections from scratch with no scripts or infusions in 3 minutes just from researching this issue. I'm hoping there's some sort of workaround like maybe a different driver for the NHA we can install from the repo. It sucks since the only reason i have the NHA is i bought the Pineapple Elite Pack. If i could figure out how to get the WPS button/Button Infusion to work with 2.7.7 it wouldn't be AS stressful. Hopefully one of the more Elite members with more experience can shed some light on one of these issue's or a bandaid to use til 3.0 goes into Beta Testing. Even if some1 knows how to make the Pineapple function properly with wlan0/phy0/radio0 as wan and wlan1/phy1/radio1 as lan would be very helpful...

I've figured out that on 2.8.0 radio0 connects perfectly to my wpa2 network. Is there any reason not to use wlan0 for wan and wlan1 for lan? Will there be any sort of sacrifice in functionality setting it up that way like karma, sslstrip, urlsnarf, or anything else reliant on radio0 running in AP mode?

WOW! I completely misread your question. Sorry about that. Must've not been paying attention and just saw connect and Windows. I'm editing that out so I only look stupid to the people that already read my answer. q=]

Same exact problem here. I have tried absolutely everything. Scoured the OpenWRT documentation. Added and removed every option possible in my /etc/config/wireless;network;and firewall. Played with the hostapd/pid/wpa_supplicant in /var/run, edited the /etc/defconfig/network file. Then I flash back to 2.7.7, set up my /etc/config/wireless and network files and it works flawlessly right from the jump with no scripts or infusions needed. I flash back and use all the same configurations and it absolutely will not work. I've have my wpa_supplicant.conf in /etc/. I used all the connect scripts on here, Tried with and without Network Manager, it's been drivin me nuts. Probly wasted like 60-80 hours flashing/reflashing/setting up/configuring in the past cpl weeks.I have the NHA from the hakshop too. On 2.7.7 it works flawlessly. But on 2.8.0 there's something that's absolutely blocking it from associating. I found kernel panic=3 in (i think it was the preinit file) and tried using it to get to the bottom of it but i've hit a brick wall with it. If anybody has any insight about what changes in 2.8.0 could possibly be causing this you would be helping out tremendously. Otherwise I guess I'm just gonna have to stick with 2.7.7 until the next firmware.

The uninstall of the modules occures through the interface but the reason everybody clicks uninstall on your module is because after you install it the name field is blank for only this infusion in the modules list so it's unusable. Then when you click remove all of the modules disappear. So aside from the disappearing of all the modules from the gui, you need to solve why you're module never appears in the gui after it is installed. The rest of the field is normal, just the name is blank so there's nothing to click on to open it.

Network Manager's an insusion. There's no networkmanager in the repo

It's only this one. And like I said, it seems like it's only removing everything from the gui for some reason. The amount of memory in storage stays the same from before it removes the modules through reinstalling them all. So they're still there somewhere. Just can't access them. And after reinstalling the modules they are all still configured from before it removed them.

I get the same screen as DyFukA. Also when I click remove it removes every single Module from the Infusions menu. It seems as though it only removes them from the menu though because the used and free memory doesn't change at all. Even when reinstalling them all one by one the memory stays the same and alll the sub-packages for all the modules remain installed