Difference between revisions of "Unusually restrictive firewalls block teleporting"
Wiki Scribe (talk | contribs) m (Robot: kicking Template:Multi-lang) |
m (Text replace - '{{KBmaster}}' to '<noinclude>{{KBmaster}}</noinclude>') |
||
| Line 1: | Line 1: | ||
{{KBmaster}} | <noinclude>{{KBmaster}}</noinclude> | ||
If your [http://en.wikipedia.org/wiki/Firewall_(networking) firewall] is blocking outbound TCP port 12043, the following activities won't work: | If your [http://en.wikipedia.org/wiki/Firewall_(networking) firewall] is blocking outbound TCP port 12043, the following activities won't work: | ||
Revision as of 11:44, 26 October 2010
If your firewall is blocking outbound TCP port 12043, the following activities won't work:
- Teleporting
- Viewing the World Map
- Crossing regions
- Related activities
This is because in Second Life 1.13.2, we've enabled Capabilities, which require outbound traffic to communicate with our servers.
So far, we've found this to be a very rare occurrence involving unusually restrictive firewalls, and should not affect the majority of Residents. So chances are this does not apply to you, but in the event that it does:
To resolve this issue, what you need to do is allow traffic on outbound TCP port 12043.
Some corporate firewalls that restrict all outgoing TCP connections need to either:
- Open outgoing connections to this port on our nets.
- Handle these connections the same way they do other HTTP and HTTPS traffic (in theory, by redirecting it to a proxy).
For more info on firewalls, see:
and for specific instructions not covered here, consult your firewall's manual.
Further technical details about Capabilities, also known as "Sim-Caps", can be found in the Official Linden Blog post "A big change you'll barely notice" by Zero Linden.