Wifi as car remote - manual connect

My car (a Mitsubishi Outlander PHEV) has its own SSID which is used to connect and operate f.ex pre heating.
My phone connects to this wifi-network just fine, but then stays connected until I connect to another wifi-network, turn off wifi or deletes the network from my phone.
What I want is to keep auto connect as default for all networks, but I want to be able to set manual connect for some networks, f.ex my car's Wifi. I also need to be able to do a disconnect from the car's network when I am finnished operating it, as I want to use 3G when in the car without the hazle of turning Wifi off and then remember to turn it on again when I am no longer in the car.
IOS seems to have auto connect on or off for all wifi-networkc as the only option, and no disconnect function exists as far as I can see.

I only partly understand your answer
1: "There is no way to do what you want." - ok, then I request a change in IOS. Who can handle this?
2: "Why does it have to auto disconnect?" I have not written that it disconnects! I want to manually disconnect to be able to use 3G. And I want to mannually connect to this network - no auto connect for this network.

Similar Messages

Imac won't wake up connected to wifi. i have to manually connect now. how do i fix?

my imac won't wake up connected to wifi. i have to manually connect now. how do i fix?

Many have had success using the following. If you don't understand the text then watch the YouTube video.
Lion WiFi problems fix & WiFi Lion Fix on YouTube

I just switched from iphone 4s to LG G3. I'm having issues with bluetooth in my car, iphone would sync automatically but with G3 I have to manually connect to my car's bluetooth every time I turn it on - it won't sync automatically. Any fixes?

I just switched from iphone 4s to LG G3. I'm having issues with bluetooth in my car, iphone would sync automatically but with G3 I have to manually connect to my car's bluetooth every time I turn it on - it won't sync automatically. Any fixes?

You can turn on BT tethering but it disables Wifi so if I have to do that step every time I get in my car, I just as well manually connect on BT every time.

Since upgrading to Lion OS, the wifi connectivity keeps blocking up intermittently and we need to manually keep switching on and off the wifi utility to get the connection back. even locking the preferred wifi network in system preferences does not help.

Since upgrading to Lion OS 10.7.1, the wifi connectivity keeps blocking up intermittently and we need to manually keep switching on and off the wifi utility to get the connection back. even locking the preferred wifi network in system preferences does not help. This never used to happen with Snow Leopard

This is a big thank you to Rys Sinnefeldt who posted this fix.
Rys has made this fix very easy to do and takes literally 2 mins. It involves replacing the Atheros Lion driver 4.0 and replacing it with the snow leopard driver. Don't worry, Rys has made this so simple to do even I could do it and so far I have had no more wifi drops.
follow this link
http://rys.pixeltards.com/2011/09/04/osx-lion-wifi.html
Thanks again to Rys.

VZaccess Manager changes WiFi connections to manually connect from automatic

VZaccess Manager changes WiFi connections to manually connect from automatic.
I have Panasonic CF-19s with VZaccess manager installed with a NDIS connection that automatically connects to Cellular service. I need my WiFI connections to also connect when available and have them set to automatically connect and managed by Windows (WiFi connection in accessmanager is set to None). When I first configure it, it works fine and we use Netmotion to decide which connection to use. After exiting VZaccess manager and restarting it, it changes my WiFi connections to "manually connect" even though accessmanager is not managing it. As soon as I exit out of Accessmanager the connections are changed back to "automatically connect". I need both connections to be active at the same time so the switchover to cellular is immediate when the WiFi connection is lost.

Hi,
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options
Your instance is started from the 10g ORACLE_HOME. You mentioned you started it from the 11g ORACLE_HOME but it's not the case.
Here is an example with a 10gR2 database started from a 11gR2 ORACLE_HOME :
SQL> startup upgrade pfile =/u01/app/oracle/product/10.2.0/db_1/dbs/initP102.ora
ORA-32006: BACKGROUND_DUMP_DEST initialization parameter has been deprecated
ORA-32006: USER_DUMP_DEST initialization parameter has been deprecated
ORACLE instance started.
Total System Global Area 167387136 bytes
Fixed Size                  1335248 bytes
Variable Size              88080432 bytes
Database Buffers           75497472 bytes
Redo Buffers                2473984 bytes
Database mounted.
Database opened.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsNotice the Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 part.
In your case it was Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0
To solve the issue follow the official documentation, you have specific actions with oradim etc. to do (it's always a bit more complicated than with Unix/Linux but it's documented) :
http://download.oracle.com/docs/cd/B28359_01/server.111/b28300/upgrade.htm#insertedID8
Best regards
Phil

