On the Gateways page, you can configure a Virtual Asset or a Subnet, both of which require a Linux Asset running the XTNA-agent to provide access. We call this Linux asset the providing asset.
A virtual asset is a device that doesn't have an XTNA-agent running on it, but is made available by the providing asset.
The virtual asset must have an IP that is reachable from the providing asset (usually from the same local area network), this IP goes into the public IP field of its configuration.
Currently, we grant access to such a Virtual Asset to all Clients that have access to the Providing Asset and all of its Peer Assets. You can still limit the ports accessible on the Virtual Asset by configuring services, just as you can configure services on an Asset.
Typical use cases are devices where you can't install our XTNA-agent but still want to make them available to clients, e.g. printers, NAS, IP cameras or industrial devices.
Instead of specifying a single IP you can also make a whole network range available, this is done by configuring a Subnet.
Also for the Subnet the traffic will be routed through the Providing Asset. However, if the accessing client/asset already has an IP in the configured network range, it will not route through the providing asset, but will use its local interface to reach it.
Currently, we grant access to the Subnet to all Clients that have access to the Providing Asset and all of its Peer Assets.