Minor build document improvments (#926)

* Improve some build documentation

* Address build failure

doc/Building.md

@@ -220,3 +220,11 @@ destination.
 
 This is not a good way to produce binaries for embedded environments (like OpenWRT)
 as they will often use a different libc environment.
+
+# N2N Packages
+
+There are also some example package build recipes included with the source.
+
+- [Debian](../packages/debian/README)
+- [RPM](../packages/rpm)
+- [OpenWRT](../packages/openwrt/README.md)

packages/openwrt/README.md

@@ -2,9 +2,14 @@
 
 This instructions explain how to build an OpenWRT .ipk package for n2n.
 
-Before going on, it is required to have a working cross-compiling build
-environment for the OpenWRT version installed into your device. This usually
-comes down to the following steps:
+You will either need to build a full OpenWRT buildchain (See the github
+action for building openwrt.yml for some example steps) or have a working
+cross-compiling build environment for the OpenWRT version installed into
+your device.
+
+### Downloading a cross-compiling build environment
+
+This usually comes down to the following steps:
 
 1. Download and extract the SDK toolchain for your device. The toolchain
    must match the *exact* OpenWRT version installed in your device. Toolchain

src/edge.c

@@ -1080,7 +1080,7 @@ int main (int argc, char* argv[]) {
             conf.federation_public_key = calloc(1, sizeof(n2n_private_public_key_t));
             if(conf.federation_public_key) {
                 traceEvent(TRACE_WARNING, "using default federation public key; FOR TESTING ONLY, usage of a custom federation name and key (-P) is highly recommended!");
-                generate_private_key(*(conf.federation_public_key), FEDERATION_NAME + 1);
+                generate_private_key(*(conf.federation_public_key), &FEDERATION_NAME[1]);
                 generate_public_key(*(conf.federation_public_key), *(conf.federation_public_key));
             }
         }