Pineapple seems to freeze after being on for a few minutes

[jman012]

As I said, I'm having a problem where, after the Pineapple has been on for only several minutes, it crashes/freezes. This is after running the wp4.sh script with default settings: internet sharing, pinging, ssh, and the web interface all work fine. When it crashes/freezes the Wlan, Lan, WPS, and Power lights on the device are still on and everything, but pinging gives no results, and it is impossible to SSH into it, or access the web interface. This usually requires a reboot to fix, when after yet another few minutes it'll crash/freeze. When I leave it alone for a bit it seems to take longer to crash. After the crash, re-running the wp4.sh script does not fix the matter.

For instance, one time it stayed up for quite a while, until we tried installing something through the web interface (randomroll), and at about 90% of the way through it crashed/froze. Has anyone else encountered this problem and is there any solution? Even after reflashin with a fresh install the problem persisted so I'm not sure what else to do. Thanks

• Pineapple Hardware Version (ex: Mark III, Mark IV, etc.): Mark IV
• Pineapple Software Version (ex: 2.5.0, 2.6.4): 2.8.1
• OS used to connect to the pineapple: Kali Linux
• Network layout of how your setup is connected (including IP information): laptop connected to pineapple through ethernet and connected to the internet through wireless router. Using the wp4.sh script to create connection and internet sharing between the laptop and pineapple. All network settings default and this does work when the pineapple is initially turned on. Am able to connect to it through both ssh and the web interface for a few minutes before it crashes/freezes
• All the tools/options that are running on the pineapple when the issue happened: Fresh flashed pineapple with nothing extra added in at all
• Ping results from computer to pineapple: For the first 5 or so minutes the pineapple responds to ping requests and everything fine. Can access it through web and ssh. After a few minutes however it stops responding everywhere. No ping back with an error of "Destination Host Unreachable" and web and ssh are both down as well. The entire thing seems to completely freeze.
• Is the problem repeatable (Yes/No): Yes, every time I start up the pineapple it crashes after 5 minutes. Have to reboot to regain access and then it happens again
• Steps taken which created the problem: Just leave it sitting there for about 5 minutes
• Error Messages: --
• Log file information(use spoiler tags for large logs): Here are the most recent logfiles from the pineapple right after a fresh flash of 2.8.1 in case there's anything useful in there:

21:00:17 Pineapple authpriv.notice dropbear[1642]: Password auth succeeded for 'root' from 172.16.42.42:44374

21:00:14 Pineapple authpriv.warn dropbear[1642]: Bad password attempt for 'root' from 172.16.42.42:44374

