Routing: Difference between revisions
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
<nowiki>--------------------------------------------------------------------------------------------------</nowiki> | <nowiki>--------------------------------------------------------------------------------------------------</nowiki> | ||
== INSTRUCTIONS | == INSTRUCTIONS == | ||
First you should know, | |||
We are looking for servers with good bandwidth and connectivity, in most | We are looking for servers with good bandwidth and connectivity, in most | ||
| Line 35: | Line 19: | ||
A. Have you (admin) read and understood the Server Application Guidelines | A. Have you (admin) read and understood the Server Application Guidelines | ||
and believe your server to meet the requirements of linking to | and believe your server to meet the requirements of linking to INTERSHELLS? | ||
B. Is your server provider-sponsored, or being paid for by you or | B. Is your server provider-sponsored, or being paid for by you or | ||
| Line 61: | Line 45: | ||
<nowiki>-------------------------------</nowiki> CUT HERE --------------------------------- | <nowiki>-------------------------------</nowiki> CUT HERE --------------------------------- | ||
== | == Main Application. == | ||
=== Section 1: Server Information === | === Section 1: Server Information === | ||
| Line 119: | Line 103: | ||
2. Admin's E-Mail address: | 2. Admin's E-Mail address: | ||
3. Admin's nickname on | 3. Admin's nickname on INTERSHELLS: | ||
4. Does admin have "root" access on server: | 4. Does admin have "root" access on server: | ||
| Line 132: | Line 116: | ||
One Buzznet admin will be required to be given sudo access to the machine for emergancys. | One Buzznet admin will be required to be given sudo access to the machine for emergancys. | ||
<nowiki>--------------------------------------------------------------------------</nowiki> | <nowiki>--------------------------------------------------------------------------</nowiki> | ||
| Line 161: | Line 129: | ||
Note: For security reasons, any information provided in 4b and 4f will be removed from your application before it is shared beyond the Routing team. | Note: For security reasons, any information provided in 4b and 4f will be removed from your application before it is shared beyond the Routing team. | ||
Latest revision as of 18:22, 18 December 2025
--------------------------------------------------------------------------------------------------
Intershells Server Link Application - Version-2.0 - 12/18/2025 by Parrot
--------------------------------------------------------------------------------------------------
INSTRUCTIONS
First you should know,
We are looking for servers with good bandwidth and connectivity, in most
cases hosted and sponsored by ISPs or network operators.
Applications that do not follow these instructions will be ignored!
==========================================================================
Section: Quick Link Eligibility Check List
A. Have you (admin) read and understood the Server Application Guidelines
and believe your server to meet the requirements of linking to INTERSHELLS?
B. Is your server provider-sponsored, or being paid for by you or
your business? Paid servers are allowed, so long as the admin can
convince us it is long term and financially fees able for the admin to
maintain the fees.
C. Are you running some flavor of UNIX? We suggest strongly one of the More Popular forms of Linux, Ubuntu, CentOS, Debian, Mint,
D. Is your server capable of absorbing massive, multi-GBit/second DDoS
attacks? At this point you should have a server that performs proper filtration
and utilizes multiple firewalls.
If you answered No to any of the above questions, do not submit an
application. Do not submit this portion with your application.
==========================================================================
------------------------------- CUT HERE ---------------------------------
Main Application.
Section 1: Server Information
a. Full server (machine) hostname: i.e. (irc.funeral.housemartin.org and the full dns reverse to the machine. 195.20.230.38 -> director.medical-abuse.com)
b. Server's IPv4 address:
c. Server's IPv6 address:
d. Hosting Provider:
e. Ports (ports 6665-6669, 7000,, 6697[ssl] required):
g. Server's operating system/version:
h. Server's processor info (type/speed/cores):
i. Server's memory:
j. Is the machine dedicated to IRCd(The fewer daemons running the better, as this reduces the number
of required ports to be open on the machine):
k. Server's geographic location (city, state/country):
l. Maximum clients you will allow. By now you should have or go ahead and install
the latest version of the unrealircd, the # of file descriptors and clients allowable will
automatically be set durring its compile:
M. Are you or your sponsor applying or linked to any other IRC networks?
(please list):
n. Is this a physical server or a virtual machine?:
If virtual, please complete questions 1q-1v
o. Are the CPU/RAM resources dedicated to the guest dynamically shared,
or dedicated to the irc vm?
p. VM Host Software & Version:
q. VM Host hardware specifications (Total CPU/Cores/RAM):
r. Approximate number of guests on this host infrastructure:
s. Please list anyone with administrative access to the VM Host:
--------------------------------------------------------------------------
Section 2: Personal Information
1. Admin's real name (Last, First):
2. Admin's E-Mail address:
3. Admin's nickname on INTERSHELLS:
4. Does admin have "root" access on server:
5. Who else has "root" access on server (Please list and explain why):
Note: Console/admin access to a VM host counts as root access.
6. Server owner's name (or ISP):
7. Server owner's E-Mail address:
One Buzznet admin will be required to be given sudo access to the machine for emergancys.
--------------------------------------------------------------------------
Section 4: Routing Information
. How much outgoing bandwidth (in Mbit/s) is available to the server?
. Describe, in detail, how your server will be filtered from Denial of
Service attacks. Make sure you include the hardware type and software
release running on the devices doing the filtering.
Note: For security reasons, any information provided in 4b and 4f will be removed from your application before it is shared beyond the Routing team.