Upgaded ios on 3gs to ios 6.0. Manual connect to wifi and works. Will not reconnect after the phone shuts off unless I do it manually. The old ios would. Suggestions??

Upgraded ios on iphone 3GS to ios 6.0. I manually connected to the wifi and it works. After the phone shuts off, it will not connect back to wifi when it turns on unless I reconnect manually again. I have the "Ask to join Networks" button turned on. Frustrating and could get expensive if I forget and start using ATT data. Suggestions??

Settings, Reset, Reset Network Settings. Then attempt to connect again. Passwords will be deleted when you do this, so it will ask for the password again. After that, see if it will connect.

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

Remote Desktop Connection stopped working

I made a change to my Verizon TV and Internet package, downgrading from Ultimate HD to Extreme HD and from 35/35 to 25/25. This morning, when I ran a speed test it showed the new speed. I went out for a few hours, and when I returned, my internet connection was not working at all.
I called Verizon's support number and, after talking to two different people, one who wanted to swap out my router, and one who wanted to send a tech to check out my ONT, they finally figured out the problem was with their configuration, not any of the hardware in my house, and got me running again at the correct speed.
During the trouble shooting process, they had me do multiple soft and hard reboots of my router, they remotely rebooted it, and had me push the recessed reset button once, restoring it to factory defaults. This led to problems with my wireless devices, so I loaded a configuration file to the router that I had thankfully saved some time prior to this problem, and everything seemed to be working properly.
Then, I tried to open a remote desktop connection from one of my machines to another one, both on my internal home network, a connection that had worked flawlessly up until now, and it would not work. Moreover, trying to ping the "remote" machine from the one trying to initiate the connection gets no reply, but pings are replied to in the other direction. And, both machines can see and access each other's shared folders and files, and both can see each other in the network map in the networking and sharing control panel app.
I never made any configuration changes to either machine during the trouble shooting process, but to be sure, I used system restore on both machines and took them back to restore points made yesterday, when everything was working.
I am at a loss to understand what has gone wrong, and would appreciate any constructive and helpful suggestions as to how to remedy this situation.
ps
I am running two different web servers on the target machine, and am running stunnel on it to provide secure nntp connections to a news client that doesn't have that capability built in, and none of these servers are available from other machines. Nothing seems to be getting through to the target pc except windows network sharing!

