FS#8422 - Network/Wireless issues with 2.6.23

Attached to Project: Arch Linux
Opened by James Rayner (iphitus) - Friday, 26 October 2007, 00:21 GMT
Last edited by James Rayner (iphitus) - Friday, 07 December 2007, 21:57 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Cannot use some wireless networks with 2.6.23. Can successfully associate and gain an IP on the network, but am unable to then use it.

If I type 'route' at console, the first two lines appear, and the third one always after 10 seconds, it seems to be timing out on something. The third line is the gateway.

Networks that don't work:
* Uni, WPA Enterprise, dhcp
* Another Uni, No Security, dhcp
* State Library, No security, dhcp

Network that works:
* Home, wpa personal, dhcp

Additional info:
* kernel26-2.6.23.1-3
* ipw2100
* disabling ipv6 has no effect
* loopback is up

Will post output of route, dmesg, ifconfig and iwconfig when I get home. Also will test previous versions of kernel26 next monday/sunday if I can to nail down the version, or whether it was something else that has caused the problem.
This task depends upon

Closed by  James Rayner (iphitus)
Friday, 07 December 2007, 21:57 GMT
Reason for closing:  Not a bug
Comment by Tobias Powalowski (tpowa) - Saturday, 27 October 2007, 09:44 GMT
please try 2.6.23.1-6 from testing
Comment by James Rayner (iphitus) - Sunday, 28 October 2007, 09:06 GMT
This bug really annoys me. I had a similar/same thing with my old wireless router.

New kernel doesn't fix it, though one of the 'problem' networks started working randomly this afternoon after not working in the morning.

I tried 2.6.22, and was able to reproduce it there, so I don't think it's kernel related after all. Something in userspace, or possibly some horribly odd and hard to track bug.

I've got some ideas, which i'll try tomorrow. It may be dhcpcd...
Comment by Tobias Powalowski (tpowa) - Sunday, 28 October 2007, 15:11 GMT
yes dhcpcd can be weird too
Comment by James Rayner (iphitus) - Monday, 29 October 2007, 08:47 GMT
Almost definitely dhcpcd, I'll file a bug with the author.

My old wireless router, which I've since given to someone else, exhibited this behaviour frequently. Today I found I could connect fine with dhclient.

Just then, the same problem occurred. Did dhcpcd -k ipw0, then dhclient ipw0, and it's all working again.

James
Comment by Tobias Powalowski (tpowa) - Friday, 07 December 2007, 14:04 GMT
status on this?
Comment by James Rayner (iphitus) - Friday, 07 December 2007, 21:57 GMT
oh, sorry. filed a bug upstream, did some research, PEBKAC, nothing to see here.

Loading...