Z4ub4d3 Posted November 14, 2013 Share Posted November 14, 2013 Hey everyone, Let me clear a few things up: SSLStrip: I know many of you are having issues. The easiest way to resolve them is build the fixes (uninstalling some python libraries, creating symlinks, installing sslstrip, etc) right into the SSLStrip infusion, at least right now. What I'll be doing this week, is adding a postinstall script to the SSLStrip package. That means it will run all of these fixes for you upon install. However, this is NOT a bug in the firmware. It is a bug in SSLStrip, at least with newer libraries. However, as we haven't changed SSLStrip or anything to do with it in 1.0.1, I'm not sure what is going wrong. Randomroll: The reason randomroll is broken is because of our recent security fixes. The fixes and the result were intentional though. What happens is that ANY file that is not in the /www/ folder has a file prepended and appended. Those check if you are logged in or not and potentially do a few different things in the future. The issue here is that Foxtrot is using symlinks, like he should, as the files are too large. So, the issue is that the files aren't actually in /www/ but rather in a subfolder of /sd/. So, the script we wrote will automatically protect any .php files there. So, how can we fix it? I'm sure Foxtrot will be pushing this as an update later, but for now, install randomroll as you normally would. Before setting it set up, SSH in and edit the following file: /sd/infusions/randomroll/assets/files/index.php. Go to the VERY end of the file and add <?php exit(); ?> to it. This needs to be the last entry in the file. Once you have completed that step, proceed setting up randomroll (especially the enable index.php). If you have already set up randomroll, first disable index.php and then do the above changes. Then re-enable it. Karma has in no way changed. It was just brought up in the context of the broken randomroll. I just wanted to clarify this as people might otherwise be deterred from upgrading. So, if overall the only complain is randomroll, I think it was a successful upgrade. Best Regards, Sebkinne I had a feeling that it was something along these lines. For my part, I carefully and intentionally worded my post so I never indicated a "bug", but that something was introduced, and perhaps expected behavior. This was an upgrade after all with improvements at the security level, and I had a suspicion this was the side effect of an improvement pushed in the new update and not unexpected. I'm glad to know what the issue is, fix it up, and get on with it, thanks again for taking such good care of us seb! We love you brother! :) i also did not think it was a bug per say in the update. although, karma was not working for me .. i think it was something i did though as after i reflashed the new update for the second time karma worked fine. /shrug (side note: whether introduced by untended behavior or changes when something breaks it is sort of a bug...) i must say, WOW!! Seb the turn around time on finding a fix for these issues is nothing short of amazing (no i am not sucking up, genuinely impressed). i have not yet implemented said fixes as i a not near my pineapple but will be doing so son as i can. as to randomroll being a big deal. um it kinda is. randomroll is the safest, least intrusive, most benign way to demonstrate to people just how vulnerable they leave themselves by using certain lazy measures. randomroll also entertains those being shown and those showing. my three cents (no longer two as it has been adjusted for inflation) Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted November 14, 2013 Author Share Posted November 14, 2013 i also did not think it was a bug per say in the update. although, karma was not working for me .. i think it was something i did though as after i reflashed the new update for the second time karma worked fine. /shrug (side note: whether introduced by untended behavior or changes when something breaks it is sort of a bug...) i must say, WOW!! Seb the turn around time on finding a fix for these issues is nothing short of amazing (no i am not sucking up, genuinely impressed). i have not yet implemented said fixes as i a not near my pineapple but will be doing so son as i can. as to randomroll being a big deal. um it kinda is. randomroll is the safest, least intrusive, most benign way to demonstrate to people just how vulnerable they leave themselves by using certain lazy measures. randomroll also entertains those being shown and those showing. my three cents (no longer two as it has been adjusted for inflation) Thank you! Kind words are always appreciated! I never said Randomroll wasn't a great infusion, or that it wasn't a big deal that it was broken. Just that fixing it isn't a big deal! An update to randomroll was already released, so all good now anyway ;) Best Regards, Sebkinne Quote Link to comment Share on other sites More sharing options...
totidem Posted November 15, 2013 Share Posted November 15, 2013 (edited) Help my pineapple has fallen and it can't get up! Hak5 Alert! How long does it typically take to complete the update? Started the update around 10 last night and its still flashing blue when I go up at 6:00. Edited November 15, 2013 by totidem Quote Link to comment Share on other sites More sharing options...
jermain69 Posted November 15, 2013 Share Posted November 15, 2013 (edited) Just a helpful hint to those challenged few such as me... If you aren't running the default AP name before the flash it's going to default back to it after. So I kept getting this pretty light show of solid green and Red Blue Orange consecutively but my laptop never reconnected to the AP. So I clicked on the wifi icon and it refreshed the list and I then noticed the default AP being broadcasted and once I connected to that it brought me through the initial setup process and the light show ended. I'm just a bit thick tonight but in the event that this helps anyone else from creating a softbrick/mental frustration... I don't mind admitting it. Having the same issue. Tried recovery mode. Says "Upgrade Failed, make sure you used the correct firmware,etc" Tried renaming the file from upgrade1.0.1 to upgrade 1.0.. No such luck. It started when i tried to update from the configuration tile. Said new update "Flash" , so i did. Need help on this one. Much thanks. Edited November 15, 2013 by jermain69 Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted November 15, 2013 Author Share Posted November 15, 2013 Having the same issue. Tried recovery mode. Says "Upgrade Failed, make sure you used the correct firmware,etc" Tried renaming the file from upgrade1.0.1 to upgrade 1.0.. No such luck. It started when i tried to update from the configuration tile. Said new update "Flash" , so i did. Need help on this one. Much thanks. You are not following the instructions. Follow https://wifipineapple.com/?flashing at the very bottom word by word and you'll have it working again. Quote Link to comment Share on other sites More sharing options...
jermain69 Posted November 15, 2013 Share Posted November 15, 2013 You are not following the instructions. Follow https://wifipineapple.com/?flashing at the very bottom word by word and you'll have it working again.Th Thanks Seb. Was watching the lovely booklet and not the site. Thanks much Quote Link to comment Share on other sites More sharing options...
thesugarat Posted November 15, 2013 Share Posted November 15, 2013 (edited) I'm seeing something funny in my syslog... any idea what all those 1798 errors are about? If wlan1 is busy (as mine is with client mode) what's trying to request DHCP from it?? 13:30:30 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:30:15 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:30:12 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:30:12 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:30:05 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:30:01 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:29:32 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:27:50 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:27:44 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:27:19 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:27:11 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:26:32 Pineapple kern.info kernel: [ 170.160000] usb 1-1.4: reset high-speed USB device number 4 using ehci-platform13:26:28 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:26:27 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:26:10 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:26:03 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:26:03 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan113:25:44 Pineapple cron.err crond[1678]: time disparity of 23075844 minutes detected13:25:21 Pineapple kern.info kernel: [ 99.200000] usb 1-1.4: reset high-speed USB device number 4 using ehci-platform16:01:14 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan116:01:10 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan116:01:10 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan116:01:08 Pineapple user.info sysinit: setting up led wlan116:01:08 Pineapple user.info sysinit: setting up led wlan016:01:08 Pineapple user.info sysinit: setting up led ethernet16:01:08 Pineapple daemon.info dnsmasq-dhcp[1798]: DHCPREQUEST(br-lan) 172.16.42.227 7c:d1:c3:df:94:6716:01:08 Pineapple daemon.info dnsmasq-dhcp[1798]: DHCPACK(br-lan) 172.16.42.227 7c:d1:c3:df:94:67 Allens-Air16:01:07 Pineapple user.notice firewall: Reloading firewall due to ifup of wan (wlan1)16:01:07 Pineapple daemon.info dnsmasq[1798]: using nameserver 8.8.8.8#5316:01:07 Pineapple daemon.info dnsmasq[1798]: using nameserver 64.134.255.2#5316:01:07 Pineapple daemon.info dnsmasq[1798]: using nameserver 64.134.255.10#5316:01:07 Pineapple daemon.info dnsmasq[1798]: using nameserver 192.168.8.1#5316:01:07 Pineapple daemon.info dnsmasq[1798]: using local addresses only for domain lan16:01:07 Pineapple daemon.info dnsmasq[1798]: using local addresses only for domain lan16:01:07 Pineapple daemon.info dnsmasq[1798]: started, version 2.66 cachesize 15016:01:07 Pineapple daemon.info dnsmasq[1798]: reading /tmp/resolv.conf.auto16:01:07 Pineapple daemon.info dnsmasq[1798]: read /etc/hosts - 1 addresses16:01:07 Pineapple daemon.info dnsmasq[1798]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth16:01:07 Pineapple daemon.info dnsmasq-dhcp[1798]: read /etc/ethers - 0 addresses16:01:07 Pineapple daemon.info dnsmasq-dhcp[1798]: DHCP, IP range 172.16.42.100 -- 172.16.42.249, lease time 12h16:01:06 Pineapple daemon.notice netifd: Interface 'wan' is now up16:01:05 Pineapple daemon.notice netifd: wan (1670): Sending select for 192.168.8.99...16:01:05 Pineapple daemon.notice netifd: wan (1670): Lease of 192.168.8.99 obtained, lease time 360016:01:05 Pineapple daemon.info hostapd: wlan0: STA 7c:d1:c3:df:94:67 IEEE 802.11: associated (aid 1)16:01:04 Pineapple daemon.info hostapd: wlan0: STA 7c:d1:c3:df:94:67 IEEE 802.11: authenticated16:01:03 Pineapple user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!16:01:03 Pineapple user.notice dnsmasq: Allowing 127.0.0.0/8 responses16:01:02 Pineapple daemon.notice netifd: wan (1670): Sending select for 192.168.8.99...16:01:01 Pineapple daemon.notice netifd: wan (1670): Sending discover...16:01:00 Pineapple kern.info kernel: [ 60.630000] wlan1: associated16:01:00 Pineapple kern.info kernel: [ 60.620000] wlan1: associate with 00:15:c6:28:dc:30 (try 1/3)16:01:00 Pineapple kern.info kernel: [ 60.620000] wlan1: RX AssocResp from 00:15:c6:28:dc:30 (capab=0x421 status=0 aid=117)16:01:00 Pineapple kern.info kernel: [ 60.600000] wlan1: send auth to 00:15:c6:28:dc:30 (try 1/3)16:01:00 Pineapple kern.info kernel: [ 60.600000] wlan1: authenticated16:01:00 Pineapple kern.info kernel: [ 60.140000] wlan1: authenticate with 00:15:c6:28:dc:3016:01:00 Pineapple auth.info sshd[1687]: Server listening on 0.0.0.0 port 22.16:00:58 Pineapple daemon.notice netifd: wan (1670): udhcpc (v1.19.4) started16:00:58 Pineapple daemon.notice netifd: wan (1670): Sending discover...16:00:58 Pineapple cron.info crond[1678]: crond: crond (busybox 1.19.4) started, log level 516:00:56 Pineapple daemon.info hostapd: wlan0: STA 7c:d1:c3:df:94:67 IEEE 802.11: authenticated16:00:53 Pineapple user.info sysinit: command failed: Device or resource busy (-16)16:00:52 Pineapple kern.info kernel: [ 52.830000] br-lan: port 2(wlan0) entered forwarding state16:00:50 Pineapple kern.info kernel: [ 50.830000] br-lan: port 2(wlan0) entered forwarding state16:00:50 Pineapple kern.info kernel: [ 50.820000] br-lan: port 2(wlan0) entered forwarding state16:00:50 Pineapple kern.info kernel: [ 50.770000] device wlan0 entered promiscuous mode16:00:45 Pineapple user.notice firewall: Reloading firewall due to ifup of lan (br-lan)16:00:44 Pineapple kern.info kernel: [ 44.970000] device eth0 entered promiscuous mode16:00:44 Pineapple daemon.notice netifd: Interface 'loopback' is now up16:00:44 Pineapple daemon.notice netifd: Interface 'lan' is now up16:00:43 Pineapple user.notice usb-modeswitch: 1-1.4:1.0: Manufacturer=Generic Product=Mass_Storage_Device Serial=058F0O1111B116:00:43 Pineapple user.notice usb-modeswitch: 1-1.1:1.0: Manufacturer=Manufacturer_Realtek_RTL8187_ Product=RTL8187_Wireless Serial=0013378142CB16:00:43 Pineapple kern.info kernel: [ 43.780000] usbserial: USB Serial Driver core16:00:43 Pineapple kern.info kernel: [ 43.780000] usbcore: registered new interface driver usbserial_generic16:00:43 Pineapple kern.info kernel: [ 43.770000] usbcore: registered new interface driver usbserial16:00:43 Pineapple kern.info kernel: [ 43.770000] USB Serial support registered for generic16:00:43 Pineapple kern.info kernel: [ 43.720000] usbcore: deregistering interface driver usbserial16:00:43 Pineapple kern.info kernel: [ 43.710000] usbcore: deregistering interface driver usbserial_generic16:00:43 Pineapple kern.info kernel: [ 43.710000] USB Serial deregistering driver generic16:00:43 Pineapple kern.info kernel: [ 43.160000] usbserial: USB Serial Driver core16:00:43 Pineapple kern.info kernel: [ 43.150000] usbcore: registered new interface driver usbserial_generic16:00:43 Pineapple kern.info kernel: [ 43.150000] USB Serial support registered for generic16:00:43 Pineapple kern.info kernel: [ 43.140000] usbcore: registered new interface driver usbserial16:00:43 Pineapple kern.info kernel: [ 43.060000] usbcore: deregistering interface driver usbserial16:00:43 Pineapple kern.info kernel: [ 43.060000] USB Serial deregistering driver generic16:00:43 Pineapple kern.info kernel: [ 43.050000] usbcore: deregistering interface driver usbserial_generic16:00:42 Pineapple user.notice usb-modeswitch: 1-1:1.0: Manufacturer=? Product=USB2.0Hub Serial=?16:00:42 Pineapple kern.info kernel: [ 42.410000] usbserial: USB Serial Driver core16:00:42 Pineapple kern.info kernel: [ 42.400000] usbcore: registered new interface driver usbserial_generic16:00:42 Pineapple kern.info kernel: [ 42.400000] USB Serial support registered for generic16:00:42 Pineapple kern.info kernel: [ 42.390000] usbcore: registered new interface driver usbserial16:00:42 Pineapple kern.info kernel: [ 42.220000] usbcore: deregistering interface driver usbserial16:00:42 Pineapple kern.info kernel: [ 42.210000] usbcore: deregistering interface driver usbserial_generic16:00:42 Pineapple kern.info kernel: [ 42.210000] USB Serial deregistering driver generic16:00:41 Pineapple user.notice usb-modeswitch: 1-0:1.0: Manufacturer=Linux_3.3.8_ehci_hcd Product=Generic_Platform_EHCI_Controller Serial=ehci-platform16:00:41 Pineapple kern.info kernel: [ 41.220000] usbserial: USB Serial Driver core16:00:41 Pineapple kern.info kernel: [ 41.210000] usbcore: registered new interface driver usbserial_generic16:00:41 Pineapple kern.info kernel: [ 41.200000] usbcore: registered new interface driver usbserial16:00:41 Pineapple kern.info kernel: [ 41.200000] USB Serial support registered for generic16:00:41 Pineapple kern.info kernel: [ 41.170000] usbcore: deregistering interface driver usbserial16:00:41 Pineapple kern.info kernel: [ 41.170000] USB Serial deregistering driver generic16:00:41 Pineapple kern.info kernel: [ 41.160000] usbcore: deregistering interface driver usbserial_generic16:00:40 Pineapple kern.info kernel: [ 40.300000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)16:00:40 Pineapple kern.info kernel: [ 40.050000] Adding 1004024k swap on /dev/sda2. Priority:-1 extents:1 across:1004024k16:00:40 Pineapple kern.err kernel: [ 40.250000] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities16:00:40 Pineapple kern.err kernel: [ 40.240000] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities16:00:38 Pineapple kern.info kernel: [ 35.920000] usbcore: registered new interface driver asix16:00:38 Pineapple kern.info kernel: [ 35.780000] usbserial: USB Serial Driver core16:00:38 Pineapple kern.info kernel: [ 35.770000] usbcore: registered new interface driver usbserial_generic16:00:38 Pineapple kern.info kernel: [ 35.760000] usbcore: registered new interface driver usbserial16:00:38 Pineapple kern.info kernel: [ 35.760000] USB Serial support registered for generic16:00:38 Pineapple kern.info kernel: [ 35.520000] usbcore: registered new interface driver ath9k_htc16:00:38 Pineapple kern.info kernel: [ 35.040000] xt_time: kernel timezone is -000016:00:38 Pineapple kern.info kernel: [ 34.330000] nf_conntrack version 0.5.0 (965 buckets, 3860 max)16:00:38 Pineapple kern.info kernel: [ 34.180000] NET: Registered protocol family 2416:00:38 Pineapple kern.info kernel: [ 33.950000] ip_tables: © 2000-2006 Netfilter Core Team16:00:38 Pineapple kern.info kernel: [ 33.690000] tun: © 1999-2004 Max Krasnyansky16:00:38 Pineapple kern.info kernel: [ 33.680000] tun: Universal TUN/TAP device driver, 1.616:00:38 Pineapple kern.info kernel: [ 33.650000] PPP generic driver version 2.4.216:00:38 Pineapple kern.info kernel: [ 33.390000] RPC: Registered tcp transport module.16:00:38 Pineapple kern.info kernel: [ 33.390000] RPC: Registered tcp NFSv4.1 backchannel transport module.16:00:38 Pineapple kern.info kernel: [ 33.380000] RPC: Registered udp transport module.16:00:38 Pineapple kern.info kernel: [ 33.380000] RPC: Registered named UNIX socket transport module.16:00:38 Pineapple kern.info kernel: [ 33.150000] Button Hotplug driver version 0.4.116:00:38 Pineapple kern.info kernel: [ 33.130000] usbcore: registered new interface driver rtl818716:00:38 Pineapple kern.info kernel: [ 33.130000] rtl8187: wireless switch is on16:00:38 Pineapple kern.info kernel: [ 33.120000] rtl8187: Customer ID is 0x4616:00:38 Pineapple kern.info kernel: [ 33.100000] ieee80211 phy1: hwaddr 00:13:37:81:42:cb, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 216:00:38 Pineapple kern.info kernel: [ 32.690000] usbcore: registered new interface driver rt2800usb16:00:38 Pineapple kern.info kernel: [ 32.660000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)16:00:38 Pineapple kern.info kernel: [ 32.650000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)16:00:38 Pineapple kern.info kernel: [ 32.640000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)16:00:38 Pineapple kern.info kernel: [ 32.630000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)16:00:38 Pineapple kern.info kernel: [ 32.630000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)16:00:38 Pineapple kern.info kernel: [ 32.620000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)16:00:38 Pineapple kern.info kernel: [ 32.610000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)16:00:38 Pineapple kern.info kernel: [ 32.600000] cfg80211: Regulatory domain changed to country: US16:00:38 Pineapple kern.info kernel: [ 32.600000] cfg80211: Calling CRDA for country: US16:00:38 Pineapple kern.info kernel: [ 32.590000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=216:00:38 Pineapple kern.info kernel: [ 32.530000] usbcore: registered new interface driver rt73usb16:00:38 Pineapple kern.info kernel: [ 30.980000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)16:00:38 Pineapple kern.debug kernel: [ 33.130000] Registered led device: rtl8187-phy1::tx16:00:38 Pineapple kern.debug kernel: [ 33.130000] Registered led device: rtl8187-phy1::rx16:00:38 Pineapple kern.debug kernel: [ 33.130000] Registered led device: rtl8187-phy1::radio16:00:38 Pineapple kern.debug kernel: [ 33.100000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'16:00:38 Pineapple kern.debug kernel: [ 32.590000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'16:00:38 Pineapple kern.debug kernel: [ 32.590000] ath: doing EEPROM country->regdmn map search16:00:38 Pineapple kern.debug kernel: [ 32.590000] ath: country maps to regdmn code: 0x3a16:00:38 Pineapple kern.debug kernel: [ 32.590000] ath: Regpair used: 0x3a16:00:38 Pineapple kern.debug kernel: [ 32.590000] ath: EEPROM indicates default country code should be used16:00:38 Pineapple kern.debug kernel: [ 32.590000] ath: Country alpha2 being used: US16:00:38 Pineapple kern.debug kernel: [ 32.590000] Registered led device: ath9k-phy016:00:38 Pineapple kern.debug kernel: [ 32.580000] ath: EEPROM regdomain: 0x0 By the way Seb, nice signature bar update... :) Very useful links. Edited November 15, 2013 by thesugarat Quote Link to comment Share on other sites More sharing options...
bASketCaSE Posted November 16, 2013 Share Posted November 16, 2013 Just to clarify should i upgrade my MARK V (wifipineapple.com) to 2.81 MD5 17e4384a79e7fef9c267f7da34ed4743 (under mark 4) or 1.0.1 MD5 2cd9f28a975d0d7cf270918adbf17370 2013-11-14 (under mark 5). Sorry, I just wanna be sure. Quote Link to comment Share on other sites More sharing options...
Z4ub4d3 Posted November 16, 2013 Share Posted November 16, 2013 (edited) 1.0.1 under mark V Edited November 16, 2013 by Z4ub4d3 Quote Link to comment Share on other sites More sharing options...
King Crimson Posted November 16, 2013 Share Posted November 16, 2013 I WANT MY TROLOLOLOL!!! :( Quote Link to comment Share on other sites More sharing options...
thesugarat Posted November 16, 2013 Share Posted November 16, 2013 Random Roll is working. Why don't you have your troll? Quote Link to comment Share on other sites More sharing options...
totidem Posted November 16, 2013 Share Posted November 16, 2013 (edited) Learned a few things when updating my Pineapple MK5. (After you restore your pineapple back to pre-brick condition:) 1. RTFM 2. Have a fresh SD card inserted before doing the update to 1.0.1 (refer to 1) NOTE: The Hak5 crew provided a way to format your SD without having to use another computer. Goto Resources->USB Info 3. Know your DIP Switch (refer to 1) 4. Don't blow away the SD that came with your purchase. (Don't be cheap, buy more!) BTW: To answer my own question. It doesn't take that long to complete the update. After Unbricking (AU) and Before Setup (BS) it was 5 minutes or less from start, download, install, reboot. Edited November 16, 2013 by totidem Quote Link to comment Share on other sites More sharing options...
thesugarat Posted November 16, 2013 Share Posted November 16, 2013 Nobody responded to my post above.... Anyone else seeing these errors in their syslog? Is it normal? 13:30:30 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan1 Quote Link to comment Share on other sites More sharing options...
Z4ub4d3 Posted November 16, 2013 Share Posted November 16, 2013 I am not seeing this error, sorry :( Quote Link to comment Share on other sites More sharing options...
Mit0s1s Posted November 16, 2013 Share Posted November 16, 2013 yup me neither, not seing this error. Quote Link to comment Share on other sites More sharing options...
jdoe Posted November 17, 2013 Share Posted November 17, 2013 Just wondering if anyone is still having the radio0/radio1 swapping issue? I know 1.0.1 was suppose to fix it, but it seems after every factory reset, as soon as I connect to an AP in client mode, wlan1 becomes radio0 and wlan0 becomes radio1 (and on occasion, even eth0 gets in on the radio action)... Quote Link to comment Share on other sites More sharing options...
thesugarat Posted November 17, 2013 Share Posted November 17, 2013 Thanks for looking… I'm not sure what it means. Quote Link to comment Share on other sites More sharing options...
shoeless89 Posted November 17, 2013 Share Posted November 17, 2013 The update finally let me connect to my network with the Realtek in client mode. Great work! Quote Link to comment Share on other sites More sharing options...
Sailor Posted November 17, 2013 Share Posted November 17, 2013 Nobody responded to my post above.... Anyone else seeing these errors in their syslog? Is it normal? 13:30:30 Pineapple daemon.warn dnsmasq-dhcp[1798]: no address range available for DHCP request via wlan1 I have had this in my log on both the Mark IV en V but never found a solution. It doesn't affect the workings though (as I know of). Quote Link to comment Share on other sites More sharing options...
sawks Posted November 17, 2013 Share Posted November 17, 2013 (edited) Hi, ive noticed a few people talk about wireless degradation since the update, and I've found the same. I was using the Mk5 without any problems, updated some of the infusions and generally surfing through the mk5 without problems. Then i spotted the upgrade, and upgraded. Then i went to set everything up and noticed really bad wireless connection from the mk5 to my access point. I tried to connect directly to the access point with no problem. As soon as i tried to download anything, or at random times i would loose ping to the internet from the pineapple and to the access point ip. You can see below, massive chunks of missing pings. So just to check i reset the pineapple and did a fresh install with the same experience. Then i put the backup of the card i got with 1.0.0 back in, and all was well again. No complaints, just thought I would share my experience. ... 64 bytes from 8.8.8.8: seq=216 ttl=44 time=18.759 ms 64 bytes from 8.8.8.8: seq=217 ttl=44 time=18.730 ms 64 bytes from 8.8.8.8: seq=251 ttl=44 time=1013.053 ms 64 bytes from 8.8.8.8: seq=252 ttl=44 time=18.584 ms 64 bytes from 8.8.8.8: seq=253 ttl=44 time=18.517 ms .... 64 bytes from 8.8.8.8: seq=16 ttl=44 time=18.943 ms 64 bytes from 8.8.8.8: seq=17 ttl=44 time=19.108 ms 64 bytes from 8.8.8.8: seq=18 ttl=44 time=20.621 ms 64 bytes from 8.8.8.8: seq=51 ttl=44 time=2016.394 ms 64 bytes from 8.8.8.8: seq=52 ttl=44 time=1016.505 ms 64 bytes from 8.8.8.8: seq=53 ttl=44 time=19.104 ms ... 64 bytes from 192.168.10.200: seq=92 ttl=64 time=1.310 ms 64 bytes from 192.168.10.200: seq=93 ttl=64 time=3.420 ms 64 bytes from 192.168.10.200: seq=168 ttl=64 time=1995.034 ms 64 bytes from 192.168.10.200: seq=169 ttl=64 time=995.277 ms 64 bytes from 192.168.10.200: seq=170 ttl=64 time=1.366 ms 64 bytes from 192.168.10.200: seq=171 ttl=64 time=10.327 ms 64 bytes from 192.168.10.200: seq=172 ttl=64 time=1.671 ms 64 bytes from 192.168.10.200: seq=173 ttl=64 time=1.700 ms ... EDIT: retried new update, had same problem. Disabled WLAN1 and enabled and all is good again. A few reboots, i can replicate the problem but shutting down WLAN1 and bringing it back up fixes it. No matter what, still love it. Edited November 17, 2013 by sawks Quote Link to comment Share on other sites More sharing options...
jjd Posted November 18, 2013 Share Posted November 18, 2013 (edited) Hi, ive noticed a few people talk about wireless degradation since the update, and I've found the same. I was using the Mk5 without any problems, updated some of the infusions and generally surfing through the mk5 without problems. Then i spotted the upgrade, and upgraded. Then i went to set everything up and noticed really bad wireless connection from the mk5 to my access point. I tried to connect directly to the access point with no problem. As soon as i tried to download anything, or at random times i would loose ping to the internet from the pineapple and to the access point ip. You can see below, massive chunks of missing pings. So just to check i reset the pineapple and did a fresh install with the same experience. Then i put the backup of the card i got with 1.0.0 back in, and all was well again. No complaints, just thought I would share my No matter what, still love it. Same issue here. I noticed it because when Internet sharing from wlan0 to wlan1 my client machine was timing out trying to load google. Same result when I did a Ping test. It does not seem to happen to me on every boot however but most. Edited November 18, 2013 by jjd Quote Link to comment Share on other sites More sharing options...
mreidiv Posted November 18, 2013 Share Posted November 18, 2013 (edited) I have found a small issue. When i click refresh on the small tile for WiFi Pineapple MK5 it says there is an update found but when i go to the large tile and click check for update there is none. Edited November 18, 2013 by mreidiv Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted November 18, 2013 Author Share Posted November 18, 2013 I have found a small issue. When i click refresh on the small tile for WiFi Pineapple MK5 it says there is an update found but when i go to the large tile and click check for update there is none. Thanks. Not a firmware issue, but a system infusion issue. Fix is coming to your local WiFi Pineapple bar soon! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.