| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Pinebuds volume in each e...
Forum: General
Last Post: CaptSpify
10 hours ago
» Replies: 0
» Views: 16
|
Unable to switch from Was...
Forum: General Discussion on PineTime
Last Post: Bruce Kissinger
11 hours ago
» Replies: 0
» Views: 19
|
Searching for a PinePhone...
Forum: PinePhone Accessories
Last Post: RubiksCube
Yesterday, 12:35 PM
» Replies: 0
» Views: 35
|
PinePhone Beta Edition wi...
Forum: Manjaro on PinePhone
Last Post: spazz
Yesterday, 05:55 AM
» Replies: 9
» Views: 8,325
|
Unable to use umlaut key ...
Forum: General Discussion on Pinebook Pro
Last Post: ili
10-01-2024, 01:36 PM
» Replies: 2
» Views: 90
|
Shipping Update and Stock...
Forum: News
Last Post: tllim
10-01-2024, 11:05 AM
» Replies: 89
» Views: 105,515
|
Ethical sourcing practice...
Forum: General
Last Post: cinnabarwinner
09-30-2024, 07:19 PM
» Replies: 2
» Views: 424
|
FIXED-Newer ver of EC25 M...
Forum: PinePhone Hardware
Last Post: DarciFoxe
09-30-2024, 02:08 PM
» Replies: 3
» Views: 294
|
Star64: GPU firmware load...
Forum: Getting Started
Last Post: Marco2024
09-30-2024, 02:49 AM
» Replies: 14
» Views: 6,648
|
Troubleshooting Pinedio L...
Forum: PinePhone Accessories
Last Post: lavabrilliant
09-29-2024, 09:17 PM
» Replies: 2
» Views: 521
|
|
|
| Etcher, the superior burning choice! |
|
Posted by: Ghost - 09-21-2016, 02:14 AM - Forum: General
- Replies (42)
|
 |
Hi
Many of the threads here on the forums, when talking about burning operating system images mention the use of Win32DiskImager. But there is a better alternative called Etcher.
It's user-friendly, open source, cross-platform, and most importantly, it verifies that a burn has been completed successfully.
You can download it here.
|
|
|
|
| Surround Sound Possible on Any OS? |
|
Posted by: methvenc - 09-20-2016, 07:53 PM - Forum: General Discussion on PINE A64(+)
- Replies (1)
|
 |
Hello,
My end goal is to use this with a plex media client connected to my TV and audio receiver via HDMI and get surround sound.
I have tested Android 5.1 which as far as I know is not capable of surround sound, I assumed that it would because my nexus player running the same software did support surround sound, I was wrong. I thought that perhaps the nexus was running Android TV OS, so that could be the issue. I have tested Android TV, that also does not produce surround sound, only stero sound via my receiver.
My question is, is there any software (remix, Linux) that can supports surround sound via HDMI? If so, is it possible to run plex from that OS?
Not sure why the nexus player is capable of playing surround sound but this is not, from what I understand it is more complicated than them sharing similair OS.
If anyone could point me in any direction it would be appreciated. I checked the forums in each OS but couldn't find anything to confirm this works.
|
|
|
|
| LCD Monitor resolution problem |
|
Posted by: S265 - 09-20-2016, 02:52 PM - Forum: Debian
- Replies (2)
|
|
Hi all. The Pine64 Debian Xfce image does not detect my LCD monitor resolution correctly. For some reason it is using 1280 x 760 or such. The correct resolution is 1920 x 1080. The Pine64 Ubuntu mate image does not suffer from this problem - It works at the correct resolution. My OpenSuse Desktop also uses this monitor at 1920 x 1080. Any ideas on how to address this?
|
|
|
|
Howto: Getting Bluetooth (serial console) working on Debian |
|
Posted by: pfeerick - 09-20-2016, 03:18 AM - Forum: Wifi/BT Module
- Replies (14)
|
 |
