Note: This chapter describes the remote maintenance of servers from the Antcas Hub portal side. For help with setup see the chapter Remote Access
▸ Antcas Hub.
The remote access has been available since version 2.0. Over the years, this feature has undergone various protocol revisions, including improvements in connection security. Therefore, we now refer to this access method as Legacy Mode. Version 5.0 introduces a new approach via Hub Mode. This mode enables remote maintenance through a proxy server using a VPN tunnel. Security, stability, and speed have been significantly enhanced as a result. We recommend always using the Hub Mode when possible. The Hub Mode includes a fallback to the Legacy Mode, so you don't need to worry if access via Hub Mode is not available. The Legacy Mode has also been improved in version 5.0, now fully supporting asynchronous transfers.
When establishing a connection, the URL on the portal displays according to the type of connection used. A new secid is generated and provided via subdomain. This path is fixed and reassigned after one year if not used. The connection only requires port 443 on the client side and optionally UDP for the WebRTC services.
| URL | Type |
|---|---|
| secid.antcas.cloud | The connection was successfully established via VPN proxy in Hub Mode. |
| secid.legacy.antcas.cloud | The connection was established in Legacy Mode. |
The new Antcas Hub now includes an integrated VPN. This is available directly in the Hub Mode with VPN. The connection is established via WireGuard VPN through the portal. Communication takes place using UDP and does not require incoming firewall rules.
Before connecting to a server, you must first download the configuration. This can then be imported into the WireGuard client. Depending on the client, you can import the ZIP file or scan the QR code. After that, you can immediately establish a connection. This works as long as you are logged into the portal. The connection will then be automatically terminated. Since WireGuard is only passive, no error message is displayed if the connection cannot be established. If a connection has been successfully established, you can see this from the transfer. The byte counters should increase in both directions.
Warning: Connect to Antcas Hub with only one client at a time. Otherwise, this may lead to an unstable connection.
Now you can establish a VPN connection by right-clicking on a server in Hub Mode. Once this is done, the server also establishes a connection to the portal. The connection status is then displayed at the bottom right.
WireGuard communicates using peer endpoints; there is no client/server model as typically used in VPN connections. The Antcas Hub configuration file creates a split connection. This means that only all local IP addresses are transmitted via the VPN. It is also possible to transmit all data traffic via the VPN. To do this, the configuration must be adjusted. Change the AllowedIPs section under [Peer] to:
AllowedIPs = 0.0.0.0/0, ::/0
This instructs the operating system's routing table to send all data via Antcas Hub. However, this can affect browsing speed and should only be configured if absolutely necessary.
For a split connection, use the following configuration:
AllowedIPs = 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fd26:26:26:26::/64
For IPv6, only the range fd26:26:26:26::/64 is forwarded to the VPN, as these are the only ones used by Ancas Hub.
If a DNS server also needs to be provided, it can be stored in the configuration. To do this, a new line must be added under [Interface]:
DNS = 8.8.8.8, 8.8.4.4