More configuration on the Pi

Since my last post, although my [fun][geek] evening time was limited, I managed to fix a few issues on my home network, thanks to my Raspberry Pi.
First, I made it reachable from the Internet. Nothing difficult there: I already had this setup for my "old" Dell Linux machine. Just a matter of:

  1. Assigning a fixed local IP address to the RPI.
  2. Configuring a NAT rule on the Internet gateway that maps an external port (e.g. 12345) to the SSH daemon port on the RPI (port 22).
  3. Having a small client that registers the Internet gateway external IP address to a free dynamic  DNS service. For that I installed and configured "ddclient" with an account from DynDNS.


Cool... How geek, now I can remotely connect to my home network from the Internet. Well, this is needed for later: I want it to be the center and the entry to my home network. Home-automation, security here we go!

Since my [fabulous] Internet gateway still refuses to persist DHCP static lease bindings, I decided to turn off its DHCP server and let the Raspberry Pi be the new DHCP server of the network. That way, it controls which device gets which IP address... Again, very simple, I just had to follow the steps described here. All IP addresses are defined in the "/etc/hosts" files and the "/etc/dhcp/dhcpd.conf" contains only the hostnames.

Alright I am set. Now my next target is to develop a simple light-weight application to handle HTTP REST calls; this little server would run on the RPI and provide the means for initiating actions or fetching information from my home...
Time to go back to the C world (and hopefully to C++ too)... I don't feel like learning Python or using Java. And I think I found what I need: GNU libmicrohttpd!

Comments

Post a Comment

Popular posts from this blog

ZWay: getting the device list.

Back after a while... and a son! Here is a piece of code that can be used with the latest version of the ZWay library. It makes it possible to retrieve the Z-Wave device list and display the device names and associated XML file (each recognized device can be associated to an XML that contains a bunch of meta-data: name, description etc.). int main(int argc, char ** argv) { ZWay theZWay; ZWError result; memset(&theZWay, 0, sizeof(theZWay)); result = zway_init(&theZWay, "/dev/ttyAMA0", "/home/pi/src/razberry-proxy/config", "/home/pi/src/razberry-proxy/translations", "/home/pi/src/razberry-proxy/ZDDX", stdout, Warning); if (result == NoError) { result = zway_start(theZWay, &terminationCb); if (result == NoError) { printf("Discovering...\n"); result = zway_discover(theZW
Read more

First steps with the ZWay library

The Z-Wave "RaZberry" installation comes with everything needed to be able to do some custom development in C; everything is installed in the /opt/z-way-server  directory. There, one can find: A set of (documented, nice!) C header files found in /opt/z-way-server/libzway-dev : CommandClassesPublic.h FunctionClassesPublic.h ZDataPublic.h ZDefsPublic.h ZErrors.h ZPlatform.h ZWayLib.h A set of libraries found in /opt/z-way-server/libs : libmicrohttpd.so libv8.so libzwayhttp.so libzwayjs.so libzway.so For the ZWay stack to run properly, it is needed to provide the necessary configuration files. Instead of using these directly from the installation folder, I made a copy in order not to mess up too much with my working/configured setup. The following directories from the ZWay installation folder are needed: config translations ZDDX For experimenting I made a small Makefile in order to build and run. main.out: main.c gcc -I/opt/z-way-server/li
Read more

Libcurl: perform a REST HTTP PUT

The libcurl library does not provide a clear example on how to issue HTTP PUT operations in a REST context; the examples are mainly about file transfers . For my proxy application this is not really what I need: I want to perform a REST HTTP PUT, keep it simple, meaning without using the "Expect" and "Transfer-Encoding" that libcurl adds by default. After some struggling I discovered that this behavior can be changed by using the following code: CURL * pCurl; struct curl_slist *headers = NULL; headers = curl_slist_append(headers, "Content-Type: application/json "); headers = curl_slist_append(headers, "Content-Length: 12345 "); headers = curl_slist_append(headers, "Expect:"); headers = curl_slist_append(headers, "Transfer-Encoding:"); pCurl = curl_easy_init(); curl_easy_setopt(pCurl, CURLOPT_VERBOSE, 1); curl_easy_setopt(pCurl, CURLOPT_PUT, 1); curl_easy_setopt(pCurl, CURLOPT_URL, " https://your-server.app
Read more