[ CSSCLNT][3160521600]clsssInitNative: failed to connect to (ADDRESS=(PROT

Version: 11.1.0.7.4
What is the meaning of below message in log file under $ORA_CRS_HOME/log/hostname/client ?
$>pwd
/u01/app/oracle/product/11.1.0/crs/log/myhostname/client>
$> cat clsc46.log
Oracle Database 11g CRS Release 11.1.0.7.0 - Production Copyright 1996, 2007 Oracle. All rights reserved.
2010-10-20 10:06:06.997: [ CSSCLNT][3160521600]clsssInitNative: failed to connect to (ADDRESS=(PROTOCOL=ipc)(KEY=OCSSD_LL_myhostname_)), rc 9

Hi
The CSS is trying to start and can not, because any problem.
This message may appear in several problems.
Regards,
Levi Pereira

Similar Messages

  • [ CSSCLNT][1]clsssInitNative: connect failed, rc 9

    Hi All,
    I am installing oracle 10gR2 on IBM AIX v6.1. I am getting the follow error.
    bash-3.00# /u01/app/oracle/product/10.2.0/crs_1/root.sh
    WARNING: directory '/u01/app/oracle/product/10.2.0' is not owned by root
    WARNING: directory '/u01/app/oracle/product' is not owned by root
    WARNING: directory '/u01/app/oracle' is not owned by root
    WARNING: directory '/u01/app' is not owned by root
    WARNING: directory '/u01' is not owned by root
    Checking to see if Oracle CRS stack is already configured
    Setting the permissions on OCR backup directory
    Setting up NS directories
    Oracle Cluster Registry configuration upgraded successfully
    WARNING: directory '/u01/app/oracle/product/10.2.0' is not owned by root
    WARNING: directory '/u01/app/oracle/product' is not owned by root
    WARNING: directory '/u01/app/oracle' is not owned by root
    WARNING: directory '/u01/app' is not owned by root
    WARNING: directory '/u01' is not owned by root
    Successfully accumulated necessary OCR keys.
    Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
    node <nodenumber>: <nodename> <private interconnect name> <hostname>
    node 1: plpar4 plpar4-priv plpar4
    node 2: plpar5 plpar5-priv plpar5
    Creating OCR keys for user 'root', privgrp 'system'..
    Operation successful.
    Now formatting voting device: /dev/rhdisk10
    Format of 1 voting devices complete.
    Startup will be queued to init within 30 seconds.
    Adding daemons to inittab
    Adding daemons to inittab
    Expecting the CRS daemons to be up within 600 seconds.
    Failure at final check of Oracle CRS stack.
    10
    in css.log
    it is showing that
    [ CSSCLNT][1]clsssInitNative: connect failed, rc 9
    Earlier I am getting the error while running root.sh in second node. Based on metalink
    Note:344841.1 . I changed the run level from 2 to 3 (in both nodes). Now I am trying to reinstlling CRS but I am getting the above error in First node. Can any body help me.
    Regards
    Kiran

    Hi All,
    trace : ocssd.log
    ->con: dump of 0x0, len 976
    [    CSSD]--- DUMP GROCK STATE DB ---
    [    CSSD]--- END OF GROCK STATE DUMP ---
    [    CSSD]------- End Dump -------
    [    CSSD]2008-05-16 13:19:12.974 [1030] >TRACE: clssnmReadDskHeartbeat: node(
    1) is down. rcfg(2) wrtcnt(85) LATS(2292599491) Disk lastSeqNo(85)
    Is it helpful to resolve the issue.
    kiran

  • CRS starting problem "CSSCLNT][1]clsssInitNative: connect failed, rc 9"

    We have one 2 node HP-UX 10.2.0.4 cluster. Due to power problems we shutdowned the nodes and started the nodes after a week.
    The CRS is not coming. I check the priv NICs, OCR/VOTE disks and their permissions, etc,...... Everything is fine.
    In the log directory $CRS_HOME/log/<node_name>/client , there were thousands of css*.log files.
    All the file contains same word
    Oracle Database 10g CRS Release 10.2.0.4.0 Production Copyright 1996, 2008 Oracle. All rights reserved.
    2009-04-13 19:50:08.877: [ CSSCLNT][1]clsssInitNative: connect failed, rc 9
    How to solve this issue ?

    delete all the files inside .oracle directoery in /var/tmp or /tmp.

  • When replying to an add on Craig's List, for example, it goes back to my old email address I had with IE, and fails to connect with the ad's author and I'd like to know how to make it use my gmail address with Firefox instead.

    When replying to an ad, via email, posted on Craig's List , for example, it attempts to use my old email address I had with IE, then fails to connect with the ad's author. How do I get it to only use my gmail address with Firefox?
    == This happened ==
    Every time Firefox opened

    See https://support.mozilla.com/en-US/kb/Changing+the+e-mail+program+used+by+Firefox

  • Cannot connect to server with ttisqlcs, Failed to retrieve IP address of the system

    Please help me, I installed timesten server and client on different machines in LAN, but with the same user and group - ttadmin:ttgroup
    When I tried to connect to server with ttisqlcs -connStr "DSN=sampleCS"
    The output gave me error messages as below
    connect "DSN=sampleCS";
    S1000: Failed to retrieve IP address of the system. System error: -2
    The command failed.
    Done.
    The related part in sys.ttconnect.ini is set as below
    [192.168.0.206]
    Description=TimesTen Server
    Network_Address=192.168.0.206
    TCP_PORT=53397
    And the sys.odbc.ini
    [ODBC Data Sources]
    sampleCS=TimesTen 11.2.2 Client Driver
    [sampleCS]
    TTC_SERVER=192.168.0.206
    TTC_SERVER_DSN=nredb_ds
    What does it mean by "retrieve IP" ?
    Does it try to resolve IP by the hostname even when I already gave it the ip address?
    By the way I can ping 192.168.0.206 and telnet at port 53397 with no problem.
    Please help me, thanks~

    Try changing your entries as follows and see if it fixes it:
    sys.ttconnect.ini
    [myserver]
    Description=TimesTen Server
    Network_Address=192.168.0.206
    TCP_PORT=53397
    sys.odbc.ini
    [ODBC Data Sources]
    sampleCS=TimesTen 11.2.2 Client Driver
    [sampleCS]
    TTC_SERVER=myserver
    TTC_SERVER_DSN=nredb_ds
    Chris

  • BB 8320 Failed to obtain IP address when connecting to wireless router

    I do not have a data plan but am trying to connect thru my wireless router.  When i try to connect after typing the WEP Key in it searches and comes back with "Failed to obtain IP address". How do I fix this? 

    Hey LoveKizzy,
    Welcome to the BlackBerry Support Community Forums.
    Use the Wi-Fi Diagnostics tool on your BlackBerry smartphone to find out where the problem is: http://www.blackberry.com/btsc/KB13299
    I hope this helps!
    -HB
    Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
    Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

  • On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

    I have a new install of Windows 2012.  I have two physical servers.  One is a W2012 std Domain Controller ("DC").  The Second is configured as W2012 HyperV  ("HV").  Under HV I have
    two VMs.  One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS").  All systems are behind a firewall appliance.  Exchange is working via Outlook and OWA internally and externally.  The self
    created SSL must be installed manually on external machines since it comes up as an untrusted certificate.  Once installed remote outlook works and OWA works.  I have configured the terminal server and I am able
    to login remotely as various users under my "TS group".  The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
    on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
    for alias@ domain, then fails the logging on to the mail server)  The error reads:  "Outlook cannot log on.  Verify you are connected to the network and are using the proper server and mailbox name.  The
    connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC.  I have
    tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command.  I have also tried to use the guid via "Get-Mailbox
    ALIAS | fl name, exchangeguid.  Keep in mind all desktop users on the network are connecting to Outlook without issue.
    I would appreciate any thoughts on solving this issue.

    Hi,
    According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
    Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
    open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
    Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
    autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Error sending emails to Internet: Failed to connect. Winsock error code: 10051

    Our exchange 2013 CU2 (CAS+MBX, Win2012) was sending emails to Internet using another server (a kerio email server) and outbound internet email was working as expected.
    We have now removed the Kerio server, I also removed the kerio_Send_Connector I was using to send emails to internet and I also changed the email domain in Exchange to be authoritative. I created a new Internet send connector with default values, but the same
    bad behavior is present.
    Our Exchange 2013 receives emails internally and externally with no problems. The problems are sending emails to Internet. I am suspecting something in the firewall but i need to do some more research.
    If from the same Exchange server I telnet to an Internet email host:25 I do get the smtp banner but as soon as I start typing HELO/EHLO I get disconnected and errors are logged.
    Errors when sending emails to any emails address (this is from an email sent to google, all others are the same):
    Remote Server at aspmx3.googlemail.com (74.125.136.26) returned '400 4.4.7 Message delayed'
    7/1/14 9:52:44 a. m. - Remote Server at aspmx3.googlemail.com (74.125.136.26) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10051, Win32 error code: 10051." Attempted
    failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 74.125.136.26:25'
    I cannot find any references from such Winsock error that are related to Exchange 2013.
    So far all email is being queued at the Exchange Server 2013. I am afraid to install CU3 and make things worse.
    Thanks for your comments.

    Just check if the receive connector settings are set to fine
    check the send connector properties and see whether it is  set to use DNS to route emails through external DNS/Internal DNS or smart host .
    Do a telnet to external domain like hotmail,yahoo and see  at what transaction you are getting an error
    Enable verbose logging, restart the transport service and check if you get the same error in the verbose logs as well
    Get in touch with the ISP and see if the port 25 for Outbound SMTP is  opened.
    YOu can check if SMTP Proxy is enabled in the firewall. If so disable the SMTP proxy in the firewall and check.
    Good Luck!!
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.
    That will encourage me - and others - to take time out to help you.
    Regards,
    Sathish

  • Facetime fails to connect

    I am trying to FaceTime with my daughter in Sweden. I am using OS 10.9.4 on a MacBook Pro with Facetime 3.0. She is using an iPad mini with the current software. The query initally goes through and says "connecting" then fails to connect. I have checked the firewall settings in my Airport Extreme and the modem and they are correct, and have tried with the MacBook's firewall on or off without success. What am I missing?
    Randy Black

    Failure to connect is most commonly due to not being fully updated per http://support.apple.com/kb/TS5419 but that does not sound like your case.  Have you tried connecting by using the email address of the recipient instead of a telephone number?

  • Airport fails to connect at login (only)

    Using a MacBook with OSX 10.5, I am trying to connect to a WPA2 Enterprise network. All of the settings are correct, and the certificate is set on 'always trust'.. but on startup/login, Airport fails to connect (no error message, but IP address is self-assigned). If I turn airport off and back on, it properly connects instantly, with no prompts at all.
    Does anyone know a reason why the machine would be unable to automatically connect to the network at login, but able to just fine if I manually turn the airport off and back on?

    Hmm.. in retrospect this probably isn't the right sub-forum for this question.. it should maybe go in a sub-forum for OS X 10.5 instead (it's not related to the airport basestation). Please feel free to move this, if so.

  • Apex fails to connect after rebooting XE

    Hi:
    My environment is Apex 4.0.0, Oracle XE 10.2.0, Apex default Gateway, Windows 2008 32 bit.
    After I reboot the database, Apex fails to connect.
    If I check the Apex port number, it lists 8080, as expected. (SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;)
    Look at the Oracle Listener status below after the reboot, notice the host value in line
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8080))(Presentation=HTTP)(Session=RAW))
    When I reset the Apex port number to 8080, I can then connect OK (EXEC DBMS_XDB.SETHTTPPORT(8080); )
    Look at value of HOST in the Oracle Listener status below after the reset, the HOST lists the Server Name.
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
    This is a major problem, because if the Server is rebooted, nobody can connect to Apex.
    I assume this is an Oracle Listener problem.
    I have made no changes to the LISTENER.ora file, see values below.
    Any suggestions on how to overcome this problem will be helpful.
    Status of Oracle Listener after a reboot.
    LSNRCTL> status
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
    Start Date 02-JUN-2011 09:03:47
    Uptime 42 days 22 hr. 31 min. 5 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Default Service XE
    Listener Parameter File D:\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
    Listener Log File D:\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8080))(Presentation=HTTP)(Session=RAW))
    Status of Listener after resetting the Port number to 8080, notice the HOST = a ServerName in line:
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
    Start Date 02-JUN-2011 09:03:47
    Uptime 42 days 22 hr. 34 min. 40 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Default Service XE
    Listener Parameter File D:\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
    Listener Log File D:\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
    The parameters in LISTENER.ora
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oraclexe\app\oracle\product\10.2.0\server)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = CLRExtProc)
    (ORACLE_HOME = D:\oraclexe\app\oracle\product\10.2.0\server)
    (PROGRAM = extproc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
    (ADDRESS = (PROTOCOL = TCP)(HOST = galapp13.bsci.bossci.com)(PORT = 1521))
    DEFAULT_SERVICE_LISTENER = (XE)

    Hi
    Where did you find the latest WLan driver?
    Here on this Toshiba driver page you can find the latest Wlan driver:
    http://aps2.toshiba-tro.de/wlan/
    I recommend uninstalling firstly the old driver and then to install the newer version.
    Furthermore its necessary to update the BIOS. I read in the forum that similar issues could be solved by BIOS update.
    Greets

  • Wicd fails to connect/inconsistently connects, manual connect works.

    Hi all, wicd is failing to connect after an update today. I've tried both my wired and wireless networks; it fails to connect to both for the majority of the time. I've been able to connect 1 or twice to both without failure, however. Manually running "sudo dhcpcd eth0" connects without issue. The issue seems to be with dhcpcd 5.5.4-1, as a downgrade to the [core] version (5.2.12-4) fixes the issue. Any ideas?
    /var/log/errors.log:
    Feb 8 23:37:53 localhost dhcpcd[5808]: dhcpcd not running
    Feb 8 23:37:54 localhost dhcpcd[5814]: dhcpcd not running
    Feb 8 23:37:54 localhost dhcpcd[5820]: dhcpcd not running
    Feb 8 23:37:57 localhost dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
    Feb 8 23:38:00 localhost dhcpcd[5856]: dhcpcd not running
    Feb 8 23:39:50 localhost dhcpcd[6067]: dhcpcd not running
    Feb 8 23:39:50 localhost dhcpcd[6074]: dhcpcd not running
    Feb 8 23:39:51 localhost dhcpcd[6082]: dhcpcd not running
    Feb 8 23:40:08 localhost dhcpcd[6216]: dhcpcd not running
    Feb 8 23:40:09 localhost dhcpcd[6238]: dhcpcd not running
    /var/log/wicd/wicd.log:
    2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: checking for 192.168.1.7
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 :: dhcpcd[3603]: forked to background, child pid 3626
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 :: DHCP connection successful
    2012/02/08 23:26:04 :: Connecting thread exiting.
    2012/02/08 23:26:05 :: Sending connection attempt result success
    2012/02/08 23:27:23 :: Connecting to wireless network s_wifi
    2012/02/08 23:27:24 :: Putting interface down
    2012/02/08 23:27:24 :: Releasing DHCP leases...
    2012/02/08 23:27:24 :: Setting false IP...
    2012/02/08 23:27:24 :: Stopping wpa_supplicant
    2012/02/08 23:27:24 :: Flushing the routing table...
    2012/02/08 23:27:24 :: Putting interface up...
    2012/02/08 23:27:26 :: Running DHCP with hostname carbon
    2012/02/08 23:27:26 :: dhcpcd[3760]: version 5.5.4 starting
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: waiting for carrier
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: carrier acquired
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sending IPv6 Router Solicitation
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sendmsg: Cannot assign requested address
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: broadcasting for a lease
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:27 :: dhcpcd[3760]: received RA for unexpected interface from fe80::222:75ff:fed5:73d4
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 :: dhcpcd[3760]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 :: dhcpcd[3760]: forked to background, child pid 3784
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 :: DHCP connection successful
    2012/02/08 23:27:27 :: not verifying
    2012/02/08 23:27:27 :: Connecting thread exiting.
    2012/02/08 23:27:30 :: Sending connection attempt result success
    2012/02/08 23:28:04 :: Putting interface down
    2012/02/08 23:28:04 :: Error checking link using /sys/class/net/eth0/carrier
    2012/02/08 23:28:04 :: Releasing DHCP leases...
    2012/02/08 23:28:04 :: Setting false IP...
    2012/02/08 23:28:04 :: Stopping wpa_supplicant
    2012/02/08 23:28:04 :: Flushing the routing table...
    2012/02/08 23:28:04 :: Putting interface up...
    2012/02/08 23:28:06 :: Running DHCP with hostname carbon
    2012/02/08 23:28:06 :: dhcpcd[3899]: version 5.5.4 starting
    2012/02/08 23:28:06 ::
    2012/02/08 23:28:06 :: dhcpcd[3899]: eth0: waiting for carrier
    2012/02/08 23:28:06 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: carrier acquired
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sending IPv6 Router Solicitation
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sendmsg: Cannot assign requested address
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: broadcasting for a lease
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: checking for 192.168.1.7
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: forked to background, child pid 3922
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: DHCP connection successful
    2012/02/08 23:28:08 :: Connecting thread exiting.
    2012/02/08 23:28:09 :: Sending connection attempt result success
    2012/02/08 23:35:31 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:35:31 :: Removing PID file...
    2012/02/08 23:35:31 :: Shutting down...
    2012/02/08 23:35:31 :: Exception KeyError: KeyError(139867792365312,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:35:33 :: ---------------------------
    2012/02/08 23:35:33 :: wicd initializing...
    2012/02/08 23:35:33 :: ---------------------------
    2012/02/08 23:35:33 :: wicd is version 1.7.1 717
    2012/02/08 23:35:33 :: setting backend to external
    2012/02/08 23:35:33 :: trying to load backend external
    2012/02/08 23:35:33 :: successfully loaded backend external
    2012/02/08 23:35:33 :: trying to load backend external
    2012/02/08 23:35:33 :: successfully loaded backend external
    2012/02/08 23:35:33 :: Automatically detected wireless interface wlan0
    2012/02/08 23:35:33 :: setting wireless interface wlan0
    2012/02/08 23:35:33 :: automatically detected wired interface eth0
    2012/02/08 23:35:33 :: setting wired interface eth0
    2012/02/08 23:35:33 :: setting wpa driver wext
    2012/02/08 23:35:33 :: setting use global dns to False
    2012/02/08 23:35:33 :: setting global dns
    2012/02/08 23:35:33 :: global dns servers are None None None
    2012/02/08 23:35:33 :: domain is None
    2012/02/08 23:35:33 :: search domain is None
    2012/02/08 23:35:33 :: setting automatically reconnect when connection drops True
    2012/02/08 23:35:33 :: Setting dhcp client to 0
    2012/02/08 23:35:33 :: Wireless configuration file found...
    2012/02/08 23:35:33 :: Wired configuration file found...
    2012/02/08 23:35:33 :: chmoding configuration files 0600...
    2012/02/08 23:35:33 :: chowning configuration files root:root...
    2012/02/08 23:35:33 :: Using wireless interface...wlan0
    2012/02/08 23:35:33 :: Using wired interface...eth0
    2012/02/08 23:35:47 :: Connecting to wireless network s_wifi
    2012/02/08 23:35:47 :: Putting interface down
    2012/02/08 23:35:48 :: Releasing DHCP leases...
    2012/02/08 23:35:48 :: Setting false IP...
    2012/02/08 23:35:48 :: Stopping wpa_supplicant
    2012/02/08 23:35:48 :: Flushing the routing table...
    2012/02/08 23:35:48 :: Putting interface up...
    2012/02/08 23:35:50 :: Running DHCP with hostname carbon
    2012/02/08 23:35:50 :: dhcpcd[5483]: version 5.2.12 starting
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: waiting for carrier
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: carrier acquired
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: broadcasting for a lease
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: offered 192.168.1.3 from 192.168.1.1
    2012/02/08 23:35:51 ::
    2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: acknowledged 192.168.1.3 from 192.168.1.1
    2012/02/08 23:35:51 ::
    2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: checking for 192.168.1.3
    2012/02/08 23:35:51 ::
    2012/02/08 23:35:55 :: dhcpcd[5483]: wlan0: leased 192.168.1.3 for 283824000 seconds
    2012/02/08 23:35:55 ::
    2012/02/08 23:35:55 :: dhcpcd[5483]: forked to background, child pid 5514
    2012/02/08 23:35:55 ::
    2012/02/08 23:35:55 ::
    2012/02/08 23:35:55 :: DHCP connection successful
    2012/02/08 23:35:55 :: not verifying
    2012/02/08 23:35:55 :: Connecting thread exiting.
    2012/02/08 23:35:58 :: Sending connection attempt result success
    2012/02/08 23:37:39 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:37:39 :: Removing PID file...
    2012/02/08 23:37:39 :: Shutting down...
    2012/02/08 23:37:39 :: Exception KeyError: KeyError(139889612089088,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:37:40 :: ---------------------------
    2012/02/08 23:37:40 :: wicd initializing...
    2012/02/08 23:37:40 :: ---------------------------
    2012/02/08 23:37:40 :: wicd is version 1.7.1 717
    2012/02/08 23:37:40 :: setting backend to external
    2012/02/08 23:37:40 :: trying to load backend external
    2012/02/08 23:37:40 :: successfully loaded backend external
    2012/02/08 23:37:40 :: trying to load backend external
    2012/02/08 23:37:40 :: successfully loaded backend external
    2012/02/08 23:37:40 :: Automatically detected wireless interface wlan0
    2012/02/08 23:37:40 :: setting wireless interface wlan0
    2012/02/08 23:37:40 :: automatically detected wired interface eth0
    2012/02/08 23:37:40 :: setting wired interface eth0
    2012/02/08 23:37:40 :: setting wpa driver wext
    2012/02/08 23:37:40 :: setting use global dns to False
    2012/02/08 23:37:40 :: setting global dns
    2012/02/08 23:37:40 :: global dns servers are None None None
    2012/02/08 23:37:40 :: domain is None
    2012/02/08 23:37:40 :: search domain is None
    2012/02/08 23:37:40 :: setting automatically reconnect when connection drops True
    2012/02/08 23:37:40 :: Setting dhcp client to 0
    2012/02/08 23:37:41 :: Wireless configuration file found...
    2012/02/08 23:37:41 :: Wired configuration file found...
    2012/02/08 23:37:41 :: chmoding configuration files 0600...
    2012/02/08 23:37:41 :: chowning configuration files root:root...
    2012/02/08 23:37:41 :: Using wireless interface...wlan0
    2012/02/08 23:37:41 :: Using wired interface...eth0
    2012/02/08 23:37:46 :: Connecting to wireless network s_wifi
    2012/02/08 23:37:46 :: Putting interface down
    2012/02/08 23:37:46 :: Releasing DHCP leases...
    2012/02/08 23:37:46 :: Setting false IP...
    2012/02/08 23:37:47 :: Stopping wpa_supplicant
    2012/02/08 23:37:47 :: Flushing the routing table...
    2012/02/08 23:37:47 :: Putting interface up...
    2012/02/08 23:37:49 :: Running DHCP with hostname carbon
    2012/02/08 23:37:49 :: dhcpcd[5759]: version 5.5.4 starting
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sending IPv6 Router Solicitation
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sendmsg: Cannot assign requested address
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: broadcasting for a lease
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: forked to background, child pid 5777
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: DHCP connection successful
    2012/02/08 23:37:49 :: not verifying
    2012/02/08 23:37:49 :: Connecting thread exiting.
    2012/02/08 23:37:52 :: Sending connection attempt result success
    2012/02/08 23:37:52 :: Autoconnecting...
    2012/02/08 23:37:53 :: Putting interface downAttempting to autoconnect with wired interface...
    2012/02/08 23:37:53 ::
    2012/02/08 23:37:53 :: Releasing DHCP leases...
    2012/02/08 23:37:53 :: Setting false IP...
    2012/02/08 23:37:53 :: Stopping wpa_supplicant
    2012/02/08 23:37:53 :: Flushing the routing table...
    2012/02/08 23:37:53 :: Putting interface up...
    2012/02/08 23:37:55 :: Running DHCP with hostname carbon
    2012/02/08 23:37:55 :: dhcpcd[5828]: version 5.5.4 starting
    2012/02/08 23:37:55 ::
    2012/02/08 23:37:55 :: dhcpcd[5828]: eth0: waiting for carrier
    2012/02/08 23:37:55 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: carrier acquired
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sending IPv6 Router Solicitation
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: broadcasting for a lease
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: checking for 192.168.1.7
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: forked to background, child pid 5851
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: DHCP connection successful
    2012/02/08 23:37:58 :: Connecting thread exiting.
    2012/02/08 23:38:00 :: Sending connection attempt result success
    2012/02/08 23:38:01 :: No wired connection present, attempting to autoconnect to wireless network
    2012/02/08 23:38:04 :: Unable to autoconnect, you'll have to manually connect
    2012/02/08 23:39:43 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:39:43 :: Removing PID file...
    2012/02/08 23:39:43 :: Shutting down...
    2012/02/08 23:39:43 :: Exception KeyError: KeyError(140388630619904,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:39:45 :: ---------------------------
    2012/02/08 23:39:45 :: wicd initializing...
    2012/02/08 23:39:45 :: ---------------------------
    2012/02/08 23:39:45 :: wicd is version 1.7.1 717
    2012/02/08 23:39:45 :: setting backend to external
    2012/02/08 23:39:45 :: trying to load backend external
    2012/02/08 23:39:45 :: successfully loaded backend external
    2012/02/08 23:39:45 :: trying to load backend external
    2012/02/08 23:39:45 :: successfully loaded backend external
    2012/02/08 23:39:45 :: Automatically detected wireless interface wlan0
    2012/02/08 23:39:45 :: setting wireless interface wlan0
    2012/02/08 23:39:45 :: automatically detected wired interface eth0
    2012/02/08 23:39:45 :: setting wired interface eth0
    2012/02/08 23:39:45 :: setting wpa driver wext
    2012/02/08 23:39:45 :: setting use global dns to False
    2012/02/08 23:39:45 :: setting global dns
    2012/02/08 23:39:45 :: global dns servers are None None None
    2012/02/08 23:39:45 :: domain is None
    2012/02/08 23:39:45 :: search domain is None
    2012/02/08 23:39:45 :: setting automatically reconnect when connection drops True
    2012/02/08 23:39:45 :: Setting dhcp client to 0
    2012/02/08 23:39:45 :: Wireless configuration file found...
    2012/02/08 23:39:45 :: Wired configuration file found...
    2012/02/08 23:39:45 :: chmoding configuration files 0600...
    2012/02/08 23:39:45 :: chowning configuration files root:root...
    2012/02/08 23:39:45 :: Using wireless interface...wlan0
    2012/02/08 23:39:45 :: Using wired interface...eth0
    2012/02/08 23:39:50 :: Autoconnecting...
    2012/02/08 23:39:50 :: Attempting to autoconnect with wired interface...
    2012/02/08 23:39:50 :: Putting interface down
    2012/02/08 23:39:51 :: Releasing DHCP leases...
    2012/02/08 23:39:51 :: Setting false IP...
    2012/02/08 23:39:51 :: Stopping wpa_supplicant
    2012/02/08 23:39:51 :: Flushing the routing table...
    2012/02/08 23:39:51 :: Putting interface up...
    2012/02/08 23:39:53 :: Running DHCP with hostname carbon
    2012/02/08 23:39:53 :: dhcpcd[6087]: version 5.2.12 starting
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: waiting for carrier
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: carrier acquired
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: broadcasting for a lease
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:39:54 ::
    2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:39:54 ::
    2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: checking for 192.168.1.7
    2012/02/08 23:39:54 ::
    2012/02/08 23:39:58 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:39:58 :: Removing PID file...
    2012/02/08 23:39:58 :: Shutting down...
    2012/02/08 23:39:58 :: Exception KeyError: KeyError(140583090784000,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:40:00 :: ---------------------------
    2012/02/08 23:40:00 :: wicd initializing...
    2012/02/08 23:40:00 :: ---------------------------
    2012/02/08 23:40:00 :: wicd is version 1.7.1 717
    2012/02/08 23:40:00 :: setting backend to external
    2012/02/08 23:40:00 :: trying to load backend external
    2012/02/08 23:40:00 :: successfully loaded backend external
    2012/02/08 23:40:00 :: trying to load backend external
    2012/02/08 23:40:00 :: successfully loaded backend external
    2012/02/08 23:40:00 :: Automatically detected wireless interface wlan0
    2012/02/08 23:40:00 :: setting wireless interface wlan0
    2012/02/08 23:40:00 :: automatically detected wired interface eth0
    2012/02/08 23:40:00 :: setting wired interface eth0
    2012/02/08 23:40:00 :: setting wpa driver wext
    2012/02/08 23:40:00 :: setting use global dns to False
    2012/02/08 23:40:00 :: setting global dns
    2012/02/08 23:40:00 :: global dns servers are None None None
    2012/02/08 23:40:00 :: domain is None
    2012/02/08 23:40:00 :: search domain is None
    2012/02/08 23:40:00 :: setting automatically reconnect when connection drops True
    2012/02/08 23:40:00 :: Setting dhcp client to 0
    2012/02/08 23:40:00 :: Wireless configuration file found...
    2012/02/08 23:40:00 :: Wired configuration file found...
    2012/02/08 23:40:00 :: chmoding configuration files 0600...
    2012/02/08 23:40:00 :: chowning configuration files root:root...
    2012/02/08 23:40:00 :: Using wireless interface...wlan0
    2012/02/08 23:40:00 :: Using wired interface...eth0
    2012/02/08 23:40:09 :: Putting interface down
    2012/02/08 23:40:09 :: Releasing DHCP leases...
    2012/02/08 23:40:09 :: Setting false IP...
    2012/02/08 23:40:09 :: Stopping wpa_supplicant
    2012/02/08 23:40:09 :: Flushing the routing table...
    2012/02/08 23:40:09 :: Putting interface up...
    2012/02/08 23:40:11 :: Running DHCP with hostname carbon
    2012/02/08 23:40:11 :: dhcpcd[6245]: version 5.2.12 starting
    2012/02/08 23:40:11 ::
    2012/02/08 23:40:11 :: dhcpcd[6245]: eth0: waiting for carrier
    2012/02/08 23:40:11 ::
    2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: carrier acquired
    2012/02/08 23:40:12 ::
    2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: broadcasting for a lease
    2012/02/08 23:40:12 ::
    2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:40:13 ::
    2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:40:13 ::
    2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: checking for 192.168.1.7
    2012/02/08 23:40:13 ::
    2012/02/08 23:40:18 :: dhcpcd[6245]: eth0: leased 192.168.1.7 for 283824000 seconds
    2012/02/08 23:40:18 ::
    2012/02/08 23:40:18 :: dhcpcd[6245]: forked to background, child pid 6272
    2012/02/08 23:40:18 ::
    2012/02/08 23:40:18 ::
    2012/02/08 23:40:18 :: DHCP connection successful
    2012/02/08 23:40:18 :: Connecting thread exiting.
    2012/02/08 23:40:19 :: Sending connection attempt result success
    excerpt from dmesg:
    [ 220.232167] iwlwifi 0000:03:00.0: PCI INT A disabled
    [ 235.617077] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [ 235.617084] Copyright(c) 2003-2011 Intel Corporation
    [ 235.617227] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    [ 235.617297] iwlwifi 0000:03:00.0: setting latency timer to 64
    [ 235.617467] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [ 235.617472] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900117e4000
    [ 235.617477] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [ 235.618087] iwlwifi 0000:03:00.0: irq 56 for MSI/MSI-X
    [ 235.618299] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [ 235.618699] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 235.647477] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [ 235.647483] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
    [ 235.647488] iwlwifi 0000:03:00.0: Valid Tx ant: 0X7, Valid Rx ant: 0X7
    [ 235.647519] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [ 235.650620] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [ 235.650965] Registered led device: phy1-led
    [ 235.651159] ieee80211 phy1: Selected rate control algorithm 'iwl-agn-rs'
    [ 246.254967] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 246.261863] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 246.530405] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 246.537210] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 246.685081] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 251.545715] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 251.552573] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 251.752912] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 252.006076] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.058081] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.060295] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 252.305685] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.357970] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.359622] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 253.667466] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 253.674333] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 253.880956] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 254.137065] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 254.189437] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 254.191042] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 254.282074] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 254.288879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 254.493939] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 256.572737] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 256.627057] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 256.634142] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 256.636012] wlan0: authenticated
    [ 256.737360] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 256.786082] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 256.826726] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 256.828337] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 256.881172] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 256.884801] wlan0: authenticated
    [ 256.986051] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 256.991611] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 256.991618] wlan0: associated
    [ 257.006311] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 541.311145] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 541.368832] cfg80211: Calling CRDA to update world regulatory domain
    [ 541.453885] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 541.460755] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 541.683356] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 542.134773] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 542.187993] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 542.189715] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 545.110702] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 545.111269] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 546.693999] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 546.700730] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 546.936168] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 547.190401] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 547.243068] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 547.244623] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 547.340217] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 547.347099] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 547.560981] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 549.644554] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 549.647565] wlan0: authenticated
    [ 549.647945] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 549.651558] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 549.651564] wlan0: associated
    [ 549.664372] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 551.461505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 551.463148] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 552.308069] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 552.361536] cfg80211: Calling CRDA to update world regulatory domain
    [ 552.462798] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 552.469740] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 552.690035] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 552.942343] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 552.994174] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 552.995790] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 555.897119] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 555.898730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 579.349813] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 579.356589] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 579.591802] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 579.846307] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 579.898914] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 579.900576] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 580.152275] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 580.205302] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 580.206916] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 582.895184] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 582.896930] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 585.270436] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 585.277198] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 585.499201] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 585.854505] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 585.906564] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 585.908183] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 588.995907] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 588.997528] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 663.872912] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 663.879693] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 664.081192] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 664.334184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 664.385981] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 664.387425] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 664.487889] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 664.494654] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 664.717618] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 666.791284] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 666.793798] wlan0: authenticated
    [ 666.794109] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 666.797735] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 666.797743] wlan0: associated
    [ 666.813158] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 667.322243] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 667.323899] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 670.192203] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 670.263747] cfg80211: Calling CRDA to update world regulatory domain
    [ 670.358193] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 670.365031] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 670.589231] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 670.840405] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 670.893001] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 670.894626] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 675.344581] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 675.346128] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 703.509218] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 703.515992] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 703.736371] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 703.985977] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.038426] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.040078] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 704.292262] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.344831] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.346446] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 706.924844] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 706.926454] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 709.146741] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 709.153635] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 709.380526] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 709.727666] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 709.779778] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 709.781421] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 712.682663] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 712.683237] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1163.099577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1163.106361] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1163.334124] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1163.785622] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1163.838170] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1163.839786] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1164.088913] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1164.141284] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1164.142888] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1166.755012] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1166.761833] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1166.791221] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1167.001157] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1167.002730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1167.256207] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1167.308293] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1167.309927] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1167.433323] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1167.440189] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1167.683916] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1169.766437] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 1169.769518] wlan0: authenticated
    [ 1169.769895] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 1169.773508] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 1169.773514] wlan0: associated
    [ 1169.788727] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1170.264529] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1170.266191] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1250.157515] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 1250.213474] cfg80211: Calling CRDA to update world regulatory domain
    [ 1250.304748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1250.311548] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1250.531278] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1250.786838] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1250.839522] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1250.841153] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1253.742306] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1253.743948] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1285.564500] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1285.571291] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1285.799384] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1286.050860] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1286.102984] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1286.104632] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1286.225143] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1286.231901] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1286.434212] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1288.467235] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 1288.469740] wlan0: authenticated
    [ 1288.470052] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 1288.473730] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 1288.473738] wlan0: associated
    [ 1288.485867] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1289.075695] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1289.077339] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1291.610215] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 1291.654374] cfg80211: Calling CRDA to update world regulatory domain
    [ 1291.749248] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1291.755994] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1291.979161] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1292.230432] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.283644] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.285268] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1292.534611] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.586642] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.588281] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1293.916374] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1293.923205] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1294.158126] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1294.410095] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1294.461555] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1294.463149] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1296.861675] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1296.863283] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1299.572965] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1299.579879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1299.802442] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1300.160999] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1300.212812] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1300.214548] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1303.095815] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1303.097470] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1409.502302] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1409.509094] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1409.732008] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1409.987074] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.039305] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.040915] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1410.289187] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.342358] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.344038] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1413.025445] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1413.027081] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1427.879453] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1427.886240] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1428.101077] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1428.452191] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.505126] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.506718] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1428.756124] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.808184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.809809] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1431.511433] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1431.513072] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    roobie wrote:
    I had a similar problem yesterday (especially reffering to the error "Exception KeyError: KeyError(-1219500352,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored"
    And after reading https://bbs.archlinux.org/viewtopic.php?id=121589 i synced my system time with my hwclock and it worked after that. The command I used:
    hwclock -u -systohc
    It may be the cause of your problem as well...
    My hardware clock and system time are in sync and there's no change of time in my logs like is mentioned in the thread. I don't think this is the issue.
    EDIT: This seems to be limited to my home network, possibly an IPv6 problem. Maybe the IPv6 address is not being assigned properly somewhere?
    Last edited by soupcan (2012-02-10 00:23:03)

  • IPad fails to connect to Wi-Fi????

    After eliminating e-mail's with no message my iPad fails to connect to my Wi-Fi, yet my Touch connects. How to resolve?

    Some things to try first:
    1. Turn Off your iPad. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
    2. Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
    3. Change the channel on your wireless router (Auto or Channel 6 is best). Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
    4. Go into your router security settings and change from WEP to WPA with AES.
    5.  Renew IP Address: (especially if you are droping internet connection)
        •    Launch Settings app
        •    Tap on Wi-Fi
        •    Tap on the blue arrow of the Wi-Fi network that you connect to from the list
        •    In the window that opens, tap on the Renew Lease button
    ~~~~~~~~~~~~~~~~~~~~~~~~~
    iOS 6 Wifi Problems/Fixes
    Fix For iOS 6 WiFi Problems?
    http://tabletcrunch.com/2012/09/27/fix-ios-6-wifi-problems/
    Did iOS 6 Screw Your Wi-Fi? Here’s How to Fix It
    http://gizmodo.com/5944761/does-ios-6-have-a-wi+fi-bug
    How To Fix Wi-Fi Connectivity Issue After Upgrading To iOS 6
    http://www.iphonehacks.com/2012/09/fix-wi-fi-connectivity-issue-after-upgrading- to-ios-6.html
    iOS 6 iPad 3 wi-fi "connection fix" for netgear router
    http://www.youtube.com/watch?v=XsWS4ha-dn0
    Apple's iOS 6 Wi-Fi problems
    http://www.zdnet.com/apples-ios-6-wi-fi-problems-linger-on-7000004799/
    ~~~~~~~~~~~~~~~~~~~~~~~
    Look at iOS Troubleshooting Wi-Fi networks and connections  http://support.apple.com/kb/TS1398
    iPad: Issues connecting to Wi-Fi networks  http://support.apple.com/kb/ts3304
    WiFi Connecting/Troubleshooting http://www.apple.com/support/ipad/wifi/
    How to Fix: My iPad Won't Connect to WiFi
    http://ipad.about.com/od/iPad_Troubleshooting/ss/How-To-Fix-My-Ipad-Wont-Connect -To-Wi-Fi.htm
    iOS: Connecting to the Internet http://support.apple.com/kb/HT1695
    iOS: Recommended settings for Wi-Fi routers and access points  http://support.apple.com/kb/HT4199
    How to Quickly Fix iPad 3 Wi-Fi Reception Problems
    http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
    iPad Wi-Fi Problems: Comprehensive List of Fixes
    http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
    Fix iPad Wifi Connection and Signal Issues  http://www.youtube.com/watch?v=uwWtIG5jUxE
    Fix Slow WiFi Issue https://discussions.apple.com/thread/2398063?start=60&tstart=0
    How To Fix iPhone, iPad, iPod Touch Wi-Fi Connectivity Issue http://tinyurl.com/7nvxbmz
    Unable to Connect After iOS Update - saw this solution on another post.
    https://discussions.apple.com/thread/4010130
    Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
    ~~~~~~~~~~~~~~~
    If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
     Cheers, Tom

  • Ipad2 'fails to connect' to my Wifi.

    My Ipad2 'fails to connect' to my Wifi whereas my Iphone 3GS successfully connects and works without issue on the same router. Wifi is WEP encrypted with 26 character code. The Ipad 2 sees the network, yet will not connect. I have tried the 'reset network settings' option and I'm looking for any further suggestions?

    The process of checking your router settings depends on the router you have.  You will need the manual that came with your router.  If you don't have one, you probably can download a manual from the router manufacturer's website.
    Basically the process is starting your web browser on a computer that is connected to your network.  Entering the IP address of the router in the web address line.  Usually the IP address of the router is the same as the IP address of the computer connected to your network except the last number is 1.  For example if the IP address of the computer is 192.168.0.132, then the IP address of the router would be 192.168.0.1.
    The next question you may have is how do you find the IP address of the computer. If you have a Windows computer, go to Start/Run or Start/Programs/Accessories/Run. Type in "CMD" (no quote marks) and press the Enter key.  A DOS window will appear.  At the command prompt type "ipconfig" and press the Enter key.  The resulting listing should show you the IP address of the computer and the IP address of your router (listed as Default Gateway.)  If you have a Mac I can't help you, because I don't have a Mac, but I'm sure someone on this forum would be able to help.
    Once you enter th IP Address of your router, you should get a login screen.  You will need to log into the router.  Note that the login password is not the network passcode.  If you do not know the Admin login name and password and you are sure no one has changed the password from the default, the router manual will have this information.
    When you are logged into the router you need to consult the router manual to find out how to check the settings.  If purchance you have a D-link DIR-625 I can help.

  • Wifi scans but fails to connect on Thinkpad W520

    Running Network Manager on a Lenovo Thinkpad W520 and able to scan but unable to connect to wifi.  Wifi works fine in dualboot on Windows, and ethernet works fine in both.
    $ lspci -vv
    03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
    Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 35
    Region 0: Memory at d5300000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: <access denied>
    Kernel driver in use: iwlwifi
    $ sudo systemctl status NetworkManager-wait-online.service
    ● NetworkManager-wait-online.service - Network Manager Wait Online
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Sun 2014-12-21 22:58:55 EST; 12min ago
    Main PID: 500 (code=exited, status=1/FAILURE)
    Dec 21 22:58:55 Defiant systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE
    Dec 21 22:58:55 Defiant systemd[1]: Failed to start Network Manager Wait Online.
    Dec 21 22:58:55 Defiant systemd[1]: Unit NetworkManager-wait-online.service entered failed state.
    Dec 21 22:58:55 Defiant systemd[1]: NetworkManager-wait-online.service failed.
    $ sudo systemctl status NetworkManager-dispatcher.service
    ● NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled; vendor preset: disabled)
    Active: inactive (dead)
    $ sudo systemctl status NetworkManager.service
    ● NetworkManager.service - Network Manager
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Active: active (running) since Sun 2014-12-21 22:58:23 EST; 13min ago
    Main PID: 341 (NetworkManager)
    CGroup: /system.slice/NetworkManager.service
    └─341 /usr/bin/NetworkManager --no-daemon
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Disabling autoconnect for connection 'Bifröst'.
    Dec 21 23:10:12 Defiant NetworkManager[341]: <warn> Activation (wlp3s0) failed for connection 'Bifröst'
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): deactivating device (reason 'none') [0]
    Dec 21 23:10:12 Defiant NetworkManager[341]: <warn> Connection disconnected (reason -3)
    Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): supplicant interface state: completed -> disconnected
    Dec 21 23:10:15 Defiant NetworkManager[341]: <warn> Could not get scan request result: Scan request rejected
    Additionally, after stopping NetworkManager and trying wifi-menu, it scans correctly but fails to connect, never even prompting for a passphrase.
    So I tried wpa_supplicant on its own:
    $ sudo wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase "Bifr\xc3\xb6st" "mypassword")
    Successfully initialized wpa_supplicant
    wlp3s0: failed to initialize driver interface
    For good measure:
    $ rfkill list
    0: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: no
    Hard blocked: no
    1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    2: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
    $ ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f0:de:f1:62:13:b8 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.11/24 brd 10.0.0.255 scope global enp0s25
    valid_lft forever preferred_lft forever
    3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:24:d7:c6:ab:48 brd ff:ff:ff:ff:ff:ff
    I'm at a loss. and I've googled my little heart out.  Any help would be appreciated.

    Welcome to the forums - and thanks for a great initial post, all the needed information seems to be here.
    Specifically, the following error from wpa_supplicant will most likely be best to dig into:
    wlp3s0: failed to initialize driver interface
    I see several results of this error in a google search, but none of them quickly translated into solutions yet.  To get some more information on it, could you run the same wpa_supplicant command, but with the verbose debugging flag "-dd" and post the ouput here?
    I don't have a intel wireless card, so I don't know what the diagnostic signs are for the problem addressed in the wiki, but you may want to try the modprobe options shown in this section of the wiki.
    EDIT: there is a similar but unresolved thread on these forums here which points to using the -D flag for wpa_supplicant to specify other drivers.  I was thinking this too upon my first reading, but I don't fully understand what these are so I was reluctant to suggest it.  It certainly can't hurt anything to use the command in the wiki to see which drivers are available, then try each one.
    EDIT 2: and this thread seems to indicate that the -D flag driver specification is the right solution.  So start here with the -D flag and only if that fails follow up with my initial debugging suggestions.
    Last edited by Trilby (2014-12-22 12:52:13)

