rt2x00.serialmonkey.com

Hmm, I don't understand much about WPA-encryption. I can only tell you that I have the following options for WPA with my FritzBox:


or


I don't really know what this Group-Key-Intervall is for (it was set to 3600sec by default), and I also don't know if this is WPA-PSK or not.

Unfortunatelly I can't find further informations on the AVM-website or in my handbook.

Using driver rt2x00 instead is impossible for me in the moment, because Mandriva 2006 only has kernel 2.6.12

Are you sure about this PSK-thing?
Or could you explain what this Group-Key-Intervall is for?

Would it perhaps make sense to set this to a higher/lower amount and try again?

Group key interval is how often the group key is re-exchanged between the clients and AP.

It looks like your AP only support PSK - not 802.11x (otherwise it wouldn't ask you to enter a key). I assume there is nowhere on that page in your AP to setup something like a RADIUS server ?

_________________
--------------------
Regards,
Mark Wallis
Project Administrator
http://rt2x00.serialmonkey.com

Well, now I'm VERY confused!

While Vern posted this:

you are now writing the opposite:


What's correct now?

I actually don't know what my FritzBox does support, the manuals only say something about TKIP (WPA) and about the standards IEEE 802.11b and IEE 802.11g being supported.
But I contacted AVM yesterday to get further information about my FritzBox.

And now my question to you is - as I think you are not one with each other:
Do I need an AP with WPA-PSK to get connected with my rt2500-chip with the currently used driver rt2500, or not?

Who of you guys is right?



No, there isn't - what do you conclude about my FritzBox?


Isn't it normal that I have to let the AP know about the WPA-key the wireless network should use? What exactly do you mean with this?

PSK means Pre Shared Key, this means that you have to enter a encryption key in the AP as well as the client. During authentication stage the keys are basically compared (through various algorithms for safe comparison of keys without informing the world what the key is)
The fact that your AP has an option to enter a encryption key, means that it supports the Pre Shared Key method.

The 802.11i standard is about authentication without Pre Shared Keys and work (usually) with a radius server for authentication. Which works something like LDAP, users passwords are stored in database, upon authentication attempt the user with his password is verified.
If your AP does not have a option for a Radius server or 802.11i authentication is does not support 802.11i.

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com

Yes, I have to enter a WPA key in my AP - so my FritzBox does support WPA-PSK!!!

So that would mean that Vern was wrong again with his conclusion that my AP wouldn't support this.

And what does the rt2500-driver support? WPA-PSK I guess - right? Hopefully Vern was right with this information!?


So, to summarize it:
I have an AP which supports WPA-PSK and a driver that should do the same thing.
But in fact WPA doesn't work for me since one year! I've posted several debug-traces - but what goes wrong here?

I'm told to change my startup-script, because this could cause the failure. I do so, but the script in new order doesn't work for me, so I keep the old one.
Next possible failing I was told is the file RT2500STA.dat which would still present in my system, but it's not, as also shows the debug-trace.
Then I'm told that I mustn't switch my AP to WPA via WLAN which would cause the error - but switching it over cable shows that this has no positive effect, also.
The last assumtion is that my AP doesn't support the WPA-mode needed to work with the driver - which seems to be wrong, also.
Switching to the rt2x00-driver is not possilbe for me, because of the kernel being used in my distro. Beside this in the past the rt2x00-driver didn't work with WPA, what is its status right now?

Any ideas how to proceed now?
Some more debug-traces?
Some more patches for bug-hunting?

Or is giving up the "best" solution right now?

There is a patch of Vern's going into CVS in the next day or two - you can wait and try that, otherwise you will need to wait for your distro to catch up with it's kernel updates and move to rt2x00

_________________
--------------------
Regards,
Mark Wallis
Project Administrator
http://rt2x00.serialmonkey.com

Hi MadMax,

First, thanks for introducing me to dhcpcd. It is, in my view, a much better behaved facility than dhclient..

You wrote:

Yes, you do. You might refer to 802.11i pp. 14-17. You can download IEEE specs from

http://standards.ieee.org/getieee802/

Under the Hail, Mary! dept, you might do this:

1. iptables-save (save results).
2. ifconfig (save results)
3. route -n (save resuilts)
4. Try to bring up air link (save results).
5. iptables-save (save results).
6. ifconfig (save results)
7. route -n (save results).

The intent of all this is to see if your NAT, routing, and firewall policies are tracking DHCP IP address assignments.

Post them all here, and I'll take a look.

Well, I've never felt there is a need for special hostnames, but it cought my eye when opening a console that the standard hostname "localhost" of my computer was suddenly called "noname" everytime I established successfully a connection to the internet.
Then I found out that it must have something to do with DHCP, played around with the two existing dhcp-clients and finaly I'm using dhcpcd now without problems.
As you can see in my debug-traces, my standard hostname now is "MaxOffline" and it will be set to "MaxWLAN" or "MaxCable" depending which connection I choose (when I use my distro's networking-skripts to bring up the network).
Like this I can see also in a simple console if everything works fine with my network!

But back to your proposal now:

I don't have "iptables" installed in my present configuration, so I don't really have a firewall set-up.
Should I install iptables now to provide you with the infos of "iptables-save", or is this misleading because you thought I would use a firewall?

Do I need the vanilla-driver for this?



Btw: My FritzBox has a built-in Firewall to block access from outside...
As you have downloaded the manual you could take a look at it.

No iptables? Omit steps 1 and 5.

What model of Fritz!Box do you have?

Can you post sreenshots of the dialog boxes (In English - if available. Otherwise, I'll try to guess German)?

Sorry for my late answer, but I was busy with other things a while.

I hope you are still willing to help me with my WPA-problem.

Meanwhile I've updated to today's CVS-version of rt2500-driver, but WPA still fails on my system!


Here are the results of your last requested steps to do:

1. ifconfig (save results)


2. route -n (save resuilts)


3. Try to bring up air link (save results).
Don't really know what I should save here, I just ran my old script to establish WPA-connection:


4. ifconfig (save results)


5. route -n (save results).



Could this help you to spot the problem?

Wow!

Debug log?

Also, there's a thread

where the OP also has a Fritzbox & a similar problem, only with the RT2570 (USB) version of the driver.

Maybe that could provide some ideas. If it does, post the solution.

Anyway, send up a log captured during the procedures used in your most recent post, and I'll take a look at it.

Debug log?
Once again?
Sure?

To answer me that question please read through the hole thread here first, I've provided you with so many debug-traces in the past.
Even with various patches applied to the vanilla-driver.

If you think I should do it once again because many things of the driver have been changed in the last 2 months - then I will do so.


Perhaps you remember me - I was the guy who could establish a WPA-connection, but failed to load most pages in the internet. One of a few exeptions was that I could reach google via WPA.
And it's all still the same - also with latest CVS-driver.

Btw. thank you for the link to the other thread. This made me playing around with scanning the AP:

To do that I made the following script:


If I set the AP to WEP mode and run the script, I get the following output:


If I set the AP to WPA mode and run the script, I get the following output:


Broadcasting the AP's ESSID was switched on in ALL cases!!!



Only if I have established a WPA-connection with my script mentioned somewhere in this thread, I'm able to scan the AP:



Is this behaviour normal, that the AP can't be found with "iwlist ra0 scanning" when the AP was set to WPA-mode and there was no connection established, yet but network is already up (up'ed with "ifconfig ra0 up")??

I thought this shouldn't matter! What's going wrong here??

Yes, I do remember you.

I understand that generating all this debug info is - as they say - a royal PITA. However, you can rest assured that after doing so, and after you have sauntered off to suck down a German brewski, I will spend much more time analyzing that log than you will have spent generating it.

Two more questions:
1. What is the exact model of your Fritzbox AP.
2. Does it - or does it not - support WPA with pre-shared key (WPA-PSK)? If you're not sure, please post a screen shot showing the AP's authentication menu.

O.k. - I will provide you with a debug-log tomorrow. *sigh*


This one is easy - it's a FRITZ!Box SL WLAN
http://www.avm.de/de/Produkte/FRITZBox/ ... index.html
Seems that for this model there is no English information available on avm's HP.

But you could choose the manual for FRITZ!Box Fon WLAN instead, which should be pretty much the same, aside from the additional VoiP-support which my model doesn't have.
http://www.avm.de/en/service/manuals/FR ... n_WLAN.pdf


Oh, I thought we already had clarified this - as you have to enter the WPA-key in the FritzBox => PSK.
Moreover I also asked the avm-support and they answered that the FritzBox uses WPA-PSK. So I would say this is sure for 100%.