tinc running openwrt (mikrotik metarouter mips)

[Yazeed Fataar]

Hi Graham

Regarding the tun lib , see mine.

root at OpenWrt:~# /lib/modules/3.3.8/tun.ko

And like i mention to Maxim , i have tinc running in a Linux Debian
environment with 4 nodes successfully. I am experimenting now in openwrt
due to the "light weight" environment.

Regards
Yazeed Fataar
<yazeedfataar at hotmail.com>

On Tue, Jan 19, 2016 at 8:27 PM, Yazeed Fataar <yazeedfataar at gmail.com>
wrote:

> Hi Graham
>
> Can you perhaps share with me the mr-mips metarouter image you are using?
>
> Regards
> Yazeed Fataar
> <yazeedfataar at hotmail.com>
>
> On Tue, Jan 19, 2016 at 8:01 PM, Graham Cobb <g+tinc at cobb.uk.net> wrote:
>
>> On 19/01/16 03:57, Yazeed Fataar wrote:
>> > Hi Marek
>> >
>> > I managed to setup everything in openwrt. However I am getting errors
>> > when trying to run tinc daemon. Below is my debug output. Please help..
>> > How do I fix tunnel interface error?
>> >
>> > root at OpenWrt:/etc/tinc/vpn# tincd -n vpn -D -d3
>> >
>> > tincd 1.0.21 (Mar  9 2014 18:26:59) starting, debug level 3
>> >
>> > /dev/net/tun is a Linux ethertap device
>>
>> On my OpenWrt system, the corresponding log entry says:
>>
>> /dev/net/tun is a Linux tun/tap device (tun mode)
>>
>> I don't know if that is a real problem.  And I don't know how the tun
>> device gets created -- I don't remember having to do anything special
>> (but it was a long time ago when I set it up).
>>
>> However, I do start tinc using "/etc/init.d/tinc start", not by running
>> tincd directly.
>>
>> > Executing script tinc-up
>> >
>> > ifconfig: SIOCGIFFLAGS: No such device
>> >
>> > ifconfig: SIOCSIFADDR: No such device
>> >
>> > Script tinc-up exited with non-zero status 1
>>
>> That doesn't look good!
>>
>> My /etc/tinc/NETWORK/tinc-up file contains:
>>
>> #!/bin/sh
>> ifconfig $INTERFACE 1.2.3.4 netmask 255.255.0.0
>> /etc/init.d/firewall reload
>>
>> (with the real IP address for this node of the VPN instead of 1.2.3.4,
>> of course).
>>
>> I do remember some work being needed to get the firewall set up
>> correctly.  But you aren't getting that far.
>>
>> I would support Maxim's suggestion: make sure you have a simple tinc
>> network working on ordinary Linux systems first, to make sure you know
>> how the keys and addressing work.
>>
>> Graham
>> _______________________________________________
>> tinc mailing list
>> tinc at tinc-vpn.org
>> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20160119/4a542f44/attachment.html>