Tested on a Pine64+ 1GB running Debian 8 “jessie” (3.10.102-3) using the official WIFI 802.11BGN/BLUETOOTH 4.0 Module.
What's it all about? These were the steps I followed to be able to view the text output of a bluetooth-enabled USB power meter, and most of these steps apply to getting bluetooth working at all if it isn't already configured in your chosen image. If it is already enabled, you can probably jump straight to step 5. Regardless, steps 1-5 should get your bluetooth working and a device paired with your pine64, but what you do after that if you don't want the text output (ie. you instead want a bluetooth mouse, audio) like I did I wouldn't know! ;)
Step 1: Make sure you have the bluetooth stack and utilities installed! If you want to all make sure you have all of the stuff this guide uses in one hit, you can add "rfkill git screen minicom" to the list of stuff to install.
sudo apt-get install bluez
Step 2: Get the firmware binaries for the BT from https://github.com/lwfinger/rtl8723bs_bt
This repo contains the programs and firmware to operate the Bluetooth section of the RTL8723BS. This basically loads the firmware into the module, which makes it a bluetooth module! if you don't have git, install it by running "sudo apt-get install git".
Quote:git clone https://github.com/lwfinger/rtl8723bs_bt.git
Step 3: Compile and load the firmware.
Change into the newly cloned repo, and run "make", which will compile the main program needed, rtk_hciattach. Then run "sudo make install" to install the firmware.
You’ll then want the following command to run at bootup, so perhaps put it in /etc/rc.local. For the moment though, you can run it as shown below.
Quote:sudo ./start_bt.sh
This is the command that does real magic… it configures the BT module and makes it available for use.
Step 4: Remove soft block, scan for devices
For some reason or another, the device is "soft blocked" (meaning it is blocked by software), which is easy to fix when you know how. Run
Quote:sudo rfkill list
and you should see something like this (if you don’t, something has gone horribly, horribly wrong already). If you get a message saying rfkill can’t be found, thats ok… just run "sudo apt-get install rfkill" to install it, and try again.
Quote:0: sunxi-bt: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
The entry of interest is the last one (the one for hci0: Bluetooth). That is the bluetooth adapter we’re trying to use, and as you can see, it is currently soft blocked. To fix that, just run (if yours is listed as 3 also)
Quote:sudo rfkill unblock 3
and it will be unblocked. You sould then see if you run "sudo rfkill list" again that this is the case, and if you run hcitool dev, you should also have something like this as the ouput, listing the MAC address of the pine64’s BT adapter.
Quote:Devices:
hci0 34:C3:D2:71:BE:ED
Step 5: Power on bluetooth module and pair your device
You can then run bluetoothctl (as sudo) in order tha manage the bluetooth connection. Install via ‘sudo apt-get install bluez-utils’ if it is missing. You should get an immediate message about a new bluetooth controller… this is a good sign… everything is working so far if you get that message. If you get a message about no default controller, something is wrong. Assuming you don’t have any issues, run the following commands, which power on the BT module and sets it as the default BT agent.
Quote:power on
agent on
default-agent
If all has gone well, you should be seeing something like this.
Quote:[NEW] Controller 34:C3:D2:71:BE:ED pine64 [default]
[NEW] Device 00:BA:55:56:D8:7E SPP-CA
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
You can then then enter "scan on" to start discovery of BT devices, and if you have any devices available for pairing, you should see messages about them appear (prefixed by [NEW]). If they’re not ready for pairing, this is the time to make them ready.
Once your device appears, you can run "scan off" to make the system a bit more responsive again, as it seems pretty laggy at times whilst the scan process is running.
To pair the device you’re trying to pair the pine64 with, enter the command "pair <your-bluetooth-deviceaddress>" . For example, my USB power meter with BT serial had an address of “00:BA:55:56:D8:7E”, so I entered “pair 00:BA:55:56:D8:7E” and entered the device pin when prompted. Once you see a message about the pair being successful (I had to do it a couple of times, it didn’t seem to take the first time) you can exit the bluetoothctl program with the quit command.
Step 6: Bind bluetooth device for usage
This step is what makes the bluetooth device available for you to access. It’s really simple.. just run "sudo rfcomm bind hci0 <your-bluetooth-device-address>"
For example,
Quote:sudo rfcomm bind hci0 00:BA:55:56:D8:7E
This binds hci0 (which you might remember from the rfkill list output from earlier) to the bluetooth device you specificied (usb power meter in my case).
Step 7: Do something with it!
Since I simply wanted to view the serial output from the meter, and I prefer using screen I ran
Quote:sudo screen /dev/rfcomm0 9600
in order to connect to the bluetooth device (made available at /dev/rfcomm0) at 9600 baud. (run "sudo apt-get install screen" to use screen as it’s not installed by default). For those of you who prefer minicom, you could do the same thing by running
Quote:sudo minicom -D /dev/rfcomm0 -b 9600
And then try figuring out how to exit it – hint: it’s Ctrl+a, z, q, enter).I then get a line like this every 5 seconds (the update rate I have the meter set to) telling me the voltage and amperage being measured by the meter. Success!
Quote:052496,005516
052496,005420
All it needs then is some simple decoding to change the interger values sent to their decimal equivalents (ie. the second line is 5.2496v and 0.5420A).
Assuming you were working with a device that didn’t work one way (the meter only ouputs the data, it doesn’t have any configuration or anything over the BT link), you sould then have proper two-way communication via your device and the pine64 over bluetooth!
Acknowledgements:
This information/guide would not be possible without the following sources:
Errata:
2016-09-25 - removed redundant part of step 3
2016-10-10 - removed reference to bluez-utils as isn't needed (or available!) for jessie
|
|
|
|
| Geekbench Scores for Android 7.0 with longsleep kernel? |
|
Posted by: tkaiser - 09-20-2016, 12:46 AM - Forum: Android on Pine A64(+)
- Replies (6)
|
|
Just curious: Did anyone already ran Geekbench on the latest Android 7.0 build with longsleep kernel?
I just ask since when we started tweaking cpufreq / dvfs scaling back in March it was pretty obvious that 'performance' of any demanding task lasting longer than 60 seconds depends on heat dissipation (hardware issue: enclosure vs. none, heatsink vs. none, heavy loads as cpuburn-a53 required already heatsink + fan) and on ths / throttling settings (software issue: killing CPU cores vs. reducing frequencies, providing more cpufreq steps vs. less and so on).
When looking through scores made for Android 5.1 (all with Allwinner's boring and outdated 3.10.65 kernel and most probably ths / cooler_table settings from hell) it looks like different environmental conditions have been 'benchmarked' (especially enclosure vs. none): https://browser.primatelabs.com/v4/cpu/s...q=PINE+A64
Is Geekbench smart enough to take throttling into account? Or at least reporting/monitoring (changes of) /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq?
|
|
|
|
| Don't vi on me and tell me it's raining! Where's pico? |
|
Posted by: tampadave - 09-19-2016, 05:15 PM - Forum: Getting Started
- Replies (20)
|
 |
Hello all,
Love it.
I've not used vi seriously since the 1990's, and as a modal editor, I managed to remember enough to quit. :q! My current editor of preference is sublime text, which is awesome!, but not on the basic boot images found here, let alone for arm instruction sets.
My long time editor is emacs, cause it does lots, and the key bindings work for Cisco kit too, and lots of other systems. Missing.
My go to ultra light weight editor is pico, taken from the pine email program (yeah, any one using pine yet, on pine???), and it provides plenty of what's needed for basic system editing. But that's not here either.
Copying from my netbook does no good, cause the binaries are all x86_64, and pine64 is AArch64.
So, I am looking for these as precompiled binaries, and failing that, I'll have to cross compile on the netbook. Or I could refresh myself on vi, but...yeah... that's gonna happen.
I'll post my solution once I've found it.
David
|
|
|
|
| shipping status still no change |
|
Posted by: flamboyant - 09-19-2016, 02:11 PM - Forum: Shipment Related Discussion
- No Replies
|
|
Hello anybody,
I've ordered one Pine A64+ on Sep 4th, but until today there isn't any change on the shipment status. It is still on "Your package is being prepared to ship"
Is this normal? Today we have Sep 19th! On my two emails I got no reply, but they charged my VISA card after the order directly. This isn't nice...
Could somebody be so nice to check this? My order number is #8165400.
thanks in advance,
Christian
|
|
|
|
| Received my Z-Wave chip & Enclosure - Surely I'm doing something wrong here... |
|
Posted by: tycoonbob - 09-19-2016, 10:23 AM - Forum: openHAB
- Replies (13)
|
|
So today, after waiting what seems forever, finally arrives my Z-Wave (US) Module and PINE64 Enclosure. Originally I backed the PINE A64+ IoT Package (2GB), and finally got my board in early July, and mid-Sept I got the rest of my order. I was backer 13,893.
So imagine my excitement thinking I could finally, after waiting almost a year, play with OpenHAB and finally set up, after waiting 6+ months, the Z-Wave gear that I had recently bought (deadbolts, thermostat, motion sensors, etc -- ~$500 in Z-Wave gear).
Here is my thought progression..
What I received:
http://imgur.com/dPDR92l.jpg
Logic says they go together like this:
http://imgur.com/jI5ISAC.jpg
This is how it fits on the PINE64 board, right?
http://imgur.com/tBR7Xtg.jpg
Cool, now let's put the FINISHED board into my fancy new case:
http://imgur.com/mBd4ivP.jpg
Wait...will the top fit on? This module sticks up pretty high..
http://imgur.com/qnF4MVW.jpg
Hmm...yeah, that's not going to work:
http://imgur.com/5f4smvq.jpg
So please, help me. Did I install this incorrectly? Without seeing any instructions I can only assume I did this all correctly.
Beyond that, are my assumptions correct that the latest Pine OpenHAB build is still 20160415? That means that the new Z-Wave module isn't even supported? Maybe I should just trash this Z-Wave module (that doesn't even appear to fit) and use my Z-Stick with Home Assistant or something...
I like to think I've been pretty patient with all this, but I'm starting to get upset by this whole adventure. I thought by now I would have a plug-and-play OpenHAB box with Z-Wave, Wifi, and Bluetooth support. The Pine board is pretty nice and runs great with DietPi, and this case seems very solid and would fit nicely on the shelf on my server rack. But I guess I'll have to put up with a big Z-stick sticking out of it. Hmm, maybe I'll just ditch this whole project and put the PINE in my storage tote next to my Pi B+ and my oDroid XU4 and put the Z-Stick in a rack-mount piece of gear. Bleh, what a mess.
|
|
|
|
| WiFi PineA64 Pineapple |
|
Posted by: Ghelorn - 09-19-2016, 07:48 AM - Forum: Linux on Pine A64(+)
- Replies (2)
|
|
im building a pineapple with one of my pines. well why not. i figured i would post my instructions. this is adapted from an install script i wrote for reaver a few months back.
remember that any of these tools must be used on networks that you own or have permission to use.
some of these tools on here can interfere with computers/devices on a network.
i will not be held responsible for killing your router, causing nuclear winter, you going to prison or your neighbour bashing the shit out of you for using all of his internet and costing him a small fortune.
i will also not answer questions on how to use the software included. everything has a "--help" or man page for usage. if you still dont know what your are doing then this is not the guide for you.
THIS IS ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING
my setup.
pine a64+ 2GB board + 64GB SD card. metasploit alone takes up 10gigs.
pine64 wifi module. used for connecting to personal wireless hotspot provided by my mobile device. dont plug this in just yet. we dont want this called wlan0 or wlan1
2 x external wireless network cards with reasonable antennas. most of the wireless tools out there only really attack the 2.4GHz band so the cards should be single band.
first download the latest debian longsleep base image.
burn SD card and boot your pine.
start by changing the default password
update system
coz im a baddie for security.
use all our avaliable storage space
lets make sure kernel and uboot is updated
Code: pine64_update_kernel.sh
pine64_update_uboot.sh
reboot
lets su and run more updates
Code: sudo -s
apt-get update
apt-get upgrade -y && apt-get dist-upgrade -y
reboot #it never hurts to do a reboot on a fresh system after updating.
setup wireless hardware
now plug in the first of your wireless adapters
check it shows up.
if nothing shows apart from wlan0 and wlan1 (presuming your using the built in wifi as well), you may need to load the wireless firmware.
i usually do this by running the following
Quote:root@pine64:/home/debian# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
here i can see my card has an atheros chipset. so now i can run.
Code: apt-cache search atheros|grep firmware
and i get the following output
Quote:firmware-atheros - Binary firmware for Atheros wireless cards
so i run
Code: apt-get install firmware-atheros
now unplug and replug your wifi card.
check again for your wireless card
Quote:wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
you will need to do this for each of your wireless cards your using.
at the end i ended up with the following output from iwconfig and lsusb
Quote:root@pine64:/home/debian# iwconfig
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
dummy0 no wireless extensions.
sit0 no wireless extensions.
lo no wireless extensions.
wlan1 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:on
root@pine64:/home/debian# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
shutdown the pine and plug in our built in wifi.
just to double check everything is good
Quote:debian@pine64:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
debian@pine64:~$ sudo iwconfig
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
dummy0 no wireless extensions.
rename7 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:on
wlan2 unassociated Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extensions.
lo no wireless extensions.
wlan1 unassociated Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
hmmm something funny going on here. the wifi module has called itself wlan1 and wlan2 while my second external adapter is called rename7
i had to play around with the udev rules making a rule for the second interface on the wifi module.
file to look at is /etc/udev/rules.d/70-persistent-net.rules
after a reboot i get the following output from iwconfig. this is what i was expecting.
Quote:debian@pine64:~$ sudo iwconfig
wlan3 unassociated Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
dummy0 no wireless extensions.
wlan2 unassociated Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extensions.
lo no wireless extensions.
wlan1 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:on
setup remote ssh wireless connection
we want to setup connection to our wireless hotspot so we can run our pentests from a tablet or even on mobile device via ssh.
edit the file /etc/network/interfaces and add the following to the end.
Quote:auto wlan2
iface wlan2 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
now edit the file /etc/wpa_supplicant/wpa_supplicant.conf and add the following
Quote:network={
ssid="YOUR_NETWORK_NAME"
psk="YOUR_NETWORK_PASSWORD"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
}
wifi software
thats our hardware and remote side of things done and setup. time to install some wifi cracking software.
make us a nice working directory.
Code: cd ~
mkdir working
cd working
install macchanger. because you should be changing your mac address on your wifi cards before doing any attack.
Code: sudo apt-get install macchanger
install aircrack-ng from source.
Code: sudo apt-get install libnl-3-dev libnl-genl-3-dev libssl-dev libsqlite3-dev
svn co http://svn.aircrack-ng.org/trunk/ aircrack-ng
cd aircrack-ng
make sqlite=true experimental=true ext_scripts=true
sudo make sqlite=true experimental=true ext_scripts=true install
sudo airodump-ng-oui-update
now lets test packet injection on our cards
Code: sudo ifconfig wlan0 down && sudo macchanger wlan0 -r && sudo iwconfig wlan0 mode monitor && sudo ifconfig wlan0 up
sudo aireplay-ng --test wlan0
sudo ifconfig wlan1 down && sudo macchanger wlan1 -r && sudo iwconfig wlan1 mode monitor && sudo ifconfig wlan1 up
sudo aireplay-ng --test wlan1
install pixiewps
Code: cd ~/working
git clone https://github.com/wiire/pixiewps.git
cd pixiewps
cd src
make
sudo make install
install wifite
Code: cd ~/working
wget https://raw.github.com/derv82/wifite/master/wifite.py
chmod +x wifite.py
sudo cp wifite.py /usr/local/bin/
install reaver with pixie dust source files. reaver-wps-fork-t6x.
reaver doesnt like the newer versions of libpcap so we will download the older ones.
Code: cd ~/working
mkdir libpcap
cd libpcap
wget https://launchpad.net/ubuntu/+archive/primary/+files/libpcap-dev_1.4.0-2_all.deb
wget https://launchpad.net/ubuntu/+archive/primary/+files/libpcap0.8-dev_1.4.0-2_arm64.deb
wget https://launchpad.net/ubuntu/+archive/primary/+files/libpcap0.8-dbg_1.4.0-2_arm64.deb
wget https://launchpad.net/ubuntu/+archive/primary/+files/libpcap0.8_1.4.0-2_arm64.deb
sudo dpkg --install *.deb
sudo apt-mark hold libpcap-dev libpcap0.8 libpcap0.8-dbg libpcap0.8-dev
install reaver now.
Code: cd ~/working
git clone https://github.com/t6x/reaver-wps-fork-t6x.git
cd reaver-wps-fork-t6x*/
cd src/
./configure
make
sudo make install
now on to Bully
Code: cd ~/working
git clone https://github.com/aanarchyy/bully
cd bully
cd src
make
sudo make install
now to make things easy with this code a lovely guy made. thanks SilentGhost for making HT-wps breaker.
Code: mkdir ~/code
cd ~/code
git clone https://github.com/SilentGhostX/HT-WPS-Breaker.git
sudo ln HT-WPS-Breaker/HT-WB.sh /sbin/HT-WB.sh
my next step is installing this in an old wireless router with a battery.
more is to come. i will be adding some exploits like metasploit and some MITM attacks like sslstrip and such. this is just the base setup. i remember there was a web interface for this. just dont remember what it was called.
edit: i added macchanger to the wifi tools. cant believe i forgot it.
|
|
|
|
|
![[Image: 20160920_143949.jpg]](https://usercontent.irccloud-cdn.com/file/iGhq0QpB/20160920_143949.jpg)