CSI Wireless P2P
- Thread starter SB250
- Start date
DeltaMac
Tech
You have 10.7?
After a short search, looks like it is related to the AirDrop feature.
Here's a hint that enables AirDrop (even if you don't have any airport wifi in use), which also stops that odd error from occurring in your logs.
http://hints.macworld.com/article.php?story=20110913213649565
After a short search, looks like it is related to the AirDrop feature.
Here's a hint that enables AirDrop (even if you don't have any airport wifi in use), which also stops that odd error from occurring in your logs.
http://hints.macworld.com/article.php?story=20110913213649565
From
defaults write com.apple.NetworkBrowser BrowseAllInterfaces 0
I got
12-02-17 11:31:53.031 AM login: USER_PROCESS: 280 ttys000
12-02-17 11:32:17.073 AM Console: Marker - 2012-02-17 11:32:17 AM
12-02-17 11:32:17.240 AM Console: Marker - 2012-02-17 11:32:17 AM
12-02-17 11:32:17.433 AM Console: Marker - 2012-02-17 11:32:17 AM
12-02-17 11:32:43.765 AM login: DEAD_PROCESS: 280 ttys000
12-02-17 11:33:47.642 AM login: USER_PROCESS: 295 ttys000
12-02-17 11:33:58.941 AM login: DEAD_PROCESS: 295 ttys000
Does this seem right ?
defaults write com.apple.NetworkBrowser BrowseAllInterfaces 0
I got
12-02-17 11:31:53.031 AM login: USER_PROCESS: 280 ttys000
12-02-17 11:32:17.073 AM Console: Marker - 2012-02-17 11:32:17 AM
12-02-17 11:32:17.240 AM Console: Marker - 2012-02-17 11:32:17 AM
12-02-17 11:32:17.433 AM Console: Marker - 2012-02-17 11:32:17 AM
12-02-17 11:32:43.765 AM login: DEAD_PROCESS: 280 ttys000
12-02-17 11:33:47.642 AM login: USER_PROCESS: 295 ttys000
12-02-17 11:33:58.941 AM login: DEAD_PROCESS: 295 ttys000
Does this seem right ?
Satcomer
In Geostationary Orbit
First make a new Network Location, DO IT NOW!!!
1. The 1st thing to do is to open System Preferences-> Network pane, the Location drop-down and select "Edit Locations".
2. Use the Edit Locations drop-down and click the + button to add a new custom named Location. After making this new custom named Location, then make sure that new location name is highlighted, click the okay button to close the Edit window.
3. Then in the network pane click on the 'Apply' button to save your new custom named Location.
Don't worry the new custom name Location will work exactly like the Automatic location. Doing this trick of making a new custom name location will fix a lot of networking problems. Good luck.
DeltaMac
Tech
There's lots of links that point to those network problems with "hackintosh" setups, maybe because of 'not quite supported' wireless hardware, or no wireless hardware installed at all.
Which Mac model are you using?
Have you tried the old fix of simply reinstalling the OS X combined 10.7.3 updater?
Which Mac model are you using?
Have you tried the old fix of simply reinstalling the OS X combined 10.7.3 updater?
I have an Imac early 2009,
I have reset the Firmware Password, reset the PRAM, erased the disk, installed OS X lion, installed the combo updater to 10.7.3, created a network location in the system preferences that has NO services - and I'm still getting this in my log
12-02-28 19:23:33,727 Finder: Terminate AirDrop P2P link
12-02-28 19:23:33,752 Finder: _CSIsWirelessP2PEnabled::copyPrimaryAirPortInterface failed
12-02-28 19:23:33,779 Finder: _CSIsWirelessP2PEnabled::copyPrimaryAirPortInterface failed
12-02-28 19:23:34,356 Finder: WormholeServer::copyMyAppleIDSecIdentity returned NULL
I have reset the Firmware Password, reset the PRAM, erased the disk, installed OS X lion, installed the combo updater to 10.7.3, created a network location in the system preferences that has NO services - and I'm still getting this in my log
12-02-28 19:23:33,727 Finder: Terminate AirDrop P2P link
12-02-28 19:23:33,752 Finder: _CSIsWirelessP2PEnabled::copyPrimaryAirPortInterface failed
12-02-28 19:23:33,779 Finder: _CSIsWirelessP2PEnabled::copyPrimaryAirPortInterface failed
12-02-28 19:23:34,356 Finder: WormholeServer::copyMyAppleIDSecIdentity returned NULL
ElDiabloConCaca
U.S.D.A. Prime
How often do those messages occur (once a second, once a minute, once an hour, etc.)?
Are you experiencing any problems with your wireless, or are you just concerned about those entries in the log file out of curiosity?
Log files contain a bunch of stuff, and seeing something akin to "Error: no something-something found, killing process" or "Warning: Assertion failed on port 123456, falling back to stone-age mode" don't necessarily mean that anything is wrong with your computer; in fact, those messages may be perfectly normal. Errors may not indicate anything wrong -- in fact, errors are encountered many times per second even when you're working on a perfectly-fine computer... it's just how those errors are handled by the processes that determine if anything's wrong.
For example, concerning AirDrop (which is Apple's drag-and-drop wireless sharing feature), your computer may find another computer on the network that doesn't support AirDrop. Your log file may contain entries such as:
Despite the "WARNING" and "ERROR" and "FAILED" words in the log, the process is acting EXACTLY as it should be, and there really aren't any errors happening at all. It is simply a computer trying to make a connection to another computer, failing to do so (rightly), and erroring out gracefully. That's normal operation for a computer: try something, if it fails (for perfectly normal reasons), error gracefully.
In the case of AirDrop, a computer won't know if another computer supports it without trying to connect to it first. If the computer doesn't support it, that means that an error has occurred, but not an error in the sense of improper operation -- an error in the sense of "I tried, but failed to do this, so it doesn't support AirDrop, so let's just go about our business anyway."
So, are you seeing your logs FLOODED with those messages (which may indicate a potential situation), or are they sporadic, which would mean they're just fine and otherwise benign and an indication of proper operation?
Are you experiencing any problems with your wireless, or are you just concerned about those entries in the log file out of curiosity?
Log files contain a bunch of stuff, and seeing something akin to "Error: no something-something found, killing process" or "Warning: Assertion failed on port 123456, falling back to stone-age mode" don't necessarily mean that anything is wrong with your computer; in fact, those messages may be perfectly normal. Errors may not indicate anything wrong -- in fact, errors are encountered many times per second even when you're working on a perfectly-fine computer... it's just how those errors are handled by the processes that determine if anything's wrong.
For example, concerning AirDrop (which is Apple's drag-and-drop wireless sharing feature), your computer may find another computer on the network that doesn't support AirDrop. Your log file may contain entries such as:
Code:
12:34:56: Found: BSD member computer ID 12:34:56:78:90
12:34:56: WARNING: No promiscuous mode on wireless dev wan0 supported
12:34:57: ERROR: Cannot initiate AirDrop connection to 12:34:56:78:90: unsupported mode
12:34:58: FAILED ASSERTION on interface wan0 to 12:34:56:78:90... DYINGDespite the "WARNING" and "ERROR" and "FAILED" words in the log, the process is acting EXACTLY as it should be, and there really aren't any errors happening at all. It is simply a computer trying to make a connection to another computer, failing to do so (rightly), and erroring out gracefully. That's normal operation for a computer: try something, if it fails (for perfectly normal reasons), error gracefully.
In the case of AirDrop, a computer won't know if another computer supports it without trying to connect to it first. If the computer doesn't support it, that means that an error has occurred, but not an error in the sense of improper operation -- an error in the sense of "I tried, but failed to do this, so it doesn't support AirDrop, so let's just go about our business anyway."
So, are you seeing your logs FLOODED with those messages (which may indicate a potential situation), or are they sporadic, which would mean they're just fine and otherwise benign and an indication of proper operation?
Satcomer
In Geostationary Orbit
Did you install the latest wireless firmware for your 2009 iMac like iMac Wi-Fi Update v1.0? It just came out less than a week ago.
This network set up (attachment) and turning off IPV6 with this code in terminal
networksetup -listallnetworkservices
networksetup -setv6off Ethernet
The code was found here
http://forums.macrumors.com/showthread.php?t=1250993
Seems to stop the CSI Wireless P2P events in the log, so far.
networksetup -listallnetworkservices
networksetup -setv6off Ethernet
The code was found here
http://forums.macrumors.com/showthread.php?t=1250993
Seems to stop the CSI Wireless P2P events in the log, so far.
