Network
Static IPs for a direct asset connection
In some cases the Teleport is directly connected to an asset via ethernet, i.e. there is an ethernet cable going from the asset to one of the Teleport’s ETH port without any network equipment, such as a router. In those cases both the Teleport and the asset should configure a static IP. Please see the following guidelines for choosing a static IP, and other properties.
- The asset should have an even static IP in the
10.0.100.0
-10.0.100.250
range. For example10.0.100.0
,10.0.100.2
,10.0.100.4
, etc. - All assets should have an unique IP address. So if there are multiple assets directly connected to the Teleport you should use IPs
10.0.100.0
for the first asset and10.0.100.2
for the second asset. It is not supported to have two assets with the same IP. - The asset should have subnet mask
255.255.255.0
. - If the asset requires configuration of a gateway, please configure it to
0.0.0.0
. - If the asset requires configuration of a DNS server, or multiple DNS servers, please use the following IPs.
8.8.8.8
, a Google public DNS server.8.8.4.4
, a Google public DNS server.1.1.1.1
, a public Cloudflare DNS server.