dslr595148 wrote:
#1 In the router go to Advanced -> Universal Plug and Play OR to Advacned -> UPnP (what ever exist in your router).
#2 If you do not have at least two special computers that support Universal Plug and Play (UPnP) where you can not define the ports that they use, turn off UPnP.
A perfect example. At least two game consoles. Any two (Two Xboxes, two Playstations, One Xbox and one Playstation).
#3 If you have at least two special computers that support UPnP where you can not define the ports that they use....
Do you only use one at time or are there times when at least two are on?
#4 In the router go to Advanced -> IP Address Distribution Or to Advanced -> Private LAN
#5 What is the Starting and Ending IP Address, that is listed in there?
We have two Xboxes and a Logitech Revue. I have Windows Media Sharing enabled on three computers, and am also running a beta of Logitech Media Server on one. It is possible that there are times when two or more streaming clients are in operation, but that is a very rare occasion. Two of the computers, the ones I mention in my original post, are on almost continuously.
In Advanced -> Universal Plug and Play, both Allow Other Network Users to Control Wireless Broadband Router's Network Features and Enable Automatic Cleanup of Old Unused UPnP Services are checked, and WAN Connection Publication: is set to Publish Only the Main WAN Connection.
In Advanced -> IP Address Distribution, under Dynamic IP Range it says192.168.1.2 - 192.168.1.254. However, in Advanced -> IP Address Distribution -> Connection List I have set all the lease types to Static, because I was having problems using the Verizon web page to access my set top boxes, particularly the MRDVR. The Static IP addresses for the computers, game consoles, Bluray player etc. are in the range 192.168.1.2 - 192.168.1.12, and the set top boxes are at 192.168.1.100 & 192.168.1.101.
One thing I did not mention in my original post is that I have two unmanaged gigabit ethernet switches in my home network. There are two computers, the ones I mention in my original post, and the Logitech Revue plugged into one switch. That switch plugs into another switch which also has one pc, an Xbox, and a Bluray player plugged into it, and that switch then plugs into one of the ports on my Verizon supplied Actiontec MI424-WR Rev C, firmware version 4.0.16.1.56.0.10.14.4. All of the other ethernet ports on the router are unused. In addition, we have a laptop, a notebook, another Xbox, and a Wii that connect through the Actiontec's wireless.
I don't know if media streaming is still working and I don't really care if it is because we use it so seldomly. It never worked consistently or to our satisfaction. When we want to watch or listen to media from one computer on another, we copy it over the network from shared folders. We have a Homegroup, to which all of the computers belong. If we want to watch or listen to media on one of the game consoles, we copy it to a flash drive. The Bluray player is only connected to the network for firmware updates and for discs with network enabled content.
This same setup was operating before the problem developed, and I can't figure out what has changed to create the problem. The router configuration file that I am using is from June of 2011, and I'm pretty sure that everything was working fine then, and don't recall making any changes to the router's configuration since then.

Remote Desktop Connection from a Windows 8.1 laptop to a work PC using Windows 7

Hi!
I posted this question in the MS Community forums and they redirected me here... I searched the forums here but didn't find anything that helped with my problem. So here is my original question (posted originally here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/remote-desktop-connection-to-a-work-pc/5fa25045-de24-4a7c-9c8e-caf9ce17e444):
For the past few weeks, I've been trying to set up a VPN connection to my work PC so I can work from home.
Work PC runs on Windows 7 (I assume Pro, but I can't confirm at the moment).
Home laptop runs on Windows 8.1 (the laptop came with Windows 8 already installed, so I assume it's the standard, or Home, edition. I manually upgraded to 8.1).
Now, after many migraines and sleepless nights fiddling with settings, the VPN connection works. However, what prevents me from completing the connection is Remote Desktop Connection.
Here's the error I get:
"Remote Desktop can't find the computer "<computer name>". This might mean that "<computer name>" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
Note:
- I DO have the correct computer name. I have a working connection to my work PC from my personal desktop PC (running XP), though I sometimes need to travel and a laptop is much more practical to carry around than a PC... ;)
The VPN Connection Wizard never asked me to enter my destination PC username and password (so my work Windows credentials). Why?
Any ideas as to why Remote Desktop doesn't want to connect?
Any suggestions as to what I can try to fix the problem?
Thank you for all the help!
Julie

Are you able to ping the remote system by name? It sounds as though you are connecting to VPN but are unable to resolve the names of the host network. A few things that I would think of:
If the home system is not on a domain and the work system is, you may need to use the Fully Qualified Domain Name (FQDN). For example, instead of
computer you would enter computer.domain.com.
You may want to check if your VPN connection is configured as a default gateway, otherwise if your home and VPN network have the same IP address range you may be experiencing a conflict.
See the instructions provided here.
You also may want to check the DNS settings for the VPN connection to ensure that it is finding the DNS server for the remote network and thus is able to resolve the hostname.
You may want to try connecting Remote Desktop via IP address to determine if the issue is with name resolution (DNS) or connectivity.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet

Could not join "wifi network name". A connection timeout occurred.

Mac Pro running 10.7.5.
Whenever the computes wakes from sleep or logs in, it no longer automatically connects to my wifi network. When I manually select the network for from the Wi-Fi status in the menu bar, I get the following message: Could not join "wifi network name". A connection timeout occurred.
Even though I get that message the machine joins the network with no other problems. I am led to believe that is is on the Mac Pro as my Macbook and iPad/iPhone join the network with no issues.
I have tried deleting and restoring the preferred network, and remember networks is checked. I have also restored my airport express base station.
Any suggestions?

Hello,
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
10.5, 10.6, 10.7 & 10.8…
System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
10.5.x/10.6.x/10.7.x instructions...
System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
The interface that connects to the Internet should be dragged to the top of the list.
If using Wifi/Airport...
Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.

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)

