Karmic

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)
Loading ... Loading ...

Who the hell is Karmic? He/she/it (to be evaluated) is the successor of Arch, the new Buildserver of the Piranha Project. Starting with the next Piranha 3.0 snapshot release 100217+1, the Piranha firmware will be build with Ubuntu 9.10 instead of Archlinux, still a headless CLI only setup though. Actually this is a major change as Archlinux served as the Buildserver OS since the very beginning of the Piranha Project back in Oct 2008.

Other changes include:

  • switch from Big to Midi Tower
  • WOL capability (god bless you)
  • RAM upgrade from 512 Megs to 1 Gig
  • 6 Gigs harddisk for / and 2x 10 Gigs (LVM) for /home

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

Piranha 3.0 100217

1 Star2 Stars3 Stars4 Stars5 Stars (5 votes, average: 5.00 out of 5)
Loading ... Loading ...

This update to Piranha 3.0 is all about stability and reliability. With Piranha 3.0 100117, released exactly one month ago, a simultaneous station- and AP mode configuration has been introduced as the default. After doing extensive testing the last days, I decided to revert back to a station-only configuration starting with this Piranha 3.0 100217 snapshot release (the stability penalties caused to AAP 2.0 are just not worth it from my perspective). That said, if you nevertheless prefer the previous configuration, you can adjust your /e/c/network and /e/c/wireless as described here.

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:

  • OpenWrt trunk r19684
  • station-only configuration
  • AAP 2.0 100217
  • FON heartbeat 100217

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

1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)
Loading ... Loading ...

As promised earlier, Piranha 3.0 snapshot release 100214 “speaks” Japanese by default, ships with GNU Screen and is available for your convenience. Especially for new users of the Piranha firmware, I’d like to provide an overview about its complete feature set (so far) this time.

Piranha 3.0 100214 ships with:

  • OpenWrt trunk r19628
  • AAP 2.0 100202
  • Aircrack-ng 1.0
  • CIFS share support
  • MMC card support (ext2)
  • FON heartbeat 090925
  • Mac Changer 1.5.0
  • MDK3 v6
  • GNU Screen 4.0.3
  • “Japan mode” (Wifi channels 1-14)
  • station- and simultaneous AP mode configuration (10.0.0.0/24)
  • custom station- and monitor mode scripts
  • patched madwifi for AAP 2.0

Get your copy of Piranha 3.0 100214 here. Any feedback is certainly appreciated.

GNU Screen

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

Starting with the next Piranha 3.0 snapshot release 100202+1, I’m going to ship GNU Screen installed by default. In combination with the recently introduced MMC card support (ext2), this should significantly enhance usability when operating your Fonera in monitor mode.

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!

Konnichiha

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)
Loading ... Loading ...

No, I’m not going to switch languages but countrycodes. By default OpenWrt (and Piranha 3.0) ships with support for Wifi channels 1-11, but after reading the Madwifi documentation I was highly ambitious to change this and I finally succeeded. Fellow community members, we’re now able to utilize Wifi channels 1-14 or in other words: We’re going to speak Japanese by default as of the next Piranha 3.0 snapshot release (if that turns out to be stable)! There’s no need to wait though, you can enable Wifi channels 1-14 right now.

# uci set wireless.wifi0.country=392
# uci commit wireless

Actually, it’s that easy. Just reboot and enjoy! Opinions?