Login Form

Upcoming Events

Installfest Sat Apr 19 @10:00AM - 04:00PM
Linux Installfest/14.04 release party/Room 206&207 Sat Apr 19 @10:00AM - 04:00PM
Linux Installfest Sat Apr 19 @10:00AM - 04:00PM
AZLOCO Weekly Meeting Sun Apr 20 @ 9:00PM - 10:00PM
Ubuntu Hour Tempe Az Thu Apr 24 @ 7:00PM - 08:00PM
Az Loco North Installfest Sat Apr 26 @ 9:00AM - 02:00PM
AZLOCO Weekly Meeting Sun Apr 27 @ 9:00PM - 10:00PM
Installfest Sat May 03 @10:00AM - 04:00PM
April 2014
30 31 1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 1 2 3

AZ Loco News

  • Todd and I spent a morning installing and configuring owncloud on the team server. Things worked fairly well - with essentially only one glitch that I'll discuss at the end.

    owncloud was installed on a new virtual machine with Ubuntu server 12.04.3 as the initial install. Immediately after the install from an ISO image, the server was updated with the latest updates.

    A web search suggested that there are only install packages for OpenSuse. Later on (more by accident) we found out that Ubuntu has an owncloud package, but we didn't use that.

    The instructions we followed were these:
    We did put the whole owncloud content directly into /var/www. That worked for us, because the server is dedicated to the owncloud service.

    Also - make sure that ssl is running.

    At that point we were able to get to the opencloud server from within the local network via Firefox.

    Getting to the opencloud from the Internet was done by re-directing port 8081 from tempe.from-az.net to the firewall behind which all AzLoco servers sit. The firewall then does forward the request to the https port of the owncloud server.

    The main glitch that needed a bit of sleuthing was this:
    When going into the admin of the owncloud server (through the web interface), there was a message that WebDAV was misconfigured. In the end it turns out that owncloud uses CURL to test if the WebDAV works. CURL gets tripped-up on the fact that the certificate being used by apache used a fully qualified domain name that was different than what was in the web request URL. Once the certificate was re-created with the fully qualified domain name matching the host in the request URL, webDAV worked fine.

    We didn't attempt to get CA endorsed certificates, because the intent of this owncloud use is for team members, so overriding the certificate trust on the browser is acceptable.

  • AttachmentSize
    Notes_PI_VPN.pdf373.78 KB

    The basic idea here is to add a VPN connection to an existing residential network. The way its implemented is as an add-on to the existing network, so that the existing network doesn't need to be modified at all. Turning off VPN is simply done by shutting down the PI, no other reconfigs necessary.

Copyright for each contribution is retained by the contributor unless otherwise noted.
Hosting generously provided by Duncan Multimedia