Ping and ssh don't work after waking from sleep

Question

Hi!
I have been running Arch on my 2010 Macbook since May and there's always been this one annoyance which I can't figure out: after it is woken from sleep, the wireless (using netctl) happily reconnects and I can browse, check email, run pacman, do dns lookups---everything, it seems, apart from ssh or ping.  Both ping and ssh seem to hang.  If I reboot or restart [email protected], then they both work.
Running :
$ ssh XXX.XXX.XXX.XXX
connect(3, {sa_family=AF_INET, sin_port=htons(22), sin_addr=inet_addr("XXX.XXX.XXX.XXX")}, 16
where XXX.XXX.XXX.XXX is my work computer. (Full strace: http://pastie.org/private/xhmee0oltrnx3qmblnzq)
Running strace ping google.com (as root) gives the repeated lines:
$ strace ping google.com
sendmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("173.194.34.102")}, msg_iov(1)=[{"\10\0\270\345b\325\0\2\336\36QR\0\0\0\0\353\376\2\0\0\0\0\0\20\21\22\23\24\25\26\27"..., 64}], msg_controllen=0, msg_flags=0}, 0) = 64
recvmsg(3, 0x7fff2f6d6f90, 0) = -1 EAGAIN (Resource temporarily unavailable)
(Full strace: http://pastie.org/private/bfygaqtccz0ms2w8hqea4g)
I can, however, sucessfully ping my router and other devices connected to it.  I have not been able to find out anything relevant that might fix this. I've checked the MTU settings match those on the router and my other laptop running Arch does not have this problem.
Any suggestions on how to debug this further?
Thanks!

Answer 1

I have several mid-2009 8-core Mac Pro's, all running Snow Leopard, and all have been having this problem as well.
I will not guarantee this is going to work for anyone else....but we have found a (slightly inelegant) workaround for it that has been working for several weeks now without fail.
Prior to putting your MacPro to sleep, run the volume all the way up and leave it there. Afterwards, put it to sleep as usual. We use the keyboard to do this, but I would imagine any method should have the same affect. However, I've not experimented.
Anyway...this has worked 100% of the time for us. The only downside of it is that you have to remember to run it up before....and then back down after waking (else that first alert sound or music file you play will really wake YOU up!)
If this works for anyone else, let me know.
Apple should never have let this one out the door with this bug. Especially, as Apple Support is....wanting, at best.
...sT