Difference between revisions of "Unusually restrictive firewalls block teleporting"
Fritz Linden (talk | contribs) (Initial Parature import) |
Fritz Linden (talk | contribs) (Initial Parature import) |
||
| Line 1: | Line 1: | ||
{{Seal}} | {{Seal}} | ||
If your [http://en.wikipedia.org/wiki/Firewall_(networking) firewall] is blocking outbound TCP port 12043, the following activities won't work: | |||
If your firewall is blocking outbound TCP port 12043, the following activities won't work: | |||
* Teleporting | * Teleporting | ||
| Line 11: | Line 8: | ||
* Related activities | * Related activities | ||
* | * | ||
This is because in Second Life 1.13.2, we've enabled Capabilities, which require outbound traffic to communicate with our servers. | 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: | 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. | 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: | Some corporate firewalls that restrict all outgoing TCP connections need to either: | ||
# Open outgoing connections to this port on our nets. | # 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). | # 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: | For more info on firewalls, see: | ||
* [[How do I configure my software firewall (such as Norton Internet Security, McAfee Personal Firewall, or ZoneAlarm)|How do I configure my software firewall?]] | * [[How do I configure my software firewall (such as Norton Internet Security, McAfee Personal Firewall, or ZoneAlarm)|How do I configure my software firewall?]] | ||
| Line 36: | Line 26: | ||
* [[How do I configure my hardware firewall (such as a router)|How do I configure my hardware firewall?]] | * [[How do I configure my hardware firewall (such as a router)|How do I configure my hardware firewall?]] | ||
* | * | ||
and for specific instructions not covered here, consult your firewall's manual. | 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 "[http://blog.secondlife.com/2006/12/21/a-big-change-youll-barely-notice/ A big change you'll barely notice]" by Zero Linden. | |||
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. | |||
[[Category:Moving Around]] | [[Category:Moving Around]] | ||
[[Category:Inworld Issues]] | [[Category:Inworld Issues]] | ||
Revision as of 12:03, 5 October 2009
This article is part of the Extended Second Life Knowledge Base that includes advanced and specialized information. This information was originally provided by Linden Lab, but is not actively maintained nor guaranteed to be accurate. Linden Lab does not certify nor assume any responsibility for this information.
See the official Second Life Knowledge Base for the most current information.
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.