This message shows up in my system log quite a bit.
I've noticed that it doesn't happen while doing a file transfer or actively browsing the web, so I started to wonder if it was some sort of sleep mode or inactivity mode/power saving mode by the card.
So just for the heck of it I decided to run a continuous network action in the background to see if that had any impact, and it turns out....it did. I haven't seen this error message in the log since I ran this command. All I did was drop to terminal and type:
ping core &
core is a fileserver on my lan. & puts the command into the background.
I'm interested to know if anybody else that's seeing this message in their error log could do this and report back. You can use any non-local IP address/hostname on your LAN. ie Don't use your own address or 127.0.0.1. Your router would be fine.
If you use the & sign at the end, you can safely close terminal and it will continue to run in the background.
I've noticed that it doesn't happen while doing a file transfer or actively browsing the web, so I started to wonder if it was some sort of sleep mode or inactivity mode/power saving mode by the card.
So just for the heck of it I decided to run a continuous network action in the background to see if that had any impact, and it turns out....it did. I haven't seen this error message in the log since I ran this command. All I did was drop to terminal and type:
ping core &
core is a fileserver on my lan. & puts the command into the background.
I'm interested to know if anybody else that's seeing this message in their error log could do this and report back. You can use any non-local IP address/hostname on your LAN. ie Don't use your own address or 127.0.0.1. Your router would be fine.
If you use the & sign at the end, you can safely close terminal and it will continue to run in the background.