21:00:12 Pineapple authpriv.warn dropbear[1642]: Bad password attempt for 'root' from 172.16.42.42:44374
21:00:07 Pineapple authpriv.info dropbear[1642]: Child connection from 172.16.42.42:44374
00:01:43 Pineapple kern.info kernel: [ 103.640000] br-lan: port 1(eth0) entered forwarding state
00:01:41 Pineapple kern.info kernel: [ 101.640000] eth0: link up (1000Mbps/Full duplex)
00:01:41 Pineapple kern.info kernel: [ 101.640000] br-lan: port 1(eth0) entered forwarding state
00:01:41 Pineapple kern.info kernel: [ 101.640000] br-lan: port 1(eth0) entered forwarding state
00:01:40 Pineapple kern.info kernel: [ 100.140000] eth0: link down
00:01:40 Pineapple kern.info kernel: [ 100.140000] br-lan: port 1(eth0) entered disabled state
00:01:05 Pineapple user.info sysinit: setting up led WLAN
00:01:05 Pineapple user.info sysinit: setting up led WAN
00:01:05 Pineapple user.info sysinit: setting up led USB
00:01:05 Pineapple user.info sysinit: setting up led LAN
00:01:05 Pineapple user.info sysinit: Selected interface 'wlan0'
00:01:05 Pineapple user.info sysinit: OK
00:01:04 Pineapple kern.info kernel: [ 64.650000] br-lan: port 2(wlan0) entered forwarding state
00:01:02 Pineapple kern.info kernel: [ 62.650000] br-lan: port 2(wlan0) entered forwarding state
00:01:02 Pineapple kern.info kernel: [ 62.640000] br-lan: port 2(wlan0) entered forwarding state
00:01:02 Pineapple kern.info kernel: [ 62.490000] device wlan0 entered promiscuous mode
00:01:01 Pineapple kern.info kernel: [ 61.270000] device wlan0 left promiscuous mode
00:01:01 Pineapple kern.info kernel: [ 61.270000] br-lan: port 2(wlan0) entered disabled state
00:01:01 Pineapple daemon.info dnsmasq[1444]: using nameserver 8.8.8.8#53
00:01:01 Pineapple daemon.info dnsmasq[1444]: using local addresses only for domain lan
00:01:01 Pineapple daemon.info dnsmasq[1444]: using local addresses only for domain lan
00:01:01 Pineapple daemon.info dnsmasq[1444]: started, version 2.62 cachesize 150
00:01:01 Pineapple daemon.info dnsmasq[1444]: reading /tmp/resolv.conf.auto
00:01:01 Pineapple daemon.info dnsmasq[1444]: read /etc/hosts - 1 addresses
00:01:01 Pineapple daemon.info dnsmasq[1444]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack
00:01:01 Pineapple daemon.info dnsmasq-dhcp[1444]: read /etc/ethers - 0 addresses
00:01:01 Pineapple daemon.info dnsmasq-dhcp[1444]: DHCP, IP range 172.16.42.100 -- 172.16.42.249, lease time 12h
00:00:57 Pineapple user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
00:00:57 Pineapple user.notice dnsmasq: Allowing 127.0.0.0/8 responses
00:00:54 Pineapple authpriv.info dropbear[1385]: Running in background
00:00:53 Pineapple cron.info crond[1368]: crond: crond (busybox 1.19.4) started, log level 5
00:00:52 Pineapple kern.info kernel: [ 52.620000] br-lan: port 2(wlan0) entered forwarding state
00:00:51 Pineapple daemon.notice netifd: wan (904): Sending discover...
00:00:50 Pineapple kern.info kernel: [ 50.620000] br-lan: port 2(wlan0) entered forwarding state
00:00:50 Pineapple kern.info kernel: [ 50.610000] br-lan: port 2(wlan0) entered forwarding state
00:00:50 Pineapple kern.info kernel: [ 50.570000] device wlan0 entered promiscuous mode
00:00:48 Pineapple daemon.notice netifd: wan (904): Sending discover...
00:00:47 Pineapple user.notice ifup: Enabling Router Solicitations on loopback (lo)
00:00:46 Pineapple user.notice ifup: Enabling Router Solicitations on lan (br-lan)
00:00:46 Pineapple kern.info kernel: [ 46.960000] br-lan: port 1(eth0) entered forwarding state
00:00:45 Pineapple daemon.notice netifd: wan (904): Sending discover...
00:00:44 Pineapple kern.info kernel: [ 44.960000] eth0: link up (1000Mbps/Full duplex)
00:00:44 Pineapple kern.info kernel: [ 44.960000] br-lan: port 1(eth0) entered forwarding state
00:00:44 Pineapple kern.info kernel: [ 44.960000] br-lan: port 1(eth0) entered forwarding state
00:00:44 Pineapple kern.info kernel: [ 44.360000] device eth0 entered promiscuous mode
00:00:44 Pineapple daemon.notice netifd: wan (904): udhcpc (v1.19.4) started
00:00:44 Pineapple daemon.notice netifd: Interface 'loopback' is now up
00:00:44 Pineapple daemon.notice netifd: Interface 'lan' is now up
00:00:42 Pineapple user.notice usb-modeswitch: 1-0:1.0: Manufacturer=Linux_3.3.8_ehci_hcd Product=Generic_Platform_EHCI_Controller Serial=ehci-platform
00:00:39 Pineapple kern.warn kernel: [ 0.680000] m25p80 spi0.0: found mx25l6405d, expected m25p80
00:00:39 Pineapple kern.warn kernel: [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
00:00:39 Pineapple kern.warn kernel: [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
00:00:39 Pineapple kern.notice kernel: [ 10.640000] SCSI subsystem initialized
00:00:39 Pineapple kern.notice kernel: [ 9.700000] JFFS2 notice: (452) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (0 unchecked, 0 orphan) and 12 of xref (0 dead, 3 orphan) found.
00:00:39 Pineapple kern.notice kernel: [ 2.940000] Bridge firewalling registered
00:00:39 Pineapple kern.notice kernel: [ 0.750000] 0x0000007f0000-0x000000800000 : "art"
00:00:39 Pineapple kern.notice kernel: [ 0.750000] 0x000000050000-0x0000007e0000 : "firmware"
00:00:39 Pineapple kern.notice kernel: [ 0.740000] 0x0000007e0000-0x0000007f0000 : "nvram"
00:00:39 Pineapple kern.notice kernel: [ 0.740000] 0x000000650000-0x0000007e0000 : "kernel"
00:00:39 Pineapple kern.notice kernel: [ 0.730000] 0x000000550000-0x000000650000 : "rootfs_data"
00:00:39 Pineapple kern.notice kernel: [ 0.720000] mtd: partition "rootfs" set to be root filesystem
00:00:39 Pineapple kern.notice kernel: [ 0.710000] 0x000000050000-0x000000650000 : "rootfs"
00:00:39 Pineapple kern.notice kernel: [ 0.710000] 0x000000040000-0x000000050000 : "u-boot-env"
00:00:39 Pineapple kern.notice kernel: [ 0.700000] 0x000000000000-0x000000040000 : "u-boot"
00:00:39 Pineapple kern.notice kernel: [ 0.690000] Creating 7 MTD partitions on "spi0.0":
00:00:39 Pineapple kern.notice kernel: [ 0.690000] 7 cmdlinepart partitions found on MTD device spi0.0
00:00:39 Pineapple kern.info kernel: [ 35.020000] usbcore: registered new interface driver rtl8187
00:00:39 Pineapple kern.info kernel: [ 34.870000] usbcore: registered new interface driver rt73usb
00:00:39 Pineapple kern.info kernel: [ 33.530000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
00:00:39 Pineapple kern.info kernel: [ 33.530000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
00:00:39 Pineapple kern.info kernel: [ 33.520000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
00:00:39 Pineapple kern.info kernel: [ 33.510000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
00:00:39 Pineapple kern.info kernel: [ 33.500000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
00:00:39 Pineapple kern.info kernel: [ 33.500000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
00:00:39 Pineapple kern.info kernel: [ 33.490000] cfg80211: World regulatory domain updated:
00:00:39 Pineapple kern.info kernel: [ 33.490000] cfg80211: Calling CRDA to update world regulatory domain
00:00:39 Pineapple kern.info kernel: [ 33.370000] compat.git: wireless-testing.git
00:00:39 Pineapple kern.info kernel: [ 33.370000] Backport based on wireless-testing.git master-2013-02-22
00:00:39 Pineapple kern.info kernel: [ 33.360000] Compat-drivers backport release: compat-drivers-2013-01-21-1
00:00:39 Pineapple kern.info kernel: [ 32.410000] eth0: link down
00:00:39 Pineapple kern.info kernel: [ 12.000000] USB Mass Storage support registered.
00:00:39 Pineapple kern.info kernel: [ 11.990000] usbcore: registered new interface driver usb-storage
00:00:39 Pineapple kern.info kernel: [ 11.990000] Initializing USB Mass Storage driver...
00:00:39 Pineapple kern.info kernel: [ 11.870000] uhci_hcd: USB Universal Host Controller Interface driver
00:00:39 Pineapple kern.info kernel: [ 11.750000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
00:00:39 Pineapple kern.info kernel: [ 11.620000] hub 1-0:1.0: USB hub found
00:00:39 Pineapple kern.info kernel: [ 11.620000] hub 1-0:1.0: 1 port detected
00:00:39 Pineapple kern.info kernel: [ 11.620000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
00:00:39 Pineapple kern.info kernel: [ 11.600000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
00:00:39 Pineapple kern.info kernel: [ 11.570000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
00:00:39 Pineapple kern.info kernel: [ 11.560000] ehci-platform ehci-platform: Generic Platform EHCI Controller
00:00:39 Pineapple kern.info kernel: [ 11.550000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
00:00:39 Pineapple kern.info kernel: [ 10.960000] usbcore: registered new device driver usb
00:00:39 Pineapple kern.info kernel: [ 10.950000] usbcore: registered new interface driver usbfs
00:00:39 Pineapple kern.info kernel: [ 10.950000] usbcore: registered new interface driver hub
00:00:39 Pineapple kern.info kernel: [ 6.950000] eth0: link up (1000Mbps/Full duplex)
00:00:39 Pineapple kern.info kernel: [ 2.960000] Freeing unused kernel memory: 208k freed
00:00:39 Pineapple kern.info kernel: [ 2.950000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
00:00:39 Pineapple kern.info kernel: [ 2.940000] 8021q: 802.1Q VLAN Support v1.8
00:00:39 Pineapple kern.info kernel: [ 2.930000] TCP cubic registered
00:00:39 Pineapple kern.info kernel: [ 2.930000] NET: Registered protocol family 17
00:00:39 Pineapple kern.info kernel: [ 2.920000] ag71xx ag71xx.0: eth1: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
00:00:39 Pineapple kern.info kernel: [ 2.370000] eth1: Atheros AG71xx at 0xb9000000, irq 4
00:00:39 Pineapple kern.info kernel: [ 1.330000] eth0: Found an AR7240/AR9330 built-in switch
00:00:39 Pineapple kern.info kernel: [ 0.780000] eth0: Atheros AG71xx at 0xba000000, irq 5
00:00:39 Pineapple kern.info kernel: [ 0.780000] ag71xx_mdio: probed
00:00:39 Pineapple kern.info kernel: [ 0.720000] mtd: partition "rootfs_data" created automatically, ofs=550000, len=100000
00:00:39 Pineapple kern.info kernel: [ 0.680000] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
00:00:39 Pineapple kern.info kernel: [ 0.660000] console [ttyATH0] enabled, bootconsole disabled
00:00:39 Pineapple kern.info kernel: [ 0.660000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
00:00:39 Pineapple kern.info kernel: [ 0.650000] io scheduler deadline registered (default)
00:00:39 Pineapple kern.info kernel: [ 0.650000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
00:00:39 Pineapple kern.info kernel: [ 0.640000] msgmni has been set to 56
00:00:39 Pineapple kern.info kernel: [ 0.640000] io scheduler noop registered
00:00:39 Pineapple kern.info kernel: [ 0.630000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
00:00:39 Pineapple kern.info kernel: [ 0.630000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) © 2001-2006 Red Hat, Inc.
00:00:39 Pineapple kern.info kernel: [ 0.600000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.600000] NET: Registered protocol family 1
00:00:39 Pineapple kern.info kernel: [ 0.590000] UDP hash table entries: 256 (order: 0, 4096 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.590000] TCP reno registered
00:00:39 Pineapple kern.info kernel: [ 0.580000] TCP: Hash tables configured (established 1024 bind 1024)
00:00:39 Pineapple kern.info kernel: [ 0.570000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.570000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.570000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.560000] Switching to clocksource MIPS
00:00:39 Pineapple kern.info kernel: [ 0.560000] NET: Registered protocol family 2
00:00:39 Pineapple kern.info kernel: [ 0.550000] bio: create slab at 0
00:00:39 Pineapple kern.info kernel: [ 0.100000] MIPS: machine is ALFA NETWORKS Hornet-UB
00:00:39 Pineapple kern.info kernel: [ 0.090000] gpiochip_add: registered GPIOs 0 to 29 on device: ath79
00:00:39 Pineapple kern.info kernel: [ 0.090000] NET: Registered protocol family 16
00:00:39 Pineapple kern.info kernel: [ 0.080000] pid_max: default: 32768 minimum: 301
00:00:39 Pineapple kern.info kernel: [ 0.080000] Mount-cache hash table entries: 512
00:00:39 Pineapple kern.info kernel: [ 0.000000] Writing ErrCtl register=00000000
00:00:39 Pineapple kern.info kernel: [ 0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
00:00:39 Pineapple kern.info kernel: [ 0.000000] Readback ErrCtl register=00000000
00:00:39 Pineapple kern.info kernel: [ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.000000] NR_IRQS:51
00:00:39 Pineapple kern.info kernel: [ 0.000000] Memory: 29132k/32768k available (2102k kernel code, 3636k reserved, 404k data, 208k init, 0k highmem)
00:00:39 Pineapple kern.info kernel: [ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
00:00:39 Pineapple kern.info kernel: [ 0.000000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
00:00:39 Pineapple kern.debug kernel: [ 35.050000] ath: doing EEPROM country->regdmn map search
00:00:39 Pineapple kern.debug kernel: [ 35.050000] ath: country maps to regdmn code: 0x37
00:00:39 Pineapple kern.debug kernel: [ 35.050000] ath: EEPROM regdomain: 0x833a
00:00:39 Pineapple kern.debug kernel: [ 35.050000] ath: EEPROM indicates we should expect a country code
00:00:39 Pineapple kern.debug kernel: [ 35.050000] ath: Country alpha2 being used: GB
00:00:39 Pineapple kern.debug kernel: [ 6.380000] Registered led device: alfa:blue:wps
00:00:39 Pineapple kern.debug kernel: [ 6.380000] Registered led device: alfa:blue:wlan
00:00:39 Pineapple kern.debug kernel: [ 6.380000] Registered led device: alfa:blue:wan
00:00:39 Pineapple kern.debug kernel: [ 6.380000] Registered led device: alfa:blue:usb
00:00:39 Pineapple kern.debug kernel: [ 6.380000] Registered led device: alfa:blue:lan
00:00:39 Pineapple kern.debug kernel: [ 0.610000] PCI: CLS 0 bytes, default 32

• Anything else that was attempted to 'fix' the problem: Reflashed the pineapple over ssh to new firmware 2.8.1 - - no success

[Sebkinne]

Hey Jman012,

I haven't seen this behavior before, but let's see if we can help you out.

First of all, can you time the time between booting and crashing? Is it always the same (if left alone)?

How are you powering the Pineapple? Wall / USB / battery etc? If this happens over USB, have you tried the wall adapter?

Does the Pineapple get hot? Best way to test this is by taking it out of the case and seeing if a specific spot overheats. That would seem like faulty hardware.

Did you buy the pineapple through the hakshop or was it a DIY one? If DIY, have you attemted a new clean flash over serial? I doubt that would fix anything but worth a shot.

Thanks for giving such a detailed report, I wish everyone did this. I hope we can get you back up and running.

Oh, one last thing: Has this happened since a specific point in time or did you get it and it has been doing this since the beginning?

Best Regards,

Sebkinne

[jman012]

First of all, can you time the time between booting and crashing? Is it always the same (if left alone)?

It's literally about 5 minutes. I just timed it right now and it was about 4:55 or so (+- maybe 5-10 seconds since i looked away while it was pinging). It's pretty constant but I've seen it sometimes take a minute or two longer and in other cases when I'm downloading a package like randomroll (with nothing else major running at the same time), it will crash as well. However, as I said, all the LEDs remain on. PWR, USB are on and LAN and WLAN are blinking.

How are you powering the Pineapple? Wall / USB / battery etc? If this happens over USB, have you tried the wall adapter?

It's plugged into the wall through the adapter it came with.

Does the Pineapple get hot? Best way to test this is by taking it out of the case and seeing if a specific spot overheats. That would seem like faulty hardware.

I don't think it's overheating as feeling the outside everything seems cool and fine, however I haven't taken it out of the case to check specific parts. I can do this later

Did you buy the pineapple through the hakshop or was it a DIY one? If DIY, have you attemted a new clean flash over serial? I doubt that would fix anything but worth a shot.

Hakshop! Got it around the holidays when the sales were going on. Played with it for a while but hadn't touched it in a couple months. Just got it and my alfas out of my laptop bag to setup with my new laptop to start using it again now that I have more time and ran into this problem.

Thanks for giving such a detailed report, I wish everyone did this. I hope we can get you back up and running.

No problem! I know how hard it is to diagnose problems when not given enough information so I made sure to get everything I possibly could. Please let me know if there's anything else I can get for you to help figure out the problem.

Oh, one last thing: Has this happened since a specific point in time or did you get it and it has been doing this since the beginning?

I don't recall problems like this when I first got it. I would sometimes have the pineapple reboot (indicated by the led's turning off) because of what I think was probably overusage of memory, but not like this where it apparently is freezing yet not rebooting. It's very odd which is why I posted here - I have no clue how to solve this.

Thanks so much for your reply! I hope we can figure this issue out so I can go back to being able to use the pineapple!

Edited June 24, 2013 by jman012

[jman012]

Sorry to bump this, but do you have any idea as to what the problem could be?

[Mr-Protocol]

I would say downgrade to the last "Stable" firmware release and see if the problem persists. It's kind of drastic but hey worth a shot to test hardware.

[jman012]

So, I had a revelation!

I've found out that the Pineapple is not the source of the problem here. I was intrigued at how the Pineapple had its lights still on after "freezing". Well I tried connecting another device to it through it's SSID and sure enough it connected, and pinging it works fine. So this means that the problem is the connection from my computer (where I run the wp4.sh to give internet) and the Pineapple.

My computer is an Asus EEE laptop running the latest (1.0.3) version of Kali Linux, and I think the problem is with the Network Manager. This explains my problems because leaving the Pineapple idle doesn't disrupt the connection, it only does after SSH and Web activity where Network Manager might be ruining the connection.

wp4.sh runs fine initially since I get a connection at first, but again, re-running it doesn't seem to help. The Ethernet cord to the Pineapple is in the correct port.

Anyways so I tried disabling the Network Manager and manually connecting to internet (tethered iPhone) which worked fine. But again, after running wp4.sh after a few minutes the connection was once again disrupted.

Any new ideas into this?

[Foxtrot]

So, I had a revelation!

I've found out that the Pineapple is not the source of the problem here. I was intrigued at how the Pineapple had its lights still on after "freezing". Well I tried connecting another device to it through it's SSID and sure enough it connected, and pinging it works fine. So this means that the problem is the connection from my computer (where I run the wp4.sh to give internet) and the Pineapple.

My computer is an Asus EEE laptop running the latest (1.0.3) version of Kali Linux, and I think the problem is with the Network Manager. This explains my problems because leaving the Pineapple idle doesn't disrupt the connection, it only does after SSH and Web activity where Network Manager might be ruining the connection.

wp4.sh runs fine initially since I get a connection at first, but again, re-running it doesn't seem to help. The Ethernet cord to the Pineapple is in the correct port.

Anyways so I tried disabling the Network Manager and manually connecting to internet (tethered iPhone) which worked fine. But again, after running wp4.sh after a few minutes the connection was once again disrupted.

Any new ideas into this?

Try disabling network manager and making sure WICD is closed, then run the script

-Foxtrot

[jman012]

Try disabling network manager and making sure WICD is closed, then run the script

-Foxtrot

Just tried this. Killed the network manager and made sure wicd was closed while running the wp4 script and still no dice. After only a couple minutes of being connected over ssh, was disconnected again with the pineapple becoming unreachable. Am only able to run a couple commands before this keeps happening. I have no clue what is causing the issue as now I've tried it on two different computers, one running kali and one running just ubuntu and it's happening on both machines. Seems like no matter what i do, even quitting all network managers isn't stopping this problem. What I don't understand is why the connection jsut randomly breaks after a certain amount of time. And why would restarting the pineapple and re-running wp4 fix the problem yet just rerunning wp4 doesn't. What would even cause that? It just doesn't make sense to me....

Edited June 26, 2013 by jman012

[jman012]

Well the Pineapple got bricked after trying to upgrade it (because the connection was lost again). After buying the serial connector to flash it manually, everything is working again! I guess the problem was more low-level stuff that required an entire reflashing, not just an upgrade of firmware. But it's all fixed, able to install infusions, have users connect to it, and run the modules, etc.

[Foxtrot]

Well the Pineapple got bricked after trying to upgrade it (because the connection was lost again). After buying the serial connector to flash it manually, everything is working again! I guess the problem was more low-level stuff that required an entire reflashing, not just an upgrade of firmware. But it's all fixed, able to install infusions, have users connect to it, and run the modules, etc.

Good to hear you solved it :), If you would, mark the thread Solved :)

-Foxtrot