lunokhod

I think a USB-Ethernet adapter would be a very elegant way to allow the WiFi Pineapple to connect into an existing internet "equipped" network. Android tether, WiFi Client and USB 3G being the other ways. Can't wait to hear more about this from the WiFi Pineapple team!

I think the Raspberry Pi might be a little underpowered for Metasploit.

I asked this question (after your original post). https://forums.hak5.org/index.php?/topic/31607-plugging-a-mk-v-into-a-dhcp-equipped-lan/ I was able to modify the Wifi Pineapple eth0 interface settings to get an IP address from an existing DHCP server on my Ethernet based network. You also need to disable the internal DHCP server "dnsmasq" (which is also a DNS forwarder), you don't want two arguing DHCP servers on one network. This sort of worked and I was able to access the WiFi Pineapple from computers on my lan, the default route worked fine and I could download infusions, etc. You need to be aware that any infusion or external scripting that requires the WiFi Pineapple to be found at 172.16.42.1 will NOT work when it gets assigned a different IP address by your DHCP server. Things like DNS spoofing might not work if dnsmasq is turned off and DNS requests bypass the WiFi Pineapple... not sure, just speculating. Clients that connect to your WiFi Pineapple would then get IP addresses from your networks DHCP server. Once again if an infusion expects the connected clients to be in a certain IP address range, things might not work as expected. In the end I reverted back to the original factory settings, too much weird stuff was happening.

This looks great. I'm going to try it out on my pen test lab at home in coming days. A quick question about deauth... in jasagerPwn the first item in CONFIGURATION / VARIABLES is :- # [System Information]deauth_interface="wlan0" # Interface for local deauthentication attacks I'd prefer to use my Alfa 036H plugged into the WiFi Pineapple as wlan2. Does jasagerPwn allow you to select which interface you want to use to deauth clients? I know I'll find this out when I get everything set up properly... :-) Regards, Lunokhod

Starting RandomRoll seemed to overwrite my index.php, error.php and redirect.php and did not restore them when stopped. I had to restore the files from /rom/www/

I should mention that I am connecting to the WiFi Pineapple in a slightly different way. Instead of a fixed IP address for eth0, I have modified the network file to allow eth0 to get an address via DHCP from my home network. I will change it back to the "factory default" fixed IP address and see if the same WiFi Manager behavior is seen.

It's the basic ifconfig up/down commands. The same thing happens when I click enable/disable in the Logical Interfaces section of WiFi Manager. Issue "ifconfig wlan0 down" There is no output on the terminal after issuing the command. When I check WiFi Manager I see this (MAC partially blanked!) :- Physical Interface radio0 [eth0] - HWAddr [00:13:37:xx:xx:xx] After "ifconfig wlan0 up" (still no output in SSH terminal), I see this in WiFi manager :- Physical Interface radio0 [wlan0] - HWAddr [00:13:37:xx:xx:xx] When wlan1 is disabled with the same method "ifconfig wlan1 down"... WiFi Manager shows this :- Physical Interface radio1 [-] - HWAddr [00:13:37:xx:xx:xx] It's not really a problem as such... I just want to know if this behavior is normal or not. Below is a separate observation not directly linked to WiFi Manager... I also notice that starting wlan0 (ifconfig wlan0 up or enabling wlan0 in WiFi Manager) does not start the access point on wlan0 (no blue LED and also confirmed by running airodump-ng on a Raspberry Pi & Alfa 036H). I have to uncheck the radio0 enable tick box, then "save" and "commit"... then recheck radio0 enable tick box and "save" and "commit" before the access point becomes "alive" and blue LED illuminates. Enabling and Disabling wlan0 via the Network Tile does appear to start and stop both the wlan0 interface and the access point operation as expected. Starting wlan0 via "ifconfig wlan0 up" or clicking enable in WiFi Manager also shows that wlan0 is enabled in the Network Tile. But until you disable and then enable in the Network Tile the wlan0 access point (and blue LED) does not operate. Lunokhod

I know it's not directly related to the WiFi Manager infusion, but this is where I see this interesting anomaly... Why does the radio0 physical interface get "associated" with eth0 when I disable wlan0?? Is this normal? Regards, Lunokhod

disabling wlan0 should stop it. if you connect to the Wifi Pineapple via wlan0 this will also stop.. just be careful you don't lock yourself out!

Maybe try the Yagi with vertical polarity? Most antennas on wireless routers/access points are vertically polarized.

Thanks awskier08!! That was quite simple (ashamed I didn't think of that ) and works perfectly. The br-lan interface got it's IP address via eth0 and the existing network DHCP server. Does this change also stop the WiFi Pineapples own DHCP server? I suppose a simple DIP solution would be to have two "network" files stored in the WiFi Pineapple... one left untouched for standalone operation with a directly Ethernet connected laptop (with internet sharing) and one for use on a LAN with an external DHCP. The default DIP switch setting could "cp /root/temp/network-default /etc/config/network" and another DIP switch setting would "cp /root/temp/network-lan /etc/config/network". Depending on the DIP switch setting this would copy the appropriate file (and rename it to "network"). Hopefully the DIP switch function operates BEFORE the network starts up. Might also need to restart eth0 to pick up the new settings. Of course approach this would undo any other changes that have been made in the /etc/config/network file on each boot of the Wifi Pineapple eg. for wireless interfaces. Lunokhod

I'm trying to update the time zone information on my Wifi Pineapple to give me local time. I've added time zone info for Australia/Adelaide in /usr/share/zoneinfo from a recently updated Raspberry Pi... then updated the symbolic link... ln -s /usr/share/zoneinfo/Australia/Adelaide /etc/localtime But I still am having no luck. root@Pineapple:/# date Tue Jan 21 09:50:22 GMT 2014 :( Time to create a Bug Report I think. Lunokhod

Hi Everybody, I'm still experimenting with my new Wifi Pineapple V and came across a scenario that I'd like some advice on. So far to get internet connectivity to my Mk V I have used internet connection sharing via a laptop connected directly to the Ethernet port and I have also configured wlan1 as a client to a nearby WiFi access point. Both of these methods have worked well. I'd also like be able to connect the Mk 5 to an existing wired LAN network (with internet access) via Ethernet and then access the Mk 5 via the network. This network has it's own DHCP server and router/gateway. As you know the Mk 5 has a fixed IP address and DHCP server to hand out IP addresses to clients. I'm thinking that I could possibly configure a DIP switch setting to disable the DHCP server on the Mk 5 at boot and enable dynamic addressing on the eth0 device. I could then find the IP address assigned to the Mk 5 via the gateway routers DHCP table. Has anyone else used a Mk5 in a situation like this? Lunokhod

Sorry to hi-jack the thread... but this is related to support... On top of page 2 in the little WiFi Pineapple booklet that came in the box it mentions registering your product (WiFi Pineapple serial number) at www.wifipineapple.com before you can use WiFi Pineapple techincal support. I have had a good look around www.wifipineapple.com and cannot find anywhere I can register my newly arrived WiFi Pineapple. Can anyone reading this thread point me in the right direction? Regards, Lunokhod.

Just be careful with batteries and solar power. I asked in a different thread how tolerant the Wifi Pineapple Mk5 is of over voltage and it seems from replies that it doesn't like much more than 12V. The float voltage of a 12V lead acid battery (incl. gel/SLA) is ~13.8V. A solar panel suited to charging a 12V battery will produce voltages far in excess of 12V... never hook one of these up to the MK5 without a regualtor of some kind. A good solar regulator for a 12V battery will keep the battery at around 13.8V when the sun is shining. It would be prudent to measure the open circuit voltage with a multimeter when exposed to full sunlight to make sure that it isn't allowing a higher voltage through to the Mk5. Lunokhod

Hi Everybody, I've have my WiFi Pineapple V for a week and today I have decided to sit down and have a play. First thing that I have noticed is that my time zone is not in the drop down list! :( I live in South Australia where we are normally 9.5 hours ahead of UTC. At the moment with daylight savings we are 10.5 hours ahead of UTC. Neither of these options are available so I can never set my WiFi Pineapple to my local time. The Northern Territory is also affected by this but they don't change for daylight savings, they stay at 9.5 hours ahead all year. There are a number of regions in the world that have weird time zones. There is even a 45 minute time zone in Australia and Nepal is 5.75 hours (5 hours 45 minutes) ahead of UTC. http://www.timeanddate.com/time/time-zones-interesting.html What is the best way to submit a "bug report" about this? The addition of a "daylights savings" check box would be good too... a simple way to add an hour to the local time offset. eg. +9.5 hours ahead of UTC becomes +10.5 hours... -5.0 hours behind UTC becomes -4.0 hours and so on. For now I am working in UTC... being a ham radio operator I am used to this. But it would be nice if the log files are named in local time. Lunokhod

yeah that would work... but I'm not a fan of the cigarette lighter plug system for power. I've been using 30A Anderson Power Poles for all my ham radio gear. Plus I like building stuff. :)

I've got some Traco Power TEN 9-2411WI DC-DC converters lying around here somewhere. I'll make up a small regulator for the Mark V. http://www.tracopower.com/products/ten8wi.pdf 9-36V in, 5V 1600 mA out. Plugs into a DIP-24 socket. I also like 'em because they are VERY RF quiet.

Oh well... that rules out using the Mark V in a car (at least while the engine is running) and in a remote situation where a battery is augmented with a solar charging system. I'll use an external TracoPower 5V regulator to give the Mark 5 a nice stable 5v power supply. I did the same thing with my Raspberry Pi Portable D-Star HotSpot. http://vk5rex.squarespace.com/photo-gallery/portable-hot-spot/

Well... I don't want to risk it, that's why I'm asking here. It would make sense to have a little leeway when in comes to the voltage input.

Hi Everybody, What is the absolute maximum voltage that can be applied to the DC input jack? I know it can handle 12 Volts, but how much more before damage will result? I'm thinking of situations where the Mark V is connected to a SLA battery AND a charging system that can raise the voltage above 12 V. Most lead acid batteries charge systems float around the 13.8 Volt level... some up to 14 Volts. I'd like to use the Mark V while in my car... but don't want to damage it. Same thing would apply to a solar panel & battery setup. Luno.