Zylla

"Cannot execute binary file: exec format error" That error message is typical if you are trying to execute a binary file compiled for another cpu-architecture. For example when trying to run 64-bit binaries on a x86 operating-system. What architecture-type are your Ubuntu installation? That SDK is for 64-bit.

Yes you can. I made this package specifically for those interested in only using ssltrip+ and dns2proxy, as it originally was a part of my Mana Toolkit. https://github.com/adde88/sslstrip-hsts-openwrt

Try doing exactly this below, and report back the output you're getting. cd /home/user/OpenWrt-SDK-15.05-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/ ./mips-openwrt-linux-uclibc-gcc test.c -o test If it manages to find the command "mips-openwrt-linux-uclibc-gcc" after doing this, you are having issues with your environment variables somehow not working.

Same password does not mean that you're using the same type of encryption. And i'm not only thinking about: WEP, WPA. WPA2. But also: TKIP, AES, TKIP+AES (WPA/WPA2). If the encryption-type used on the AP differs, the client will not connect. Also, you do not need to clone the MAC to get clients to connect. It's enough to copy the SSID+enc.key. Hope this will help you a bit :)

You don't need high privileges to use gcc, or any part of the SDK. (You can run it as root, but it's not adviced.) IF the PATH variable is setup correctly, you should be able to find "mips-openwrt-linux-uclibc-gcc" When you issue a command in the terminal it looks through all the folders in the PATH variable to find the file you are trying to execute. The reason we're adding the toolchain/bin directory to PATH is so that you can launch the "mips-openwrt-linux-uclibc-gcc" command in that terminal session. (That file is located within the toolchain/bin directory) If you add the "export PATH" and "export STAGING_DIR" command to ~/.bashrc you will get persistence for you user, and won't need to execute them every time you start a new terminal session.

Yes. I used an exact copy of the Makefile and "patch-files" on my SDK.

"Generating to much traffic." Now that's odd. Here's another link for you :) https://mega.nz/#!CokDRIqB!RFihHl9iCgkvrbSYwebjwYwchHreP_OFfUnfWDo72hc

I'm running Kali Rolling 2016.2 (x64) - with kernel 4.9.0.

After extracting that file, you will find the toolchain dir under staging_dir. You need to export STAGING_DIR and PATH as i showed you above.

You are trying to build OpenWRT. You are NOT downloading a specific SDK to compile binaries for that exact version of OpenWRT, which i thought you wanted to do. If you wanted to cross-compile stuff for you WiFi Pineapple TETRA/NANO, you would download and extract this file: https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/OpenWrt-SDK-15.05-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar.bz2

For example. here are my two variables: export PATH=$PATH:/home/zylla/OpenWrt-SDK-15.05-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/ export STAGING_DIR=/home/zylla/OpenWrt-SDK-15.05-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/staging_dir

make menuconfig make V=s This is used when you're using the SDK to build packages, and even entire firmware-images. Not if you're just using the toolchain to compile a simple c-file. If i'm going to help you more, i'm going to have to know exactly what you wrote when you set your two variables. Because it looks like it's not set correctly. If it was, it should have recognized the command: "mips-openwrt-linux-uclibc-gcc"

kbeflo: Here's you IPK for Shellinabox :) https://www.dropbox.com/s/0us3dibiqkpnwuc/shellinabox_2.10-1_ar71xx.ipk?dl=1

Yes. https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/packages/gcc_4.8.3-1_ar71xx.ipk gcc for Chaos Calmer 15.05. This one is for the ar71xx (mips) There are lots of other archs. and openwrt-versions supported.

Yes you can. I have both OpenWRT and the new "LEDE" version running in VMware (using the x86_64 arch.) I'm not emulating mips, though you can do that using QEMU. Btw "Kerravon": I just noticed your gcc command is not correct. You're supplying the "-o" (output) argument two times. Also, please show me your PATH variable and your STAGING_DIR variable. Also, i need the folder path to where you extracted the OpenWRT-SDK.

