I tested this against my home router a Netgear DGN2200 using my eee-pc with an Atheros wireless chipset and the FOSS ath5k driver.
Target: Netgear DGN220
After tweaking the command line parameters a bit, I managed to crack the password in 7 hours 45 minutes.
Cracked in 7 hours 45 minutes later
Lessons learnt:
1. It is all about hardware / drivers – tried using other hardware – about three times slower using HP laptop with Intel chipset
2. Tweaking the command line helps a lot, in this case the delay between attempts and the way it handles AP lock outs
Next step
The WPS feature can be disabled in the Netgear control panel – I disabled WPS and am running reaver against it again
Update
Netgear FAIL – when you turn-off the WPS pin, it only slows down the brute force attack, but does not prevent it. It took 30 hours to crack.
Philip showing cool T-Shirt from 2600 – http://store.2600.com/nexthopetshirt.html
USBuino
USBuino soldering
Toby and I met up on Thursday and devised the USBuino – combining the Arduino Pro-mini with the USB shield. It is a single board with full Arduino and USB capability!
We can think of a couple of applications and high on the priority list is the cellbot-racer :
Jossekin (mostly) and I continued the 3d printer build and managed to get to the point where we manually control the x,y and z axis. Marius helped me to shoot a short video using my phone – so apologies in advance for the quality
To make up for this, I found a creepy soundtrack on Free Music Archive. As required the attribution and link: 11 strANGE Ls (Mark Neil) / CC BY-NC-SA 3.0
Due to popular demand , we are planning to have the Basic Electronics Course this Saturday the 10th.
Nick will be presenting this course and as per his mail will cover
1. transistor ac & dc amplifiers Emitter followers , darlington pairs , inverters
2. Op-Amps (741 / 747s)
3. D/A converter using OP/amps , Hi Pass and Low Pass filters
4. 555 timers
5. Some TTL gates
6. LM335 temperature sensors
I still have to buy the components, but estimate the cost of the course to be R300, this include the above hardware.
You will need to bring a breadboard, laptop and Arduino – shout if you need one of these.
We will start at 9:00 and run till 13:00
Please mail me at schalk dot heunis at gmail dot com, if you want to attend the course this Saturday
TL;DR – Basic Electronics Course this Saturday 9-13, R300, mail if you want to come
Update
Received confirmation from:
Adam – with Arduino, cable and breadboard
Alex
Devin
Philip
Willie
Marius
Gerhard
Jarrod – with Arduino, cable and breadboard
Andrew
We are fully booked for Saturday!
Some additional resources as we went through the course:
What an awesome event, can’t wait for next time! Our team’s solution (H2flow) took first prize and I hope our solution makes the impact it was intended. Briefly the weekend:
Three challenges were posed at RHOK Pretoria this weekend:
Water metering reading in Sierra Leone and community based water management in Eastern Cape – a low cost mobile solution is required
Donor management by local children homes and charities who depend on donations for their sustainability
Crowdsourcing early warnings for pending social disasters – using the data streams from social media to identify clusters of sentiments that could leading indicators for brooding disasters
Starting at 9 on Saturday, these were presented to the group and we split into teams – four teams were formed – two teams tackled the donor management (different visions about the solutions).
Representing House4Hack, I participated in the water meter reading and water management challenge. Our team started as three (Schalk, Klaas and Jabu) and as the weekend wore on were assisted by Vuyo and Madeleine. These are extremely talented people with Klaas an entrepreneur in the mobile space (Bamboo) and both Jabu and Madeleine PhD students working at SAP research !
Technology wise we tackled the problem using:
Android for mobile reporting and problem reporting – Klaas and Jabu respectively
Couchdb for back-end and web2py for reporting and management – Schalk
Sunday morning saw me phoning HC to get some advice on web2py – thanks HC, made a huge difference!
Unfortunately Klaas could not attend Sunday and we ended up only presenting the water management solution at 15:30, the judges selected this as the best solution for the weekend!
Thanks for Jossekin and friends at SAP Research for organising this great initiative and SAP Research for sponsoring the venue, food and prizes.
We got off to a great start on Tuesday evening (22 Nov) with the build of the H4H RapMan 3.1 3D Printer!
Thanks to Andrew, Mikkel, Jossekin, Nick and Philip who made up the first build team.
Was funny to hear us referring to parts as “geared things” and “starred jobs”!
We learned alot and would like to share the experience and some tips with everyone. This way, future build teams can hopefully build on this methodology and the experience we picked up.
Below is the video of what we got up to and further down I wrote up lots more.
We finished the following (refer “D100239 Build Manual Printed .pdf”):
Practice Parts (Page 12/13)
1.01 Bttm Corner Block R x 2 (page 15)
1.02 Bttm Corner Block L x 1 (page 16)
1.03 Z Motor Block x 1 (Page 17/18)
Next build team should carry on from page 19: “1.04 Top Corner Block R x 2″ .
Tips:
Have at least 2 tables to work off – also suggested by the manual
Tools – We almost had a problem here, Nick came to the rescue
Stress test on acrylic part’s tensile strength -> Finger tight screws! (See our video)
The nice big LCD display at h4h + more laptops to display all manuals/videos
A projector would come in handy, could be projected onto wall in build space
Label completed build sections / parts. Still outstanding!
First 14 pages printed with Laser Cut Panel ID’s is available in 3D Printer build space
Main manual to work from is “D100239 Build Manual Printed .pdf”, we viewed page 15 and onward on screen
3D parts in 3D-PDF (On screen, can rotate parts in 3D! Need Adobe Acroread 9)
Use the printed Workflow chart (page 4) to encircle built parts in pen and depict in there which team built what on which date, this way next team would also know where to carry on from
Most important manuals:
Sources :
a) http://3dpedia.3dsystems.com/login.action?os_destination=%2Fhomepage.action&os_username=bfbcustomer&os_password=3dprinting
b) http://www.bitsfrombytes.com/ :: Support :: Technical Resources (takes one to same link as above, logging one into 3dpedia. Permalink not possible so will try to upload manuals to github, also available via certain H4H members. Once Technical Resources linked was followed and one is logged into 3dpedia, direct access to manuals via this link: http://3dpedia.3dsystems.com/display/BFBCustTechRes/RapMan+3.1+Setup
D100239 Build Manual Printed .pdf (Main manual)
D100240 Rapman 3D Build Manual V3-1-0 Part 1.pdf
D100240 Rapman 3D Build Manual V3-1-0 Part 2.pdf
D100242 Extruder Manual V3-1-0.pdf
D100245 Extruder Manual V3.1 issue 2.pdf
D100244 Hot End Manual V3-1-0.pdf
D100250 Double Head Installation Manual 3-1.pdf
Build methodology:
A good build methodology one could use (from our experience).
Work from the Workflow chart on page 4 of “D100239 Build Manual Printed .pdf”.
Everything broken down into Build Sections.
There are 18 Build Sections with sub-builds under each.
Depicts which parts to build first
Depicts which finished parts makes up bigger parts
All Build sections eventually comes togeter as the complete 3D Printer
Follow instructions from “D100239 Build Manual Printed .pdf” for each part being build.
First 14 pages printed and is available in build space
To identify parts refer to printed pages :
Parts list (page 5)
“Laser Cut Parts ID Main Panels” (pages 6 – 10)
Bolt Tray Contents (page 11)
What worked for us, seeing that we were 5 members during this build :
One could assign 2-3 members to:
ID parts
Remove parts from laser cut panels
Build parts
Assign another 2 members to
Drive computer / cameras / setup manuals on LCD/projector
Quality Assurance on built parts
Guide team on progress
Make coffee / Bring cookies / Moral support
What could perhaps also work is when having enough members involved in a build, split the Build Sections between subgroups, work faster, get printer build done quicker
Tools needed:
We might need to invest in an Allen Key set, or perhaps get a member to share theirs.
Nick fetched his awesome tool set which assisted us a lot, still we did not have Allen Key’s or all specs on tools at hand.
I made a list from the RapMan PDF manual on what we need. On my Linux system I could run :
This extracted only the tools mentioned on each page’s top right hand corner for a specific build section or part’s build. It got me a decent tool list which I made a frequency histogram of most referred to least referred tool in the manual:
18 2.5mm Allen Key
15 5.5mm Wrench
8 4mm Allen Key
7 Tweezers
6 Setting Jig x 2
5 8mm Wrench
4 13mm Wrench x 2
3 1/16” Allen Key
3 Foot Jig x 4
3 Wire Cutters
2 2mm Flat
2 Needle File
2 Screwdriver
2 Wire Strippers
1 1/16” Allen key
1 13mm x 2 Wrench
1 20001 Steel Rod
1 2mm Allen Key
1 5.5 mm Wrench
1 608 Bearing (Bin 11)
1 8mm Wrench x 2
1 Allen Key 4mm
1 Files
1 Ruler
1 Test Filament
1 Wrench 13mm x 2
1 Wrench 8mm x 1
Anyhow, there should be enough info in here for House4Hackers interested to come help build our own 3D Printer!
Awesome! We are actually building our own 3D Printer!
The training area (Space I) in the house gets very hot in summer and we got some airconditioning on Friday. This made a huge difference. We installed two 18000 BTU units Samsung Mid wall Smartinverter units which seems to have done the trick.
The company that installed it was GNAir (http://www.gnair.co.za/) – I could really recommend them. They committed to having the system in on time and delivered, despite some inevitable hurdles. Very professional – thanks Roelof and team.
Some photos:
Samsung Smart Interver Midwall unit
Mid wall units in the training area
Roelof & Christo from GNAir
Panorama of Space I
Also a nice panorama of the training area (mouse over for effect):