AVILA: AP mode with WEP-128 broken

[samueldg]

Trying to configure an avila (2348-2 or -4) to use one of the atheros interface as access point, I discover the clients didn't go associated with the AP.

Into the avila I use iwconfig to review the ath1 configuration and all appears to be fine, the ath1 added to the br0, etc.... all fine but my intel 2200 don't want to associate to the access point. I use wpa_supplicant with no problems when the AP's are broadcoms (buffalo, linksys).

I detected some things in the AVILA when configuring 1 interface as AP (BG-MIXED mode):

1) The second onboard led goes off after some seconds. 2) I can't see any hostapd process running in the avila. 3) Using kismet I can't see the device.

I don't know what is the problem, but here is it.

[BrainSlayer]

WEP does not use hostapd. all is working. ensure that your hex keys are correct

[samueldg]

Sebastian, all configuration is a well known working configuration. The same configuration is used for devices as wrt54g or buffalo whr-g54s.

I reviewed the ath1 configuration with iwconfig and all appears to be fine, but I can't see the avila using kismet or trying to connect to it.

The same test client connect to a wrt54g without problems with the same WEP configuration. That is the cause I write the bug. Perhaps some type of incompatibility (don't know now).

[BrainSlayer]

i configured my avila now for WEP too and its all working including association. do you use the latest internal releases, or official sp1?

[samueldg]

I'm using avila 19/11/2008 v24 pre-sp2. ath0 is configured as wds-sta to link to another (its working fine), ath1 is configured as AP with wep.

We tried (in our testlab) to change channel wide (I think 20MHz for BG is well), tried to disable "extended" parameters too.

Our laptop has an intel abg (2200 driver) that works fine with the same build for buffalos or linksys wrt's family.

Like I described before, with kismet (running on the intel or in an atheros abg pcmcia) we can't see the avilas ath1 signals.

It's very curious. We can test more things, but now I don't know what we can test.

Thanks

[samueldg]

This is in the same status.

Any test to do more verifications?

[samueldg]

The same using today build, at least, now, we can see the network with kismet.

If I configure an atheros pcmcia, it works fine, but appears not to be working (for now) with an Intel 2945 (ABG) minipci card (ipw2200 driver).

I'm doing more test now that I can link the laptop to the network.

[samueldg]

Appears to be any type of incompatibility with ipw2200 driver. Don't know what could be the problem. The same iwconfig commands were done against the intel minipci (and tested more that isn't needed by atheros one).

Info about the ipw2200 driver:

# modinfo ipw2200 filename: /lib/modules/2.6.18-92.1.13.1.el5_ArcosCom/kernel/drivers/net/wireless/ipw2200.ko license: GPL author: Copyright(c) 2003-2006 Intel Corporation version: 1.2.0kmprq description: Intel(R) PRO/Wireless 2200/2915 Network Driver

Don't know if the kernel could be the problem, because the driver is working fine linking against any broadcom with any v24 pre-sp2 version (or stable ones).

I don't know what more I can test, sorry. I'll post the problem in the forum to see if anybody can help with this problem.

Regards

[samueldg]

More test (after upgrade avila with - 20081130 - pre-sp2):

1) Using intel drivers (old one and new one) under windows this don't work. 2) Using wrt/buffalo with last ddwrt v24 pre-sp2 work. 3) Clients with atheros works.

Hardware incompatibility?

[samueldg]

Could anybody confirm the problem?

[anonymous]

Milestone v24 final deleted

[Sash]

intel wifi nic's are the worst i see on the market...