Maybe you are looking for

  • New to Mac and to video editing...need some guidance, please

    I've decided to make the switch and ordered a new 3Ghz 24" iMac. I chose a 1TB HD and 4G of RAM. I want to do some photo and video editing (nothing professional, simply vacation photos and video). I'll be purchasing an HD camcorder later this year to

  • Server 2012 Standard error 0x80073701 when installing DHCP role

    Have not been able to get past this error no matter what Google or Technet has to offer. Please Help!

  • Minority interest - functional knowledge & grouping for Consolidation

    Hi Experts, Scenario A > holds 100% in B, 10% in C, 5% in D B > holds 90% in C, 95% in D, 100 % in E, 1 % in F E > holds 99 % in F No shares are owned by parties outside the group. 1) Minority Interest In case like this will MI be accounted for? Can

  • WebServer problem on cfp-2220

    I've seen older posts on this, but not a solution.  I cannot get the web server to run on my cfp-2220.  I have set it up in the configuration, tried several ports, deployed and rebooted many times.  When I try to create the web service, no servers sh

  • Recipient stops hearing me after few minutes in a ...

    Hello, For the last few weeks I have this problem: everything's okay for the first few minutes and then the recipient stops hearing me completely. This happens every single time, I am helpless. I use Skype for years and never came across anything lik