walts

DUH! I was focusing on the "System Infusions" box - I never even thought about "User Infusions" , since, of course, I never wrote any. I never even noticed the "Show/Hide" button! Thank you, DataHead, for pointing out the obvious to a dunderhead! Walt

OK, I made a fresh start, flashing 2.3.0. Here are several screenshots that may help. screenshot 1 is just after the first login after setup .. Setup helpfully told me that I had an "Orphan" infusion on the SD card and installed it. Screenshot 2 is the pineapple bar immediately afterward. The I clicked on Pineapple Bar: Available. Screenshot 3 Finally I connected with Putty and went to the /pineapple/components/system/bar/files directory. I had to chmod +x the downloader and installer scripts, then I ran them Screenshot 4 Finally, I went back to the Installed tab, and there was my newly installed infusion Screenshot 5 Hopefully that will give you some ideas about how I can fix this. By the way, I did all this in Firefox. I'll try Chrome in a few minutes and let you know if there is any difference. EDIT: Chrome behaved the same as Firefox. Walt

Maybe I've been posting in the wrong forums. I am having a problem with the Pineapple Bar on my Mark V. The Pineapple Bar: Availaable tab only shows headings, never the list of infusions. I have learned how to install infusions manually, using the downloader and installer scripts in /pineapple/components/system/bar/files from a command prompt, but it would be a lot easier if I could get the menu working. I have reflashed the Pineapple numerous times, even using the "Bricked" procedure but nothing changes. Apart from reflashing (and making sure I'm connected to the Internet) no one in the Mark V forum has been able to help. Maybe I've just been asking in the wrong place. Does anyone have any ideas? Thanks, Walt

Yes, Foxtrot, I've reflashed several times, both following the "Bricked" procedure, and manually reflashing 2.2.0 and 2.3.0. Version 2.3.0 was installed both OTA and by SCPing the file from my PC and running the process manually on the Pineapple. I have the same symptoms with IE and Firefox. I'm running Windows 8.1. ZaraByte, I do have Internet available to the Pineapple (That's how I used the downloader script to get the infusions) and the Infusions I have tried all work correctly (nmap, tcpdump and site survey) and Karma behaves properly too. Then infusions I installed by hand do appear in the Installed tab of the Pineapple Bar This is a major jump for me - my last Pineapple was one of the original FON devices which I flashed Jasager flashed on - so I'm still getting used to the new structure and terminology. I'm curious about the fact that the scripts did not have Execute privileges, until I chmod'd them. Is there a "repair permissions" program I should run? Is there something in the flashing process that could be going amiss? The flashing take about 5 minutes, and I have always been able to immediately connect and log in on the Ethernet port to run the setup routines. Thanks for the help! Walt

I asked for help with the infusions menu here: https://forums.hak5.org/index.php?/forum/78-mark-v/ but no one answered. Can someone please help me? Here's what I've accomplished so far: - The scripts in /pineapple/components/system/bar/files did not have the execute bit set. I did a chmod +x. - Now I can manually run the downloader and installer scripts, and the infusions are installed properly. But still the Pineapple Bar:Available function does not work! It returns only the headers, no info on infusions. I can get along like this OK, but I'd really like to have the Pineapple Bar functioning. Thanks. Walt

I'm starting a new topic because they one is marked as "Answered" but the answers don't work for me: https://forums.hak5.org/index.php?/topic/34961-infusions-site-offline/ I have a Mark V Pineapple, and out of the box, the Infusions menu worked fine. Then I upgraded to version 2.3.0 and from then on I haven't been able to access any infusions. I can access the infusions website, and was able to download one of the infusion files manually, but apart from the file appearing in the "User Infusions" section, I don't know what to do with it. I have followed the "Unblocking" procedure more than once. After the latest attempt, I immediately went to the PineappleBar:Available. Meanwhile on my PC I captured the conversation using Wireshark. A connection was made to 52.149.31.76, and total of 30 packets went back and forth. I could see the initial SSL connection being made, then three packets of encrypted "Application data". The next packet was an "Encryption Alert" from 52.149.31.76 followed by a FIN,ACK packet to break the connection. On the Pineapple interface, the Infusions headers showed up, but with no data. This PC is a fresh inatall of Windows 8, upgraded to 8.1 with all the Microsoft patches installed. Please, can anyone help? Walt

Thanks for the help. I can get to the website you suggested - it looks like a text listing of all the available infusions. I unbricked the Pineapple as you suggested, and did nothing but set up the passwords and SSID. Then I immediately went to the PineappleBar:Available. meanwhile on my PC I captured the conversation using Wireshark. A connection was made to 52.149.31.76, and total of 30 packets went back and forth. I could see the initial SSL connection being made, then three packets of encrypted "Application data". The next packet was an "Encryption Alert" from 52.149.31.76 followes by a FIN,ACK packet to break the connection. On the Pineapple interface, the Infusions headers showed up, but with no data. This PC is a fresh inatall of Windows 8, upgraded to 8.1 with all the Microsoft patches installed. I'm truly stumped at this point. Is there a way I can download the infusions directly from the server to my PC and then copy them over to the Pineapple? Thanks Walt

BUMP! Please... I've cleared teh cache, checked /pineapple/components/system/bar/files/downloader and the commands are correct, Internet and DNS are good. Still, after a few seconds delay, I get only headings, not Infusions. Walt

When I was running 3.2.0, I saw several infusions in the Pineapple Bar when I clicked Pineapple Bar: Available. Before I went further, I decided I should upgrade to the latest release, 2.3.0. First I tried the OTA upgrade, and after about 15 minutes, I tried to reconnect, but could not, so I downloaded the file on my PC ans copied it over to /tmp/ on the Pineapple, and did the upgrade there. Everything worked fine, I can connect to the web interface, I have Internet connectivity, but Pineapple Bar: Available just gives me the headings. Any ideas are welcome. Can I download infusions directly and apply them as I did with the firmware? Walt

Still having some problems.... The OTA download went fine and the update process seemed to be working, but after 15 minutes I still couldn't connect over the wired ethernet connection. So, I downloaded the update file to my PC, SCP'd it over to the Pineapple and ran the upgrade there. That worked fine, but I had 2 infusions loaded via the Pineapple bar, and now when I try to get them back, I get the headers for the list of available infusions but no content. Where have the infusions gone? Can I download them on the PC and install them manually? Walt

I've been trying to set up connection sharing on my Mac running Yosemite following the instructions on the wiki: http://wiki.wifipineapple.com/#!ics.md but they must be for an older version of iOS. Specifically, I can get the Ethernet port configured as 172.16.42.42 and connect to the Pineapple web interface, and set up Internet Sharing to supposedly share my Wi-Fi connection over the Ethernet port. In step 5, there is no "bridge100" device showing in ifconfig. In step 6, the /etc/bootpd/plist has no mention of the 172.16.42 network, nor is there a key called net_range. Here's my bootpd.plist file: sh-3.2# cat bootpd.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>bootp_enabled</key> <false/> <key>detect_other_dhcp_server</key> <false/> <key>dhcp_enabled</key> <false/> <key>dhcp_ignore_client_identifier</key> <true/> <key>use_server_config_for_dhcp_options</key> <false/> </dict> </plist> sh-3.2# Any help would be appreciated. Walt

http://wiki.hak5.org/wiki/Universal_U3_LaunchPad_Hacker

bugmenot, search the forums for u3 installer - you'll learn a lot more than if I just gave you the link. bitzero, I apologize for taking so long to get back to you. If things settle down here, computerwise, maybe we can share the load, each of us masking some files and swapping. When we are sure they work OK we can post publicly. Of course if anyone else wants to join in the effort they are welcome! I still don't have a working environment to do this work in. I use a Mac and in the past have used my Boot Camp partition for U3 stuff, but the Boot Camp partition is now Windows 7 and I have XP in a virtual machine. I think, but have not yet proven, that the U3 installer will work in that environment. I should know within a week. The problem has been in the past that programs that like to work directly with the hardware won't run well in a virtual environment, and I'm unsure if the U3 installer fits that category. Once I finish building that VM I will know. Walt

I would love to see this project resurrected. I use it mostly in a "friendly" way, not to break into anyone's machine - unless they ask me to ;-) but it is annoying having to explain why their A-V has gone berserk! Since I have XP and Windows 7 VMs with a variety of A-V products available, I would be glad to contribute in testing, but I would need someone else to do the actual coding. It's been a while, but I think I can still remember how to build a new U3 device, given all the necessary files. Walt

You get to the Jasager screen by using a web browser pointing to the address you set up in the Jasager. I have the IP address of my Ethernet port on the Jasager set to 192.168.0.250, so with the Ethernet cable connected from the PC to the Jasager, I type http://192.168.0.250 for the Jasager screen and http://192.168.0.250/webif.html for the router maintenance screen. And yes, the Jasager should be able to connect mimicking any of the SSIDs your computer has in its list of previous connections. HTH Walt

DMilton, I hope you are feeling better! While we're waiting, I am doing a bit of work on the U3 version myself, and as soon as I am satisfied it's working I'll post the files. So far it's just been fine-tuning the batch files so they work on my various test systems. I'm wondering where I can find newer versions for some of the executables? Most of my Google searches turn up lots of posts about how to REMOVE these evil things, but no place to get the actual files themselves. Walt

OK I think I get it. Both ends nee to know the key before any packets are exchanged. Thinking further about it, Windows machines at least try to connect with every SSID they've ever associated with, so the likelihood of a given PC having an unencrypted SSID in its list are pretty good. So unless the operator is vigilant, they may well connect to us anyway, no? Walt

I've been wondering about that. I'm not totally familiar with the WEP packets, but if my understanding is correct, the connecting PC recognizes the AP based on its SSID, and then sends a packet encrypted with what it knows as the key for that SSID. If the AP agrees, the session is established. From then on the AP must decrypt the packets before sending them on to the Internet or wherever. Now we know that in the case of WEP, the key can be derived fairly quickly by flooding the connection with ARP requests; since the format of the ARP reply packets is well known, the key can be derived in relatively few packets. Given that there is room and CPU power on the FON, couldn't a WEP key decryptor be written to calculate the key? Once established, then the conversation could be decrypted and go along as usual with the decoded packets now available at the FON. Of course everyone should be using WPA. That's a whole different story! :) Walt

Thanks! I was unaware that there were different cables, other than the terminals on the ends. (my camera uses a "regular" USB cable!) I'll head out to get a Kyocera cable after the holidays. Walt

I was using the cli instead of the web interface to try to debug my Jasager setup. (I wanted to reduce the clutter on wireshark and I'm not very good at setting up capture filters) Anyway it worked and my Jasager setup is happy. The anomaly I noticed is that after karma_cli -s on Karma was certainly on - I could connect fine with a wireless PC, but the "Wlan" light on the Fon did not come on the way it does when I use the web interface. Is that by design, or does the web interface do something different than the cli? Walt (Curious, not complaining)

Maybe you can save me some grief. What do you mean by a usb-serial cable? I saw in the example where you were using a camera cable with a phone plug on the (unused) end, but don't the wires connect directly to the usb type A plug on the other end? What I've done so far (following the thread in the forum) I took a standard USB cable with a type A plug on one end and a mini-B on the other, and clipped off the mini-B connector. What I now have is the red wire connected to the "A" plug pin 1 (Vcc) the white to pin 2 (Data -) green to pin 3 (Data+) and black to pin 4 (Gnd). I checked that with a meter and with the usb standard. I was getting ready to connect the Data+ to Pin 2 on the Fon (Rx, yellow in the example) and Data- to pin 3 (Tx, red in the example) and Gnd to pin 5. If that doesn't work I was planning to reverse the Data+ and Data- Next on the XP end of things, is there anything I need to do to set up the connection? Walt

Thanks. I think the confusion about bridging came about from the ambiguity of the webif maintenance page. That's why I was thinking of re-flashing to get a "clean" start, but I like your idea better, of setting up static IP addresses for testing. I will try that tomorrow and post back what I find. Walt

Thanks. I'm beginning to think that my problem is more basic than that. Sorry for not being "artistic" but I'll try to describe what's happening. I have the FON connected to my Mac via wireless, connected to OpenWrt. with Karma "on" I connect to the FON from a Nokia N800 (Basically a Linux box with WIFI) N800 (192.168.0.216) <----> (?.?.?.?) FON (192.168.10.1) <--------> (192.168.0.180) Mac ifconfig on the FON does not show an IP address for ath0 or wifi0. With Wireshark running on the Mac, I can see web traffic for the control program going back and forth to the FON, but no traffic from the N800 passing through the FON to get to the outside. I do see a number of DNS refusals aimed at the FON but being sent to the Mac instead. So it looks to me as if the FON is not performing its bridging function correctly. I could re-flash it, but before I do I'd like to try to figure out what's going wrong. The web interface to OpenWrt doesn't seem to be all that friendly (per the wiki and my experience, the Network tab doesn't work reliably) so I've been working with /etc/config/network directly. Here is how it stands: root@OpenWrt:~# cat /etc/config/network # Copyright (C) 2006 OpenWrt.org config interface loopback option ifname lo option proto static option ipaddr 127.0.0.1 option netmask 255.0.0.0 config interface lan option ifname eth0 option type bridge option proto 'static' option ipaddr '192.168.10.1' option netmask 255.255.0.0 root@OpenWrt:~# I don't understand why there is no entry for ath0 or wifi0, and when you configure eth0 as "bridge", don't you need to say bridged to what? TIA for the help! Walt

HMMM.... I get what you're doing, but unfortunately the BSD Unix that underlies OS X does not have an iptables command. Instead that is replaced by ipfw which has a forwarding function, in you example it would be ipfw add allow ip from 10.1.1.0/24 to any fwd 192.168.2.1 (If I read the man pages correctly) Unfortunately that comes back with ipfw: unrecognized option [-1] fwd\n and further reading reveals that this only works if the kernel was compiled with IPFIREWALL_FORWARD. So, unless there's a Mac expert reading this who can clarify, I will probably go back to Windows and fight with that some more. Walt

Yes, please document it! I've been going nuts trying to get this working with Windows, with my WIFI network in 10.100 and the Jasager in 192.168. I have a Mac, and I'm fairly sure your Linux solution would work using the uderlying Unix on the Mac. Walt