From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from mail.saemichips.co.kr ([211.55.81.226]:38809 "EHLO
	mail.ebizcenter.co.kr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750703Ab3AWFj5 convert rfc822-to-8bit (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Wed, 23 Jan 2013 00:39:57 -0500
Received: from GYJ ([39.115.113.222]:1459)
	by ktpbx.com with [XMail 1.22 PassKorea080324 ESMTP Server]
	id <S6155C2> for <linux-wireless@vger.kernel.org> from <gyj@x-node.co.kr>;
	Wed, 23 Jan 2013 14:14:25 +0900
From: =?ks_c_5601-1987?B?sce/68H4?= <gyj@x-node.co.kr>
To: "'Julian Calaby'" <julian.calaby@gmail.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
References: <000301cdf87b$0ef2a020$2cd7e060$@co.kr> <CAGRGNgU8qDPZCWR0KryJ7_P0En-01AccBAH+qzyCExv9TFRSsQ@mail.gmail.com> <000301cdf911$4eb3d120$ec1b7360$@co.kr> <CAGRGNgVYr90v8-XhCm3-8LC7bafrbXkaD5pGGSvto-HDMParHw@mail.gmail.com>
In-Reply-To: <CAGRGNgVYr90v8-XhCm3-8LC7bafrbXkaD5pGGSvto-HDMParHw@mail.gmail.com>
Subject: RE: AR6003 :: IP packet is not received.
Date: Wed, 23 Jan 2013 14:39:50 +0900
Message-ID: <000e01cdf92c$10163320$30429960$@co.kr> (sfid-20130123_064002_991988_C1289350)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

Thank Julian.
Please see my answer below.
And why the packet that starts at the PC does not expect to get a hint
about the arrival.


-----Original Message-----
From: Julian Calaby [mailto:julian.calaby@gmail.com] 
Sent: Wednesday, January 23, 2013 12:26 PM
To: ±Ç¿ëÁø
Cc: linux-wireless@vger.kernel.org; ath6kl-devel@qualcomm.com
Subject: Re: AR6003 :: IP packet is not received.

Hi Gueon,

I should have been clearer, I do not speak Korean.

That said, thanks for replying, I've translated it with Google, and
gotten the following:


2013/1/23 ±Ç¿ëÁø <gyj@x-node.co.kr>:
> Hello Julian. Korean Please're very nice to have.
>
> First'll answer the questions below you, so far, I made
> Once again, we will briefly described.
> 1) wpa_supplicant AP mode operation.
> Attachments (AR6000_Linux_SW_User_Guide.pdf) of page 45 in the simple
example
> Can.
> Hostapd as a test - but the situation is the same.
> 2) AR6003 lan card apparently lived, PC wireless embedded Board
> Were successfully connected (associated).

Just to confirm, it works if the embedded board is the Station and the
PC is the Access Point?
	==> PC is STA, embedded board(V210Board) is AP mode.


> 3) But first IP packet transfer from the PC AR6003 driver from any
> Is not responding.
> Confirmation of this phenomenon loosen all the the debug_mask ath6kl
driver
> Looked OK.
> So, do not receive any response for DHCP needs phenomena
> Showing that speculation.
> 4) embedded Board sends the IP packet to the PC, then it just
> Response from the PC, nor be
> PC from the beginning of IP packet transmission.
> 5) embededBoard, and hold the first ping, PC network settings
> If you modify the DHCP to get its IP address can also come.
> 6), and that was running on the PC ping ping stops from embededBoard also
> Does not like.
> Of course embededBoard back again to force a ping, ping from the PC
> Will be revived.
> [PC continue to do this as a ping-t 192.168.11.1
> Put]
> **) The transfer of the IP packet ping've

But not if the embedded board is the Access Point and the PC is the Station.

> My guess is that the H / W and driver porting seems to have no problem,
just
> that there is something wrong with the settings and ath6kl set the item
cfg80211 and related
> items
> Is there thought.
> I config entry for the wireless LAN on the basis of technical
understanding is not high
> Understanding is not high.

So you're assuming that the driver and hardware work, it's just
configuration settings. I think you're correct.

> [Now I proceed to rearrange let.]
>
> 2-1] that I use wifi EVM Taiwan USI WM-BN-AQ-01 is a board
> S5PV210 to use the connection.
> 2-2] USI associated with porting drivers from the
> Received Ath6kl_RCPatch4_LinuxRelease.tar.gz file attached files
> Had been included.
> 2-3] USI materials are distributed in ath6kl driver had been included, the
> there was something wrong driver.
> If you run ifconfig wlan0 up drvier null pointer
> had access to the phenomenon would die
> 've Asked a solution and report the problem to the USI, atheros support
> Direct answers that must be received.

So the driver you were provided did not work.

> 2-4], so I search through the internet compat-wireless-3.5.4-1.tar.bz2 the
> Saw the first porting
> But also ath6kl driver contained in this package, a few of the potential
problems and
> Can.
> Ifconfig wlan0 up and down repeatedly on the PC side of the AP name
occasionally
> You see, but not you see the phenomenon that occurs more commonly noticed
> Nl80211's know the exact cause, but I checked the log LOWER_UP
> Well, it did, and which flag, flag set, and also when the SSID from the PC
> Search
> Symptoms do not match.
> RTM_NEWLINK: operstate = 1 ifi_flags = 0x11043
> ([UP] [RUNNING] [LOWER_UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added

And compat-wireless 3.5.4 partially worked.
	==> yes, Often does not. LOWER_UP.

> 2-5] compat-wireless-3.6.8-1.tar.bz2 customized porting were in the 2-4
> Phenomenon disappeared.
> May disappeared modified as follows. compat-wireless-3.
> 5.4-1 driver was modified from LOWER_UP phenomenon that does not
> Did not see.
> # If 1 / * gyj :: for set option :: set by this always
> RTM_NEWLINK: operstate = 1 ifi_flags = 0x11043 ([UP] [RUNNING]
[LOWER_UP]) by
> Is * /
> static unsigned int suspend_mode = WLAN_POWER_STATE_ON;
> static unsigned int wow_mode = WLAN_POWER_STATE_ON;
> # Else

And compat-wireless 3.6.8 worked, but you had to disable power saving?
	==> yes.

> 2-6] in the firmware image using the Ath6kl_RCPatch4_LinuxRelease.tar.gz
> Image, but had to use the firmware image from the GIT site
> Just bdata.bin from USI and file separately Flyer
> Attachments :: A93F.bin]. A lot of difference in the RSSI values seen on
the PC side
> Can.

Just to confirm, you are using the latest firmware?

There's instructions on the driver's wiki page:
http://linuxwireless.org/en/users/Drivers/ath6kl
	==> I used GIT site firmware.


> 2-7] run-time log file attached.
> 1) hostapd1.conf :: hostapd settings.
> 2) on the ath6kl_boot.txt :: ATH6KL_DBG_BOOT message is received.
> 3) hostapd_start_debug.txt :: hostapd trigger the coming
> Message.
> AP scan on the PC side hayeoseo
> No longer any connection sikyeodo message does not occur.
> PC side, a well-connected
> Appears to be DHCP, DHCP settings during attempts.
> 4) V210Board_ping_hostapd_msg.txt ::
> When you try to ping PC with Embedded Board hostapd
> Appearing debug message.
>
> Thank you for taking the time to read a lot of information.
> Thank you please.

So Access Point mode simply does not work.

Reading the page I linked above, Access Point mode requires hostapd
1.0 or newer.

Have you tried upgrading hostapd to the latest version?
	==> I'm using version 2.0.
			./hostapd -v
			  hostapd v2.0-devel

Other than that, there's not much else I can do. I don't know this
particular hardware and driver.

That said, recent development on it has been to add support for new
versions of the hardware, so it should work.

Can anyone else help?
         ==> Not the person to ask about this issue.

Thanks,

Julian Calaby


==== Original ====

