So there are all kinds of RaspberryPi projects out there, and many of them involve some kind of capture and ensuing notification. Pictures from the Pi camera, or motion logs from a passive infrared sensor, or any other alerts you could imagine. Some projects tell you how to post these these to Twitter, Facebook, google drive, and a bunch of others. Some even suggest using email, and this is what I want to do, use email. The one thing I have found lacking, is clear, concise details on using Gmail as the email server. While there are a ton of details, it took me a while to piece it all together for myself, and these are my findings.

At work we have a lab setup, complete with serial console access to a variety of appliances. This console access was provided through an old console server, which was FULL of problems. The biggest thing was just a lack of connectivity. Since moving, we have replaced those old console servers and denied access to the lab to most peoiple, so this setup has been rendered unnecessary. But I have an old IP Appliance sitting at home, which I have been wanting to tinker with, and it has a serial console connector, and the computer I have set up does not. So now I am revisiting the RasPi Serial Client to get it going at home, and serve as a bit of a console server (even though there is only 1 serial connection). Read on to see how I went about accomplishing this.

Please note that this is my first larger-scale How-To. So you have any suggestions/improvements, feel free to use the comments section and I will take a look.

So often I need to get files to or from my Raspberry Pi, though the same could be said for just about every internet connected device out there... But how to do so? Especially when you don't want to go through all the hassle of setting up SMB and network shares... There is a much easier way, and applies to not only the Raspberry Pi, but just about any device running open SSH (including Check Point's Gaia Operating System). Here's how to do it:

While setting up SFTP is easier, and far more secure, there are times when good ol' FTP is the only thing that'll work. This is often the case with legacy software, as is the case with an old IP260 I am setting up in a lab. My primary purpose for it is to set up Check Point's IPSO 4.2 and R65 (the newest stuff an IP260 can handle). While these both are far long end-of-life and are no longer officially supported by Check Point, there are still setups out with this (believe it or not). So what to do? If you have a Windows (ewww...) box, setting up Filezilla Server is a piece of cake. But what about Linux or the Raspberry Pi? While Filezilla is absolutely available for Linux (and the Pi), it is a bit more difficult to configure. Enter: vsftp: Very Small FTP. This is applicable for just about any Debian (and derivatives, including Raspbian for the Pi). Here's how to set it up and get a (very) basic config going:

So I am playing around with my Raspberry Pi and Pi Noir camera. One of the limitations of the Pi (if you even want to consider it a "limitation")  is the fact that it runs off an SD Card. While not a problem in and of itself, it means that I only a limited amount of storage space on the Pi. My solution to this was to simply throw in a 16GB USB stick.