August 2003 Archives

James Conner Isn't dead!

Of winewhores and lan party....infamy, James Conner isn't dead. He posted me a silly story about this nuisance of a lawsuit with SCO and IBM. I don't put any weight on it at all really. Even if the OSS movement had to roll back to 1.0 the talent is there to revamp in finite time. But that's not going to happen, because this is a scam; not sure who's, but it's a scam. This is all just corporate bullshit. Keep hacking and pass the bottle.

Opinion on the SCO/IBM/Linux furball?

What's your take on the mess? Given their less than spetacular showing of evidence at the Las Vegas SCO show, and their recent attacks on the GPL itself by declaring it overruled by copyright law, and so on ... It's certainly promising to be entertaining, at the very least.

But I feel that the one good thing that can come out of this mess is that the GPL is finally going to see it's day in court. If it passes being challenged, then it'd be a bit easier to get corporations to embrace OSS and develop for the OSS platforms.

BTW ... Hi Jim!

Compaq 3650 Whirlwind

I inherited a hand me down Compaq iPaq 3650 at work. I've been losing sleep playing with the damn thing. It's been exciting because the device leads me in all different directions networking, programming, project management etc. I wanted to reflect a little bit of that spirit here and share some of the things I've been sleepless over...

First things first, you gotta have net otherwise it's a glorified rolodex/gameboy. First I threw a linksys WPC11 wireless 802.11b card in there. Linksys is kind enough to provide drivers on their website. That's a really sweet setup for the home user (or anybody on WEP), but at work we use Cisco's LEAP authentication which means you either have to have a cisco card or have third party drivers to provide LEAP. I couldn't find WinCE drivers for anything. So, I got an aironet 350 from work. The aironet cards are more expensive, but they are quality and there are drivers for everything known to man, including wince. The driver's are awesome, intuitive, and offer articulate control. Highly recommnded. Hopefully with recent accusitions the gap will narrow between linksys and cisco (same company now).

We're on the net. Here's my list of tools on the PC

My apps on the Windows Desktop Apps on my Apple Laptop
  • Missing-Sync for PocketPC - ($$$) A mac synchronization server. Works with the iTools suite (iCal, AddressBook, iPhoto, iMusic). It can also mount the device.

Cool links

The WinCE environment is doable. It's a bare bones piece of hardware so you can't ask for too much anyway. There are plenty of linux ports out there and even a debian distro called intimate. I look forward to trying it, but right now I'm just trying to get my basic PDA functions together before the fall semester starts.

I'm really enjoying the PocketPC as a hardware platform. The palm gave me most everything I needed in both a PIM and something to hack on, but this device is just so much more comparable to a desktop PC, plus the integration isn't so "third party". I was really strong on a Palm for a while, but I just don't see how a proprietary OS is going to compete against the windows monolith and the linux culture. I think their (and handspring's) stock is testament to that. Either way intel is getting their money because it seems like everybody is porting to ARM.

I converted one of my geeklog themes to a format that is much more condusive to the pocketPC browser. It's really simple and seems to work good. The palm site and my normal sleepless site are just lndir's of each other and feed off of the same MySQL database.

Finally, some cool snappies. A narcissistic story wouldn't be complete with out some braggart screenshots.

Some really bad fuzzy shots of the iPaq w/ expansion pack & cisco PCMCIA card

My today page using the MS Horizon Theme

Rainer's OpenSSH port public keyed into my linux server

My sleepless template running on an apache virtual host that's sharkfishing of the main db

Complete masturbation about my hardware button layout, very OS-ish

Source editing with CEdit

Resco Explorer in my /unix/bin directory

PocketMusic playing my 12,000 song M3U off of a network share mounted via Resco Explorer. Oh and it's wireless network.

Anyway, it's loads of fun. I expect it will be as helpful as my palm was, but with mp3's and net!

Using Cricket to Monitor the LinkSys WAP11

| | Comments (1)
I stumbled on cricket when working with oracle SNMP. It's a nice graphing package that's a lot more flexible and modular compared to MRTG. I'm switching. But the point is I've finally unlocked the code that will let you SNMP monitor ATMEL AT76C510 wireless access points. I'm going to post my configuration to the cricket-developers list to have it put on the contrib page. But if you want it now...

You can download the current version here. The rest of this is cut and pasted from the readme.

Jim Weller
8/3/2003 10:36PM

This is a sample config directory for cricket to monitor wireless access points 
based on the AT76C510. I'm working with the linksys wap 11, but it should work 
with comparable smc and netgear devices.

readme.txt - this file - script to querty atmel device via snmp and print cricket values
AT76C510.mib - the mib that came with the "Access Point SNMP Manager"
wireless/ - a sample cricket config directory
wireless/Defaults - sample cricket data defaults file
wireless/Targets - sample cricket targets file for two wap11's

The linksys's use some bastardized SNMP values. Normally datums about 
interfaces come as single objects via SNMP. Atmel's take multiple datums and 
pack them into a single SNMP object. So their is no way to use cricket's 
smoothie OID mechanism to get to the data (without perl trickery). 

There are many versions of the AT76C510.mib file floating around the net. Most 
of them don't compile properly in ucd-snmp/net-snmp, but are functional enough 
for exploring. Many have been edited. The one from linksys in particular has 
been butchered. The version from ATMEL in the "Access Point SNMP Manager" 
application is kind enough to document the format of the packed values. 

Many of the values have been removed or changed on the device by the vendor. 
Plus, much about the SNMP implementations vary by firmware revision. Whether from 
MIB compilation problems or differing implementations, either way you'll find it 
difficult to 'snmpwalk' these devices. 'snmpget's seem to work fine.

Copy the script to your $CRICKET_HOME/util folder. Make sure it 
is executable by whatever user runs your cricket's jobs. Also make sure that (a cricket snmp_utils wrapper) is available in $CRICKET_HOM/lib.

The script takes two arguments (Usage: 
/usr/share/cricket/util/ host community) that it will get from 
your 'Targets' file. Your host will be the IP of your WAP, use the USB/SNMP 
config utilities to set this. You're community can be set via the same utility.

Copy the 'wireless' folder into your cricket config directory. Then edit the 
wireless/Targets file to suit your needs.

Recompile the cricket directory.

Just some snippets to help show what I learned.

These are the OID's that "Access Point SNMP Manager" fetched on 
connection/refresh. I found this using tcpdump on a hub.

. =
. =
. =
. =
. =
. =
. =
. =
. =
. =

These are the packs of long integers from the ATMEL snmp implementation. (Why 
god, why, why?).