Modify

Opened 8 years ago

Closed 8 years ago

Last modified 22 months ago

#2777 closed defect (fixed)

netgear wag302 - second radio on netgear wag302 doesn't work

Reported by: gdistasi@… Owned by: kaloz
Priority: normal Milestone: Barrier Breaker 14.07
Component: kernel Version:
Keywords: Cc:

Description

There are 2 devices: wifi0 and wifi1.
I created two athX devices, everything seems ok, but the second radio (from wifi0 device, at 5Ghz doesn't work). It doesn't associate neither in adhoc or managed mode.
The first radio (from wifi1) seems to work well.

Attachments (0)

Change History (11)

comment:1 in reply to: ↑ description Changed 8 years ago by anonymous

Replying to gdistasi@gmail.com:

There are 2 devices: wifi0 and wifi1.
I created two athX devices, everything seems ok, but the second radio (from wifi0 device, at 5Ghz doesn't work). It doesn't associate neither in adhoc or managed mode.
The first radio (from wifi1) seems to work well.

I made a mistake. This error seems to relate to the kernel, not to the packages.
Maybe the first radio needs a particular initialitation, an initialitation that atheros drivers don't do.

comment:2 Changed 8 years ago by kaloz

  • Component changed from packages to kernel
  • Owner changed from developers to kaloz
  • Status changed from new to assigned

Please confirm you have a WAG302 v2, not a v1.

comment:3 Changed 8 years ago by anonymous

Hi, I have a WAG302, v1. Is that ok?

comment:4 follow-up: Changed 8 years ago by kaloz

That needs additional support. Stay tuned, will have something in a week for you.

comment:5 in reply to: ↑ 4 Changed 8 years ago by anonymous

Replying to kaloz:

That needs additional support. Stay tuned, will have something in a week for you.

Ok, thanks... I'm really looking forward to it.

comment:6 follow-up: Changed 8 years ago by kaloz

I've added support in [10197], please test

comment:7 in reply to: ↑ 6 Changed 8 years ago by anonymous

Replying to kaloz:

I've added support in [10197], please test

I tested it... it's a great step forward.
As you certainly know, there is no need to load the firmware for the ethernet interface manually, but: the ethernet address of the interface is not set properly (it is 00:00...:00). But if you do:

ifconfig eth0 down
ifconfig eth0 hw ether mac_address (specifying the right mac address, discovering it with redboot);
ifconfig eth0 x.y.z.k

and wait for a while, eth0 starts working! It takes a while for the link to be established (the cable is not recognised immediately), and after that, it still takes some seconds for eth0 to start working (but that happens with redboot too, so It may be related to other problems).

About the radios, I haven't tested it enough, but it seems there are still problems (I'll let you know soon).

Another problem is with leds (the eth led always winkle).

comment:8 follow-up: Changed 8 years ago by kaloz

I'll fix the mac address handling soon, just got a nice flu.. I'll update the ticket when it's commited to svn.

Please test the radios in the meantime.

comment:9 in reply to: ↑ 8 Changed 8 years ago by anonymous

Replying to kaloz:

I'll fix the mac address handling soon, just got a nice flu.. I'll update the ticket when it's commited to svn.

Please test the radios in the meantime.

That's sad (the flu)... I had it at the beginning of the year... a very strong one :).

I tested the radios... they work! Both, the one at 5Ghz and the one at 2,4Ghz, even toghether.
I still have some minor problems (apart from those related to eth0 I mentioned already):
wpa does not work
wep tested and working.

There is another problem much likely not related to openwrt:
I created a bridge where I put the eth0 interface, the ath0 interface and the ath1 interface. In this scenario, the dhcp server doesn't answer to clients' queries on both the wireless interface. If I remove one of the two wireless interface from the brigde, the dhcp server answers correctly. Namely, having two wireless interface in the bridge creates problems.
Thanks.

comment:10 Changed 8 years ago by kaloz

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:11 Changed 22 months ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.