Computer committee

Committee for house computers and network

• Computer Committee/Shaw Installation Notice
• Computer Committee/Troubleshooting
• Phone System
• Technical
• Change password
• OpenWrt
• IMAP

Contents 1 Meetings 2 Wiki organization 3 DHCP, DNS, TFTP 4 UFW 5 Members 6 Tasks 7 TODO 8 Notes

Meetings

• Computer meeting 2007-04-16
• Computer meeting 2007-03-27

Wiki organization

Some things the wiki is actually getting used for is Category:Meetings and Category:Committees - to make the wiki more friendly and usable, there should be a big header at the top of the page with "Committees" and "Meetings"

Probably there should also be links from the home page, but more subtle - like maybe in the footer? How about putting search on the home page too?

Also there should be links to Category:Policies and Category:Proposals? and to the handbook

This should *really* get done!

1. Search on homepage
2. Consistent footer on homepage and wiki
   • Meetings
   • Events - link to Facebook
   • Committees - heading with sub links
   • Handbook
   • Policies?
   • Proposals?
   • Contact
   • Memorials
3. Integrate "latest discussions" somehow? like http://kohanaframework.org/

Maybe later consider integrating a Facebook widget, or wall feed?

DHCP, DNS, TFTP

2009-12-26

Generally I prefer ISC dhcpd and BIND for DHCP and DNS, while many other folks rave about dnsmasq - maybe this is because I don't like monolithic systems

- but it seems the AudioCodes gateways need a TFTP server and I've no experience setting one up. OTOH dnsmasq comes with an integrated TFTP server

So I'm switching to dnsmasq to give it a try

UFW

Configure masquerading according to, https://help.ubuntu.com/9.10/serverguide/C/firewall.html#ip-masquerade-ufw

Both DEFAULT_FORWARD_POLICY="ACCEPT" and net/ipv4/ip_forward=1 required

before.rules,

@@ -64,3 +64,12 @@
 
 # don't delete the 'COMMIT' line or these rules won't be processed
 COMMIT
+
+
+*nat
+
+-A POSTROUTING -s 192.168.1.0/24 -o eth0 -j MASQUERADE
+
+
+# don't delete the 'COMMIT' line or these rules won't be processed
+COMMIT

$ sudo ufw allow OpenSSH
$ sudo ufw allow Postfix
$ sudo ufw allow Bind9
$ sudo ufw allow bootps
$ sudo ufw allow tftp
$ sudo ufw allow http
$ sudo ufw allow imap
$ sudo ufw allow ldap
$ sudo ufw allow sip

Members

• User:Jbates
• User:Amessak

Tasks

• Run cable for wireless access point in 609
• Get OpenWrt running on second wireless access point
• Maintain home page
• Write computer documentation!

TODO

• Would be nice to have lots of stuff public (Coop policy handbook available to new applicants, etc.) but other things private, like contact information and phone numbers
• Review blocked ports policy

• Figure out why booting with nss_ldap doesn't work : (
• SquirrelMail interface to mail forwarding address
• SquirrelMail user data from LDAP
  • Set LDAP information from SquirrelMail
• Cyrus autocreate patch
  • http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435598
• List commands module
• Voicemail
  • Install Asterisk 1.4
• Router
• Documentation!
• MediaWiki login
• Run cable for wireless access point
• Support "list all" in SquirrelMail address interface
• Think of a way to deal with Liv's Winblows machine getting the wrong IP for campcoop.com?

Notes

There's concern about the mailing list archives being indexed by Google. At least there's no concern about them being public, yet. I think we can keep them from being indexed with a robots.txt file

However, institutional amnesia is one of the great problems at the coop. Ideally, the mailing list would serve to record communication. It should also be backed up. Recording the information is useless if it is not searchable, and Google is probably the best search. Can we have some list traffic searchable, and other not? Can we improve the findability of some content, while making other content less accessible to the public?