If you read though the cross-compile section you will find some info about adding the toolchain dir to your PATH variable, and also the STAGING_DIR variable. Then you can launch the gcc compiler, or Makefile through the terminal inside the folder of the stuff you're trying to compile. mips-openwrt-linux-uclibc-gcc -o output_binary csample.c CC=mips-openwrt-linux-uclibc-gcc LD=mips-openwrt-linux-ld make ./configure --build=x86_64-unknown-linux-gnu --host=mips-openwrt-linux-uclibc ^ Some sample commands you can use inside your project-folder after having setup your PATH variable correctly. (On your linux-desktop) This will not create a IPK, but simply compile your code for a different cpu-architecture.

I can try to compile it a bit later today if you want (a bit busy at the moment). But by just glancing over it fast i would say that it should compile just fine. :)

To install GCC on your Pineapple Nano you need to issue: opkg update opkg install gcc --dest sd If you have a Tetra, just remove "--dest sd" from that command. (gcc and its dependencies takes up some megabytes of space) Regarding the SDK you can download the correct OpenWRT SDK (which you can use to cross-compile binaries for the latest Pineapple on your desktop) here: https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/OpenWrt-SDK-15.05-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar.bz2 I'm going to have to refer to the links i posted above about using the SDK/Toolchain, because it's to much information for me to go in depth with in just a single post. But you should be able to get started cross-compiling after reading them thoroughly. If you just need to compile a few bytes of code without much dependencies, just download gcc on your pineapple and test it. Be warned. If you're trying to compile stuff that are "heavy"/big on your Pineapple with gcc, you most likely will need to compile alot of dependencies as well. And not everyone compiles as easy on the Pineapple as on your desktop. (Different cpu architecture)

You can use both iwconfig and iw to set the interface channel. Examples: iwconfig wlan0 channel 11 iw dev wlan0 set channel 11 Your interface can only be in 'one channel at a time'. When attacking/listening for a specific AP that you know the channel of, it would we wisest to set your interface to the same channel, to not miss out any packets. When airodump-ng is using "all channels" it is automatically hopping through all the channels. (Staying on one channel for a few milliseconds, before jumping to the next) So for that "brief period of time" that you are not on the same channel as your target, you will miss out on any packets transmitted at that time.

For OpenWRT you can theoretically use gcc, like you would on any other linux version. If your goal is to compile C-code to run on a openwrt-distro. I would recommend that you start by downloading the correct SDK for your OpenWRT version (and CPU), and also check out these links below: https://wiki.openwrt.org/doc/devel/crosscompile https://wiki.openwrt.org/doc/howto/obtain.firmware.sdk

Have you tested it without wlan2 attached? Just curious :)

If you are referring to the Pineapples interface on the windows machine, then it's because that interface does not provide your machine with a internet connection. Glad you got it sorted out ! :)

You're not exactly providing a lot of information as to what you are doing exactly, and it's not easy to help when we don't have exact details. What are you talking about here exactly? I'm guessing it's the Pineapple website: http://172.16.42.1:1471 Is that correct? If you have lost the password to login to your Pineapple, you can use the reset button (which is located on the Pineapple) to reset it to its factory default setttings.

iwconfig, which you used on you Linux machine, displays your wireless interfaces. (On you linux machine) And as far as i can see, you Linux machine seems to be connected to WifiLAN over wlp2s0. I'm guessing that this is where you get internet from. After running wp6.sh you linux machine should then "share" this connection to the Pineapple's interface. This interface i cannot see, because it's not a wireless interface. ifconfig would be better to pinpoint which interface belongs to the Pineapple. That interface should btw have an IP like this: 172.16.42.42 ifconfig eth1 172.16.42.42/24 What happens if you try to SSH to the Pineapple, or even browse to it: http://172.16.42.1:1471 ?

It would depend on the situation i think. For instance; when walking around doing a pentest, and you're trying to cover a big area. You would also free one of the radios which gets locked in station mode when connected to your iPhone over wifi. Also, when Android can do it and iPhone cannot, i get a weird anxiety like feeling in my stomach. Which would probably go away if i made it work, lol. :)