CTWUG Rules 2013

!!! WORK IN PROGRESS !!!

Glossary

Please consult the CTWUG Glossary for definitions to some of the terms used in this document.

Everyday WUG Use

Network Access

For the purpose of network access, there is one class of membership to the Cape Town Wireless User Group. This will herein be referred to as a member. For the purpose of network access, all users are equal, meaning no user will have traffic priority over another user - regardless of their designation in the organisation as per constitution. Requirements for membership is defined in the group's constitution.

A member:

• will have full access to the network without any bandwidth restrictions except where necessary for the health of the network or network segment.
• may vote at the group's meetings when asked to do so by the group committee as defined in the group's constitution.
• may donate money to further assist in growing and expanding the wireless network.

Responsibilities of the Member

It is the member's responsibility to:

• Protect themselves from digital threats that may arise from being connected to the network. This includes (but is not limited to) antivirus software, firewalls and password security.
• Protect their subnet network from abuse by other members. This includes ADSL or other internet connections and any other services that may exist on your subnet.
• Content available on this network is the sole responsibility of members of this network. The Cape Town Wireless User Group is not responsible for any content on this network other than the official group website and servers owned by the group.

Guarantees of Service

Whether expressly implied or otherwise under no cicumstances are there are no guarantees of service on the Cape Town Wireless User Group network. It is run by volunteers in their own time. If something fails or a node goes down, node owners and administrators will tend to it as time, money, and motivation permits. Do not spam the administrators or the forums regarding this.

802.11 wireless network equipment is designed to operate at a distance deemed by the equipment you own. Cape Town Wireless User Group does not guarantee constant speeds or signal levels. There is no guarantee of service at any given point or time. Cape Town Wireless User Group is not responsible for the costs incurred in obtaining any equipment that fails to connect to the network due to environmental, geographic or any other reasons.

Cape Town Wireless User Group is not responsible for obtaining equipment for future wuggers. The group maintains active accounts with wireless equipment distributors that members of the group are able to use at their own cost.

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:

2.2.1. Respect other users.
2.2.2. Avoid CAPS usage. It is considered SHOUTING to use CAPS, and rude to use it all the time.
2.2.3. Official channel languages are English and Afrikaans. Other languages, including "leet" speak, MXit/SMS speak, are not allowed.
2.2.4. No blasphemy or excessive use of crude language.
2.2.4. Keep the topics family friendly.
2.2.5. No talk of software piracy. This includes the tools used to obtain pirated software.
2.2.6. Ops have a right to private message you and/or kick/ban you at their discretion.
2.2.7. If you use the /away command, make sure that your client does not spam channels with your away status.
2.2.8. 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 forward-confirmed 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 forward-confirmed reverse DNS by adding address names to the relevant WiND node. If a Wugger has been assigned a /29 of address space, there are 8 IP addresses that require DNS entries. This is true regardless of how many of these addresses might be in use on the node's network at any point in time. Wuggers must consult CTWUG Admin staff or fellow Wuggers if DNS help is needed, and must persevere with such until DNS configuration is confirmed working.

Unacceptable WUG activities

2.4.1. 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.
2.4.2. Flooding and Denial of Service attacks are forbidden.
2.4.3. Traffic sniffing at transit points that reveals packet payloads is forbidden.
2.4.4. Hacking, cracking, and brute force attempts against any equipment or service on the WUG is forbidden, unless arranged prior between all involved parties.
2.4.5. IP address spoofing and hijacking is forbidden.
2.4.6. 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.
2.4.7. Operation of commercial, paid-for network services on the WUG is forbidden. This includes commercial Internet access.
2.4.8. Racism, hate speech, repeated excessive aggression, and threats against Wuggers is forbidden.

High Site Setup and Maintenance

General

3.1.1. 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.
3.1.2. Point-to-Point links must use a single /30 IP address block.
3.1.3. Wireless links must be planned in co-operation with other nearby high sites so as to avoid interference, and optimise network routing.
3.1.4. All IP addresses bound to high site network devices must have working reverse DNS.

CTWUG owned High Sites

3.2.1. May only be maintained and managed in full by CTWUG Admin staff and/or the Committee.
3.2.2. During maintenance, CTWUG Admin staff may engage non-admins for assistance, or for the purpose of education.
3.2.3. CTWUG Admin must grant administrative access on relevant routers to admins from peer high sites on request.
3.2.4. Changes:
3.2.4.1. involving temporary down time must be published 12 hours in advance on the CTWUG Forums.
3.2.4.2. involving long-term down time must be published 14 days in advance on the CTWUG Forums.
3.2.4.3. requiring configuration changes by backbone peers must be announced to and acknowledged by all relevant peers 48 hours in advance.
3.2.4.4. requiring configuration changes by clients must be published 14 days in advance on the CTWUG Forums.
3.2.4.5. requiring hardware changes by backbone peers must be planned and executed in full co-operation with the relevant peers.
3.2.4.6. requiring hardware changes by clients must be published 6 months in advance on the CTWUG Forums.

Transit Routers at Backbone high sites

3.3.1. Must be managed by Wug Management System, and administrative access granted to CTWUG Admin.
3.3.2. Internet interfaces must be approved by CTWUG Admin prior to instatement.
3.3.3. Firewall and NAT rules must be approved by CTWUG Admin prior to instatement.
3.3.4. Area high sites are optionally exempt from section 3.3.

Backbone links

3.4.1. Must achieve 20 Mbps of throughput upstream and downstream simultaneously.
3.4.2. Must maintain a 95th percentile CCQ of 80% or higher in both directions.

CTWUG Administrators

3.5.1. May not make unauthorized changes at private high sites, with exceptions:
3.5.1.1. Disabling of routing protocols and/or adjustment of routes in the case of a poorly performing link provided traffic flow resumes through alternate paths.
3.5.1.2. Disabling of routing protocols and/or adjustment of routes as a last resort in defending against network abuse.
3.5.1.3. Disabling of routing protocols when leaving them active would otherwise cause instability across the greater CTWUG network.
3.5.2. All other changes at private high sites must be approved in advance in writing by the site owner or caretaker.

Network Management

IP address allocations

4.1.1. May only be allocated from CTWUG's master pool by CTWUG Admin.
4.1.2. The smallest IPv4 allocation from CTWUG's master pool is a /25.
4.1.3. High sites requiring less than a /25 must obtain a sub allocation from its nearest peer.

IP address assignments

4.2.1. No wugger will be assigned less than a /29 address block.
4.2.2. High site administrators must assign sufficient addresses to meet a Wugger's network needs, and avoid the use of NAT.