FreeRadius

Visseroth

I'm having problem with FreeRadius. When I connect via wireless it'll connect and then disconnect then connect and disconnect again and keep doing it.

I put in the user name and password and it doesn't help.

Does anyone have any information and/or can point me in the direction of some directions on how to set it up properly.

I figure this is a noob ID10T moment so please help me take this tag off (mediforicly speaking)

Visseroth

I only posted this in hopes that someone could point me in the directing of a how to or something of the sort. I know this should be pretty simple but I'm having problems with FreeRadius and/or my AP not allowing machines on the network. I'm using the PEAP configuration so that I can let users connect with a user name and password but my laptop will only associate then disassociate. It never pulls an IP address.

I confirmed that my laptop (running Winblows XP) is configured to use peap and I gave it the user name and password but it associates then disassociates and it'll do it about half a dozen times then give up.

Anyone have any ideas? I am currently using wallwatcher to see my router's output in real time but that's all that is going on.

Edit:
OK, so after finding the log file for the radius server (which I would like to have a tab avaliable for in the system logs area) I found that freeradius apparently isn't letting me connect because it says my user name and/or password is bad. I know they are good, I put them in and confirmed they are correct. I also have entered them in to my laptop and still no go…..

Sun Feb 22 06:11:42 2009 : Auth: Login incorrect: [user/<no user-password="" attribute="">] (from client AP port 1 cli 0012F0C3EDE3)
Sun Feb 22 06:17:51 2009 : Info: rlm_eap_md5: Issuing Challenge
Sun Feb 22 06:17:51 2009 : Auth: Login incorrect: [user/<no user-password="" attribute="">] (from client AP port 1 cli 0012F0C3EDE3)
Sun Feb 22 06:21:49 2009 : Info: rlm_eap_md5: Issuing Challenge
Sun Feb 22 06:21:49 2009 : Auth: Login incorrect: [user/<no user-password="" attribute="">] (from client AP port 1 cli 0012F0C3EDE3)</no></no></no>

Re-sending Access-Request of id 234 to 127.0.0.1 port 1812
        User-Name = "user"
        User-Password = "user"
        NAS-IP-Address = 255.255.255.255
        NAS-Port = 1892
radclient: no response from server for ID 234

After playing with it a bit here it also appears that my AP is trying to target port 1025 on my PfSense for the accounting requests. The radius log states that it's a non-accounting port though my AP is configured for port 1882 or something. I don't remember anymore as I have been playing the the ports a bit trying to get this stupid thing to work.

I've also received errors here and there that another radius server has been seen on the network on port 1892 though I don't have another radius server. Maybe it's the SBS box I have on the network which is going to be scrubbed soon.

Anyhow, any suggestions? Any help here, I'm at a loss.