This is probably fixed in 6.6d, but even after release I'll leave this thread in the main issues tracker for the indefinite future, because network code like this is hard to test locally and I may still be missing something.