Showing posts with label OwnCloud. Show all posts
Showing posts with label OwnCloud. Show all posts

Friday, February 1, 2013

PC-BSD 9.1 - More Jails and Linux

v 0.3.1
1 Feb 13
2 Feb 13
4 Feb 13

As I mentioned a couple of posts ago, most things are easy in hindsight, but maddening when you have to work them out.  Another such example I have found with PC-BSD Jails under the "Warden".  Rather than try and organise what I've found into little chunks, this will be a narration of the adventure.

I started learning about Jails using a Linux Jail.  I used an IP address within the router address space.  All was well until I tried to communicate with services within the Jail that I thought I'd started.  Not only that, but when I check the router's "attached devices" list, my Jail was nowhere to be seen.

I remembered there were two tutorial articles about Jails in BSD Magazine, one on Linux Jails in issue 12/12 and a tutorial on installing OwnCloud in a Standard Jail in issue 9/12.

The article on Linux Jails went into NAT configuration on the host and editing a few configuration files - I must confess I found this puzzling as a requirement since everything else about PC-BSD organisation of Jails was so automated.  Eventually I went back to the beginning and went through the tutorial setting up a standard BSD Jail.

What I found with the BSD Jail was that there were several other tools to manage these Jail types - including a Process manager, where I could make sure the processes I wanted were started.  That is where I started remembering the list of ports being monitored in the Linux Jail ....  Also, it was about that time I chanced on reading a statement in the PC-BSD forums where the poster pointed out that Warden does quite a few things in the background.

So ...

I cloned my BSD Jail, giving one an IP in the router address space, and the other another address in another address space.  I made sure the Apache process was started in each Jail and that the firewall had opened port 80.  Then I went to another computer on my network and simply typed in the IP address of each jail in a web browser.  The Jail with the router address space address worked immediately and Apache talked back.  The other one, not.

My conclusion as to Jail IP address:
  • If you are simply starting a Jail - give it an IP in the router address space.
  • If you are going to configure NAT on the host system, use another address space.
How do you find the Jail if the router does not know about it?  When you address your Jail, the router queries each of its attached machines.  When it queries the host machine, that machine recognises the Jail address and passes the request on to the Jail.  So the router doesn't have to know about the Jail, it just has to be able to have an address in its address space that it can give to the host machine that then knows.

NOW .. I went back to my Linux Jail - with its IP address in the router address space.  I installed an SSH server, made sure it was started (the listened port came up on the info tab).  I opened the SSH port on the firewall.  I then went to another machine on the network,

ssh (ip address)

The Jail replied!  Victory!

So you can now configure your router to talk to a Jail just like any other attached machine.  I would guess you could even assign a static IP to a Jail, using the mac address of the host machine.

A final note about Debian Jails.  When you install the Jail, there are several configuration tasks that are not taken care of that would normally be done so in a Debian Install, but are not.  That is my next little task to take care of with a Debian Linux Jail ....


Later ............

PS
For Debian,
  • an easy way to manage startup services is to load package " rcconf " and use that to graphically set services.
  • to set the default Locale, install package  " locales " and run " dpkg-reconfigure locales " to select and set your desired Locale.


Tuesday, May 29, 2012

The Law and TLD, The Cloud and Home Servers

v 0.22
12 Jun 12

I've recently had a few disparate threads of the Cosmos come together to lead me down a new line of interest with my Computing.  It all started a few months ago when I was reading my daily dose of "Slashdot" and has finished with me starting to set up a Home Server for myself.

The Law

Whilst the Slashdot article was about the US Government seeking the extradition of a UK Student, the issue was their assertion that all ".com , .net , .org " etc domain names were subject to US Law, no matter where the servers or businesses or organisations were located.  Now, whilst the current actions involve copyright infringement allegations, I can see that this could easily be extended to other areas of the law,  were it convenient for those in power.  A link to a relevent article:

http://www.theinquirer.net/inquirer/news/2083906/claims-com-net-websites-jurisdiction

Whether the legalities of this assertion by the US Government are shown to be valid or not, what it means (to me, anyway) is that if you host a website with one of these top level domains, then you potentially must comply with US Law.  You may, for example, run a business in one particular country using such a website, so not only do you need to comply with your own country's laws, you must also comply with those of the US.  Some (legitimate) Canadian businesses are already discovering this.

The lesson I've taken away from this is that if I need a business or other serious website, then a domain name from maybe my own country would be a better decision.

The Cloud

The Cloud is certainly a convenient place to store data, and in all normal circumstances, your data should be quite safe - Google has just received security certification for its services.  Dropbox, whilst convenient, doesn't store your data encrypted, whilst SpiderOak does.  If you are paranoid and want to use Cloud storage, then SpiderOak would be great.  Or encrypt your data on ANY Cloud device.

Of course the problem comes when your provider has their server seized by whichever Law Enforcement agency, because of some other entity which also uses that server ........

Home Servers

