http://wiki.lvl1.org/api.php?action=feedcontributions&user=RedWagon&feedformat=atomLVL1 - User contributions [en]2024-03-28T18:58:35ZUser contributionsMediaWiki 1.34.1http://wiki.lvl1.org/index.php?title=File_Server&diff=8747File Server2015-12-04T02:51:04Z<p>RedWagon: </p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|arrived=?<br />
|doesitwork=Working<br />
|contact=Aaron V.<br />
|where=next to Member Storage<br />
|picture=LVL1Network.jpg}}<br><br />
<br />
=Basic Info=<br />
* Web interface at http://files/<br />
* Can also be accessed via samba/SMB with the standard lvl1 credentials.<br />
* ssh is also possible, but there is no safety check for accidentally deleting files this way.<br />
=Setting up on Ubuntu=<br />
* Prerequisites:<br />
<pre><br />
sudo apt-get install autofs smbfs<br />
</pre><br />
* create autofs config files<br />
* /etc/auto.master<br />
<pre><br />
/mnt /etc/auto.files --timeout=6000 --ghost<br />
</pre><br />
* /etc/auto.files<br />
<pre><br />
z -fstype=smbfs,credentials=/etc/auto.auth ://files/shared<br />
</pre><br />
* /etc/auto.auth<br />
** (replace CENSORED with the lvl1 credentials)<br />
<pre><br />
username=CENSORED<br />
password=CENSORED<br />
</pre><br />
* run the following:<br />
<pre><br />
sudo chmod 400 /etc/auto.auth<br />
sudo service autofs restart<br />
</pre><br />
* the files share will be mounted in /mnt/z<br />
* to make this easily accessible, run<br />
<pre><br />
ln -s /mnt/z ~/z<br />
</pre><br />
* Desktop file for adding to menu (place in /usr/share/applications/<br />
<pre><br />
[Desktop Entry]<br />
Name=File Share<br />
Comment=LVL1 central file server<br />
Exec=nautilus /home/lvl1/z<br />
Icon=system-file-manager<br />
Terminal=false<br />
Type=Application<br />
StartupNotify=true<br />
OnlyShowIn=GNOME;Unity;<br />
Categories=GNOME;GTK;Utility;Core;<br />
MimeType=inode/directory;application/x-gnome-saved-search;<br />
X-GNOME-Bugzilla-Bugzilla=GNOME<br />
X-GNOME-Bugzilla-Product=nautilus<br />
X-GNOME-Bugzilla-Component=general<br />
X-GNOME-Bugzilla-Version=3.4.2<br />
Actions=Window;<br />
X-Ubuntu-Gettext-Domain=nautilus<br />
<br />
[Desktop Action Window]<br />
Name=File Share<br />
Exec=nautilus /home/lvl1/z<br />
OnlyShowIn=Unity;<br />
</pre><br />
=Server Setup=<br />
==File Systems==<br />
===Device===<br />
* Root is on a single drive. Important files are symlinked to the raid array.<br />
* Raid device is /dev/md0<br />
** Do not access this directly<br />
** Check status with <br />
<pre>cat /proc/mdstat</pre><br />
* Cache device is /dev/bcache0<br />
** This adds SSD caching on top of the /dev/md0<br />
** Interact with /dev/bcache0 as if it were a disk.<br />
** Mounted on /mnt/bcache0<br />
===Samba===<br />
* Samba is used to share files and provide a recycling mechanism<br />
* Services like elFinder that access member files use a mounted samba share so that samba can protect files from being deleted<br />
* Config file: /etc/samba/smb.conf<br />
===Autofs===<br />
* Used to mount the samba share locally<br />
* Config files<br />
** /etc/auto.master<br />
** /etc/auto.files<br />
** /etc/auto.files.auth<br />
* Dir<br />
** /mnt/autofs/z<br />
===ClamAV===<br />
* Virus scanner<br />
* Currently I only have a cronjob setup to manually scan the shared directory<br />
* cronjob /etc/cron.hourly/clamav<br />
* scans /home/lvl1/shared/<br />
* moves infected files to /home/lvl1/infected/<br />
* logs to /var/log/clamav.log<br />
<br />
=CloneZilla=<br />
This is the process for backing up computers to the file server.<br />
* Boot a clonezilla iso<br />
* Clonezilla Live<br />
* device-image<br />
* ssh_server<br />
* dhcp<br />
* 10.0.0.10<br />
* 22<br />
* lvl1<br />
* /home/lvl1/images<br />
* yes (if it asks for ssh key)<br />
* Beginner<br />
* disk device<br />
* I lost track here... but you should be good.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=MOTHER_LED&diff=8491MOTHER LED2015-10-11T18:27:06Z<p>RedWagon: </p>
<hr />
<div>This page documents the integration of MOTHER with BigBrite LED Signs. Although a lot of this information is related to connecting the LED signs with MOTHER, a lot of the information found here is related to the general hacking of the BigBrite LED signs. <br />
==Usefull Software and Links==<br />
[ http://ltxfaq.custhelp.com/cgi-bin/ltxfaq.cfg/php/enduser/std_adp.php?p_faqid=928 Lantronix CPR Software]<br />
Python libraries:<br />
ccprek's custom written library from the protocol pdf:<br />
https://github.com/ccprek/ledsign<br />
fork with some extra communication examples:<br />
https://github.com/RedWagon/ledsign<br />
<br />
==BigBright Communication==<br />
Most of the BigBrite signs have an rj11 or rj45 jack that allows the sign to be programmed via rs232 serial communication. It's possible that some of the these signs have an rs485 port that is meant to be plugged into an Internet connection, but none of these signs have been tinkered with yet. <br />
<br />
===Ethernet to Serial Adapters===<br />
* All of these seem to be from http://www.lantronix.com/<br />
* The software is surprisingly updated<br />
====Methods for configuring the adapters====<br />
* telnet port 9999<br />
* web inetrface port 80 (very broken)<br />
** leave username and password blank<br />
* There is a controller software that can help you find and configure all Lantronix devices called "DeviceInstaller"<br />
** It is installed on the stand up station on the workbenches in the main room<br />
** I recommend using the software instead of a normal web browser since there are some problems with the javascript<br />
** If the web interface does not exist updating the firmware should fix it<br />
====Communication====<br />
* Baud on the single line BigBrite is 9600<br />
* Pick a TCP port for each serial line (10001 is the default)<br />
* Passive Connection: Yes<br />
* Active Connection: Any Character<br />
* The dual ones might need a firmware update to put a port on each serial output.<br />
* Example code for python to sign on tcp serial adapter: https://github.com/RedWagon/ledsign/blob/master/simple_text.py<br />
===Serial port===<br />
* Works really well (much more reliable than the network adapters)<br />
* Example code for python to serial port: https://github.com/RedWagon/ledsign/blob/master/serial_test.py<br />
==BigBrite Connection Options ==<br />
The serial port was intended to be a connected to the "Multimedia 2007" software provided by BigBrite. The software allows you to make various screens, animations, and set settings related to the signs operation, which it can then transmit to the sign over the serial port. The serial port has been tested using the Rs232 DigiKey wireless modules and the lantronix rs232 over serial modules. The lantronix modules can be used with the multimedia software or by using the Lantronix CPR software (Com port replicator). The CPR software will let you add as many virtual ports as you want and then map each one to a lantronix Internet connected modules.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Graphtec_Vinyl_Cutter&diff=8278Graphtec Vinyl Cutter2015-08-24T02:27:26Z<p>RedWagon: /* Setting up Linux */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=20120801<br />
|model=Graphtec CE-5000<br />
|arrived=March 2013<br />
|doesitwork=Yes<br />
|contact=Brian W, Aaron V<br />
|where=Upstairs Loft<br />
}}<br />
<br />
=Basic Info=<br />
* Located upstairs<br />
* stuff and things<br />
* it's really awesome<br />
=Configuration=<br />
* The knife should not cut through the paper backing! A little scratching is OK, but if it's leaving holes in the paper you've got the pressure set too high.<br />
* 15 is a good pressure for the vinyl we have now.<br />
* I'll write up more later...<br />
=Using the Plotter=<br />
===Load Vinyl===<br />
* Place roll on back rack<br />
* Put lever in down position to unlock<br />
* feed vinyl in from the back<br />
** it will get stuck on lips as you push it through. I suggest using a small tool to help lift it up.<br />
[[File:leverdown.jpg]]<br />
===Position Rollers===<br />
* With the lever unlocked, slide the rollers into the appropriate spots<br />
* Rollers can only be placed underneath the blue lines<br />
** If you look closely in the picture, you can see the knurling on the bar beneath the rollers. This is how the machine moves the vinyl, if the rollers are not in these spots the plotter will refuse to run.<br />
* The plotter will only cut in between the rollers, make sure they are placed bigger than your cut.<br />
* Ideally the rollers should be as close as possible to make it less likely for the vinyl to fold up.<br />
[[File:positionroller.jpg]]<br />
===Lock Vinyl===<br />
* Flip the lever in the back up (locked)<br />
* The plotter should prompt you "ROLL 1 PRESS ENTER"<br />
** Roll 1 will automatically calibrate itself to the very front edge of the vinyl <br />
** Roll 2 will not look for the edge, but will accept the place you have locked it in as the origin<br />
** I forgot what the other modes do<br />
* Press enter<br />
* The head will move around, check roller locations, and then go to home. <br />
* Once locked and homed do not manually move things! From here on, use the keypad for movement.<br />
[[File:leverup.jpg]]<br />
===Position Head===<br />
* Move head with keypad to desired origin<br />
* Press Origin<br />
* This will set the home to wherever on the vinyl you've moved the head to.<br />
* This is handy for avoiding other peoples cuts<br />
===Cut===<br />
* You're ready to cut!<br />
* In your print settings make sure you cut a box around the print (aka weeding)<br />
* Print!<br />
===Remove Weeding===<br />
* Once the cut is done you have a few options<br />
** For large things, go ahead and cut the paper and work with the cut on a desk<br />
** For smaller things, try to work with it without cutting the backing. This makes the roll easier to work with as other people fill in the usable gaps.<br />
* With an Exacto knife (or other small, sharp tool) carefully pull out the weeding. In this example I left the backing untouched.<br />
* Even with a properly adjusted plotter, a few things will stick. Don't expect the weeding to pull out perfectly without any finesse and mash the plotter knife down to compensate. Just go slow, and use your knife to either hold down pieces or cut stuck edges. <br />
[[File:removeweeding.jpg]]<br />
===Pick up design with transfer tape===<br />
* Get some transfer tape and place it over the design<br />
[[File:transfertape.jpg]]<br />
[[File:transfertaped.jpg]]<br />
* Gently pick up design with the transfer tape<br />
* If you're picking up a design that's still attached to the roll, please pay attention to what you're doing to the good vinyl. It's easy to focus on the design and stretch out and ruin otherwise good areas of vinyl.<br />
[[File:ontransfertape.jpg]]<br />
===Clean Target Surface===<br />
* Remove old, inadequate labels made by people without awesome vinyl cutters<br />
* Clean surface<br />
[[File:removeold.jpg]]<br />
===Spray Transfer Solution===<br />
* Put a light misting of transfer solution on either the target object or your design<br />
** Lighter will stick faster<br />
** More will give you more time to place your design, but it can be hard to keep the design in place once you want it to stay<br />
** I prefer to hold the design at a distance and give it a light misting<br />
[[File:transfersolution.jpg]]<br />
===Place Design===<br />
* Place your design on the target surface.<br />
* With the solution it should be able to slide around easily<br />
* When in its final location, use a squeegee to work out some of the transfer solution. Be sure to work from the inside out.<br />
** On small things like this text, it's not going to do a lot<br />
** On big things it's easy to leave pockets of transfer solution under the vinyl. Be more diligent with larger designs.<br />
[[File:placedesign.jpg]]<br />
===Let Dry Some===<br />
* Ugh. I hate this part.<br />
* You don't have to let it dry all the way.<br />
* The vinyl needs to sit for a bit to adhere to the target surface. If you're impatient like me, you can spray a little transfer solution onto the transfer tape to wetten it and weaken its hold on the vinyl.<br />
<br />
===Peel off Transfer Tape===<br />
* Test a corner, then carefully peel off the transfer tape.<br />
* Depending on how early you peel off the transfer tape you might be able to move things around a bit. Fix any small things like punctuation, the dots above i's, etc.<br />
===Finished!===<br />
* Admire your work and don't touch it for awhile so it can dry completely.<br />
[[File:finisheddesign.jpg]]<br />
<br />
=Setting up Linux=<br />
* Hook up to USB<br />
* Install printer in CUPS<br />
* Choose Raw Queue as driver<br />
* Maker sure plotter is in HG-GL mode<br />
** Hit pause<br />
** Page Next until you see command<br />
** Enter<br />
** Arrow over to HG-GL<br />
* The best way to plot in Linux is with the Inkscape plugin, InkCut<br />
* Install inkscape<br />
* Download InkCut here:<br />
http://inkcut.sourceforge.net/<br />
<pre><br />
mv InkCut-1.0.tar.gz ~/.config/inkscape/extensions/<br />
cd ~/.config/inkscape/extensions/<br />
tar -xf InkCut-1.0.tar.gz<br />
</pre><br />
* Configure InkCut<br />
** Extensions -> Cutter / Plotter -> InkCut v1.0<br />
** Properties<br />
** Interface: Printer<br />
** Name: Graphtec_CE5000<br />
** Test Connection<br />
** You should hear the fans spin up and the vinyl cutter will cut a small box.<br />
** Save<br />
<br />
=Using InkCut and Inkscape=<br />
==Basics==<br />
* start Inkscape<br />
* draw something to print<br />
* remove Fill, add Stroke<br />
* change to Path<br />
* select it<br />
* Extensions -> Cutting/Plotting -> InkCut<br />
<br />
==Text==<br />
* Create text<br />
** fatter characters will be easier to work with<br />
* Rotate text 90 degress if needed (default will cut deep, not along the front edge of the vinyl. The laser example used above was rotated 90 degress)<br />
* Select text<br />
* Object -> Fill and Stroke<br />
** No fill<br />
** Select some stroke<br />
* Path -> Object to Path<br />
* Object -> Ungroup<br />
* Extensions -> Cutter/Plotter -> InkCut (NOTE: You can '''''[[NOT]]''''' be in a guest session)<br />
* Print!<br />
<br />
=Printing in Windows=<br />
Use Corel Draw on the Windows laptop next to the cutter. Corel draw has a plugin for cutting master. Once you have drawn your graphic, you need to click the icon under the word TEXT on the menu. There you will see the plot/cut plugin. Here is a video http://www.youtube.com/watch?v=WsYc68NQhlU Go to 4:58 to see what I am talking about.<br />
<br />
More info on Windows printing soon.<br />
<br />
<br />
=Troubleshooting=<br />
*If you run into a HPGL error on the cutter, then the cutter is in the wrong mode. Follow these instructions to put your cutter in the correct mode... <br />
http://www.signwarehouse.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=292<br />
*If your cuts do not go deep enough, then it is possible the cutter thinks it is in PEN mode. Press the '''Cond.''' key on the cutter and then choose the 09U cutter by using the arrow keys and enter.<br />
* If the cutter feeds a seemingly endless amount of vinyl before finally beginning to cut, it may have ended up in "Center Origin" mode.<br />
** In order to work properly, the cutter must be in "L.L" or Lower Left cutting mode.<br />
** To fix this, press, "Pause", then press "Next" until "Command" is selected. Hit "Enter," and select "HP-GL". Hit enter, and select "L.L" mode.<br />
*When all else fails - RTFM - http://www.graphtecamerica.com/users_manuals/CutPlot_UM/CE5000-UM-152-01.pdf</div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=7682ED-2092015-04-26T03:12:43Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use =<br />
[[File:Howtotaz1.jpg]]<br />
<br />
[[File:Howtotaz2.jpg]]<br />
<br />
= How to use - OLD METHOD = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import under Models to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
* Now that the STL is in Simplify3D, create a process by clicking Add under Processes.<br />
[[File:Create process.png]]<br />
* Make sure the LulzBot Taz 3 profile is selected and PLA as the material (ED is PLA only)<br />
* If you change any of the advanced settings, please save them under a different name<br />
** Note: I've found lulzbot PLA filament to work best at 200C (Chris)<br />
* Click OK<br />
[[File:Process_created.png]]<br />
* Now we have an STL and a process<br />
* Click Prepare to Print to generate gcode<br />
[[File:Preview.png]]<br />
* Drag the End slider back and forth if you want a quick overview of the part printing<br />
* Put the material cost in the box so we can keep buying filament<br />
* Click Save Toolpaths to Disk to save the gcode, preferably under Member Files in the file share (~/z/Member Files/)<br />
* Now it's time to print. Click the gear icon on the right to launch the Machine Control Panel (or Ctrl-P or Tools -> Machine Control Panel)<br />
[[File:Machinecontrolpanel.png]]<br />
* Turn on the Lulzbot<br />
* Select Port (should be ttyACM0 or ttyACM1) <br />
** Click refresh if it's not showing up<br />
** The custom names are not showing up in the new version of Simplify.<br />
* Click Connect<br />
* Click back to the G-Code Library tab<br />
* Select the name of the file you just exported<br />
* Click Run Selected G-Code<br />
* Alternatively, click Print then browse to the gcode file you saved.<br />
* The Lulzbot will heat up the build plate first, then the extruder so it will be a few minutes before it actually does something. You can watch it heat up on the LCD panel attached to the printer.<br />
* <b>If you must stop the print, be sure to turn off the heat or just power down the printer to be safe. The hot end and bed will not turn off if the print is stopped early.</b><br />
<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.<br />
* 06/16/2014 - Original hot-end epically and unrecoverably clogged with burnt PLA. Without active cooling (aka a fan), heat will rise into the upper sections of the hot-end and create problems with PLA. lulzbot sent a replacement nozzle, this time with a 0.5mm nozzle instead of 0.35mm as well as a cooling fan. Replaced these components and PLA printing is working great. Changed default nozzle settings in Simplify3D. 0.5mm should be an easier nozzle width for noobs to work with.<br />
* 08/14/2014 - This Lulzbot went suspiciously missing during the LVL1 move. No community members came forward to claim packing or transportation and it is presumed stolen. If this Lulzbot is found, please contact LVL1 to avoid being implicated in criminal activity. Louisville Metro Police has this theft on file as case 80-14-067531.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Howtotaz2.jpg&diff=7681File:Howtotaz2.jpg2015-04-26T03:11:43Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Howtotaz1.jpg&diff=7680File:Howtotaz1.jpg2015-04-26T03:10:51Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=7679ED-2092015-04-26T03:08:52Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use =<br />
= How to use - OLD METHOD = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import under Models to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
* Now that the STL is in Simplify3D, create a process by clicking Add under Processes.<br />
[[File:Create process.png]]<br />
* Make sure the LulzBot Taz 3 profile is selected and PLA as the material (ED is PLA only)<br />
* If you change any of the advanced settings, please save them under a different name<br />
** Note: I've found lulzbot PLA filament to work best at 200C (Chris)<br />
* Click OK<br />
[[File:Process_created.png]]<br />
* Now we have an STL and a process<br />
* Click Prepare to Print to generate gcode<br />
[[File:Preview.png]]<br />
* Drag the End slider back and forth if you want a quick overview of the part printing<br />
* Put the material cost in the box so we can keep buying filament<br />
* Click Save Toolpaths to Disk to save the gcode, preferably under Member Files in the file share (~/z/Member Files/)<br />
* Now it's time to print. Click the gear icon on the right to launch the Machine Control Panel (or Ctrl-P or Tools -> Machine Control Panel)<br />
[[File:Machinecontrolpanel.png]]<br />
* Turn on the Lulzbot<br />
* Select Port (should be ttyACM0 or ttyACM1) <br />
** Click refresh if it's not showing up<br />
** The custom names are not showing up in the new version of Simplify.<br />
* Click Connect<br />
* Click back to the G-Code Library tab<br />
* Select the name of the file you just exported<br />
* Click Run Selected G-Code<br />
* Alternatively, click Print then browse to the gcode file you saved.<br />
* The Lulzbot will heat up the build plate first, then the extruder so it will be a few minutes before it actually does something. You can watch it heat up on the LCD panel attached to the printer.<br />
* <b>If you must stop the print, be sure to turn off the heat or just power down the printer to be safe. The hot end and bed will not turn off if the print is stopped early.</b><br />
<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.<br />
* 06/16/2014 - Original hot-end epically and unrecoverably clogged with burnt PLA. Without active cooling (aka a fan), heat will rise into the upper sections of the hot-end and create problems with PLA. lulzbot sent a replacement nozzle, this time with a 0.5mm nozzle instead of 0.35mm as well as a cooling fan. Replaced these components and PLA printing is working great. Changed default nozzle settings in Simplify3D. 0.5mm should be an easier nozzle width for noobs to work with.<br />
* 08/14/2014 - This Lulzbot went suspiciously missing during the LVL1 move. No community members came forward to claim packing or transportation and it is presumed stolen. If this Lulzbot is found, please contact LVL1 to avoid being implicated in criminal activity. Louisville Metro Police has this theft on file as case 80-14-067531.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Main_Page/Network_infrastructure&diff=7581Main Page/Network infrastructure2015-03-31T00:18:34Z<p>RedWagon: </p>
<hr />
<div>This was old info, please see http://wiki.lvl1.org/Network instead.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Main_Page/Network_infrastructure&diff=7580Main Page/Network infrastructure2015-03-31T00:18:06Z<p>RedWagon: Blanked the page</p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=7579Network2015-03-31T00:14:05Z<p>RedWagon: /* I need a static IP */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/23 for wireless. The DHCP pool takes exactly 10.0.1.0/24 for wired and 10.0.3.0/24 for wireless<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static wired client<br />
** Any IP that starts with 10.0.1 is a dynamic wired cilent<br />
** Any IP that starts with 10.0.2 is a static wireless client<br />
** Any IP that starts with 10.0.3 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
== Router Details ==<br />
* Our router is a small pfSense box on the shelf in the network rack.<br />
* It has five interfaces. We only use:<br />
** WAN - connects to POE injector by TARDIS<br />
** LAN - connects to Master switch<br />
** WIRELESS - connects to wireless access point<br />
** (These are labeled on the back on of the router in permanent marker.)<br />
* DHCP runs here.<br />
== Switch Details ==<br />
* Everything is layer 2, the switches have an IP address only for management purposes.<br />
* Everything stays on default vlan.<br />
* Master is a 24 port gig switch. All other switches have 24 100MB/s ports and two gig ports.<br />
* For each access switch (A, B, C) the gig ports are trunked to provide redundancy and increase bandwidth.<br />
<pre>conf t<br />
trunk 25 trk1 trunk<br />
trunk 26 trk1 trunk</pre><br />
* On the master switch three different trunks are created (trk1-trk3) to support the three access switches.<br />
* If none of that made any sense, please just remember this: '''The links between switches have special configurations. Please do not move those cables around.'''<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
==I need a static IP==<br />
* Instead of setting a static IP on your device, create a static lease in our router.<br />
===Why?===<br />
* Your device can still use DHCP but will get the same IP every time<br />
* In some cases this can be much easier than manually setting a static IP<br />
* If you take your device somewhere else it can still use DHCP<br />
* You get a DNS entry<br />
* Visibility. We can track things better if they're in our router. Manually setting IPs makes conflicts more likely.<br />
===How?===<br />
* Log into pfSense as admin at https://10.0.0.1/<br />
** I'm not listing the creds on the wiki, any lvl1 member should be able to figure out the login<br />
* On the top bar click Status, then DHCP Leases<br />
* Scroll to the bottom of the page to pick your new IP<br />
** For wired, you'll pick an IP that starts with 10.0.0 (within 10.0.0.0/24)<br />
** For wireless, pick an IP that starts with 10.0.2 (within 10.0.2.0/24)<br />
** The IPs listed are already taken. Pick something else and remember it or write it down for the next steps.<br />
** For good measure, do a quick ping test to make sure nothing else has taken that.<br />
* Scroll back up to the top of the page and find your device. You can use the MAC address, hostname (not reliable if we have multiple things called "raspberrypi") or your current IP. Newer leases are closer to the top. <br />
* Click the + on the right next to your device. <br />
* Enter the following<br />
** IP Address: the ip address you picked earlier<br />
** Hostname: what you want the hostname to be. This will also update DNS. Please be specific, bonus points for also using your name.<br />
*** Being a good member: aaronv-pi<br />
*** Being a bad member: raspberrypi<br />
** Everything else can be ignored<br />
* Click Save<br />
* Click Apply<br />
* Renew your DHCP lease or, if you're lazy, reboot<br />
<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=7578Network2015-03-31T00:12:55Z<p>RedWagon: /* I need a static IP */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/23 for wireless. The DHCP pool takes exactly 10.0.1.0/24 for wired and 10.0.3.0/24 for wireless<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static wired client<br />
** Any IP that starts with 10.0.1 is a dynamic wired cilent<br />
** Any IP that starts with 10.0.2 is a static wireless client<br />
** Any IP that starts with 10.0.3 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
== Router Details ==<br />
* Our router is a small pfSense box on the shelf in the network rack.<br />
* It has five interfaces. We only use:<br />
** WAN - connects to POE injector by TARDIS<br />
** LAN - connects to Master switch<br />
** WIRELESS - connects to wireless access point<br />
** (These are labeled on the back on of the router in permanent marker.)<br />
* DHCP runs here.<br />
== Switch Details ==<br />
* Everything is layer 2, the switches have an IP address only for management purposes.<br />
* Everything stays on default vlan.<br />
* Master is a 24 port gig switch. All other switches have 24 100MB/s ports and two gig ports.<br />
* For each access switch (A, B, C) the gig ports are trunked to provide redundancy and increase bandwidth.<br />
<pre>conf t<br />
trunk 25 trk1 trunk<br />
trunk 26 trk1 trunk</pre><br />
* On the master switch three different trunks are created (trk1-trk3) to support the three access switches.<br />
* If none of that made any sense, please just remember this: '''The links between switches have special configurations. Please do not move those cables around.'''<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
==I need a static IP==<br />
===Why?===<br />
* Instead of setting a static IP on your device, instead create a static lease in our router.<br />
** In some cases this can be much easier than manually setting a static IP<br />
** If you take your device somewhere else it can still use DHCP<br />
** You get a DNS entry<br />
** Visibility; we can track things better if they're in our router. Manually setting IPs makes conflicts more likely.<br />
===How?===<br />
* Log into pfSense as admin at https://10.0.0.1/<br />
** I'm not listing the creds on the wiki, any lvl1 member should be able to figure out the login<br />
* On the top bar click Status, then DHCP Leases<br />
* Scroll to the bottom of the page to pick your new IP<br />
** For wired, you'll pick an IP that starts with 10.0.0 (within 10.0.0.0/24)<br />
** For wireless, pick an IP that starts with 10.0.2 (within 10.0.2.0/24)<br />
** The IPs listed are already taken. Pick something else and remember it or write it down for the next steps.<br />
** For good measure, do a quick ping test to make sure nothing else has taken that.<br />
* Scroll back up to the top of the page and find your device. You can use the MAC address, hostname (not reliable if we have multiple things called "raspberrypi") or your current IP. Newer leases are closer to the top. <br />
* Click the + on the right next to your device. <br />
* Enter the following<br />
** IP Address: the ip address you picked earlier<br />
** Hostname: what you want the hostname to be. This will also update DNS. Please be specific, bonus points for also using your name.<br />
*** Being a good member: aaronv-pi<br />
*** Being a bad member: raspberrypi<br />
** Everything else can be ignored<br />
* Click Save<br />
* Click Apply<br />
* Renew your DHCP lease or, if you're lazy, reboot<br />
<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=7577Network2015-03-31T00:07:35Z<p>RedWagon: </p>
<hr />
<div>{{Template:Space}}<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/23 for wireless. The DHCP pool takes exactly 10.0.1.0/24 for wired and 10.0.3.0/24 for wireless<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static wired client<br />
** Any IP that starts with 10.0.1 is a dynamic wired cilent<br />
** Any IP that starts with 10.0.2 is a static wireless client<br />
** Any IP that starts with 10.0.3 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
== Router Details ==<br />
* Our router is a small pfSense box on the shelf in the network rack.<br />
* It has five interfaces. We only use:<br />
** WAN - connects to POE injector by TARDIS<br />
** LAN - connects to Master switch<br />
** WIRELESS - connects to wireless access point<br />
** (These are labeled on the back on of the router in permanent marker.)<br />
* DHCP runs here.<br />
== Switch Details ==<br />
* Everything is layer 2, the switches have an IP address only for management purposes.<br />
* Everything stays on default vlan.<br />
* Master is a 24 port gig switch. All other switches have 24 100MB/s ports and two gig ports.<br />
* For each access switch (A, B, C) the gig ports are trunked to provide redundancy and increase bandwidth.<br />
<pre>conf t<br />
trunk 25 trk1 trunk<br />
trunk 26 trk1 trunk</pre><br />
* On the master switch three different trunks are created (trk1-trk3) to support the three access switches.<br />
* If none of that made any sense, please just remember this: '''The links between switches have special configurations. Please do not move those cables around.'''<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
==I need a static IP==<br />
* Log into pfSense at https://10.0.0.1/<br />
** I'm not listing the creds on the wiki, any lvl1 member should be able to figure out the login<br />
* On the top bar click Status, then DHCP Leases<br />
* Scroll to the bottom of the page to pick your new IP<br />
** For wired, you'll pick an IP that starts with 10.0.0 (within 10.0.0.0/24)<br />
** For wireless, pick an IP that starts with 10.0.2 (within 10.0.2.0/24)<br />
** The IPs listed are already taken. Pick something else and remember it or write it down for the next steps.<br />
** For good measure, do a quick ping test to make sure nothing else has taken that.<br />
* Scroll back up to the top of the page and find your device. You can use the MAC address, hostname (not reliable if we have multiple things called "raspberrypi") or your current IP. Newer leases are closer to the top. <br />
* Click the + on the right next to your device. <br />
* Enter the following<br />
** IP Address: the ip address you picked earlier<br />
** Hostname: what you want the hostname to be. This will also update DNS. Please be specific, bonus points for also using your name.<br />
*** Being a good member: aaronv-pi<br />
*** Being a bad member: raspberrypi<br />
** Everything else can be ignored<br />
* Click Save<br />
* Click Apply<br />
<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Community_Development_Initiative&diff=7076Community Development Initiative2014-12-03T22:44:57Z<p>RedWagon: /* Actionable Items */</p>
<hr />
<div>This is an ever-evolving list of things that need to be done to improve the space. Feel free to add, modify, expand upon, and most of all take action on any of these items. <br />
<br />
Try to create well-defined actionable items. Failing that, identify possible improvements that need a plan developed. Place them in the appropriate category. If you do something move it to the complete category with the names of those who need to be celebrated. <br />
<br />
== Actionable Items ==<br />
*Need permanent place for Shapeoko Mill, build rolling table for clean / dirty use<br />
*Build better form / entrance table from old Science Center kidney thing<br />
*LED signs at 2 inside entrances and parking lot window<br />
* averdow's list<br />
** Get more cable ends<br />
** Run ethernet to wood shop<br />
** Sand down ends in panel B so the blank spots can be filled in<br />
** Setup mail server on file server for Brad's scan thing<br />
** Setup KVM on file server<br />
** Move Testing servers down a couple U's, install new PDU and testing switch<br />
** Move station files out of \\files\shared and into their own shares<br />
** Print auto bed leveling parts for Taz<br />
*** http://www.thingiverse.com/thing:117957<br />
** Setup auto bed leveling on Taz<br />
** Document using Slic3r<br />
** Setup one click printing<br />
** Rename taz in udev rules<br />
** Create "Where's my Pi?" DHCP monitor<br />
** Setup some sort of monitoring system<br />
<br />
== Undeveloped Items ==<br />
*Place holder....<br />
<br />
== Completed Tasks ==<br />
*Place holder....</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Community_Development_Initiative&diff=7075Community Development Initiative2014-12-03T22:28:23Z<p>RedWagon: /* Actionable Items */</p>
<hr />
<div>This is an ever-evolving list of things that need to be done to improve the space. Feel free to add, modify, expand upon, and most of all take action on any of these items. <br />
<br />
Try to create well-defined actionable items. Failing that, identify possible improvements that need a plan developed. Place them in the appropriate category. If you do something move it to the complete category with the names of those who need to be celebrated. <br />
<br />
== Actionable Items ==<br />
*Need permanent place for Shapeoko Mill, build rolling table for clean / dirty use<br />
*Build better form / entrance table from old Science Center kidney thing<br />
*LED signs at 2 inside entrances and parking lot window<br />
* averdow's list<br />
** Get more cable ends<br />
** Run ethernet to wood shop<br />
** Sand down ends in panel B so the blank spots can be filled in<br />
** Setup mail server on file server for Brad's scan thing<br />
** Setup KVM on file server<br />
** Move Testing servers down a couple U's, install new PDU and testing switch<br />
** Move station files out of \\files\shared and into their own shares<br />
** Print auto bed leveling parts for Taz<br />
*** http://www.thingiverse.com/thing:117957<br />
** Setup auto bed leveling on Taz<br />
** Rename taz in udev rules<br />
** Create "Where's my Pi?" DHCP monitor<br />
** Setup some sort of monitoring system<br />
<br />
== Undeveloped Items ==<br />
*Place holder....<br />
<br />
== Completed Tasks ==<br />
*Place holder....</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6870Network2014-08-31T04:24:42Z<p>RedWagon: /* Misc */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/23 for wireless. The DHCP pool takes exactly 10.0.1.0/24 for wired and 10.0.3.0/24 for wireless<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static wired client<br />
** Any IP that starts with 10.0.1 is a dynamic wired cilent<br />
** Any IP that starts with 10.0.2 is a static wireless client<br />
** Any IP that starts with 10.0.3 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
== Router Details ==<br />
* Our router is a small pfSense box on the shelf in the network rack.<br />
* It has five interfaces. We only use:<br />
** WAN - connects to POE injector by TARDIS<br />
** LAN - connects to Master switch<br />
** WIRELESS - connects to wireless access point<br />
** (These are labeled on the back on of the router in permanent marker.)<br />
* DHCP runs here.<br />
== Switch Details ==<br />
* Everything is layer 2, the switches have an IP address only for management purposes.<br />
* Everything stays on default vlan.<br />
* Master is a 24 port gig switch. All other switches have 24 100MB/s ports and two gig ports.<br />
* For each access switch (A, B, C) the gig ports are trunked to provide redundancy and increase bandwidth.<br />
<pre>conf t<br />
trunk 25 trk1 trunk<br />
trunk 26 trk1 trunk</pre><br />
* On the master switch three different trunks are created (trk1-trk3) to support the three access switches.<br />
* If none of that made any sense, please just remember this: '''The links between switches have special configurations. Please do not move those cables around.'''<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6860Network2014-08-24T03:30:21Z<p>RedWagon: </p>
<hr />
<div>{{Template:Space}}<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/24 for wireless. The DHCP pool takes exactly 10.0.1.0/24<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static IP<br />
** Any IP that starts with 10.0.1 is a dynamic wired IP<br />
** Any IP that starts with 10.0.2 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
== Router Details ==<br />
* Our router is a small pfSense box on the shelf in the network rack.<br />
* It has five interfaces. We only use:<br />
** WAN - connects to POE injector by TARDIS<br />
** LAN - connects to Master switch<br />
** WIRELESS - connects to wireless access point<br />
** (These are labeled on the back on of the router in permanent marker.)<br />
* DHCP runs here.<br />
== Switch Details ==<br />
* Everything is layer 2, the switches have an IP address only for management purposes.<br />
* Everything stays on default vlan.<br />
* Master is a 24 port gig switch. All other switches have 24 100MB/s ports and two gig ports.<br />
* For each access switch (A, B, C) the gig ports are trunked to provide redundancy and increase bandwidth.<br />
<pre>conf t<br />
trunk 25 trk1 trunk<br />
trunk 26 trk1 trunk</pre><br />
* On the master switch three different trunks are created (trk1-trk3) to support the three access switches.<br />
* If none of that made any sense, please just remember this: '''The links between switches have special configurations. Please do not move those cables around.'''<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6859Network2014-08-24T03:28:32Z<p>RedWagon: </p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/24 for wireless. The DHCP pool takes exactly 10.0.1.0/24<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static IP<br />
** Any IP that starts with 10.0.1 is a dynamic wired IP<br />
** Any IP that starts with 10.0.2 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
== Router Details ==<br />
* Our router is a small pfSense box on the shelf in the network rack.<br />
* It has five interfaces. We only use:<br />
** WAN - connects to POE injector by TARDIS<br />
** LAN - connects to Master switch<br />
** WIRELESS - connects to wireless access point<br />
** (These are labeled on the back on of the router in permanent marker.)<br />
* DHCP runs here.<br />
== Switch Details ==<br />
* Everything is layer 2, the switches have an IP address only for management purposes.<br />
* Everything stays on default vlan.<br />
* Master is a 24 port gig switch. All other switches have 24 100MB/s ports and two gig ports.<br />
* For each access switch (A, B, C) the gig ports are trunked to provide redundancy and increase bandwidth.<br />
<pre>conf t<br />
trunk 25 trk1 trunk<br />
trunk 26 trk1 trunk</pre><br />
* On the master switch three different trunks are created (trk1-trk3) to support the three access switches.<br />
* If none of that made any sense, please just remember this: '''The links between switches have special configurations. Please do not move those cables around.'''<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6858Network2014-08-24T03:25:00Z<p>RedWagon: </p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/24 for wireless. The DHCP pool takes exactly 10.0.1.0/24<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static IP<br />
** Any IP that starts with 10.0.1 is a dynamic wired IP<br />
** Any IP that starts with 10.0.2 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
== Switch Details ==<br />
* Everything is layer 2, the switches have an IP address only for management purposes.<br />
* Everything stays on default vlan.<br />
* Master is a 24 port gig switch. All other switches have 24 100MB/s ports and two gig ports.<br />
* For each access switch (A, B, C) the gig ports are trunked to provide redundancy and increase bandwidth.<br />
<pre>conf t<br />
trunk 25 trk1 trunk<br />
trunk 26 trk1 trunk</pre><br />
* On the master switch three different trunks are created (trk1-trk3) to support the three access switches.<br />
* If none of that made any sense, please just remember this: '''The links between switches have special configurations. Please do not move those cables around.'''<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6857Network2014-08-24T03:17:47Z<p>RedWagon: /* Misc */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/24 for wireless. The DHCP pool takes exactly 10.0.1.0/24<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static IP<br />
** Any IP that starts with 10.0.1 is a dynamic wired IP<br />
** Any IP that starts with 10.0.2 is a dynamic wireless client<br />
* The wireless access point comes directly off the pfSense box and does not pass through the switches in the rack. This just eliminates a few points of failure.<br />
* Spanning tree is enabled (with portfast) and bpdu guard. If you create a loop the ports will get disabled. Telnet into the appropriate switch to re-enable it. All ports are labeled. <br />
** For example: A7 = port 7 on switch A. If it is disabled:<br />
<pre>telnet switch-a.lvl1.lan<br />
conf t<br />
int 7<br />
enable</pre><br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6856Network2014-08-24T03:14:03Z<p>RedWagon: /* Misc */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
* There are two subnets, 10.0.0.0/23 for wired clients and 10.0.2.0/24 for wireless. The DHCP pool takes exactly 10.0.1.0/24<br />
* What this means in laymans terms:<br />
** Any IP that starts with 10.0.0 is a static IP<br />
** Any IP that starts with 10.0.1 is a dynamic wired IP<br />
** Any IP that starts with 10.0.2 is a dynamic wireless client<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6855Network2014-08-24T03:06:35Z<p>RedWagon: /* Misc */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure. Please see parts list below.<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6854Network2014-08-24T03:05:58Z<p>RedWagon: /* Parts */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure.<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack]<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel)]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable]<br />
* [http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable]<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6853Network2014-08-24T03:05:37Z<p>RedWagon: /* Parts */</p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure.<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
== Parts ==<br />
* [http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box]<br />
* [ http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack ]<br />
* [ http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel) ]<br />
* [ http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable ]<br />
* [ http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable ]<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6852Network2014-08-24T03:05:10Z<p>RedWagon: </p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure.<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
== Parts ==<br />
* [ http://www.monoprice.com/Product?c_id=105&cp_id=10517&cs_id=1051705&p_id=7089&seq=1&format=2 2 Port Surface Mount Box ]<br />
* [ http://www.monoprice.com/Product?c_id=105&cp_id=10516&cs_id=1051603&p_id=7260&seq=1&format=2 Patch Panel for rack ]<br />
* [ http://www.monoprice.com/Product?c_id=105&cp_id=10513&cs_id=1051303&p_id=5622&seq=1&format=2 RJ-45 Jack (used in boxes and patch panel) ]<br />
* [ http://www.monoprice.com/Product?c_id=102&cp_id=10234&cs_id=1023401&p_id=8109&seq=1&format=2 Cable ]<br />
* [ http://www.monoprice.com/Product?c_id=102&cp_id=10232&cs_id=1023203&p_id=9837&seq=1&format=2 Patch Cable ]<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6851Network2014-08-24T02:58:24Z<p>RedWagon: </p>
<hr />
<div>{{Template:Space}}<br />
<br />
[[File:Lvl1-network.png]]<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure.<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Lvl1-network.png&diff=6850File:Lvl1-network.png2014-08-24T02:56:40Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=Network&diff=6849Network2014-08-24T02:34:20Z<p>RedWagon: </p>
<hr />
<div>{{Template:Space}}<br />
<br />
== Misc ==<br />
<br />
* We have standards now! Please do not add hodgepodge stuff to our network infrastructure.<br />
<br />
'''Internet Service graciously provided by http://bluegrass.net'''<br />
<br />
== Internet IPs==<br />
* 216.135.94.120/29 (LVL1 IPs)<br />
* 216.135.94.121 (bluegrass.net gateway)<br />
* 216.135.64.2 (bluegrass.net DNS 1)<br />
* 216.135.64.3 (bluegrass.net DNS 2)<br />
<br />
== Subnets ==<br />
* Wired: 10.0.0.0/23<br />
** DHCP Pool: 10.0.1.0/24<br />
** all static IPs should be between 10.0.0.1 and 10.0.0.255<br />
* Wireless: 10.0.2.0/24<br />
<br />
{{Template:Space_Footer}}</div>RedWagonhttp://wiki.lvl1.org/index.php?title=05/06/2014&diff=663805/06/20142014-05-03T03:57:12Z<p>RedWagon: Created page with "= First time Visitor Info = * Prime Directive: '''Be Excellent to Each Other''' * PARK ONLY IN THE ORI LOT OR ON THE STREET ** If you park in our neighbors private lot, they w..."</p>
<hr />
<div>= First time Visitor Info =<br />
* Prime Directive: '''Be Excellent to Each Other'''<br />
* PARK ONLY IN THE ORI LOT OR ON THE STREET<br />
** If you park in our neighbors private lot, they will block you in for fun.<br />
* Waivers of Liability - Please sign if you have not already<br />
* Our website / calendar is www.lvl1.org<br />
* Sign up for our Google Group discussion list<br />
** https://groups.google.com/forum/?fromgroups#!forum/lvl1<br />
* You can find all of our Meeting Minutes on our wiki: wiki.lvl1.org<br />
* Culture of Cleanliness<br />
<br />
= Equipment and Supplies Wanted =<br />
* (Tim) - 1/4" copper fittings<br />
** 5 x 100 lb. Propane Tanks<br />
** 1/4" copper tubing at least 2' long.<br />
** posted 6/11/2013<br />
* (Josh) - Red Bull Cans.<br />
** Posted 10/22/2013<br />
** Two Mylar weather balloons or giant white spheres<br />
** Bernheim Connect talking tree. <br />
** Posted 3/11/2014<br />
* (Justin) - Looking for a plug-n-play game system for handheld conversion. <br />
** Posted 2/25/2014<br />
* (Patrick) - Unpainted, non-galvanized scrap metal for welding workshops. <br />
** Posted 2/25/2014<br />
<br />
= Space Upgrades =<br />
* Lulzbot is now configured and documented. [http://wiki.lvl1.org/ED-209#How_to_use]<br />
<br />
<br />
= Space Downgrades =<br />
* PLA Makerbot may be down; keep an eye out & report problems<br />
* The quickest way to get something fixed is to let us know that it is broken! Send broken equipment reports to Broken@lvl1.org<br />
** This includes supplies like toilet paper and soap!<br />
<br />
= Space Moving Update =<br />
* Acquisition Date is ~May 1st.<br />
** Owner let us know on Monday that he wants us to carry insurance on the new building as of acquisition.<br />
** Working with insurance agent to accomplish this.<br />
<br />
= Regular Meetups =<br />
* '''MONDAY'''<br />
** [[Louisville Soundbuilders|Sound Builders]] (fortnightly Mondays, next 5/12 8pm)<br />
** Rope Work and Vertical Caving (1st Monday of the Month next 5/5 @ 6pm)<br />
** Caving Special topics Meetup (3rd Monday of the Month next 5/19 @ 6pm)<br />
* '''TUESDAY'''<br />
** LVL1 Open Meeting & Making (Tuesday 8pm)<br />
* '''WEDNESDAY'''<br />
** MakerEd Educators MeetUp (1st Wed of the Month 5/7 @ 7pm)<br />
** KYOSS Monthly Meeting (2nd Wed of the Month 5/14 @ 6:30pm) http://kyoss.org/<br />
** Muddytech SIG (3rd Wed of the Month 5/21)<br />
** JSLou Meetup (3rd Wed of the Month 5/21) http://jslou.org/<br />
** Java Workshop (4th Wed of the Month 5/28 @ 7pm)<br />
* '''THURSDAY'''<br />
** Muddytech Computer training (6pm upstairs) <br />
*** Looking for students<br />
** Sewing Workshop (3rd Thurs. of the Month @ 7pm, 5/15)<br />
*** Bring in an unfinished project, start something new, learn and sew it up!<br />
** Drone Meetup (4th Thurs. of the Month @ 8pm, 5/22)<br />
*** QUACC tickle your interest in Multirotors, UAVs, RC, or any other type of drone? Show up on the 4th Thursday!<br />
* '''FRIDAY'''<br />
** Irregular Movie and Open Build Night (8pm)<br />
*** Host: ???<br />
*** Movie: ???<br />
*** Group Pizza order placed at 7:30 pm ($7/person)<br />
** Louisville EAE (7pm)<br />
*** Compete in Engineering, Arts, & Extreme Sports events & contests!<br />
*** Host: Joshua M Wilcox<br />
***https://www.facebook.com/groups/LouEAE/<br />
***http://www.meetup.com/LouEAE/<br />
* '''SUNDAY'''<br />
** [[Game Dev|Game Dev Group]] (2pm)<br />
*** All game dev projects welcome! Collaborate with other teams or start your own!<br />
<br />
= Upcoming Workshops and Events =<br />
* Patrick's Ongoing Welding Workshops<br />
* April Makership Deadline - 4/30 at 11:59pm<br />
** More info about the Makership program at http://www.lvl1.org/makership<br />
* Give Local Louisville - 5/5<br />
** http://www.givelocallouisville.org/#npo/lvl1<br />
** LVL1 Can get matching funds for every donation! Help your hackerspace move, tell your friends and relatives!<br />
* Maker Faire Detroit - July 26 - 27<br />
** Call for Makers: http://www.makerfairedetroit.com/call-for-makers/<br />
** Tell them you're with LVL1!<br />
** Danielle is LVL1 Coordinator this year<br />
<br />
= Project Roll Call =<br />
<br />
=5 Minute Maintenance and Cleaning=<br />
<br />
= Meeting Notes = <br />
* Attendance: <br />
* Meeting Start:<br />
* Meeting Stop:<br />
* Dinner:<br />
* Tour Guide:<br />
* Notes Taken by:</div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6637ED-2092014-05-03T03:51:59Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import under Models to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
* Now that the STL is in Simplify3D, create a process by clicking Add under Processes.<br />
[[File:Create process.png]]<br />
* Make sure the LulzBot Taz 3 profile is selected and PLA as the material (ED is PLA only)<br />
* If you change any of the advanced settings, please save them under a different name<br />
* Click OK<br />
[[File:Process_created.png]]<br />
* Now we have an STL and a process<br />
* Click Prepare to Print to generate gcode<br />
[[File:Preview.png]]<br />
* Drag the End slider back and forth if you want a quick overview of the part printing<br />
* Put the material cost in the box so we can keep buying filament<br />
* Click Save Toolpaths to Disk to save the gcode, preferably under Member Files in the file share (~/z/Member Files/)<br />
* Now it's time to print. Click the gear icon on the right to launch the Machine Control Panel (or Ctrl-P or Tools -> Machine Control Panel)<br />
[[File:Machinecontrolpanel.png]]<br />
* Turn on the Lulzbot<br />
* Select Port (should be ttyACM0 or ttyACM1) <br />
** Click refresh if it's not showing up<br />
** The custom names are not showing up in the new version of Simplify.<br />
* Click Connect<br />
* Click back to the G-Code Library tab<br />
* Select the name of the file you just exported<br />
* Click Run Selected G-Code<br />
* Alternatively, click Print then browse to the gcode file you saved.<br />
* The Lulzbot will heat up the build plate first, then the extruder so it will be a few minutes before it actually does something. You can watch it heat up on the LCD panel attached to the printer.<br />
* <b>If you must stop the print, be sure to turn off the heat or just power down the printer to be safe. The hot end and bed will not turn off if the print is stopped early.</b><br />
<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6636ED-2092014-05-03T03:48:09Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import under Models to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
* Now that the STL is in Simplify3D, create a process by clicking Add under Processes.<br />
[[File:Create process.png]]<br />
* Make sure the LulzBot Taz 3 profile is selected and PLA as the material (ED is PLA only)<br />
* If you change any of the advanced settings, please save them under a different name<br />
* Click OK<br />
[[File:Process_created.png]]<br />
* Now we have an STL and a process<br />
* Click Prepare to Print to generate gcode<br />
[[File:Preview.png]]<br />
* Drag the End slider back and forth if you want a quick overview of the part printing<br />
* Put the material cost in the box so we can keep buying filament<br />
* Click Save Toolpaths to Disk to save the gcode, preferably under Member Files in the file share (~/z/Member Files/)<br />
* Now it's time to print. Click the gear icon on the right to launch the Machine Control Panel (or Ctrl-P or Tools -> Machine Control Panel)<br />
[[File:Machinecontrolpanel.png]]<br />
* Turn on the Lulzbot<br />
* Select Port (should be ttyACM0 or ttyACM1) <br />
** Click refresh if it's not showing up<br />
** The custom names are not showing up in the new version of Simplify.<br />
* Click Connect<br />
* Click back to the G-Code Library tab<br />
* Select the name of the file you just exported<br />
* Click Run Selected G-Code<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Machinecontrolpanel.png&diff=6635File:Machinecontrolpanel.png2014-05-03T03:44:35Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6634ED-2092014-05-03T03:38:26Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import under Models to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
* Now that the STL is in Simplify3D, create a process by clicking Add under Processes.<br />
[[File:Create process.png]]<br />
* Make sure the LulzBot Taz 3 profile is selected and PLA as the material (ED is PLA only)<br />
* If you change any of the advanced settings, please save them under a different name<br />
* Click OK<br />
[[File:Process_created.png]]<br />
* Now we have an STL and a process<br />
* Click Prepare to Print to generate gcode<br />
[[File:Preview.png]]<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Preview.png&diff=6633File:Preview.png2014-05-03T03:36:59Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6632ED-2092014-05-03T03:33:06Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import under Models to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
* Now that the STL is in Simplify3D, create a process by clicking Add under Processes.<br />
[[File:Create process.png]]<br />
* Make sure the LulzBot Taz 3 profile is selected and PLA as the material (ED is PLA only)<br />
* If you change any of the advanced settings, please save them under a different name<br />
* Click OK<br />
[[File:Process_created.png]]<br />
* Now we have an STL and a process<br />
* Click Prepare to Print to generate gcode<br />
<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Process_created.png&diff=6631File:Process created.png2014-05-03T03:31:56Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Create_process.png&diff=6630File:Create process.png2014-05-03T03:27:00Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6629ED-2092014-05-03T03:21:35Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import under Models to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
* Now that the STL is in Simplify3D, create a process by clicking Add under Processes.<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6628ED-2092014-05-03T03:20:21Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
[[File:Imported.png]]<br />
* If you want to edit the STL (scale, skew, etc) then double click on the name of the STL in the models box.<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Imported.png&diff=6627File:Imported.png2014-05-03T03:19:15Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6626ED-2092014-05-03T03:16:02Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
* Click Import to add an STL file<br />
** Don't have an STL file? Try [http://www.thingiverse.com/ Thingiverse]<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6625ED-2092014-05-03T03:11:07Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
[[File:Simplify3d.png]]<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:Simplify3d.png&diff=6624File:Simplify3d.png2014-05-03T03:10:35Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6623ED-2092014-05-03T03:10:20Z<p>RedWagon: /* How to use */</p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
* Below is the Simplify3D interface<br />
<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6622ED-2092014-05-03T03:08:32Z<p>RedWagon: </p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
[[File:S3dicon.png]]<br />
<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File:S3dicon.png&diff=6621File:S3dicon.png2014-05-03T03:06:58Z<p>RedWagon: </p>
<hr />
<div></div>RedWagonhttp://wiki.lvl1.org/index.php?title=ED-209&diff=6620ED-2092014-05-03T03:04:14Z<p>RedWagon: </p>
<hr />
<div>{{Template:Equipment<br />
|owner=LVL1<br />
|serial=KT-PR0014-5821<br />
|model=Lulzbot TAZ 3.1 3D Printer<br />
|arrived=4/1/2014<br />
|doesitwork=Yes<br />
|contact=Chris C<br />
|where=3D Printing area<br />
}}<br />
<br />
= General Info =<br />
<br />
Information with downloadable user manual [https://www.lulzbot.com/products/lulzbot-taz-3-3d-printer here]<br />
<br />
Ed uses 3mm filament.<br />
<br />
= How to use = <br />
* Simplify3D is on the 3D printer computer and configured for ED<br />
* Launch Simply3D by clicking the following icon<br />
<br />
<br />
<br />
==Maintenance Log==<br />
* 04/18/2014 - Maintenance log created.</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File_Server&diff=6487File Server2014-03-22T04:06:16Z<p>RedWagon: /* Server Setup */</p>
<hr />
<div>=Basic Info=<br />
* Web interface at http://files/<br />
* Can also be accessed via samba/SMB with the standard lvl1 credentials.<br />
* ssh is also possible, but there is no safety check for accidentally deleting files this way.<br />
=Setting up on Ubuntu=<br />
* Prerequisites:<br />
<pre><br />
sudo apt-get install autofs smbfs<br />
</pre><br />
* create autofs config files<br />
* /etc/auto.master<br />
<pre><br />
/mnt /etc/auto.files --timeout=6000 --ghost<br />
</pre><br />
* /etc/auto.files<br />
<pre><br />
z -fstype=smbfs,credentials=/etc/auto.auth ://files/shared<br />
</pre><br />
* /etc/auto.auth<br />
** (replace CENSORED with the lvl1 credentials)<br />
<pre><br />
username=CENSORED<br />
password=CENSORED<br />
</pre><br />
* run the following:<br />
<pre><br />
sudo chmod 400 /etc/auto.auth<br />
sudo service autofs restart<br />
</pre><br />
* the files share will be mounted in /mnt/z<br />
* to make this easily accessible, run<br />
<pre><br />
ln -s /mnt/z ~/z<br />
</pre><br />
* Desktop file for adding to menu (place in /usr/share/applications/<br />
<pre><br />
[Desktop Entry]<br />
Name=File Share<br />
Comment=LVL1 central file server<br />
Exec=nautilus /home/lvl1/z<br />
Icon=system-file-manager<br />
Terminal=false<br />
Type=Application<br />
StartupNotify=true<br />
OnlyShowIn=GNOME;Unity;<br />
Categories=GNOME;GTK;Utility;Core;<br />
MimeType=inode/directory;application/x-gnome-saved-search;<br />
X-GNOME-Bugzilla-Bugzilla=GNOME<br />
X-GNOME-Bugzilla-Product=nautilus<br />
X-GNOME-Bugzilla-Component=general<br />
X-GNOME-Bugzilla-Version=3.4.2<br />
Actions=Window;<br />
X-Ubuntu-Gettext-Domain=nautilus<br />
<br />
[Desktop Action Window]<br />
Name=File Share<br />
Exec=nautilus /home/lvl1/z<br />
OnlyShowIn=Unity;<br />
</pre><br />
=Server Setup=<br />
==File Systems==<br />
===Device===<br />
* Root is on a single drive. Important files are symlinked to the raid array.<br />
* Raid device is /dev/md0<br />
** Do not access this directly<br />
** Check status with <br />
<pre>cat /proc/mdstat</pre><br />
* Cache device is /dev/bcache0<br />
** This adds SSD caching on top of the /dev/md0<br />
** Interact with /dev/bcache0 as if it were a disk.<br />
** Mounted on /mnt/bcache0<br />
===Samba===<br />
* Samba is used to share files and provide a recycling mechanism<br />
* Services like elFinder that access member files use a mounted samba share so that samba can protect files from being deleted<br />
* Config file: /etc/samba/smb.conf<br />
===Autofs===<br />
* Used to mount the samba share locally<br />
* Config files<br />
** /etc/auto.master<br />
** /etc/auto.files<br />
** /etc/auto.files.auth<br />
* Dir<br />
** /mnt/autofs/z<br />
===ClamAV===<br />
* Virus scanner<br />
* Currently I only have a cronjob setup to manually scan the shared directory<br />
* cronjob /etc/cron.hourly/clamav<br />
* scans /home/lvl1/shared/<br />
* moves infected files to /home/lvl1/infected/<br />
* logs to /var/log/clamav.log</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File_Server&diff=6485File Server2014-03-22T02:56:44Z<p>RedWagon: /* Server Setup */</p>
<hr />
<div>=Basic Info=<br />
* Web interface at http://files/<br />
* Can also be accessed via samba/SMB with the standard lvl1 credentials.<br />
* ssh is also possible, but there is no safety check for accidentally deleting files this way.<br />
=Setting up on Ubuntu=<br />
* Prerequisites:<br />
<pre><br />
sudo apt-get install autofs smbfs<br />
</pre><br />
* create autofs config files<br />
* /etc/auto.master<br />
<pre><br />
/mnt /etc/auto.files --timeout=6000 --ghost<br />
</pre><br />
* /etc/auto.files<br />
<pre><br />
z -fstype=smbfs,credentials=/etc/auto.auth ://files/shared<br />
</pre><br />
* /etc/auto.auth<br />
** (replace CENSORED with the lvl1 credentials)<br />
<pre><br />
username=CENSORED<br />
password=CENSORED<br />
</pre><br />
* run the following:<br />
<pre><br />
sudo chmod 400 /etc/auto.auth<br />
sudo service autofs restart<br />
</pre><br />
* the files share will be mounted in /mnt/z<br />
* to make this easily accessible, run<br />
<pre><br />
ln -s /mnt/z ~/z<br />
</pre><br />
* Desktop file for adding to menu (place in /usr/share/applications/<br />
<pre><br />
[Desktop Entry]<br />
Name=File Share<br />
Comment=LVL1 central file server<br />
Exec=nautilus /home/lvl1/z<br />
Icon=system-file-manager<br />
Terminal=false<br />
Type=Application<br />
StartupNotify=true<br />
OnlyShowIn=GNOME;Unity;<br />
Categories=GNOME;GTK;Utility;Core;<br />
MimeType=inode/directory;application/x-gnome-saved-search;<br />
X-GNOME-Bugzilla-Bugzilla=GNOME<br />
X-GNOME-Bugzilla-Product=nautilus<br />
X-GNOME-Bugzilla-Component=general<br />
X-GNOME-Bugzilla-Version=3.4.2<br />
Actions=Window;<br />
X-Ubuntu-Gettext-Domain=nautilus<br />
<br />
[Desktop Action Window]<br />
Name=File Share<br />
Exec=nautilus /home/lvl1/z<br />
OnlyShowIn=Unity;<br />
</pre><br />
=Server Setup=<br />
==File Systems==<br />
===Device===<br />
* Root is on a single drive. Important files are symlinked to the raid array.<br />
* Raid device is /dev/md0<br />
** Do not access this directly<br />
** Check status with <br />
<pre>cat /proc/mdstat</pre><br />
* Cache device is /dev/bcache0<br />
** This adds SSD caching on top of the /dev/md0<br />
** Interact with /dev/bcache0 as if it were a disk.<br />
** Mounted on /mnt/bcache0<br />
===Samba===<br />
* Samba is used to share files and provide a recycling mechanism<br />
* Services like elFinder that access member files use a mounted samba share so that samba can protect files from being deleted<br />
* Config file: /etc/samba/smb.conf<br />
===Autofs===<br />
* Used to mount the samba share locally<br />
* Config files<br />
** /etc/auto.master<br />
** /etc/auto.files<br />
** /etc/auto.files.auth<br />
* Dir<br />
** /mnt/autofs/z</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File_Server&diff=6484File Server2014-03-22T02:35:12Z<p>RedWagon: /* Server Setup */</p>
<hr />
<div>=Basic Info=<br />
* Web interface at http://files/<br />
* Can also be accessed via samba/SMB with the standard lvl1 credentials.<br />
* ssh is also possible, but there is no safety check for accidentally deleting files this way.<br />
=Setting up on Ubuntu=<br />
* Prerequisites:<br />
<pre><br />
sudo apt-get install autofs smbfs<br />
</pre><br />
* create autofs config files<br />
* /etc/auto.master<br />
<pre><br />
/mnt /etc/auto.files --timeout=6000 --ghost<br />
</pre><br />
* /etc/auto.files<br />
<pre><br />
z -fstype=smbfs,credentials=/etc/auto.auth ://files/shared<br />
</pre><br />
* /etc/auto.auth<br />
** (replace CENSORED with the lvl1 credentials)<br />
<pre><br />
username=CENSORED<br />
password=CENSORED<br />
</pre><br />
* run the following:<br />
<pre><br />
sudo chmod 400 /etc/auto.auth<br />
sudo service autofs restart<br />
</pre><br />
* the files share will be mounted in /mnt/z<br />
* to make this easily accessible, run<br />
<pre><br />
ln -s /mnt/z ~/z<br />
</pre><br />
* Desktop file for adding to menu (place in /usr/share/applications/<br />
<pre><br />
[Desktop Entry]<br />
Name=File Share<br />
Comment=LVL1 central file server<br />
Exec=nautilus /home/lvl1/z<br />
Icon=system-file-manager<br />
Terminal=false<br />
Type=Application<br />
StartupNotify=true<br />
OnlyShowIn=GNOME;Unity;<br />
Categories=GNOME;GTK;Utility;Core;<br />
MimeType=inode/directory;application/x-gnome-saved-search;<br />
X-GNOME-Bugzilla-Bugzilla=GNOME<br />
X-GNOME-Bugzilla-Product=nautilus<br />
X-GNOME-Bugzilla-Component=general<br />
X-GNOME-Bugzilla-Version=3.4.2<br />
Actions=Window;<br />
X-Ubuntu-Gettext-Domain=nautilus<br />
<br />
[Desktop Action Window]<br />
Name=File Share<br />
Exec=nautilus /home/lvl1/z<br />
OnlyShowIn=Unity;<br />
</pre><br />
=Server Setup=<br />
==File Systems==<br />
* Root is on a single drive. Important files are symlinked to the raid array.<br />
* Raid device is /dev/md0<br />
** Do not access this directly<br />
** Check status with <br />
<pre>cat /proc/mdstat</pre><br />
* Cache device is /dev/bcache0<br />
** This adds SSD caching on top of the /dev/md0<br />
** Interact with /dev/bcache0 as if it were a disk.<br />
** Mounted on /mnt/bcache0</div>RedWagonhttp://wiki.lvl1.org/index.php?title=File_Server&diff=6483File Server2014-03-22T02:18:15Z<p>RedWagon: /* Server Setup */</p>
<hr />
<div>=Basic Info=<br />
* Web interface at http://files/<br />
* Can also be accessed via samba/SMB with the standard lvl1 credentials.<br />
* ssh is also possible, but there is no safety check for accidentally deleting files this way.<br />
=Setting up on Ubuntu=<br />
* Prerequisites:<br />
<pre><br />
sudo apt-get install autofs smbfs<br />
</pre><br />
* create autofs config files<br />
* /etc/auto.master<br />
<pre><br />
/mnt /etc/auto.files --timeout=6000 --ghost<br />
</pre><br />
* /etc/auto.files<br />
<pre><br />
z -fstype=smbfs,credentials=/etc/auto.auth ://files/shared<br />
</pre><br />
* /etc/auto.auth<br />
** (replace CENSORED with the lvl1 credentials)<br />
<pre><br />
username=CENSORED<br />
password=CENSORED<br />
</pre><br />
* run the following:<br />
<pre><br />
sudo chmod 400 /etc/auto.auth<br />
sudo service autofs restart<br />
</pre><br />
* the files share will be mounted in /mnt/z<br />
* to make this easily accessible, run<br />
<pre><br />
ln -s /mnt/z ~/z<br />
</pre><br />
* Desktop file for adding to menu (place in /usr/share/applications/<br />
<pre><br />
[Desktop Entry]<br />
Name=File Share<br />
Comment=LVL1 central file server<br />
Exec=nautilus /home/lvl1/z<br />
Icon=system-file-manager<br />
Terminal=false<br />
Type=Application<br />
StartupNotify=true<br />
OnlyShowIn=GNOME;Unity;<br />
Categories=GNOME;GTK;Utility;Core;<br />
MimeType=inode/directory;application/x-gnome-saved-search;<br />
X-GNOME-Bugzilla-Bugzilla=GNOME<br />
X-GNOME-Bugzilla-Product=nautilus<br />
X-GNOME-Bugzilla-Component=general<br />
X-GNOME-Bugzilla-Version=3.4.2<br />
Actions=Window;<br />
X-Ubuntu-Gettext-Domain=nautilus<br />
<br />
[Desktop Action Window]<br />
Name=File Share<br />
Exec=nautilus /home/lvl1/z<br />
OnlyShowIn=Unity;<br />
</pre><br />
=Server Setup=<br />
==File Systems==<br />
* Root is on a single drive. Important files are symlinked to the raid array.<br />
* Raid device is /dev/md0<br />
** Do not access this directly<br />
** Check status with <br />
<pre>cat /proc/mdstat</pre><br />
* Cache device is /dev/bcache0<br />
** This adds SSD caching on top of the /dev/md0<br />
** Interact with /dev/bcache0 as if it were a disk.</div>RedWagon