Eaopclient crashes when attempting to connect to a 802.1x PEAP

Question

Hello,
I am having a problem connecting my macbook to my school's 802.1x PEAP authenticated network.
The issue appeared after I updated my computer about 2 months ago. (today being 01/22/2008).
Any help would be appreciated.

Answer 1

Funny thing, i solved my own problem.
not sure what it was that i did, but, I will repeat the steps i took that
appear to have lead to the solution:
first, I deleted the root certificate and the stored login credentials via the
keychain access program.
be careful not to delete your entire keyring!
Then, I booted in to single user mode, via refit ( non refit people
can use do cmd-v (that's the clover, or apple key).
I then fsck'd the computer with the command
/sbin/fsck -fy
the f means force, and the y means assume yes when asking for permission to do things.
then, I did something really strange, which probably didn't cause my configuration to work, but for completeness, I shall tell it anyways.
I remounted root read-write via mount -w / and continued the booting process with a sh /etc/rc. what that does is call the script that is normally called when OS X is booting. or at least thats how it works in BSD. Sh, if you don't know, is THE shell that preceeded bash, the bourne again sh. On OS X, it's just a symlink to bash. But, I digress.
When I found that it just brought me to a blue start up screen with a mouse, I shut down the system via the power button and rebooted normally.
And, for some unknown reason, this restored the normal functionally of eapolclient.
As I'm sure the person with a decent knowledge of Unix systems may come to the conclusion that maybe all I needed to do was fsck my system. Which I will remember next time before I spend 4 hours on a OS X problem. (or any OS for that matter).