When managing multiple connections or running automated scripts on AustNet, it is important to understand the network's connection limits and cloning policies.
The Connection Limit (Cloning Policy)
To protect infrastructure stability, prevent abuse, and mitigate automated attacks, AustNet enforces a strict cloning limit per network connection.
- The Limit: AustNet permits a maximum of two (2) simultaneous connections from a single IP address.
- Bots Count Toward the Limit: Automated scripts, background clients, and auxiliary helper bots all count toward your total IP connection pool. If you connect your main chat client from your home connection and spin up two independent bot instances from the same IP, you will trigger clone limits or connection throttles.
Managing Bots Within the Policy
Because automated tools count against your connection cap, running multiple bots or hosting multi-client setups requires careful planning:
- Consolidate Scripts: Instead of running separate background clients for individual utilities, consider using a multi-threaded framework or a modular bot (like Limnoria or Sopel) that handles multiple channels and commands from a single connection.
- Use a Bouncer (ZNC) or Shell: Running your clients and bots from a persistent remote server, VPS, or bouncer ensures that connections originate from dedicated hosting infrastructure rather than hitting local residential IP constraints.
Requesting an Exemption
If your community project, shared workspace, or bot hosting setup genuinely requires more than the standard allocation of simultaneous connections from a single IP address, you can request an administrative exemption.
- How to Apply: Join
#ASD(/join #asd) on the network to speak directly with staff about your setup requirements. - What to Provide: Be prepared to explain why you need extra connections, the nature of the bots or clients you are running, and your associated host details so network operators can review your request safely.