sygo

I don't think stronger is necessarily what I need. Sometimes I need to be a bit stealthier so I go with the tiny 4 dBi and place myself reasonably close to target, if it's a wide area that I'm trying to survey of if I'm asked to assess what can be done from the Lobby then I'll use the 9 dBi. If I need to be in the parking lot or the building across the road I go with the Hawking for power and also because it's somewhat directional (meh, hit or miss - also, I didn't take a picture of the tripod I use with the Hawking) That 6 dBi though is the one that is in my bag ALL the time. it's just a really good compromise between dBi's and length. If I'm ever doing security awareness training and I need to do something on the spot that's the antenna I go for.

I had already posted this here, but here's some new pics: ready for action:

@Scanner Martel, my turn to apologize for the delay (I have no excuse though. LOL) would you please boot the pinapple, insert the usb drive and post the dmesg somewhere? (pastebin or something, no need to flood the forum with it) I need data in order to keep troubleshooting this with you :)

the sandisk 4gb should work with no problems at all with the pineapple powered via USB. you might want to measure the output of that usb port (if its a laptop some ports could be a little under 5, if it's a non powered hub and you have a few devices connected you might also notice a decrease in power being delivered)

I've been messing with the CSS files as well and I was thinking of creating an infusion that would let you chose themes. The one thing that I noticed was that existing infusions use their own CSS and they seldom call the pineapple's CSS for 'inspiration'. that means I'd need to create not only css files for the pineapple's default UI but also go through every infusion installed and change those for consistency. what I'm doing right now is running a script that copies the original css to a backup file and then I use sed to substitute name colors, it's fairly limited but it works. whenever I want to reset the theme I just copy the backup over the altered css. here's the theme I've been working on: get it here: https://gist.github.com/sygo/5116790

I'm shooting in the dark, but when you start the fdisk part press c before doing anything, that will toggle the DOS compatibility mode. might be worth a shot. if that fails try using cfdisk (same concept: sudo cfdisk /dev/sdb). It's a bit more modern than fdisk and you might get better results, it's menu based so it's hard to explain how to do stuff, but I'm sure you'll figure it out. Delete whatever is there and create everything again. Make sure the FS type is Linux and swap for sdb1 and sdb2, respectively.

Ready for this? Commands in bold. -- actually the forum ate my bolds... you'll figure it out right? get to your linux box, plug in your thumb drive. 1 -- Lets figure out what device the thumbdrive is associated with [xetic@board][0][~]> cat /proc/partitions major minor #blocks name 8 0 58605120 sda 8 1 248832 sda1 8 2 1 sda2 8 5 58353664 sda5 254 0 58352636 dm-0 254 1 56328192 dm-1 254 2 2023424 dm-2 8 16 3910656 sdb 8 17 3910640 sdb1 the last device on that list is sdb, fairly safe to assume that's it. But your milage may vary, so adapt accordingly, it might be sdc, sdd... etc. and if it's something other than sdb, make sure you substitute sdb in every command below to reflect your setup. (sudo every command or 'su -i' from now on to get the rest of this done) 2 -- lets partition the device with fdisk: root@board:/home/xetic# fdisk /dev/sdb WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). 3 -- lets delete all the partions currently there, I only have one because its a brand spanking new flash drive, you might have more, repeat the 'd' command and increment the partition number until there's none left: (the first command 'p' will print all your partitions) Command (m for help): p Disk /dev/sdb: 4004 MB, 4004511744 bytes 116 heads, 51 sectors/track, 1322 cylinders Units = cylinders of 5916 * 512 = 3028992 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 1323 3910640 b W95 FAT32 Command (m for help): d Selected partition 1 4 -- Let's create new partitions, this is a 4gb sundisk, so there no reason not to copy this verbatim: Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-1322, default 1): Using default value 1 Last cylinder, +cylinders or +size{K,M,G} (1-1322, default 1322): +3G Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (1065-1322, default 1065): Using default value 1065 Last cylinder, +cylinders or +size{K,M,G} (1065-1322, default 1322): <just press enter> Using default value 1322 5 -- Lets mark the second partiton as a swap partition, use the 't' command and pick hexcode 82: Command (m for help): t Partition number (1-4): 2 Hex code (type L to list codes): 82 Changed system type of partition 2 to 82 (Linux swap / Solaris) 6 -- Lets print it again and see if it looks good and procede to save (w) and quit (q): Command (m for help): p Disk /dev/sdb: 4004 MB, 4004511744 bytes 116 heads, 51 sectors/track, 1322 cylinders Units = cylinders of 5916 * 512 = 3028992 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 1064 3147286+ 83 Linux /dev/sdb2 1065 1322 763164 82 Linux swap / Solaris Command (m for help): wq The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) Syncing disks. Epic... now... I forgot to dismount the drive to begin with, it's all good...lets do it now: root@board:/home/xetic# umount /dev/sdb1 7 -- lets create the ext4 filesystem on it root@board:/home/xetic# mkfs.ext4 /dev/sdb1 mke2fs 1.41.12 (17-May-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 244800 inodes, 977660 blocks 48883 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1002438656 30 block groups 32768 blocks per group, 32768 fragments per group 8160 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done 8 -- Lets create the swap partition: root@board:/home/xetic# mkswap /dev/sdb2 Setting up swapspace version 1, size = 763160 KiB no label, UUID=831002c2-e123-4018-90ab-a4c7ca116935 We're done! turn off the pineapple, slap the flashdrive on it, boot it up. try the 'free' command, also 'df -h' on the pinapple. Huge Success??

the fact that in /dev you have a device called sda is half of the problem solved, but now you need to figure out why it's not seeing/mounting any partitions. mkswap /dev/sda won't do much because you're telling it to make swap space not on a partition, but on the device itself. what you need is something like mkswap /dev/sda2 (that means, device 'a' on partition '2' of that same device) I'm going to do a quick tutorial on how to set all of this up using the command line, once you go though that lets see if the problem persists. give me a few minutes and I'll get back to you.

check it out: your pineapple isn't happy with that partition table. Can you try going through the motions again and go through that initial post you mention with the tutorial to create the thumb drive? Caveats to look for: - that "take ownership" check box...it HAS to be off. - make sure that those changes to fstab are exactly the same and just to be extra paranoid: could you use the wall brick to feed power to the pineapple while we're troubleshooting this? feeding it power via USB is cool on the run, but if you're at your desk (or whatever) the external power supply won't hurt one bit.

That was totally my bad. The command should be dmesg | tail -n 50 (-f is something totally different...all I want is the last 50 lines of your dmesg after you plug in the drive, so if all else fails type in dmesg and copy paste everything after "USB disconnected" or something along those lines) if you've pugged in several drives with the same result I suspect the problem might be the way you are setting up the drive...especially on the red hat box...it should recognize pretty much anything.

you're right if lsusb lists the device it knows it's there, but it might not now what to do with it. Lets try this: after your pineapple has booted remove and reinsert the thumb drive and then do dmesg | tail -f 50 you might see stuff that is irrelevant but eventually you'll see a line saying that you removed the USB device and then a lot of output referring to when you plugged it back in. if you could paste that dmesg output here we might get a few more clues as to what is happening. (I think that poster before me was trying to ask what brand/model/size thumb drive you're using)

