Latest Update uses new ports, breaking access from behind firewalls.

Based on our firewall logs, it appears that the latest update uses new ports to communicate with the server. These ports are not included in the list at http://secondlife.com/knowledgebase/article.php?id=029 , and there was no reference to this change in the release notes.

Does anyone know of a complete list of the ports being used anywhere?

Thanks!
_jonas

I think a blog update last week said that one port that used to be UDP might now have to be TCP + UDP...

Have they actually changed port numbers or is it enabling protocols?

Exactly. Here's the blog post that Meade is referring to:

http://blog.secondlife.com/2007/01/09/changes-to-be-aware-of/

This is actually a great step forward for lag related issues, since one of SL's biggest architectural weaknesses seems to have been it's use of UDP for everything, even the things that did not need (or could not expect) timely delivery (such as textures) - for some operations they basically re-iplemented some aspects of TCP in UDP, but it caused massive amounts of extra overhead and data retries. They've now realized that many of the things they needed sent to the client were better served by a non-timely but dependable protocol, rather than some attempt at a cross-breed.

Thanks! That's the blog entry I was thinking of. And I agree: it's (in theory) a great step forward.

Still, Poinky said "ports".

I should have been more precise - the firewall logs indicate _one_ new port being used (can't recall off hand which one - 12042 perhaps?) I can login, but teleporting anywhere results in the client quitting., and I haven't tried any extensive experiments to see if if the client tries other ports in other circumstances. I'll see if the changing to UDP/TCP makes a difference - thanks for the reference!

I cannot seem to find the list of Linden Labs IP address ranges. Dangit, I know it's here, I just can't find it!!