AndLinux ports

andLinux & firewalls

andLinux must be able to communicate with Windows using TCP/IP. Since Windows contains its own software firewall and many users have software firewalls installed, some ports need to be opened in order for everything to work properly. This information is only for software firewalls and does not pertain to hardware firewalls. As long as Windows can communicate to the outside world and andLinux can communicate with Windows, your hardware firewall settings should be fine.

• Exampels of software firewalls:
  • Windows Firewall (WindowsXP SP2 and higher have this installed and enabled by default)
  • Kerio Personal Firewall
  • Zone Alarm
  • Sygate Personal Firewall

andLinux communicates using a daemon called colinux-slirp-net-daemon.exe. Some software firewalls (like Zone Alarm) allow you to add open the firewall at the application level. This means that you only need to add the colinux-slirp-net-daemon.exe to the list of trusted applications and it will allow full access for andLinux to communicate. Others (Windows Firewall) need to have each port opened and some may require it to be done by specific ip. Since there are too many software firewall applications to cover, I will outline the ports and IP that need to be opened.

• andLinux uses the following Local ports at IP 0.0.0.0
  • 21
  • 22
  • 1000
  • 1001
  • 1088 (required and communicates at remote port 6000)
  • 1135 (used for updating and communicates at remote port 80)
  • 1136 (used for updating and communicates at remote port 80)
  • 5000
  • 5001
  • 5901
  • 7100

Please note that some ports may not be required for normal use, but since no daemon is running on these ports, you should be okay to open them. Please note that except for noted above, these ports do not need to be opened to the internet... only to Windows.