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!
]]>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:
Get your copy of Piranha 3.0 100228 here and enjoy AAP 2.0 100227
]]>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
]]>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}
Other changes include:
Last but not least, some Easteregg hunting in remembrance of Arch. The first community member telling me where/how to find the following string within Piranha 3.0 100217 gets a pony!
]]>Linux version 2.6.30.10 (orange@arch) (gcc version 4.3.3 (GCC) ) #1 Wed Feb 17 05:07:55 CET 2010
Also on the stability front, AAP 2.0 now ships with a new default value for its aap_dhcptimeout configuration variable. I raised it from 30 to 60 seconds as this turned out to higher the reliability of AAP connection attempts significantly. Together with the station-only configuration mentioned above, you should encounter a much smoother AAP 2.0 experience now.
Another aspect I addressed with this Piranha 3.0 snapshot release is related to Mac Changer and /aap/aap_mlst. Both FON heartbeat and AAP 2.0 previously relied on information from /sys/class/net/ath0/address and /sys/class/net/eth0/address respectively to deal with MAC addresses for various techniques. While the co-existence with Mac Changer in Piranha 3.0 was at least partly taken into consideration, it wasn’t deliberated in order to overcome all imaginable scenarios related to MAC Spoofing that may come to your (crazy) brains, but now it is! I now use information extracted from “dmesg” to get the real hardware addresses of your device and thus all FON heartbeat and AAP 2.0 operations are guaranteed to work 100% whatever you do with Mac Changer and/or /aap/aap_mlst and whenever you do it.
Piranha 3.0 100217 changes compared to 100214:
Due to the (stability/reliability) reasons I outlined, I highly recommend upgrading to this very latest Piranha 3.0 snapshot release. I hope you’ll like it as much as I do.
Get your copy of Piranha 3.0 100217 here and have a lot of fun!
]]>Piranha 3.0 100214 ships with:
Get your copy of Piranha 3.0 100214 here. Any feedback is certainly appreciated.
]]>Why?
Screen is a full-screen window manager that multiplexes a physical terminal between several processes, typically interactive shells (…) When screen is called, it creates a single window with a shell in it (or the specified command) and then gets out of your way so that you can use the program as you normally would. Then, at any time, you can create new (full-screen) windows with other programs in them (including more shells), kill the current window, view a list of the active windows, turn output logging on and off, copy text between windows, view the scrollback history, switch between windows, etc. All windows run their programs completely independent of each other. Programs continue to run when their window is currently not visible and even when the whole screen session is detached from the users terminal.
OK, what does that mean?
Imagine you can run both airodump-ng and aireplay-ng (fake authentication and fragmentation attacks) within just one single SSH session while capturing to your SD/MMC card and you can detach (and reattach) the session at any time. The rest is up to your imagination. That said, in order to get used to GNU Screen’s usage and configuration with /etc/screenrc (this beast is highly customizable), I’d like to refer you to its official documentation.
Stay tuned!
]]># uci set wireless.wifi0.country=392
# uci commit wireless
Actually, it’s that easy. Just reboot and enjoy! Opinions?
]]>