Remote desktop connects, black screen, disconnects after a few seconds

I have several servers running Windows Server 2012 R2. These servers are used for testing, and are members of a domain which has two DCs, each of which are running DNS Server.
Yesterday I noticed one of the servers was having an issue with its remote desktop connection. If I try remoting into this machine, it connects to a black screen, sits there for 2-3 seconds and then promptly disconnects. No error message is given. I tried
this from a couple different Windows 7 machines, and got the same result. I tried from my wife's iMac, which runs Jump Desktop, and too was met with the same result.
I can, however, remote into this machine via RDP from my work-issued laptop, which is running Windows 8. However, I cannot remote into the problem machine via Remote Desktop Connection from one of the 2012 R2 servers--I am met with the same result as the
other machines: connect, black screen for 2-3 seconds, disconnect without error.
I can remote into all of the other 2012 R2 servers without issue from any machine, including the iMac. I am experiencing this problem on one server only.
Since it is a test server, I reinstalled Windows from scratch this morning. This meant formatting the SSD and wiping everything out. I reinstalled the drivers, joined the server back to the domain and installed all of the updates available from Windows Update.
And rebooted. And yet, the problem persists!
I tried troubleshooting the "usual suspects," like turning off Windows Firewall, disabling antivirus software (currently none installed), disabling IPv6, setting a static IP instead of using DHCP, etc. I did notice the network adapter said it was
on a Network, not a Domain Network. I corrected DNS settings, and the network reidentified itself as being on the ParietalBone.net network. And yet, the problem persists. Remote Desktop to this server still yields a black screen for 2-3 seconds, followed by
a disconnect--EXCEPT from the aforementioned Windows 8 machine.
I looked in the TerminalServices-LocalSessionManager log on the offending server, and there are no errors. I only see repeated entries that say "Session X has been disconnected, reason code 12," where X is 1 or 2. On a couple occasions, the reason
code is 11. But I don't see any errors indicating a breakdown in security negotiation.
Without any robust logs or debug details, I'm at a loss of where to look for a solution.

I am cautiously optimistic that this may have been resolved.
The network card in the computer was only a 10/100 built-in card, so I replaced it with a 1Gbps card. Interestingly, this did NOT resolve the issue. I ran netsh to check on the state of the chimney offload, but it was already disabled.
In the network card properties, I changed the link speed and duplex from automatic to 1Gbps full, re-ran "netsh int tcp set global chimney=disabled" and rebooted. The problem persisted.
And so I went to the network card properties and set IPv4 Checksum Offload, Large Send Offload (three of these -- IPv4, v2 IPv4 and v2IPv6) and TCP Checksum Offload (IPv4 and IPv6) to Disabled. Jumbo Frames were also disabled. I rebooted again.
After the subsequent reboot, I was able to connect to this Server from machines that previously gave me difficulty. The only machine I haven't been able to test today (I'm in the office) is my wife's iMac, which is at home. However, I was able to bring this
server up via Jump Desktop on my iPad, so I'm suspecting that perhaps one of the offload options was to blame. I'm not sure why this would allow me to connect from some machines but not others. And as noted above, I have many other machines running Server
2012 R2 and they are NOT experiencing this problem. And I've not done any tinkering with network settings on any of them, so their chimney and offload settings are all in the default configuration.
Regarding the other items -- NIC team, virtual machine, etc. -- there was no NIC team, no SRIOV and no RDMA involved.
I had to turn IPv6 off on this machine, and only on this machine, because having it enabled was causing a lot more problems. DNS registration would keep failing, it couldn't pull Group Policy, it couldn't get time sync with the DC, etc. The servers are all
set up with static IPv4 addresses. The router supports IPv6 but I'm not actually using it, so disabling IPv6 wasn't a concern to me.