It's certainly enough if you can live with the storage. I personally don't have a problem with 4gb, whatever I do with the pineapple has to be encrypted ASAP, so whatever logs end up on the thumb drive will soon be on an encrypted filesystem. Small storage forces me to be disciplined when it comes to data sanitation. And $DIVINITY knows I need all the incentive I can get. That being said, I do believe that the inconsistency with usb thumb drives is due to power contraints. I base this on the fact that if I plug that 16Gb Sundisk Fit directly into the pineapple it complains a good deal and fails to do anything with the device: [ 521.290000] usb 1-1: USB disconnect, device number 2 [ 527.260000] usb 1-1: new high-speed USB device number 3 using ehci-platform [ 542.380000] usb 1-1: device descriptor read/64, error -145 [ 557.610000] usb 1-1: device descriptor read/64, error -145 [ 557.840000] usb 1-1: new high-speed USB device number 4 using ehci-platform [ 572.960000] usb 1-1: device descriptor read/64, error -145 [ 588.190000] usb 1-1: device descriptor read/64, error -145 [ 588.420000] usb 1-1: new high-speed USB device number 5 using ehci-platform [ 593.450000] usb 1-1: device descriptor read/8, error -145 [ 598.580000] usb 1-1: device descriptor read/8, error -145 [ 598.810000] usb 1-1: new high-speed USB device number 6 using ehci-platform [ 603.840000] usb 1-1: device descriptor read/8, error -145 [ 608.970000] usb 1-1: device descriptor read/8, error -145 [ 609.080000] hub 1-0:1.0: unable to enumerate USB device on port 1 but if I plug in a powered USB hub into the pineapple and plug the same 16Gb in the hub, it's happiness all around: [ 976.970000] usb 1-1: new high-speed USB device number 7 using ehci-platform [ 977.120000] hub 1-1:1.0: USB hub found [ 977.120000] hub 1-1:1.0: 7 ports detected [ 977.420000] usb 1-1.2: new high-speed USB device number 8 using ehci-platform [ 977.550000] hub 1-1.2:1.0: USB hub found [ 977.550000] hub 1-1.2:1.0: 3 ports detected [ 977.830000] usb 1-1.2.1: new full-speed USB device number 9 using ehci-platform [ 978.050000] usb 1-1.2.2: new full-speed USB device number 10 using ehci-platform [ 978.430000] usb 1-1.2.3: new low-speed USB device number 11 using ehci-platform [ 982.520000] usb 1-1.1: new high-speed USB device number 12 using ehci-platform [ 982.660000] scsi1 : usb-storage 1-1.1:1.0 [ 983.660000] scsi 1:0:0:0: Direct-Access SanDisk Cruzer Fit 1.26 PQ: 0 ANSI: 5 [ 983.660000] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 983.680000] sd 1:0:0:0: [sda] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 983.680000] sd 1:0:0:0: [sda] Write Protect is off [ 983.690000] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 983.690000] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 983.710000] sda: sda1 sda2 [ 983.730000] sd 1:0:0:0: [sda] Attached SCSI removable disk [ 984.460000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 984.750000] Adding 953320k swap on /dev/sda2. Priority:-1 extents:1 across:953320k again, I need to run a bunch more tests, I know that if I use my external battery juice pack to feed the pineapple (it's a Unu 11000mAh dual usb that feeds out 5v at 1A or 2.1A depending on the usb port you use) the 16Gb usb doesn't work either. So it doesn't seem to be an amp issue. I need to run a multimeter on this hub and see what voltage it's feeding the usb ports, if it's above 5, that might just be it! my theory might be flawed, I'm looking at the hardware for issues/solutions, but there's much i dont't know regarding the inner workings of HALs and such, it might just be a logical issue.

