How do I configure my hardware firewall (such as a router)?

Template:Needs Translation/KB/es Template:Needs Translation/KB/el Template:Needs Translation/KB/fr Template:Needs Translation/KB/he Template:Needs Translation/KB/it Template:Needs Translation/KB/ja Template:Needs Translation/KB/ko Template:Needs Translation/KB/nl Template:Needs Translation/KB/hu Template:Needs Translation/KB/no Template:Needs Translation/KB/da Template:Needs Translation/KB/sv Template:Needs Translation/KB/tr Template:Needs Translation/KB/pl Template:Needs Translation/KB/pt Template:Needs Translation/KB/ru Template:Needs Translation/KB/th Template:Needs Translation/KB/uk Template:Needs Translation/KB/zh-Hans Template:Needs Translation/KB/zh-Hant

/KB

add versioning

Hardware firewalls need to allow access on certain network ports. Second Life needs to connect to ports 443/TCP, 12035/UDP, 12036/UDP, 12043/TCP, and 13000-13050/UDP. You should configure your firewall to allow outbound traffic on those ports, and related inbound traffic. You'll need to consult your firewall's documentation, or the manufacturer's website, for instructions on how to make these changes to your firewall. As of Version 1.13.2, released Jan. 10th, 2007, you need to enable UDP/TCP in order to access Second Life.

Cisco

If your hardware firewall is a Cisco router/switch that uses reflexive access lists (IOS 11.0 or later), add these lines to your outbound access list:

permit tcp any any eq 443 permit udp any any eq 12035 reflect outbound-SL permit udp any any eq 12036 reflect outbound-SL permit udp any any range 13000 13050 reflect outbound-SL

Then, on your inbound access list, add:

permit tcp any any established evaluate outbound-SL

Then, apply these access lists. SL should now be able to communicate through this router.

Linux Killerwall

If your hardware firewall is a Linux box that uses Killerwall, add these lines to your /etc/killerwall.acl:

IN IFACE <your lan interface> FROM 0.0.0.0/0 TO 0.0.0.0/0 tcp TOPORT 443 ACCEPT IN IFACE <your lan interface> FROM 0.0.0.0/0 TO 0.0.0.0/0 udp TOPORT 12035 ACCEPT IN IFACE <your lan interface> FROM 0.0.0.0/0 TO 0.0.0.0/0 udp TOPORT 12036 ACCEPT IN IFACE <your lan interface> FROM 0.0.0.0/0 TO 0.0.0.0/0 udp TOPORT 13000-13050 ACCEPT

Then, restart Killerwall. Killerwall automatically tracks related reply packets, so SL should now work correctly.

Linux Firewall

If your hardware firewall is a Linux box that uses IPF (Linux Firewall)

pass out quick on rl0 proto tcp from any to any port = 443 flags S keep state pass out quick on rl0 proto udp from any to any port = 12035 pass out quick on rl0 proto udp from any to any port = 12036 pass out quick on rl0 proto tcp from any to any port = 12043 flags S keep state pass out quick on rl0 proto udp from any to any port 12999 <> 13051 pass in quick on rl0 proto tcp from any to any port = 443 flags S keep state pass in quick on rl0 proto udp from any to any port = 12035 pass in quick on rl0 proto udp from any to any port = 12036 pass in quick on rl0 proto udp from any to any port 12999 <> 13051

Can I use voice from behind a firewall?

Read this article for information on using voice from behind a firewall.

What are Second Life's subnets?

Read this article for information on Second Life's subnets.