similar to: Signal tinc under Windows

(Second try to send this. I wonder if the first one gotten eaten by a spam filter; I'll link to patches instead of attaching them.) Here are the tincctl patches I've been working on. They apply to http://www.tinc-vpn.org/svn/tinc/branches/1.1@1545. I intend to commit them once the crypto stuff's fixed. Since they're basically done, I'm emailing them now for review and in case

c:\APPS\TINC\tincd.exe --mlock --net=mynet --config=C:\APPS\tinc\mynet Without --mlock, the service starts OK. With --mlock, the service fails to start.

I have the habit of putting the name of the host within the host file as a comment usually on the first line. Helps when files are renamed and tracking. The new version exports Name = victor and so the old comment style is not necessary. I would think the new version should still simply ignore lines that begin with the '#' character. For example, a normal host file named victor that

Hi, I use tinc-vpn to create private mesh vpn networks between office and house in different locations and it works really well. But somehow I'm considering if there were any possibility to add radius support for single node traffic management. I does think it will be really difficult to implement such functions as a feature of a mesh network,because all of the traffic was initiated end to

Hi! I have compiled and installed tinc 1.1pre5 on a ubuntu machine. With the tinc 1.0.x version that is included in the ubuntu repository I am used to having the config files in /etc/tinc/ and where each vpn has a own directory. The file nets.boot placed in /etc/tinc where I can specify which vpn tunnels that is going to start automatically. How can I get the vpn tunnels to start automatically

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

First off, thanks to all who have made tinc possible and continue to work developing it. I hope perhaps in time I can become a useful part of this community. :) I'm having an interesting issue with tincctl and was hoping someone could shed some light on it. Everything seems to work correctly when I build for OSX; however on linux and windows builds, I always receive connection

On 19/01/16 17:31, Yazeed Fataar wrote: > Hi Graham > > Regarding the tun lib , see mine. > > root at OpenWrt:~# /lib/modules/3.3.8/tun.ko But didn't one of your earlier mails say that tun did not appear in your lsmod output? If the module is there but not loaded, why don't you just "insmod" it? I am confused. Sorry, I can't help further. I have told

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

Hi Maxim See below. root at OpenWrt:/etc/tinc/acmevpn# modprobe -v tun -ash: modprobe: not found root at OpenWrt:/etc/tinc/acmevpn# lsmod tun Module Size Used by Not tainted crc_ccitt 928 0 root at OpenWrt:/etc/tinc/acmevpn# uname -a Linux OpenWrt 2.6.31.10 #1 Tue Jul 23 14:34:17 CEST 2013 mips GNU/Linux root at OpenWrt:/etc/tinc/acmevpn# opkg info

Thanks Graham Please excuse me as I am a noob in linux . I have come across this link through searches. I just dont know how to start... Do I "wget http://www.tinc-vpn.org/packages/tinc-1.0.26.tar.gz" to openwrt vm and then how do I compile it in openwrt? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> This

On 19/01/16 18:25, Maxim Vorontsov wrote: > Yazeed, your tun.ko for 3.3.8. Which kernel do you use? > Show your "uname -a". By the way, 3.3.8 seems very old for an OpenWrt kernel. The router I am running tinc on has 3.8.10 and is several years old. I built that image myself but it was based on Barrier Breaker r36499. You may want to find a more recent build -- for example a

This may have already been addressed, and I apologize if it has, but here is my issue. I have separated the TINCD log from syslog to isolate the VPN activity. By starting with daemon with the --logfile= switch It seems to work fine except that once log rotation takes place, the daemon does not recreate the log, nor will it write to the new log even if an empty file is put into place. The only

Forget about tinc. I won't work until you solve issue with your kernel. On Tue, Jan 19, 2016 at 9:45 PM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: > this is what happens when I try to run tincd > > root at OpenWrt:/etc/tinc/vpn# tincd -n vpn -D -d5 > > tincd 1.0.21 (Mar 9 2014 18:26:59) starting, debug level 5 > > Could not open /dev/net/tun: No such file

Hello folks, for monitoring purposes I need to query the network status in order to get all a list of all "online" nodes (that are connected to the network right now). How can I do so? Thanks in advance, Keep smiling yanosz

Hi We have several stale nodes in our tinc network and I'd like to remove these. These nodes show up in graph dumps as red nodes, indicating they are unreachable. We run: tinc -n <vpn-name> purge Nothing happens. If we tail the logs at /var/log/syslog, we dont see an ack or message concerning the purge either. The dead nodes still show up in the graphs and their certs are still

Hello, We're suffering from sporadic network blockage(read: unable to ping other nodes) with 1.1-pre17. Before upgrading to the 1.1-pre release, the same network blockage also manifested itself in a pure 1.0.33 network. The log shows that there are a lot of "Got ADD_EDGE from nodeX (192.168.0.1 port 655) which does not match existing entry" and it turns out that the mismatches

I'm a new Asterisk user. I've managed to set it up to do everything I want except sound good. Currently, Asterisk sounds considerably worse than my cell phone. I know VOIP can be _better_ than my cell phone, because I've heard Skype do it. (Using 32k iLBC, I believe.) I did an experiment with audio quality: 1) I made a recording which was pretty good. I used an iSight

You can find tinc package in openwrt repo and install it with opkg or luci. I suggest you first run couple of tinc nodes on x86, just to understand how it works. -- brgds Max On Jan 19, 2016 7:17 PM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: Any help please? Regards Yazeed Fataar On Mon, Jan 18, 2016 at 3:39 PM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: Thanks