You know that "wait...what if..." feeling you sometimes get? I had it about a week ago so I rolled up my sleeves and came up with this: Still with me? cool! check it out: The pineapple fits in a standard Lenovo hard-drive slot, albeit there is a significant amount of work involved to pull that off: The biggest issue is height, namely that condenser (blue arrow) but that is an easy fix... just swap it out for one with similar specs and bend it a little. the other big issue are the ethernet ports. Now the ethernet ports are a PITA to swap around and fit inside such a small enclosure, I purchased a pci-e ethernet card (didn't work on my lenovo, it would have been GLORIOUS if I could make everything but the antenna self-contained) off of which ended up just using the ethernet connector (red arrow), I hardwired everything and routed the cable under the metal part on the side of the enclosure. The next height issue was the power connector which I didn't want to desolder (more on that later) so I just sanded off the extra-height with a rotary tool and its now a snug fit. (green arrow) I did some reading and turns out SATA has a bunch of options when it comes to power: 5.5v, 12v, 3.3v, everything comes through that big sata power connector, so I decided to leverage on that. I got 5.5v from the sata and now the pineapple is pretty much self contained inside the laptop. Caveats? I'm not sure if it's the laptop or the cheesy hard drive tray, but I could never get any power from those wires that wasn't 5.5v, my multimeter said all the other power cables were dead, downside to that: that USB thumb drive is limited in size since it seems that any Sundisk Fit above 4gb (perhaps 8, I ordered one on amazon, I'll get back to you guys soon) requires more power than the 5.5v powered pineapple is willing to give it. (a 16gb worked sporadically, the 32Gb never worked at all) Im sure that if I could get 12v to it, it would be a different story. Why didn't I want to desolder the power connector? because if power came solely from the sata connector there would be no way to reset the pineapple, I always need that external power source to push the button and power up :/ You'll notice that the WAN port is MIA (yellow arrow), it could certainly be salvaged and all the wires re-routed, but it would require some hacking on that sata connector (literal hacking, I'd have to saw off that mofo and figure out a way to keep it in place) Comments, concerns and ideas for improvement are always welcome :)