Not what I ordered
/One of my co-worker's friends saved up some money to buy a digital camera from eBay. Due to a shipping mistake on the part of the seller, he got what can best be described as a personal lactation assistant instead. :)
One of my co-worker's friends saved up some money to buy a digital camera from eBay. Due to a shipping mistake on the part of the seller, he got what can best be described as a personal lactation assistant instead. :)
I spent much of yesterday helping Fleetwood Mac get hooked up to our network here at the University. They had 80(!) computers with them, which needed to be attached to our network, without exposing us to unecessary risk. It wound up being a major pain in the butt, since we were only given about 18 hours notice that this was going to occur, but we got it straightened out, and the geek/drummer that I was working with even got me into the show for free.
I managed to get 802.1x up and running today, at least in a test Active Directory forest. And I managed to get my Mac and a Windows XP box to authenticate through it, this should give me enough to show off to the big-wigs at work so they can decide what it is we're doing for wireless this fall. The 802.1x solution is cheap, but Mac users prior to 10.3 aren't going to work out of the box, nor are Windows users prior to Windows 2000 SP4. But, when you think about it, how many people use wireless that don't meet those system requirements? Not very many...
Since I got a snazzy new camera phone today, I now have a "Moblog" where you can see snapshots that I grab with my camera. Check it out at http://sethb.textamerica.com/
Anyone out there have any experience with 802.1x authentication for wireless networks? We're starting to look at it as a possibility for our campus network, and I'm trying to get up to speed on how it works, and determine if it's a feasible solution for us.