[Solved] Ubuntu 12.04 WPA2 Detects Wireless Network But Fails to Connect to Router

Asked by Julianloui

My Ubuntu 12.04 computer works in WEP security mode but not in WPA2. WPA2 detects the wireless network but fails to connect to it. My nephew's computer works in WPA2 fine in WIndows 7 but fails to connect to the Internet when switched to Ubuntu 12.04.
I seem to have read some Internet reports that this is a known Ubuntu 12.04 bug.

I would appreciate any help in fixing this problem or in confirming that this is a system software bug.

Julianloui

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Mark Rijckenberg
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What is the output of :

sudo lshw -C network; lsb_release -a; uname -a; sudo dmidecode -t 1

Thanks

Revision history for this message
Julianloui (julianloui) said :
#2

Andrew,
Thanks very much. I hope the information below suffices.
Julianloui

|||||||- lshw output:
  *-network
       description: Wireless interface
       product: AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express)
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:0b:00.0
       logical name: wlan0
       version: 01
       serial: 00:1b:63:cc:7a:f1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=3.2.0-60-generic-pae firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11abgn
       resources: irq:16 memory:d7300000-d730ffff
  *-network
       description: Ethernet interface
       product: 88E8058 PCI-E Gigabit Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:0c:00.0
       logical name: eth0
       version: 13
       serial: 00:1b:63:ab:46:08
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 firmware=N/A latency=0 link=no multicast=yes port=twisted pair
       resources: irq:45 memory:d7200000-d7203fff ioport:3000(size=256) memory:db600000-db61ffff

|||||||- lsb output
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise

|||||||- lsb error
No LSB modules are available.

|||||||- uname output
Linux mc 3.2.0-60-generic-pae #91-Ubuntu SMP Wed Feb 19 04:14:56 UTC 2014 i686 i686 i386 GNU/Linux

|||||||- dmidecode output
# dmidecode 2.11
SMBIOS 2.4 present.

Handle 0x0011, DMI type 1, 27 bytes
System Information
 Manufacturer: Apple Inc.
 Product Name: MacBookPro3,1
 Version: 1.0
 Serial Number: W872805AX91
 UUID: 9CFE245E-D0C8-BD45-A79F-54EA5FBD3D97
 Wake-up Type: Power Switch
 SKU Number: System SKU#
 Family: MacBook Pro

Revision history for this message
Thomas Krüger (thkrueger) said :
#3

What device (router, AP) are you connecting to?

Revision history for this message
Julianloui (julianloui) said :
#4

The AP I am trying to connect to is a Verizon FiOS wireless router made by Actiontek.

Julianloui

Revision history for this message
Thomas Krüger (thkrueger) said :
#5

OK, there are a few reports of troubles with that router and Linux clients but nothing specific. To get a better look into this can you post what is being written to the file /var/log/syslog when you try to connect? The timestamp at the beginning of the lines may be helpful to find the related events.

Revision history for this message
Julianloui (julianloui) said :
#7

[ SOLVED ]
Hi, Everyone,

I am happy to report that i can now connect to the Internet after deleting the following file. Luckily I spotted this solution tonight at www.ubuntuforums.org, to which I am very grateful.

/etc/udev/rules.d/70-persistent-net.rules

Julianloui

Revision history for this message
Julianloui (julianloui) said :
#8

2014-05-17

This confirms that my problem has now been resolved as stated above in Post # 7.

Julianloui

Revision history for this message
Best Mark Rijckenberg (markrijckenberg) said :
#9

Please set the thread status to "solved", if the issue is still solved.

Thanks.

Revision history for this message
Julianloui (julianloui) said :
#10

Thanks Mark Rijckenberg, that solved my question.