2013/1/23 ±Ç¿ëÁø <gyj@x-node.co.kr>:
> ¾È³çÇϼ¼¿ä. Julian.  Çѱ¹¾î¸¦ ÇϽǼö ÀÖ´Ù´Ï ´ë´ÜÈ÷ ¹Ý°©½À´Ï´Ù.
>
> ¾Æ·¡ Áú¹®ÇϽŠ³»¿ëºÎÅÍ ¸ÕÀú ´äº¯À» µå¸®°í,  Áö±Ý±îÁö Á¦°¡ ÁøÇàÇÑ ³»¿ëÀ»
> ´Ù½Ã Çѹø °£·«ÇÏ°Ô ¼³¸íÀ» µå¸®µµ·Ï ÇÏ°Ú½À´Ï´Ù.
>         1) wpa_supplicantµµ AP mode·Î µ¿ÀÛÀÌ µË´Ï´Ù.
> ÷ºÎÆÄÀÏ(AR6000_Linux_SW_User_Guide.pdf)ÀÇ page 45¿¡µµ °£´ÜÇÑ ¿¹Á¦°¡
> ÀÖ½À´Ï´Ù.
>             ±×¸®°í hostapd ·Îµµ  ½ÃÇèÀ» ÇØ º¸¾ÒÁö¸¸  »óȲÀº µ¿ÀÏ ÇÕ´Ï´Ù.
>         2) AR6003 lan card´Â ºÐ¸íÈ÷ »ì¾Ò°í,  PC¿¡¼­ embedded Board·Î ¹«¼±
> ¿¬°á(associated)µµ ¼º°øÀûÀ¸·Î µÇ¾ú½À´Ï´Ù.
>         3) ±×·±µ¥ PC¿¡¼­ ¸ÕÀú IP packet À» Àü¼ÛÇϸé AR6003 driver¿¡¼­ ¾î¶²
> ¹ÝÀÀµµ º¸ÀÌÁö ¾Ê½À´Ï´Ù.
>                 [ÀÌ Çö»óÀÇ È®ÀÎÀº ath6kl driverÀÇ debug_mask¸¦ ¸ðµÎ Ç®¾î¼­
> È®ÀÎÀ» ÇØ º¸¾Ò½À´Ï´Ù.]
>              ±×·¡¼­ DHCP ¿ä±¸¿¡ ´ëÇÑ ¾î¶² ÀÀ´äµµ ¹ÞÁö¸¦ ¸øÇÏ´Â Çö»óÀ»
> º¸ÀÌ°í ÀÖ´Ù°í ÃßÃøÀ» ÇÕ´Ï´Ù.
>         4) ´Ù¸¸ embedded Board¿¡¼­ ¸ÕÀú  PC·Î IP packet¸¦ º¸³»¸é  ±×¶§´Â
> PC¿¡¼­ ÀÀ´äµµ µÉ »Ó´õ·¯,
>             PC¿¡¼­ ½ÃÀ۵Ǵ IP packetµéµµ Àü¼ÛÀÌ °¡´ÉÇÕ´Ï´Ù.
>         5) embededBoard¿¡¼­ ¸ÕÀú pingÀ» ½ÃÄѳõ°í,  PC¿¡¼­ network ¼³Á¤À»
> DHCP·Î ¼öÁ¤Çϸé IPÁÖ¼Ò¸¦ ¹Þ¾Æ ¿Ã¼öµµ ÀÖ½À´Ï´Ù.
>         6) ±×¸®°í embededBoard¿¡¼­ pingÀ» ¸ØÃ߸é,  PC¿¡¼­ ½ÇÇàµÇ´ø ping µµ
> °°ÀÌ µÇÁö ¾Ê½À´Ï´Ù.
>              ¹°·Ð embededBoard¿¡¼­ ´Ù½Ã pingÀ» ÇØÁÖ¸é PC¿¡¼­ÀÇ ping µµ
´Ù½Ã
> »ì¾Æ ³³´Ï´Ù.
>                [PC¿¡¼­´Â   ping -t 192.168.11.1 ·Î °è¼Ó ¼öÇà ½ÃÄÑ
> ³õ¾Ò½À´Ï´Ù.]
>         **) IP packet ÀÇ Àü¼ÛÀº pingÀ¸·Î ÇØ º¸¾Ò½À´Ï´Ù.
>
> ÀúÀÇ ÃßÃøÀ¸·Î´Â  H/W ¹× driver porting¿¡´Â ¹®Á¦°¡ ¾øÀ» °Í °°°í, ´Ù¸¸
> cfg80211 °ú °ü·ÃµÈ Ç׸ñ ¼³Á¤°ú ath6kl ¼³Á¤ Ç׸ñ¿¡ ¹º°¡ ¹®Á¦°¡ µÇ´Â ³»¿ëÀÌ
> ¾øÀ»±î »ý°¢À» ÇÕ´Ï´Ù.
> Á¦°¡ ¹«¼±·£ ±âÃÊ ±â¼ú¿¡ ´ëÇÑ ÀÌÇصµ°¡ ³ôÁö ¾Ê¾Æ¼­  config Ç׸ñµé¿¡ ´ëÇÑ
> ÀÌÇصµ°¡ ³ôÁö ¾Ê½À´Ï´Ù.
>
>
> [ÀÚ ÀÌÁ¦ Á¦°¡ Áö±Ý±îÁö ÁøÇàÇÑ ³»¿ëÀ» ´Ù½Ã Á¤¸®ÇØ º¸°Ú½À´Ï´Ù.]
>
> 2-1] Á¦°¡ »ç¿ëÇÏ´Â wifi EVMÀº ´ë¸¸ USIÀÇ WM-BN-AQ-01 À̶ó´Â º¸µå¸¦
> S5PV210¿¡ ¿¬°áÇÏ¿© »ç¿ëÇÏ°í ÀÖ½À´Ï´Ù.
> 2-2]  USI·ÎºÎÅÍ µå¶óÀ̹ö porting°ú °ü·ÃÇÏ¿©
> Ath6kl_RCPatch4_LinuxRelease.tar.gz ¶ó´Â ÆÄÀÏÀ» ¹Þ¾Ò´Âµ¥, ÷ºÎµÈ ÆÄÀÏÀÌ
> Æ÷ÇԵǾîÁ® ÀÖ¾ú½À´Ï´Ù.
> 2-3]  USI ¿¡¼­ ¹èÆ÷ÇÑ ÀÚ·á¿¡µµ ath6kl driver´Â Æ÷ÇԵǾî ÀÖ¾ú´Âµ¥, ±×
> driver´Â ¹º°¡ ¹®Á¦°¡ ÀÖ¾ú½À´Ï´Ù.
>           Ifconfig wlan0 up À» ½ÇÇàÇÏ¸é  drvier¿¡¼­   null pointer¸¦
> accessÇؼ­ Á×¾î ¹ö¸®´Â Çö»óÀ» º¸¿´°í,
>          USI¿¡ ¹®Á¦Á¡À» reportÇÏ°í ÇØ°áÃ¥À» ¹°¾îº¸¾Ò´Âµ¥, atherosÀÇ Áö¿øÀÌ
> Á÷Á¢ ¹Þ¾Æ¾ß ÇÑ´Ù´Â ´äº¯¸¸ ¹Þ¾Ò½À´Ï´Ù.
>
> 2-4] ±×·¡¼­ Á¦°¡ ÀÎÅÍ³Ý °Ë»öÀ» ÅëÇؼ­ compat-wireless-3.5.4-1.tar.bz2 ¸¦
> ¸ÕÀú portingÀ» ÇØ º¸¾Ò½À´Ï´Ù.
>         ±×·±µ¥ ÀÌ package¿¡ Æ÷ÇÔµÈ ath6kl driverµµ ¾à°£ÀÇ ¹®Á¦Á¡À»
³»Æ÷ÇÏ°í
> ÀÖ½À´Ï´Ù.
>         Ifconfig wlan0  up°ú downÀ» ¹Ýº¹ÇÏ¸é  PCÃø¿¡¼­  APÀÇ À̸§ÀÌ °¡²û
> º¸À϶§µµ ÀÖÁö¸¸,  ¾È º¸À϶§°¡ ´õ ¸¹ÀÌ ¹ß»ýÀÌ µÇ´Â Çö»óÀÌ ³ªÅ¸³µ½À´Ï´Ù.
>         Á¤È®ÇÑ ¿øÀÎÀº ¾Ë¼ö°¡ ¾øÁö¸¸ nl80211ÀÇ log¸¦ È®ÀÎÇØ º¸´Ï,  LOWER_UP
> flag°¡  setµÉ¶§µµ ÀÖ°í, ±×·¸Ä¡ ¾ÊÀº °æ¿ìµµ Àִµ¥ ÀÌ flag¿Í PC¿¡¼­ SSID
> °Ë»öÀÌ
>         µÇÁö ¾Ê´Â Çö»ó°ú ÀÏÄ¡ ÇÕ´Ï´Ù.
>                 RTM_NEWLINK: operstate=1 ifi_flags=0x11043
> ([UP][RUNNING][LOWER_UP])
>                 RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
>
> 2-5] compat-wireless-3.6.8-1.tar.bz2 ¸¦ ¹Þ¾Æ¼­ portingÇÏ¿´´õ´Ï À§ 2-4]ÀÇ
> Çö»óÀº ¾ø¾î Á³½À´Ï´Ù.
>            ¾Æ·¡¿Í °°ÀÌ ¼öÁ¤À» Çؼ­ »ç¶óÁ³À»¼öµµ ÀÖ½À´Ï´Ù. compat-wireless-
3.
> 5.4-1 driver¿¡¼­ ¼öÁ¤À» Çߴµ¥ LOWER_UPÀÌ µÇÁö ¾Ê´Â Çö»óÀ»
>             º¸ÀÌÁö ¾Ê¾Ò½À´Ï´Ù.
>                 #if 1   /* gyj :: for set option ::  ÀÌ°ÍÀ» setÇؼ­ Ç×»ó
> RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) °¡
> µÈ´Ù. */
>                 static unsigned int suspend_mode=WLAN_POWER_STATE_ON;
>                 static unsigned int wow_mode=WLAN_POWER_STATE_ON;
>                 #else
>
> 2-6] »ç¿ëµÈ Æß¿þ¾î À̹ÌÁö´Â Ath6kl_RCPatch4_LinuxRelease.tar.gz¿¡µµ
> À̹ÌÁö°¡ ÀÖÁö¸¸  GIT site¿¡¼­ ¹ÞÀº Æß¿þ¾î À̹ÌÁö¸¦ »ç¿ëÇß°í,
>        ´Ù¸¸ bdata.binÀº  USI¿¡¼­ º°µµ·Î Àü´ÜµÈ ÆÄÀÏÀ» »ç¿ëÇÏ°í
> ÀÖ½À´Ï´Ù[÷ºÎÆÄÀÏ:: A93F.bin].  PCÃø¿¡¼­ º¸ÀÌ´Â RSSI°ª¿¡ ¸¹Àº Â÷ÀÌ°¡
> ÀÖ½À´Ï´Ù.
>
> 2-7]  ½ÇÇà½Ã log ÆÄÀÏ Ã·ºÎ.
>         1) hostapd1.conf   :: hostapdÀÇ ¼³Á¤°ª ÀÔ´Ï´Ù.
>         2) ath6kl_boot.txt :: ATH6KL_DBG_BOOT¸¦ onÇÏ¿© ¹ÞÀº ¸Þ½ÃÁö ÀÔ´Ï´Ù.
>         3) hostapd_start_debug.txt :: hostapd¸¦ ½ÃÀÛ ½ÃÄ×À» ¶§ ³ª¿À´Â
> ¸Þ½ÃÁö ÀÔ´Ï´Ù.
>                                              PCÃø¿¡¼­ AP scanÀ» ÇÏ¿©¼­
> ¿¬°áÀ» ½ÃÄѵµ  ´õ ÀÌ»ó ¾Æ¹«·± ¸Þ½ÃÁö´Â ¹ß»ýÇÏÁö ¾Ê½À´Ï´Ù.
>                                              ¹°·Ð PCÃø¿¡¼­´Â Àß ¿¬°áµÈ
> °ÍÀ¸·Î ³ªÅ¸³ª°í, DHCP ¼³Á¤½Ã¿¡´Â DHCP ½Ãµµµµ ÇÕ´Ï´Ù.
>         4) V210Board_ping_hostapd_msg.txt ::
>                 Embedded Board¿¡¼­  PC·Î  pingÀ» ½ÃµµÇÒ¶§   hostapd¿¡
> ³ª¿À´Â debug  ¸Þ½ÃÁö ÀÔ´Ï´Ù.
>
> ¸¹Àº ³»¿ëÀ» Àоî Áּż­ °¨»çÇÕ´Ï´Ù.
> ¼ö°íÇϽʽÿä.
>
> -----Original Message-----
> From: Julian Calaby [mailto:julian.calaby@gmail.com]
> Sent: Tuesday, January 22, 2013 8:36 PM
> To: ±Ç¿ëÁø
> Cc: linux-wireless@vger.kernel.org; ath6kl-devel@qualcomm.com
> Subject: Re: AR6003 :: IP packet is not received.
>
> Hi Gueon,
>
> I wish I spoke Korean so we could talk easier.
>
> On Tue, Jan 22, 2013 at 7:32 PM, ±Ç¿ëÁø <gyj@x-node.co.kr> wrote:
>> Dear ath6kl-devel,
>>
>> I Korea's human-intech Work in a company that is Gueon.
>> I am porting and embeded-board wlan AR6003 chipset features.
>> embeded-board CPU samsung S5PV210, linux kenel-2.6.32 is used.
>
> So you're porting Linux to an embedded board with a Samsung S5PV210
> CPU and a AR6003 wireless chipset.
>
> I assume that you have to use kernel version 2.6.32. I must point out
> that version is rather old and a lot of changes have been made to the
> drivers since then. That said, if needed, you may be able to use
> compat-wireless to get the latest version of the driver running on
> that particular kernel version.
>
>> wpa_supplicant using softAP mode, powered by letting success to other
> client devices (ex: Desktop PC) AP Access.
>>         [wpa_supplicant -i wlan0 -c /home/ath6k/SoftAP/softap.conf -
> Dnl80211 -B]
>>         [version : wpa_supplicant v2.0-devel Copyright (c) 2003-2012]
>>
>> Does not accept the IP address from the DHCP client device(PC), the
> problem occurs.
>
> So exactly what are you trying to do here?
>
> Are you:
>
> 1. Trying to use the embedded board as an access point and connecting
> the PC to it?
>
> 2. Trying to use the PC as an access point and connecting the embedded
> board to it?
>
> wpa_supplicant cannot run an access point. You need to use the hostapd
> program to run an access point.
>
>> I have a problem during the analysis.
>> I spoke to experiment by setting a fixed IP without using a DHCP
>> When embeded-Board from the PC to ping-test responses.
>> However, PC from the embedded-Board to ping-test does not responses.
>>
>> Whether the idea of something I could try?
>
> From what you've described, it sounds like the wireless cards are not
> connecting.
>
> What messages are you getting in the kernel log (dmesg)?
>
> If you run the "ifconfig -a" command, is your wireless card's network
> interface UP and RUNNING?
>
> Can you connect to an access point using this embedded board?
>
> Thanks,
>
> --
> Julian Calaby
>
> Email: julian.calaby@gmail.com
> Profile: http://www.google.com/profiles/julian.calaby/
> .Plan: http://sites.google.com/site/juliancalaby/
>
>



-- 
Julian Calaby

Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/
.Plan: http://sites.google.com/site/juliancalaby/