Fedora Linux Support Community & Resources Center
  #1  
Old 16th November 2009, 01:10 AM
paulch Offline
Registered User
 
Join Date: Nov 2009
Posts: 3
linuxfedorafirefox
Fedora locks up connecting by wireless to OpenWRT router

Hi,

I dual boot Windows/Fedora 11 on my Dell Latitude D830 laptop, which has an Intel PRO/Wireless 3945ABG card and I have just bought a Linksys WRT160NL wireless router. I am currently trying to set up OpenWRT linux on the router. Because of the nature of my problem I have also posted this on their forum.

I am having trouble connecting to my OpenWRT install via Fedora. Things seem okay in Windows, but when I try to connect from linux my laptop locks up completely and I have to hard reboot. I previously have never had any trouble connecting to any other router with this install of Fedora.

My story ...

I started by setting up OpenWRT (Kamikaze) on my WRT160N via ethernet. All went well and I could connect to and log in to the router over ethernet via both ssh and the LuCI web interface that comes with OpenWRT.

I then disconnected from ethernet and attempted to connect by wireless. I've been using the stock NetworkManager on Fedora, so just used that. I saw the OpenWRT box's SSID in the list and selected it.

After a few seconds of trying to connect the whole system hung on me. I had to hard reboot.

I tried it again and the same thing happened. So I tried Windows. No problems there. Saw the SSID and connected first time, ssh server, LuCI and everything.

So, I did some investigating in Fedora by connecting without NetworkManager.

After disabling the NetworkManager control of the wlan0 interface I did the following:

# iwlist wlan0 scan

The output of which included:


Cell 03 - Address: 00:03:7F:BF:10:58
Channel:9
Frequency:2.452 GHz (Channel 9)
Quality=70/70 Signal level=-23 dBm
Encryption key:off
ESSID:"constant"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000000f4a17f9a
Extra: Last beacon: 7726ms ago
IE: Unknown: 0008636F6E7374616E74
IE: Unknown: 010882848B960C121824
IE: Unknown: 030109
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F 00
IE: Unknown: 2D1A4C1003FFFF000000000000000000000100000000000000 000000
IE: Unknown: 3D1609000000000000000000000000000000000000000000


So I proceeded with:

# ifconfig wlan0 down
# iwconfig wlan0 mode Managed channel 9
# iwconfig wlan0 essid "constant" ap 00:03:7F:BF:10:58 enc off
# ifconfig wlan0 up
# ifconfig wlan0

Then

# iwconfig wlan0

reported:


wlan0 IEEE 802.11abg ESSID:"constant"
Mode:Managed Frequency:2.452 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


and

# ifconfig wlan0

reported:


wlan0 Link encap:Ethernet HWaddr 00:1C:BF:61:6A:AF
UP BROADCAST MULTICAST MTU:1500 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)


So I went ahead and tried

# dhclient -d -v wlan0

which got this far:


Internet Systems Consortium DHCP Client 4.1.0p1
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1c:bf:61:6a:af
Sending on LPF/wlan0/00:1c:bf:61:6a:af
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4


before freezing the system, just as NetworkManager had.

I got a bit more info from tail-ing /var/log/messages as it crashed, which showed:

Nov 16 00:37:31 cosmo dhclient: Copyright 2004-2009 Internet Systems Consortium.
Nov 16 00:37:31 cosmo dhclient: All rights reserved.
Nov 16 00:37:31 cosmo dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Nov 16 00:37:31 cosmo dhclient:
Nov 16 00:37:31 cosmo dhclient: Listening on LPF/wlan0/00:1c:bf:61:6a:af
Nov 16 00:37:31 cosmo dhclient: Sending on LPF/wlan0/00:1c:bf:61:6a:af
Nov 16 00:37:31 cosmo dhclient: Sending on Socket/fallback
Nov 16 00:37:31 cosmo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Nov 16 00:37:34 cosmo kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 16 00:37:35 cosmo avahi-daemon[1463]: Registering new address record for fe80::21c:bfff:fe61:6aaf on wlan0.*.

It crashes just after the avahi-daemon log message appears, just at the point where I would hope to see the client receive DHCPACK from the router.

So now I'm stumped and I don't know if this is a problem with OpenWRT, or Fedora. I've searched around a fair amount, but don't really even know where to start.

Can anybody help?

Thanks,
Paul.
Reply With Quote
  #2  
Old 17th November 2009, 05:09 PM
paulch Offline
Registered User
 
Join Date: Nov 2009
Posts: 3
linuxfedorafirefox
Update: I have confirmation from other OpenWRT users that this error is reproducible on other Fedora 11 (and 12) systems. The OpenWRT community are adamant this is a client side (i.e. Fedora) bug.
Reply With Quote
  #3  
Old 17th November 2009, 05:40 PM
leigh123linux
Guest
 
Posts: n/a
linuxfedorafirefox
Quote:
Originally Posted by paulch View Post
Update: I have confirmation from other OpenWRT users that this error is reproducible on other Fedora 11 (and 12) systems. The OpenWRT community are adamant this is a client side (i.e. Fedora) bug.
It looks more like a user configuration error to me.



Code:
Nov 16 00:37:31 cosmo dhclient: Sending on   Socket/fallback
Nov 16 00:37:31 cosmo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Nov 16 00:37:34 cosmo kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 16 00:37:35 cosmo avahi-daemon[1463]: Registering new address record for fe80::21c:bfff:fe61:6aaf on wlan0.*.
Do you use or need IPv6?
Reply With Quote
  #4  
Old 17th November 2009, 06:51 PM
paulch Offline
Registered User
 
Join Date: Nov 2009
Posts: 3
linuxfedorafirefox
Ok, that's an interesting question. It may be an IPv6 config problem. No, I don't need/use it!

So, what should I do next to try and track this down? I am worried about being bounced between FedoraForum and OpenWRT, with each blaming each other (or me) without actually helping!

Thanks,
Paul.

(By the way, if this is a 'user configuration bug' then how come I get it when I haven't 'configured' anything? I.e. I used NetworkManager on an unmodified Fedora install. Even if the config is wrong, its wrong by default and therefore its still a bug in the distro. IMHO!)

Last edited by paulch; 17th November 2009 at 07:14 PM.
Reply With Quote
Reply

Tags
connecting, fedora, locks, openwrt, router, wireless

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Connecting Printer over Wireless-router? creeping death Using Fedora 9 14th May 2009 05:41 PM
connecting fedora 9 to a wireless router kam05r Servers & Networking 5 22nd May 2008 12:31 AM
Connecting with wireless locks up FC5; Unable to set MAC mode Xtremegene Servers & Networking 1 5th August 2006 12:40 AM
newbie needs help connecting to wireless router ozzkoz Servers & Networking 2 12th August 2005 05:29 AM


Current GMT-time: 01:17 (Friday, 29-08-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat