Tinc and OpenWRT

[Lance Fredrickson]

I'm a heavy tinc/router enthusiast.  I have a few binaries 
(tinc1.1pre11) I've created for use in mipsel and arm routers available 
at the following.
http://files.lancethepants.com/Binaries/tinc/
Statically compiled, and should work (unless perhaps you're using an 
older MIPSR1 mipsel router which needs an older toolchain).

The scripts used to create these binaries are here if you'd like to 
recreate them.
https://github.com/lancethepants/tinc-mipsel-static/blob/master/tinc.sh
https://github.com/lancethepants/tinc-arm-musl-static

The mipsel binaries use the entware toolchain, which in turn I believe 
is borrowed from openwrt. The arm binaries are created from a musl libc 
toolchain I like, also referenced on github.

I like tinc so much I made an integration with gui into builds of tomato 
firmware.  I've provided some firmware images available for mipsel 
devices also available on my site (the first link). Tomato shibby has 
added my tinc gui into his mipsel and arm builds, but hasn't caught up 
with my 1.1pre11 changes as of yet. More info and screenshots at the 
following link.

http://www.linksysinfo.org/index.php?threads/tinc-mesh-vpn-beta-testing.70257/

Code for this project at the following links.
https://github.com/lancethepants/Toastman-Tinc
https://github.com/lancethepants/Toastman-Tinc-MIPSR1


On 1/26/2015 4:39 PM, Jonathan Clark wrote:
> Greetings.
>
> I'm new to tinc, but have so far managed to get a couple laptops and a
> hosted server all connected.  They're working as expected, running
> Tinc 1.1-pre11, which I compiled from source.
>
> Next I want to move on to adding my home router into the mix.  My
> routers run OpenWRT.  I don't have experience compiling anything from
> source for OpenWRT, but OpenWRT has Tinc 1.0.25 prepackaged.
>
> With that in mind, which direction should I move next?  I think my options are:
>
> (option a)
> Switch my existing/working Tinc setup to using RSA keys (instead of
> Ed25519) so they can talk to the 1.0.25 packages available on OpenWRT,
> and then go on to figure out how to get the already-packaged Tinc
> 1.0.25 working on my router.
>
> or
> (option b)
> Take a detour and learn how to cross-compile things for OpenWRT.  Use
> this new knowledge to install Tinc 1.1pre11 onto my router.  Feel
> accomplished.
>
> or something else?
>
> I'm exploring this mainly for the fun of figuring it out, so there's
> no deadline or even a business reason to succeed.  Does that suggest I
> should tackle option a, and then go ahead and try option b, resulting
> in twice the fun and sense of accomplishment?
>
> And, overall, how difficult are each of these options?
>
> Thanks, by the way, for all your work.  From what I've seen so far,
> this project is pretty impressive.
>
> Jonathan
> Kingston, New York, USA
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc