Sebkinne

Not sure if nodogsplash serves .css files. I'd suggest you put the CSS into style tags inside the .html pages. Best Regards, Sebkinne

Visit your WiFi Pineapple Bar through the Pineapple's webinterface! Best Regards, Sebkinne

I'd say c++ if you want a binary. If you are fine with a Java executable, I suggest Java for this. Yes, you may hate the language but when it comes to easy UI building, graphs and portability, Java has proven very useful. Plus it is dead easy and there is a lot of documentation on pretty much everything. Best Regards, Sebkinne

I'm guessing if Firefox doesn't work yet, there are still some remains of the adware. You might need to clean out any extensions there / check the application data. Glad I could help! Sebkinne

Sure! It's pretty simple, just an endless while look with an if statement checking the name variable which breaks it out of the loop. #!/bin/bash while true; do echo -n Enter BSSID: read name [[ "$name" == "exit" ]] && { echo Exiting. break } || { echo $name >> /tmp/blacklist.txt name="" } done Best Regards, Sebkinne

Ah yes, this is easy. See all those console errors? At first I thought you had some plugins installed. It might still be this, a failing / multiple failing browser plugins / extensions. Then I googled the names of some of those websites requested. Seems like you have a virus! Anyway, that's dodgey traffic it's loading and that's breaking your JS. Remove any plugins / viruses that are breaking your browser and it'll all be good again! Best Regards, Sebkinne Edit: It doesn't need to be a virus. It could very well be a plugin that is adding a little bit of 3rd party content to generate money. This is probably more likely. Either way, you probably DON'T want that on your machine..

Could you do me a favor and try chrome again? This time, open the developer console and check the console log. Open up the interface again and then post any errors you see here. Also, in the developer console, check the network tab. Do any requests get 500 errors? Best regards, Sebkinne

Everything is supposed to be there, indeed. Do you have Javascript turned off? Best regards, Sebkinne

The pineapple does reboot. It's possible it got got stuck because of a bug in the password setter. We used or use a fifo queue to run the passwd command. This has now changes from version 1.1.0 onwards.

Would you try again? The issue should have been resolved! The issue will not happen again in the future - an upgrade to the pineapple bar will be pushed along with 1.1.0 later this week. Best Regards, Sebkinne

I'm finishing off a large post about these types of issues right now. We'll get it sorted out even if it goes over the 30 day mark.

Karma is NOT broken. It works just like it used to. The issue is that some newer devices have stopped probing for networks, something that is required for karma to function on those devices.

To do this, you'll need to run tcpdump on the pineapple, on br-lan. You could capture to file and analyze this somewhere else if you wanted. Best regards, Sebkinne

If you are connected to eth0, you are automatically on the same vlan as anyone on wlan0. But realistically, you'd want to sniff br-lan as that is the bridge interface. Best Regards, Sebkinne

It also focuses on ease of use. The fact that you have DIP switches, a simple webinterface and a way to expand the base functionality with user contributed infusions really allows you to speed things up. It's also a great tool to learn from and get a deeper understanding of what is happening. To sum up, I'd say: Size (it's tiny and has two radios, USB and SD card slot), Price, ease of use, and supporting Hak5. There are different reasons that different people have for buying a Pineapple. This is just a small list of general things. Best Regards, Sebkinne

It's called a placeholder element. Depending on what browser you use, it's quite obvious. Glad you figured it out! Best Regards, Sebkinne

You'll need a serial cable. Information is available on our website and on this forum. You'll need to search for it. Best regards, Sebkinne

First of all, you posted in the wrong forum. This is the WiFi Pineapple MKV forum. I have moved your thread to the correct forum. The WiFi Pineapple MKIV firmware can be found here. 2.8.1 is the latest stable firmware. 3.0.0 is a development release.

Rhino, The AP121U is what the MK4 was based on. The WiFi Pineapple MKV is custom hardware and cannot be purchased somewhere else. You are of course welcome to install the MK4 firmware on the AP121U. Best regards, Sebkinne

I'm confused as to why you bought a USB stick for this. We only support the SD card for infusions (and lots of other things). USB would be used for extra user storage such as you moving files back and forth between your machine and the pineapple.. Also, you can still execute commands just like you could on the MK4.. Best regards, Sebkinne

You never stated what you problem is. What's happening?

Damn, customs must have something against you! ;) Glad you have it, enjoy! Best Regards, Sebkinne

Hey James010 and welcome to the forums! First of all, let me explain the LEDs: Green: Power (Always on as long as power hits the board) Blue: Wlan0 (Should always be on, might not if miss-configured or turned off. Flickers on transmission.) Red: wlan1 (Not on unless active and connected to a wireless network in clientmode) Amber: eth0 (On as long as ethernet is plugged in. Flickers on transmission.) Note: There is a difference between blinking/flashing and flickering Now that it's clear that the LEDs don't really help, I'd ask you to re-consider the title of this post as others have had issues with a steady blinking/flashing amber light on first boot! Either way, it would be important to know what you were doing before the wireless interfaces both died. Did you use the "wifi manager" infusion from the WiFi Pineapple Bar? You might have erased your configuration or messed it up there. The reason I ask is because a hardware failure affecting both cards is extremely rare. Therefore it will be a configuration issue. If you want a quick fix, simply perform a factory reset via the webinterface or DIP switches. Best Regards, Sebkinne

Actually, using macchanger isn't always recommended. If you search for macchanger in this forum you will get a thread with a nice script that handles it gracefully for you. We are including it into our systems soon. Best Regards, Sebkinne

It's probably the pipe not playing nicely. I'll fix it right away - will make it to 1.1.0 ;) Best Regards, Sebkinne