|
|
(33 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
− | '''!!! WORK IN PROGRESS !!!'''
| + | #REDIRECT [[CTWUG Rules]] |
− | | |
− | | |
− | =Glossary=
| |
− | Please consult the [[CTWUG Glossary]] for definitions to some of the terms used in this document.
| |
− | | |
− | | |
− | =Everyday WUG Use=
| |
− | ==Game Time==
| |
− | CTWUG maintains a system of bandwidth management called Game Time. This is a period of time during which gaming related traffic enjoys maximum priority on the network by aggressively shaping non-game related traffic in an effort to reduce network latency to a minimum.
| |
− | | |
− | Game Times have been voted the following:
| |
− | | |
− | * '''Monday - Thursday:''' 20:00 - 00:00
| |
− | * '''Friday:''' 19:00 - 03:00
| |
− | * '''Saturday:''' 15:00 - 03:00
| |
− | * '''Sunday:''' 17:00 - 00:00
| |
− | | |
− | It is the responsibility of [[CTWUG Admin]] to maintain and respond to Game Time failures. It is the duty of Wuggers to respect these times and not subvert the bandwidth limits for non-game related traffic.
| |
− | | |
− | ==IRC==
| |
− | The CTWUG IRC channel, #CTWUG, has a few rules that must be adhered to:
| |
− | | |
− | * Respect other users.
| |
− | * Avoid CAPS usage. It is considered SHOUTING to use CAPS, and rude to use it all the time.
| |
− | * Official channel languages are English and Afrikaans. Other languages, including "leet" speak, MXit/SMS speak, are not allowed.
| |
− | * No blasphemy or excessive use of crude language.
| |
− | * Keep the topics family friendly.
| |
− | * No talk of software piracy. This includes the tools used to obtain pirated software.
| |
− | * Ops have a right to private message you and/or kick/ban you at their discretion.
| |
− | * If you use the /away command, make sure that your client does not spam channels with your away status.
| |
− | * Bottie is the only bot permitted in the channel.
| |
− | | |
− | Some of these rules are relaxed in #CTWUG-Lounge. Please join there for more freedoms. Your WUG IP address must have working Reverse DNS to join the Lounge.
| |
− | | |
− | Wuggers are also free to create their own channels where they can define their own rules.
| |
− | | |
− | | |
− | ==Reverse DNS==
| |
− | It is every Wugger's duty to ensure all his assigned IP addresses have working reverse DNS by adding address names to his [http://wind.ctwug.za.net/ WiND] node. If a Wugger has been assigned a /29 of address space, he has 8 IP addresses that require DNS entries. This is true regardless of how many of these addresses might be in use on his network at any point in time. Please consult [[CTWUG Admin]] or fellow Wuggers if you need help with your DNS.
| |
− | | |
− | | |
− | ==Unacceptable WUG activities==
| |
− | * Network scans of any kind are forbidden unless all owners of affected equipment have given approval prior. This includes use of TheDude, port scans, security scans, password and/or brute force scans. Ping sweeps across IP ranges are acceptable if limited to <64 byte ICMP messages, and does not amount to a Denial of Service.
| |
− | * Flooding and Denial of Service attacks are forbidden.
| |
− | * Traffic sniffing at transit points that reveals packet payloads is forbidden.
| |
− | * Hacking, cracking, and brute force attempts against any equipment or service on the WUG is forbidden, unless arranged prior between all involved parties.
| |
− | * IP address spoofing and hijacking is forbidden.
| |
− | * Advertising is restricted to personal classifieds on the CTWUG forum. Any other advertising, spam, or solicitation is forbidden unless approved in advanced by The Committee.
| |
− | * Operation of commercial, paid-for network services on the WUG is forbidden. This includes commercial Internet access.
| |
− | * Racism, hate speech, repeated excessive aggression, and threats against Wuggers is forbidden.
| |
− | | |
− | | |
− | =High Site Setup and Maintenance=
| |
− | ==General==
| |
− | * All high sites must follow the [[CTWUG Naming Convention]]. High sites not following this must rectify their configuration in a timely manner, or grant [[CTWUG Admin]] to rectify it on their behalf.
| |
− | * Point-to-Point links must use a single /30 IP address block.
| |
− | * Point-to-Multipoint links may use unnumbered address assignments, but a /28 address block per SSID is recommended.
| |
− | * Wireless links should be planned in co-operation with other nearby high sites so as to avoid interference, and optimise network routing.
| |
− | | |
− | ==CTWUG owned High Sites==
| |
− | * May only be maintained and managed in full by [[CTWUG Admin]] and/or the Committee.
| |
− | * During maintenance, [[CTWUG Admin]] may engage non-admins in a supportive role for assistance, or for the purpose of education.
| |
− | * Planned changes:
| |
− | ** involving temporary down time must be published 12 hours in advance on the CTWUG Forums.
| |
− | ** involving long-term down time must be published 14 days in advance on the CTWUG Forums.
| |
− | ** requiring configuration changes by backbone peers must be announced to and acknowledged by all relevant peers 48 hours in advance.
| |
− | ** requiring configuration changes by clients must be published 14 days in advance on the CTWUG Forums.
| |
− | ** requiring hardware changes by backbone peers must be planned in co-operation with peers at all times.
| |
− | ** requiring hardware changes by clients must be published on the CTWUG Forums 6 months in advance.
| |
− | | |
− | ==Transit Routers==
| |
− | * Must be managed by [[Wug Management System]], and administrative access granted to [[CTWUG Admin]].
| |
− | * Internet interfaces must be approved by [[CTWUG Admin]] prior to instatement.
| |
− | * Firewall and NAT rules must be approved by [[CTWUG Admin]] prior to instatement.
| |
− | | |
− | ==CTWUG Administrators==
| |
− | * May not make unauthorized changes at private high sites, with exceptions:
| |
− | ** Disabling routing protocols and/or adjusting static routes over a poorly performing link provided doing so reroutes transit traffic through alternate paths.
| |
− | ** Disabling routing protocols and/or adjusting static routes as a last resort in defending against network abuse.
| |
− | ** Disabling routing protocols when leaving them active would otherwise cause instability across the greater CTWUG network.
| |
− | * All other changes at private high sites must be approved by the site owner or caretaker in advance in writing.
| |