On Sun, Mar 24, 2013 at 9:22 PM, Outback Dingo outbackdi...@gmail.com wrote:
bad firmware load on a crappy wireless AP probably, I just flashed the
latest firmware on a new Netgear, and had exactly the same issue
flashed back to the original firmware and the issue goes away, question is
whats
On Sun, Mar 24, 2013 at 9:26 PM, Joel Wirāmu Pauling j...@aenertia.net wrote:
Can you try disabling network manager from the init scripts (I am not
sure which distro you are using as a base but
/etc/init.d/network-manager stop ) tends to work for a percentage of
machines.
Then running
On Mon, Mar 25, 2013 at 2:23 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
Interestingly, the kernel messages from doing this were different:
wlan0: RX AssocResp from 50:46:5d:02:85:08 (capab=0x411 status=0 aid=16)
notice how now it says aid=16 instead of aid=10. WTF?
This seems
On Mon, Mar 25, 2013 at 02:23:52AM -0700, Linus Torvalds wrote:
Apparently this really is NetworkManager doing something wrong.
I'm running F18, so doing
systemctl stop NetworkManager.service
ifconfig wlan0 up
iwlist scan
wpa_passphrase *essid* *password*
On Mon, Mar 25, 2013 at 3:12 AM, Jouni Malinen jo...@qca.qualcomm.com wrote:
Did you happen to notice whether wpa_supplicant showed more than one
attempt at associating with the AP?
According to the kernel messages, there seems to be just a single
quick association:
IOW, this is what happens
Am 25.03.2013 10:23, schrieb Linus Torvalds:
On Sun, Mar 24, 2013 at 9:26 PM, Joel Wirāmu Pauling j...@aenertia.net
wrote:
Can you try disabling network manager from the init scripts (I am not
sure which distro you are using as a base but
/etc/init.d/network-manager stop ) tends to work for
On Mon, Mar 25, 2013 at 3:38 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
that web page
tells me how to add them, so I'll do that (I obviously lose my network
when I try this, so I'm not doing it while writing this email ;)
Ok, full wpasupplicant log added to the RH NetworkManager
On Mon, Mar 25, 2013 at 04:06:49AM -0700, Linus Torvalds wrote:
Ok, full wpasupplicant log added to the RH NetworkManager bugzilla,
let's hope that somebody sees the problem there. I see that there's a
gnome bugzilla for NM too, but it appears that at least Dan Williams
is on both the RH and
Likely due to some odd dhcp options or behaviours comming whatever odd
ball vendor implemented dhcp server that runs the wireless network dhcp
leases. Often in hotels or corporates they use an offloaded radius and
crypto upstream of the AP itself. These tend to be dark voodoo, Cisco and
On Tue, Mar 26, 2013 at 01:17:10AM +1300, Joel Wirāmu Pauling wrote:
Likely due to some odd dhcp options or behaviours comming whatever odd
ball vendor implemented dhcp server that runs the wireless network dhcp
leases. Often in hotels or corporates they use an offloaded radius and
On Mon, Mar 25, 2013 at 4:30 AM, Jouni Malinen jo...@qca.qualcomm.com wrote:
This looks very basic case taken into account the AP configuration (just
WPA2-Personal/CCMP) and passphrase that should not allow much of a
chance for typos or encoding issues (non-ASCII..).
Hmm. I'm certain I didn't
On Monday, March 25, 2013 03:23:53 AM Adrian Chadd wrote:
Also, would you please make sure you file a bugzilla.kernel.org ticket
so this gets tracked?
It's good to know that some combination of fast channel change and
warm versus cold reset is making things better/worse.
And although a
On Mon, Mar 25, 2013 at 09:04:14AM -0700, Linus Torvalds wrote:
Ok, I've collected a successful trace with wpa_supplicant, and added
it to the bugzilla entry.
Thanks. This log does actually show a retry of the EAPOL-Key message 1/4
about a second after the first attempt and that was the area I
On Mon, Mar 25, 2013 at 9:35 AM, Jouni Malinen jo...@qca.qualcomm.com wrote:
I'm not really familiar with debugging with NM enabled, but it could be
possible that the instructions for the older wpa_supplicant on
https://live.gnome.org/NetworkManager/Debugging could be adopted for
this. The
One for each please.
Adrian
On 25 March 2013 09:12, Christian Lamparter chunk...@googlemail.com wrote:
On Monday, March 25, 2013 03:23:53 AM Adrian Chadd wrote:
Also, would you please make sure you file a bugzilla.kernel.org ticket
so this gets tracked?
It's good to know that some
Me and other ath9k users have experienced various similar problems
for years, across different ath9k hardware. NM was usually not part
of the picture, at least never in my case, my problems were always
with only wpa_supplicant, if that.
ath9k has improved, but I still have soft issues that nobody
On 25 March 2013 11:03, Peter Stuge pe...@stuge.se wrote:
Me and other ath9k users have experienced various similar problems
for years, across different ath9k hardware. NM was usually not part
of the picture, at least never in my case, my problems were always
with only wpa_supplicant, if that.
I am running 3.5.0-rc2 for a long time, where the ath9k was available in the
kernel.
I upraded and compiled the v3.8.4 kernel from
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
modprobe ath9k
FATAL: Module ath9k not found.
I noticed that in .config the following is
On Mon, Mar 25, 2013 at 9:42 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Mon, Mar 25, 2013 at 9:35 AM, Jouni Malinen jo...@qca.qualcomm.com wrote:
I'm not really familiar with debugging with NM enabled, but it could be
possible that the instructions for the older wpa_supplicant
19 matches
Mail list logo
