Let's see if there are any clues in:Also, I suspect you'll have better luck if your router is set to WPA2 only, not any mixed mode. Please see attached.Code:cat /var/log/syslog | grep etwork | tail -n20
Let's see if there are any clues in:Also, I suspect you'll have better luck if your router is set to WPA2 only, not any mixed mode. Please see attached.Code:cat /var/log/syslog | grep etwork | tail -n20
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
Here you go:
Code:Jun 28 16:45:32 WLT NetworkManager[863]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jun 28 16:45:32 WLT NetworkManager[863]: <info> (eth0): DHCPv4 state changed nbi -> preinit Jun 28 16:45:32 WLT NetworkManager[863]: <info> (eth0): DHCPv4 state changed preinit -> reboot Jun 28 16:45:32 WLT NetworkManager[863]: <info> address 192.168.0.100 Jun 28 16:45:32 WLT NetworkManager[863]: <info> prefix 24 (255.255.255.0) Jun 28 16:45:32 WLT NetworkManager[863]: <info> gateway 192.168.0.1 Jun 28 16:45:32 WLT NetworkManager[863]: <info> nameserver '192.168.0.1' Jun 28 16:45:32 WLT NetworkManager[863]: <info> domain name 'launchmodem.com' Jun 28 16:45:32 WLT NetworkManager[863]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Jun 28 16:45:32 WLT NetworkManager[863]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... Jun 28 16:45:33 WLT NetworkManager[863]: <info> DNS: starting dnsmasq... Jun 28 16:45:33 WLT NetworkManager[863]: <info> (eth0): writing resolv.conf to /sbin/resolvconf Jun 28 16:45:34 WLT NetworkManager[863]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0] Jun 28 16:45:34 WLT NetworkManager[863]: <info> Policy set 'Auto Ethernet' (eth0) as default for IPv4 routing and DNS. Jun 28 16:45:34 WLT NetworkManager[863]: <info> Activation (eth0) successful, device activated. Jun 28 16:45:34 WLT NetworkManager[863]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. Jun 28 16:45:53 WLT NetworkManager[863]: <info> (eth0): IP6 addrconf timed out or failed. Jun 28 16:45:53 WLT NetworkManager[863]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Jun 28 16:45:53 WLT NetworkManager[863]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started... Jun 28 16:45:53 WLT NetworkManager[863]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
We see eth0, that is, your wired ethernet, connecting perfectly. Please detach the ethernet cable, try to connect with wireless and try again.
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
I've tried it without the ethernet cable, and it is still not connecting.
I've redone the
without ethernet cable and here's the results, if that'll help.Code:cat /var/log/syslog | grep etwork | tail -n20
Code:Jun 28 20:25:06 WLT NetworkManager[846]: <info> (wlan0): supplicant interface state: authenticating -> disconnected Jun 28 20:25:06 WLT NetworkManager[846]: <warn> Couldn't disconnect supplicant interface: This interface is not connected. Jun 28 20:25:09 WLT NetworkManager[846]: get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed Jun 28 20:25:09 WLT NetworkManager[846]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 28 20:25:09 WLT NetworkManager[846]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 28 20:25:09 WLT NetworkManager[846]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jun 28 20:25:09 WLT NetworkManager[846]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 28 20:25:09 WLT NetworkManager[846]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 28 20:25:09 WLT NetworkManager[846]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 28 20:25:09 WLT NetworkManager[846]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 28 20:25:09 WLT NetworkManager[846]: <info> Activation (wlan0/wireless): connection 'HOMENET' has security, and secrets exist. No new secrets needed. Jun 28 20:25:09 WLT NetworkManager[846]: <info> Config: added 'ssid' value 'HOMENET' Jun 28 20:25:09 WLT NetworkManager[846]: <info> Config: added 'scan_ssid' value '1' Jun 28 20:25:09 WLT NetworkManager[846]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jun 28 20:25:09 WLT NetworkManager[846]: <info> Config: added 'auth_alg' value 'OPEN' Jun 28 20:25:09 WLT NetworkManager[846]: <info> Config: added 'psk' value '<omitted>' Jun 28 20:25:09 WLT NetworkManager[846]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 28 20:25:09 WLT NetworkManager[846]: <info> Config: set interface ap_scan to 1 Jun 28 20:25:11 WLT NetworkManager[846]: <info> (wlan0): supplicant interface state: disconnected -> scanning Jun 28 20:25:11 WLT NetworkManager[846]: <info> (wlan0): supplicant interface state: scanning -> authenticating
When you click the Network Manager icon and edit connections, is IPv6 set to Ignore? That seems to be a common Google hit searching for this mysterious listing:Is your router reset to WPA2 only?get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
I, um, don't know how to edit my router. It was set up by someone else.
Also, the IPv6 is set to automatic; I've double checked.
Last edited by 42th; June 29th, 2012 at 11:30 PM.
I'm very sorry if I didn't make myself clear. I'm requesting that you set IPv6 to Ignore and not automatic.Also, the IPv6 is set to automatic; I've double checked.
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
Oh, sorry.
I've set the IPv6 setting to ignore now, but it still won't connect.
May I see:Code:cat /sys/module/iwlwifi/parameters/11n_disable
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
Here you go:
Code:1
Bookmarks