Network Infrastructure Group
From Interlock Rochester Wiki
(Difference between revisions)
(→Proposed Projects: added tonights meeting minutes) |
Ben Woodruff (Talk | contribs) (→Meeting Minutes) |
||
| Line 21: | Line 21: | ||
* A/V Link | * A/V Link | ||
| - | = Meeting Minutes = | + | = Meeting Agenda / Minutes = |
| - | == | + | == 2011-03-03 == |
| + | * Status of our ESX ecosystem | ||
| + | ** Wishlist | ||
| + | ** Next big project expense after SDR? | ||
| + | * Routing and switching | ||
| + | ** Would like someone to review our setup and make recommendations (looking for volunteers) | ||
| + | * Services | ||
| + | ** Am building a bind, dhcpd, and other services environment, if anyone would like to help I could use them | ||
| + | ** Goals: get services off pfSense, have failover, generally be robust | ||
| + | * Monitoring | ||
| + | ** Discussion on tools and implementation | ||
| + | * Open forum | ||
| + | |||
| + | == 2010-12-02 == | ||
* phone update | * phone update | ||
** successfull established a trunk to HackPGH | ** successfull established a trunk to HackPGH | ||
Revision as of 19:20, 3 March 2011
Contents |
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.
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
- Status of our ESX ecosystem
- Wishlist
- Next big project expense after SDR?
- Routing and switching
- Would like someone to review our setup and make recommendations (looking for volunteers)
- Services
- Am building a bind, dhcpd, and other services environment, if anyone would like to help I could use them
- Goals: get services off pfSense, have failover, generally be robust
- Monitoring
- Discussion on tools and implementation
- Open forum
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