Remote Database Connection DB2 - Oracle

Hi All
We need to maintain a remote db connection in DBACockpit. We are on DB2 UDB and we need to connect to Oracle. We have all the connection details.
Now my query is do we need to maintain connection details at DB2 level also , or is it enough to maintain them in DBACockpit.
Basically i need to connect from my SAP BI system which is on DB2 UDB 9.1 to Oracle Database.
In oracle we can connect to different databases using TNS functionality, is something there like TNS in DB2 where we have to maintain the remote DB connection details? If yes request you to provide some relevant document for the same
Thanks in Advance.
Regards
Kaleem.

Hi Kaleem,
if you want to administer your ORACLE database through DBACockpit, you need to prepare your system for a DBSL multiconnect to ORACLE as described in note 339092 ( i.e. install ORACLE client, ORACLE DBSL library, etc. ).
This multiconnect can also be used for BI Connect.
If you just want to query some ORACLE tables in your DB2 system, you may also consider to use the DB2 federation feature to create ncicknames within your DB2 database that point to ORACLE tables. In this case I suggest to consult the DB2 manuals on how to do this. You may also have to install an additional DB2 license for the hererogenous federation feature to create nicknames to ORACLE tables.
Regards
Frank

Unable to start remote desktop connection broker

somehow I could no longer start remote desktop connection broker service. I noticed that Windows image acquisition (WIA) service could be started manually and then it stopped by itself. I am not sure if they are related or not. From event viewer, I see some
errors as follows (may be related):
event 485 ESENT
tssdis (2916) An attempt to delete the file "C:\windows\system32\edbtmp.log" filed with system error 5 (0x00000005):"Access is denied." The delete file operation will fail with error- 1032 (0xfffffbf8).
Any clue or suggestion where I can look into?
Thank you very much!!!!!

Hi,
Thank you for your posting in Windows Server Forum.
register the below files using regsvr32
regsvr32 %systemroot%\system32\wuapi.dll
regsvr32 %systemroot%\system32\wuaueng.dll
regsvr32 %systemroot%\system32\wuaueng1.dll
regsvr32 %systemroot%\system32\wucltui.dll
regsvr32 %systemroot%\system32\wups.dll
regsvr32 %systemroot%\system32\wups2.dll
regsvr32 %systemroot%\system32\wuweb.dll
regsvr32 %systemroot%\system32\softpub.dll
In addition, also Try to disable UAC for your account and reboot, this might help to resolve your issue.
Source:
esent 485 event wuaueng.dll
http://social.technet.microsoft.com/Forums/windowsserver/en-US/27cd64d0-7ec7-4732-a2ac-4c36a0513690/esent-485-event-wuauengdll?forum=winservergen
Hope it helps!
Thanks.
Dharmesh Solanki

T500 Intel Wifi 5350 is unable to connect automatically with Windows 8.1

Hello, I have searched the forums to see if there is a similar problem like the one I am having, but, did not come across. I bought my T500 in 2009 with XP installed. I have recently installed Windows 8.1 and started to experience problems with my Intel Wifi 5350. Upon restart, the driver is unable to connect to my home wifi. In order to connect, I need to go through trouble shooting and reset the wifi link, which, then, fixes the problem. When I first installed Windows 8.1, I did not have this problem. It seemed to have happened after a few auto updates.
The driver software I have is 13.3.0.137 with a date of 8/15/2010. Driver provider is Microsoft.
I downloaded but not yet installed Intel® PROSet/Wireless Software for Windows 8.1 Wireless_17.1.0_De164.exe. I am not sure if this will fix it. I wanted to ask this first before I do something. If you have had this before or know the answer, could you please post specific links to which drivers I should install manually? Thanks! I appreciate if you could be specific in your responses as I am not super tech savvy.

When I press Fn+F5 I get the charms bar as attached in my 1st post, but not a popup

Wifi as car remote - manual connect

Similar Messages

Maybe you are looking for