StormNet Server Linking Requirements

(Revised – January 2026)

To link a new server as a leaf to the StormNet IRC network, applicants must meet the following requirements. These ensure network stability, security, consistency, and long-term reliability. All decisions are at the discretion of the Network Admin (studded).

• Age Requirement:
  The primary admin must be at least 18 years old at the time of application. Proposed operators should generally be at least 16 years old, with exceptions considered on a case-by-case basis.

• ISP / Uplink Permission:
  You must have explicit permission from your ISP, uplink provider, educational institution, employer, or relevant authority to run a public IRC server on their hardware and connection. This must not violate any acceptable use policies (AUP), terms of service, or applicable laws. Be prepared to provide proof (e.g., email confirmation) and contact information for verification.

• Connection & IP Requirements:
  Minimum 1 Gbps symmetric (up/down) internet connection with a static IP address. IPv6 connectivity is strongly recommended (and may become required in the future).

• Operating System:
  Must run a modern Linux distribution or recent Unix variant (*BSD, HP-UX, IBM AIX, Oracle Solaris). Root access is required. No Windows anything, macOS, BeOS, OS/2, or other unsupported platforms.

• Time Synchronization:
  Must run a time synchronization service (ntpd or chrony recommended).

• Hardware & Dedication:
  Minimum 1 GB RAM (more recommended for headroom). Modern CPU (anything released within the last 10 years should be fine). The machine should preferably be dedicated primarily to IRC; no high-bandwidth or resource-intensive co-located services that could interfere with performance or stability.

• IRC Software:
  Must run the latest stable UnrealIRCd 6.2.x series (currently 6.2.2 or newer). We will notify of required upgrades for security or compatibility. Keep the OS, UnrealIRCd, and related software fully patched.

• Capacity Commitment:
  Server must be capable of comfortably handling at least 500 concurrent clients (based on hardware, connection, and tuning).

• Configuration Compliance:
  Must implement our provided unrealircd.conf shared includes, recommended anti-flood/spamfilter settings, and MOTD requirements (in English). All relevant documents (MOTD, rules, etc.) must be in English.

• Ports & TLS:
  Mandatory listening ports for client connections: 6667 (plaintext) and 6697 (TLS/SSL). Additional standard ports (e.g., 6668, 6669, 7000) are recommended but optional—reflect any extras in your MOTD. Must accept and use the *.thestormnet.com TLS/SSL certificate provided by the network. If you have a valid SSL certificate of your own, that is acceptable, too.

• Security & DDoS Mitigation:
  Must configure firewall rules to filter incoming UDP and ICMP traffic (to prevent amplification attacks) and enable SYN flood protection, rate-limiting of inbound SYN/SYN-ACK packets, and DoS policies for TCP anomalies (e.g., excessive half-open connections). Tune UnrealIRCd's built-in anti-flood settings (set::anti-flood, class pingfreq, etc.) per our recommendations. See https://www.unrealircd.org/docs/Security for best practices.

• Uptime & Long-Term Commitment:
  Server must run 24/7/365 with high availability. Must be dedicated to the network long-term. Must monitor uptime and respond to issues (e.g., netsplits, abuse reports) in a timely manner (ideally within hours).

• Operators & Vetting:
  Admin and proposed operator nicks must be registered with NickServ. All admins/operators must read and acknowledge the StormNet AUP (https://thestormnet.com/aup). Proposed admins/operators will be interviewed individually by the Network Admin (studded) and possibly another operator. You (as admin) are responsible for your operators' conduct. Services Operator privileges will be granted only after demonstrating competence and earning trust (typically after 30–90 days of good standing).

• Bot Policy:
  Flexible—decided by the individual server admin. Your policy must be clearly stated in your MOTD. Only friendly bots allowed; no war, flood, spam, or malicious bots permitted network-wide.

• Server Naming:
  Proposed server name must be a single word or short name (e.g., "london", "phoenix"), suffixed with .thestormnet.com (e.g., london.thestormnet.com). Nothing copyrighted, offensive, racist, or inappropriate.

• Acknowledgment:
  Running an IRC server for a growing network is a significant commitment of time, resources, and responsibility. You and your operators must be prepared to contribute actively, support the community, and handle challenges as they arise—with no financial compensation expected beyond the satisfaction of helping build StormNet.

Upon successful vetting, interview, and test link (if required), your server will be added to the DNS round-robin pool (irc.thestormnet.com) and will be officially linked. If you're ready to apply, please click here to go to the Server Application page.