Return-path: Received: from mail-wi0-f179.google.com ([209.85.212.179]:59094 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752392Ab3AWD0V convert rfc822-to-8bit (ORCPT ); Tue, 22 Jan 2013 22:26:21 -0500 Received: by mail-wi0-f179.google.com with SMTP id o1so305008wic.0 for ; Tue, 22 Jan 2013 19:26:20 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <000301cdf911$4eb3d120$ec1b7360$@co.kr> References: <000301cdf87b$0ef2a020$2cd7e060$@co.kr> <000301cdf911$4eb3d120$ec1b7360$@co.kr> From: Julian Calaby Date: Wed, 23 Jan 2013 14:25:59 +1100 Message-ID: (sfid-20130123_042627_263794_2AC71198) Subject: Re: AR6003 :: IP packet is not received. To: =?EUC-KR?B?sce/68H4?= Cc: linux-wireless@vger.kernel.org, ath6kl-devel@qualcomm.com Content-Type: text/plain; charset=EUC-KR Sender: linux-wireless-owner@vger.kernel.org List-ID: 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 ?ǿ??? : > 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? > 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. > 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? > 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 > 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? 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? Thanks, Julian Calaby ==== Original ==== 2013/1/23 ?ǿ??? : > ?ȳ??ϼ???. 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, ?ǿ??? 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/