Thread: [Madwifi-users] MADWIFI based FCC/CE Certified Products
Status: Beta
Brought to you by:
otaku
From: Amin A. <ami...@ho...> - 2007-06-23 16:00:21
|
Hi, I have few questions for you related to MADWIFI based FCC/CE certified products. 1. It seems that test suite (such as continues packet transmit) related to FCC/CE certification are part of madwifi-0.9.3. Is it a correct statement? 2. Does MADWIFI provide patch for FCC/CE certification test suite? 3. What is the current normal practice to obtained FCC/CE certification based on MADWIFI? 4. Does you have any rough estimate on the number of products based on MADWIF which are also FCC/CE certified? Thanks in advance. /Amin _________________________________________________________________ Windows Live Hotmail is the next generation of MSN Hotmail. Its fast, simple, and safer than ever and best of all its still free. Try it today! www.newhotmail.ca?icid=WLHMENCA146 |
From: Michael R. <mre...@ma...> - 2007-06-27 05:02:34
|
Hi. > 1. It seems that test suite (such as continues packet transmit) related > to FCC/CE certification are part of madwifi-0.9.3. Is it a correct > statement? I'm not sure, but I'd say this is wrong. > 2. Does MADWIFI provide patch for FCC/CE certification test suite? Not exactly a patch, but Mike Taylor is currently working on related changes in the madwifi-dfs branch. You should check the archives of the madwifi-devel mailing list about previous messages from him about this topic, and you might want to join madwifi-devel in order to pose related questions there that are left open. > 3. What is the current normal practice to obtained FCC/CE certification > based on MADWIFI? What exactly does "based on MadWifi" mean here? Bye, Mike |
From: Amin A. <ami...@ho...> - 2007-06-27 22:12:39
|
Thank you Mike for your response. >What exactly does "based on MadWifi" mean here? I meant commercial WIFI products which are using Atheros chipset and MADWIFI driver. I think, before vendor(s) ship there product(s) for example in US they need the FCC certification to validate different RF parameters such as tx power and spectrum usage (FCC Part 15). Thanks again, Amin >From: "Michael Renzmann" <mre...@ma...> >To: "Amin Abdul" <ami...@ho...> >CC: mad...@li... >Subject: Re: [Madwifi-users] MADWIFI based FCC/CE Certified Products >Date: Wed, 27 Jun 2007 07:02:31 +0200 (CEST) > >Hi. > > > 1. It seems that test suite (such as continues packet transmit) related > > to FCC/CE certification are part of madwifi-0.9.3. Is it a correct > > statement? > >I'm not sure, but I'd say this is wrong. > > > 2. Does MADWIFI provide patch for FCC/CE certification test suite? > >Not exactly a patch, but Mike Taylor is currently working on related >changes in the madwifi-dfs branch. You should check the archives of the >madwifi-devel mailing list about previous messages from him about this >topic, and you might want to join madwifi-devel in order to pose related >questions there that are left open. > > > 3. What is the current normal practice to obtained FCC/CE certification > > based on MADWIFI? > >What exactly does "based on MadWifi" mean here? > >Bye, Mike _________________________________________________________________ Windows Live Hotmail. Even hotter than before. Get a better look now. www.newhotmail.ca?icid=WLHMENCA148 |
From: Michael R. <mre...@ma...> - 2007-06-28 04:46:50
|
Hi. > I meant commercial WIFI products which are using Atheros chipset and > MADWIFI driver. When it comes to WLAN cards, I don't know of any vendor who ships their cards with MadWifi. Those I know usually only provide Windows drivers. Don't know about vendors of products that rely on stuff like the SoC chipset families. In addition it could well be that Atheros provides a separate toolset for certification tests. But I'm not very deep into that topic, maybe someone else can sched more light on it. Bye, Mike |
From: Amin A. <ami...@ho...> - 2007-07-28 17:13:20
|
Hi, I am analyzing the behavior of Atheros chipset and MADWIFI driver under poor RF conditions. I am simulating the poor RF conditions by keep the TX power low at bootup time and connecting and disconnecting antennas at run time. The following is my network setup: AP RF interface STA PC antennas RX diversity is enable on both AP and STA. During my testing I notices the association table on STA display multiple entries for the AP (same BSSID). I am using get sta command to get association table. Did anyone from MADWIFI community notices the same behavior or would someone explain why I see multiple entries for the same AP. Thanks, Amin _________________________________________________________________ Show Your Messenger Buddies How You Really Feel http://www.freemessengeremoticons.ca/?icid=EMENCA122 |
From: Michael R. <mre...@ma...> - 2007-07-29 07:19:25
|
Hi. > During my testing I notices the association table on STA display multiple > entries for the AP (same BSSID). I am using get sta command to get > association table. IIRC "get sta" is to get a list of the clients that are associated to an AP VAP, but I could be wrong. Anyway, you didn't mention which version of the driver you're using. And questions like this might be better suited on the madwifi-devel mailing list. Bye, Mike |
From: Amin A. <ami...@ho...> - 2007-08-02 19:05:41
|
Hi, According to 802.11g-2003 specs: 19.4.4 Slot time The slot time is 20 µs, except that an optional 9 µs slot time may be used when the BSS consists of only ERP STAs capable of supporting this option. The optional 9 µs slot time shall not be used if the network has one or more non-ERP STAs associated. For IBSS, the Short Slot Time subfield shall be set to 0, corresponding to a 20 µs slot time. What I understood from the above statement is slot time should either be 9 or 20 but when I was scanning through the source codes of athctrl utility I notice this utility is calculating the slot time based on distance like: . int slottime = 9 + (distance / 300) + ((distance % 300) ? 1 : 0); setsysctrl(device, "slottime", slottime); I think it is a bug or I am missing something. Would you please clarify this? Thanks, Amin _________________________________________________________________ Put Your Face In Your Space with Windows Live Spaces http://spaces.live.com/?mkt=en-ca |
From: Michael R. <mre...@ma...> - 2007-08-03 04:11:10
|
Hi. > What I understood from the above statement is slot time should either be 9 > or 20 but when I was scanning through the source codes of athctrl utility > I notice this utility is calculating the slot time based on distance like: [...] > I think it is a bug or I am missing something. Would you please clarify > this? To the best of my knowledge this is intentional and not a bug. The standard assumes that WLANs are used for short distances of up to 300m iirc, where the standad values for slottime, ack timeout and so on would work fine. However, for long distance links these values have to be adjusted to make the setup work properly due to increasing roundtrip times for the signal. Bye, Mike |