Loading ...
Published on
March 3, 2010 by
orange.
As you know, I use the Web analytics software Piwik to track non-personal data from visitors of the Piranha community website. That said, I continuously discover bloodcurdling theories about the Piranha package repositories at various forums and in order to end the myths, I decided to explain this better.
Ok, first of all, Piranha 3.0 is fully compatible with OpenWrt trunk and it ships with a pre-configured /etc/opkg.conf that looks like
root@OpenWrt:~# cat /etc/opkg.conf
src/gz snapshots http://downloads.openwrt.org/snapshots/trunk/atheros/packages
src/gz piranha http://piranha.pwnz.org/pub/3.0/100228/packages
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /jffs
So, what does that mean?
As you can see, TWO repositories are defined there, “snapshots” and “piranha” in that particular order, i.e. the Piranha repository is prioritized. If you happen to desire installing whatever software (available for OpenWrt, e.g. LuCI, webif, etc.) on top of Piranha 3.0, you just need to issue
# opkg update
# opkg install foobar
and that’s it. No need at all to introduce other repositories to /etc/opkg.conf. All software NOT shipping by default with Piranha 3.0 will be pulled from the OpenWrt snapshots=trunk repository for Atheros.
The other myth is, that it is required to download the whole Piranha package repository and install every single ipk one by one AFTER flashing Piranha 3.0 to get the full feature set. Certainly this isn’t required at all as every ipk hosted at the repositories is shipping with Piranha 3.0 by default, i.e. is included in the squashfs you just flashed onto your device. In order to verify this, just issue
# opkg list_installed
and you’ll see what I’m talking about. Hope this helps!
Loading ...
Published on
February 28, 2010 by
orange.
“Was lange währt, wird endlich gut”, a German saying that actually fits the situation quite well. Anyways, I’m glad to announce that Piranha 3.0 100228 aka 100227r1 has been released. With OpenWrt trunk r19877, the OpenWrt development team introduced a major change to the existing automounting mechanism for block devices. As I accidentally missed that, Piranha 3.0 100228 needs to be pushed out as a bugfix release for 100227 in order to ensure a 100% working MMC card setup again .. and here it is!
root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.5M 2.5M 0 100% /rom
tmpfs 6.6M 100.0K 6.5M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock3 4.4M 272.0K 4.1M 6% /jffs
mini_fo:/jffs 2.5M 2.5M 0 100% /
/dev/mmcblk0p1 3.6G 7.4M 3.4G 0% /mnt/mmcblk0p1
You see, living on the bleeding edge also has its drawbacks (sometimes). That said, Piranha 3.0 100228 ships with:
- OpenWrt trunk r19886
- block-mount package by cshore
- AAP 2.0 100227
Get your copy of Piranha 3.0 100228 here and enjoy AAP 2.0 100227
Loading ...
Published on
February 27, 2010 by
orange.
Linux version 2.6.30.10 (orange@karmic) (gcc version 4.3.3 (GCC) ) #1 Sat Feb 27 21:25:10 CET 2010
Here it is! Piranha 3.0 snapshot release 100227 aka 100217+1 is now available for your convenience. Built with Karmic, it’s based on OpenWrt trunk r19886 and ships with the brand new AAP 2.0 snapshot release 100227 aka 100217+1 introduced earlier today. The AAP documentation has been updated to cover the most recent AAP feature set and configuration.
Without any further introduction, get your copy of Piranha 3.0 100227 here
Loading ...
Published on
February 27, 2010 by
orange.
With Piranha 3.0 & AAP 2.0 snapshot releases 100217+1 right around the corner, I’d like to provide some more insight into upcoming features of AAP. Certainly and most notable, the before mentioned capability to connect to hidden SSIDs utilizing /aap/aap_hlst will finally enter the stage.
Anything else?
Yes, starting with AAP 2.0 100217+1, a sorted list of suitable APs found in range (selected for connection attempts) will be easily accessible for your convenience and you’ll be able to manually skip the connection to an AP with a single command. Last but not least, while the MAC spoofing status message has been dropped, the AAP log has been streamlined in general to just provide the information (PID, time, status message) actually needed.
The complete AAP 2.0 command set will (from now on) read as follows
# aap {start|stop|restart|log|list|skip}
Loading ...
Published on
February 27, 2010 by
orange.
While the most important 90% for connection capabilities of AAP to hidden SSIDs had been implemented a long time ago (variable aap_hidden), I never took care of the missing 10%, but now I actually did. Starting with the next AAP 2.0 snapshot release 100217+1, AAP will finally be able to connect to hidden SSIDs. You’ll just need to define a tab-delimited BSSID, SSID pair per AP within /aap/aap_hlst, another newline-separated configuration file for AAP, and AAP will automagically take care of the rest. Certainly you’ll be able to combine this with the existing white-/blacklisting and MAC spoofing capabilities of AAP. I’ll update the AAP documentation as soon as Piranha 3.0 100217+1 will be out the door, the first Piranha actually shipping with this brand new AAP feature. Special thanks goes to community member foxtroop11 for the initial feature request.
(13 votes, average: 4.69 out of 5)
(1 votes, average: 4.00 out of 5)
Recent Comments