radius server

[satbir]

hi,

http://www.linuxplanet.com/linuxplanet/tutorials/6737/1/

i hv followed the procedure as mentioned in the above link .. i am using AP as zeroshell wireless …secondly zeroshell wireless has WPA+EAP + Radius 802.1x .. where in abv link it shows AP configuration should be WPA +TKIP .

I hv given the user name and password for each user in zeroshell USERS settings , when i try to connect SSID , it says authentication not valid and not asking user name and password given in zeroshell radius settings.

Please let me know what is the issue and help out.

regards,
satbir

[atheling]

@satbir wrote:

hi,

http://www.linuxplanet.com/linuxplanet/tutorials/6737/1/

i hv followed the procedure as mentioned in the above link .. i am using AP as zeroshell wireless …secondly zeroshell wireless has WPA+EAP + Radius 802.1x .. where in abv link it shows AP configuration should be WPA +TKIP .

I don’t see mention of TKIP in the article you linked. It is my understanding that TKIP was an interim fix on WEP. I believe current recommendations are to use WPA2.

I don’t recall what set of instructions I used to setup “WPA2 Enterprise” on Zeroshell, but the ones you’ve linked to seem like what I did.

@satbir wrote:

I hv given the user name and password for each user in zeroshell USERS settings , when i try to connect SSID , it says authentication not valid and not asking user name and password given in zeroshell radius settings.

Please let me know what is the issue and help out.

regards,
satbir

Can you see the authentication attempt in the Radius log on ZeroShell?

If not, verify that you’ve set the shared secret in the WiFi access point and configured it to use Radius on ZS to do authentication.

If you do see log messages, they should give you an idea of what went wrong on authentication (unknown user, bad password, etc.)

[satbir]

Hi,

In 802.1x configuration status is : certificate is not yet valid.

What will be issue.

regards,
Satbir Singh

[atheling]

@satbir wrote:

Hi,

In 802.1x configuration status is : certificate is not yet valid.

What will be issue.

regards,
Satbir Singh

I don’t recall any place in ZeroShell where the screen says 802.1x, so I’m guessing you are referring to setting up a client. I’m not 100% sure of the handshake protocol but your client machines will need to trust the ZeroShell box so you will need to install at least one certificate on each client.

If I recall correctly, I have exported the root x.509 certificate from ZeroShell and installed it as one of the trusted roots on each of my clients. The way you do that varies per operating system.

[Author]

Posts