:: the inside3d irc network :: :: leaf link application :: web > http://www.inside3d.net email> root@inside3d.net irc > irc.inside3d.net:6667 This application should help you decide whether you really want to link to the network or not and should give us the information we need to process your request in a timely manner. Keep in mind that if you have any questions, we encourage you to ask. We take official business very seriously and it's easier for everyone if you don't screw this up. If you're a company that simply wants to show its support for the gaming community and you don't have an IRC administrator, skip this application and email us with the situation. We can have one of our network admins test, set up and maintain your server with only minimal access to your machine and cooperation from its administrator. .A. [REQUIREMENTS] There are a few things that are absolutely necessary no matter what. If you can't meet these, you might as well stop here. The rules: o Your machine must be available to run the IRC server 24/7/365 and be fairly stable. Also, you must plan to run the server long-term. This is like a contract. o You'll probably have to be affiliated with or represent a major gaming website, dev house, publisher, whatever. This means news sites, fansites, id Software, Acivision and the like. We get so many applications from little servers, it's kind of hard to filter them efficiently. If you have some sick machine with so much bandwidth that we wouldn't be able to turn you down, go ahead and apply. o Your machine needs to be at least a P120 (or comparable) with 32MB of RAM for x86-compatible architectures. For Alpha boxen, an Alpha 233 seems reasonable. Sparcs would probably have to be at least a Sparc5. This rule is pretty flexible as it depen- ds a lot on what else the machine does and stuff. o It needs to run a "flavor of Unix", as most people like to say. Any of the BSD distros are okay, Linux is okay if you aren't stupid and we'd kind of have to wing it if you ran something else. Windows is not an option as there is no Win32 version of our ircd and we don't plan for there to be. Keep in mind that the ircd will need at least 1024 fd handles. Make sure you have this set up correctly. o Your machine needs to be on a fairly fast connection. This would be, in most cases, at least a T1 line, but that can be negotiated for servers outside the United States. Also, the issue isn't so much bandwidth as it is connectivity, if you know what I'm getting at. You should have pretty good routes to most, if not all, of the major networks that make up the Internet. o You need to be able to open TCP ports 6665 through 7000 and 7029. If you can't, email and we'll talk it over. o You must agree to allow your servername to be in the format .inside3d.net and be added to server pools. Where is the unique part of your server's name. The unique part is pretty flexible and can be almost anything you want, but it should be something somewhat related to the organization representing the server. Oh, we may decide to link you as a test server for a period where you'll be called by an IP address, have only local operators and not be in the pools to test your connectivity to the network. This is never permanent, though. .B. [FILL IN THE BLANKS] Now you need to fill in the blanks. As in, write the answer to the question somewhere after the question. If you have any concerns, email or come ask us in #i3D. Section 1: General Tech 1a> Server's propsed name: 1b> Server's IP address: 1c> That IP's hostname: 1d> Operating system: 1e> CPU type/speed: 1f> Amount of RAM: 1g> Other tasks this machine handles: 1h> Got root?: 1i> Geographic location: 1j> Proposed maximum number of clients: Section 2: Network Tech 2a> Describe in detail your machine's connection to the Internet. Be sure to include link speeds. "i have an oc-512" doesn't cut it. e.g., "45Mbps DS3 HSSI to cockforquarters.net" 2b> We're going to do some network diagnostics on the following hosts. One will be your uplink. . thepeel.inside3d.net (216.139.208.140) . desync.inside3d.net (209.11.26.6) First, paste a traceroute to each host. Second, paste a ping summary for each host. Ping should be run with the following parameters: . 512 byte packets . 1 second intervals . at least 100 packets at the following times: . Saturday at 3am, 12pm and 8pm CST (GMT -6) . Sunday at 10am CST (GMT -6) Please, for the love of bread, don't include the whole ping output. You might want to use at(8) or some fancy crontabbing to do the pings. Section 3: Personal Info 3a> Your nickname: 3b> Your real name: 3c> Your location (for the website): 3d> A phone number: 3e> An email address: 3f> Cup size: Section 4: Other Stuff 4a> How much time do you spend on IRC? 4b> How long have you been on IRC? 4c> How much time will you be able to dedicate to Inside3D? 4d> What past experience as an IRC administrator have you had? 4e> Write up what you think your job description should be on Inside3D. 4f> Make a list of your opers' nicks, names, locations and email addresses. 4g> How much about the inner workings of IRC do you know? 4h> Anything you want to add? .C. THE END If everything looks good, email this application to apply@inside3d.net and we'll begin the decision-making process. If at any time you have questions or comments, we can be reached via email at root@inside3d.net or on the network in #i3D. Good luck and thanks for choosing Inside3D. - the Inside3D Administrative staff