Your FREE Guide
BY INDUSTRY EXPERTS

DOWNLOAD FREE

We're an ISO27001:2013 Certified Supplier

blog-post-featured-image

The management and monitoring tools we use require network access between your servers and ours. This page details the access that is required.

Both the server names and the IP addresses for our servers have been provided in the following tables. If a you manage a firewall in your network, it would be preferable to use the server names in the firewall rules (if possible) so that we can migrate services from one IP address to another without requiring any changes to your firewall.

Connectivity Options

Ideally, we would have direct connectivity between your servers and ours as detailed below. However, we recognise that this may not always be possible; for example, you may have multiple servers behind one public IP address, making it difficult for us to directly connect to each of your servers.

Under those circumstances, we require:

  • direct ssh access as detailed below (“ssh access”) from our servers to one of your servers (the “gateway server”), and
  • ssh access from the gateway server to your remaining servers, and
  • outbound connections from each of your servers to ours as detailed below (“Outbound connections to our servers”), including OpenVPN access

Inbound Connections To Your Server

We can connect to your server over either IPv4 or IPv6 (only one is required).

IPv6

If you would like us to access your servers via IPv6, inbound connections must be open from all of the following subnets:

  • 2001:678:32c:57a0::/60
  • 2001:8b0:fbb2:2590::/60

to the following ports:

  • ICMP
  • TCP port 22 (ssh)
  • TCP 5666 (for server monitoring)

IPv4

If you would like us to access your servers via IPv4, inbound connections must be open from all of the following subnets:

  • 31.210.128.176/28
  • 31.210.130.202/32
  • 5.133.183.84/32
  • 81.187.162.2/32

to the following ports:

  • ICMP
  • TCP port 22 (ssh)
  • TCP 5666 (for server monitoring)

Outbound Connections To Our Servers

OpenVPN Access

ProtocolDestination PortDestinationIPv4 AddressIPv6 Address
UDP1195thames.tiger-computing.co.uk5.133.183.84-
UDP1194sea.tiger-computing.co.uk31.210.129.1902a01:500:1:2::4

 

Configuration Management Server

ProtocolDestination PortDestinationIP Address
TCP8140tamar.tiger-computing.co.uk31.210.130.200

 

Software Distribution Servers

ProtocolDestination PortDestinationIP Address
TCP80Any0.0.0.0
TCP443Any0.0.0.0

 

Network Time Servers

ProtocolDestination PortDestinationIP Address
UDP123Any0.0.0.0

 

Outbound Email Access

At a minimum, your servers need to be able to send email  to the following two addresses:

  • logcheck@tiger-computing.co.uk
  • security@tiger-computing.co.uk

Usually, the servers will send their own email directly, but it is possible to use any specified SMTP relay, or dedicated aliases that relay to those two addresses if that is preferred.