It almost feels to me that the concept of keeping your own data is making a comeback - perhaps not for all, but "the Cloud" is not necessarily the best move in all circumstances.  There are some really interesting Web applications that can be hosted on your own server.  Several I'm fascinated with are "OwnCloud", "OnEye", "Diaspora" and "Citadel".  I easily set up "OnEye" on a test virtual server at home, and did the same with "Citadel".

Routers

When I tried to demonstrate Citadel to an organisation I was a member of though, I found I couldn't get my router (Apple Time Capsule) to open any ports to allow this.  Googling for a solution gained me nothing other than finding more than a few others with the same problem and the best I could find was that it was a flaw in the firmware.

Bad Time Capsule .... Bad Bad Time Capsule.

So out of that, I thought maybe time for a "proper" router.  I'd recently seen an interesting "Category5TV" Episode 166 dealing with DD-WRT firmware and a Netgear router.  In the end, I chose to get a WNDR 3700 Netgear - for it's firmware flashing capabilities and the wireless range it offered.

* Subsequently I found that my ISP was blocking some ports - it wasn't helped by them denying it when I called to see if this was in fact happening.  Unfortunately I had to fall back on detective work to discover this (and then have my Nephew say "yes, of course they do, didn't you know?").  So Ultimately, I could have saved my money and continued with the Time Capsule by using unblocked ports.  Sigh

Server Hardware

As I mentioned before, I'd been playing with servers within Virtualbox Virtual Machines on my Desktop - now whilst at the time I knew my desktop wasn't the best machine to use as a server if only for its power consumption, I was prepared to live with this for a short while, however once I started thinking about the router problem, my mind drifted back a week or so to when Dell sent me an advertisement for what I considered to be a cheap desktop that would be suitable.  Of course, I wouldn't be buying the Dell because I had plenty of screens and keyboards already and saw no point in buying anymore, not to mention that I had no use for Windows on my server.  But research into the components did lead me to an interesting setup.

Motherboard   Asus P8H61-M LX Rev 3
CPU                Intel i-3 2120
Memory          8 gig
HDD               Western Digital 2 TB Caviar Green
DVD drive

This machine is about 10 times as fast as a P4 3.0 box I already have and uses less power.  How much less?   Testing I've seen indicates the machine should use between 50 and 100 watts under most conditions.  Using this as a server rather than one of the previous two I've mentioned would be a minimum saving of 200 watts.  This works out at roughly 5kwhr per day or over $1 per day where I live.  It would pay for itself in electricity charges in a year.

Server Software

Having worked out the hardware, I'm planning on replacing an old P4 desktop that is used by the family.  I intend having it used as a desktop, with Virtualbox providing servers in virtual machines.

Debian "Wheezy"  64bit
Xfce Desktop
Virtualbox

At the moment, I intend setting up one or two virtual machines as Citadel servers - one for the family and one for my organisation to evaluate.  After that, well there are a number of interesting projects that are available, even within the Debian repositories.

I think that is enough for now ... I shall report back with my installation adventures.



Later ...........

Friday, May 11, 2012

EyeOS v OnEye - Your Computing Desktop in the Cloud

v 0.2
11 May 12

For those who like looking at the last page .. I now have a onEye setup working on my home network.  It was easy to set up (using a Debian Apache webserver in Virtualbox) and is pretty neat.

Now to what I was about to talk about.

A couple of weeks ago, I was watching an episode of "The Linux Action Show" where they were talking about personal alternatives to cloud computing services.  One of these was the EyeOS product.  I was interested and had a look.  Whilst I really wanted to like this, I had the impression that the people there had moved solidly towards their "Professional" product (good on them) and their "2.5" release was just missing things that I would have liked.  I couldn't quite put my finger on it, but the feeling was there.

A bit more research and I was starting to get a feeling for what was going on.  It seems that the EyeOS has forked at the 1.9 branch as a community project, renamed "onEye" and that many people prefer this branch to what has been produced to the 2.x series.  I have the feeling that the 2.x series would appeal to businesses, whereas the 1.9 series is more for the community.  The thing that really got me interested in looking at onEye rather than EyeOS was an evaluation which suggested that installation was less than ideal in the EyeOS implementation, and that the 2.x series was incompatible to many add-on applications that had been developed.

So what is it about all this that you should be interested about?  Effectively, when you log on to onEye / EyeOS, you are logging on to a computer desktop in the cloud.  Think Dropbox with a desktop and applications.  They have a sync applicaton along with some standard apps that are supplemented by a whole swag of others.  There is even a web browser in the standard setup.  Now why would you want a web browser within a web browser?  Well for a start, all browsing traces are left in the cloud.

Whilst reaction time for this desktop over the Internet is entirely dependent upon your connection speed, on a home network it is quite snappy and could be really useful for organising the sometimes chaotic things that happen on different computers at home - particularly in centralising backups of files we don't want to use.  (of course .. ownCloud is a contender for that as well).


Later ....