linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: linux-wireless@vger.kernel.org
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: WPA2, compat-wireless-2.6.31-rc3, kernel 2.6.28 - rtl8187 - association works but no ping
Date: Fri, 24 Jul 2009 18:52:38 +0300	[thread overview]
Message-ID: <4A69D8C6.9040103@promwad.com> (raw)
In-Reply-To: <43e72e890907240824n5bcff378m1278eb948055a9a5@mail.gmail.com>

>> ifconfig:
>>
>> eth0      Link encap:Ethernet  HWaddr 02:80:AD:20:31:EB
>>          inet addr:192.168.5.1  Bcast:192.168.5.255  Mask:255.255.255.0
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:40 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:188 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:4077 (3.9 KiB)  TX bytes:17012 (16.6 KiB)
> 
> Note an IP address on eth0, most likely you have a default route using
> eht0 as well. Check with 'ip route'.
> 

No default route. eth0 only for netconsole.
I'm doing udhcpc on wlan0.
Another thing is that WPA-TKIP is working. The problem only with CCMP.
I posted also in wpa_supplicant list with detailed wpa_supplicant log:
http://lists.shmoo.com/pipermail/hostap/2009-July/020026.html

>> wlan0     Link encap:Ethernet  HWaddr 00:12:0E:98:67:FC
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:304 (304.0 B)  TX bytes:3932 (3.8 KiB)
>>
>> wmaster0  Link encap:UNSPEC  HWaddr 00-12-0E-98-67-FC-00-00-00-00-00-00-00-00-00-00
>>          UP RUNNING  MTU:0  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>
>> Neither dhcp nor setting static IP for wlan0 - no ping.
> 
> Do you have Network Manager on? Please read:
> 

No Network Manager.
Just:
wpa_supplicant -Dwext -iwlan0 -c /home/ACORP.conf -dd &
/sbin/udhcpc -n -q -i wlan0 -s /bin/default.script

> http://wireless.kernel.org/en/users/Documentation/Reporting_bugs
> 
> Specifically the section that describes getting 'iw event -t' log and
> Network Manager.
> 

I'll try with iw event -t.
Is it possible to check via debugfs something like number of received unencrypted packets?

Regards,
Ivan




  reply	other threads:[~2009-07-24 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  9:22 WPA2, compat-wireless-2.6.31-rc3, kernel 2.6.28 - rtl8187 - association works but no ping Ivan Kuten
2009-07-23 16:17 ` Luis R. Rodriguez
2009-07-24  8:13   ` Ivan Kuten
2009-07-24 15:24     ` Luis R. Rodriguez
2009-07-24 15:52       ` Ivan Kuten [this message]
2009-07-24 16:23         ` Luis R. Rodriguez
2009-07-24 16:40           ` Ivan Kuten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A69D8C6.9040103@promwad.com \
    --to=ivan.kuten@promwad.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).