similar to: Docker container for Raspberry Pi

On Mon, Sep 11, 2017 at 10:56:10PM +0000, Guillermo Bisheimer wrote: > Just wanted to mention that I've published a docker image of tinc 1.1pre15 > for the raspberry pi 2/3. > > It was compiled from source on a raspberry 3 and published as > byscontrol/tinc-rpi <https://hub.docker.com/r/byscontrol/tinc-rpi/> along > witht the configuration instructions. > > The

Thanks for the update! I've been testing Tinc 1.1pre14 for a while in linux and windows, and it's working very well. But I'm having some trouble with Windows machines (mostly Win8 and Win10) when resuming from suspended state or hibernation the tinc daemon just stop responding. I have to shut down the process and start it back up to be able to connect to the VPN. The first line on

Thanks for the update! I've been testing Tinc 1.1pre14 for a while in linux and windows, and it's working very well. But I'm having some trouble with Windows machines (mostly Win8 and Win10) when resuming from suspended state or hibernation the tinc daemon just stop responding. I have to shut down the process and start it back up to be able to connect to the VPN. The first line on

On Mon, Sep 04, 2017 at 04:16:46PM +0000, Nirmal Thacker wrote: > Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Yes, but I have not tested this extensively. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833

On Mon, Sep 04, 2017 at 04:16:46PM +0000, Nirmal Thacker wrote: > Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Yes, but I have not tested this extensively. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

I've recently built a docker container to easily install and configure tinc 1.1pre14 in any machine using docker containers. I've created a Github repo in https://github.com/bys-control/docker-tinc I'm working in a WEB based admin interface for managing tinc daemons. Right now it's just a JSON API for tinc, but I'm working in developing the front end. Any

I'm using Tinc 1.1pre14 and I'm trying to connect a node that is behind a firewall that blocks all non-standard ports. I set up a rule in the server to redirect port 25 (that is not used in the server right now) to port 655, both in tcp and udp protocols, and set up the port 25 in the server host configuration file. The client can reach the server, but after the initial sync and key

Hi! I tried these two Dockers on Synology nas: https://github.com/JensErat/docker-tinc/ https://github.com/bys-control/docker-tinc For testing i set up a master Windows machine and a client one with also Windows. Connection between of them Works. So no i try to add a Synology NAS, so i can do remote backup. But i cannot set up any connection between the Docker container and master Windows

Thank you Guillermo. I will give it a go and revert back with my results. Regards Yazeed Fataar <yazeedfataar at hotmail.com> On Mon, Feb 13, 2017 at 2:26 PM, Guillermo Bisheimer < gbisheimer at bys-control.com.ar> wrote: > Hi Yazeed, > > You have to add this to tinc.conf > > TunnelServer = yes > > Otherwise tinc will manage package routing internally. Then you

thanks, but i was able to make it work based on some suggestion on tomato shibby forums. Regards Ramesh On Sun, Jan 15, 2017 at 9:02 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Fri, Jan 13, 2017 at 06:53:07PM +0000, Guillermo Bisheimer wrote: > > > I've setup a Tinc VPN for a bunch of nodes divided in two groups: > > > > Group 1: > > IP Range

Hi everybody. Is there a way to have a list of reacheable partners and its connection status? I need to list all partners in any tinc instance, its status (connected / disconnected) and connection method (direct, relayed thru other partner, etc.) Thanks! -- *Ing. Guillermo Bisheimer* *B&S Sistemas de Control y Equipamientos* Av. de los Constituyentes 1172 (E3116CIX) Crespo, Entre Ríos

Hi to all. I'm experimenting with tinc 1.1 using ubuntu and I need to generate a .deb package to be able to install latest 1.1pre14 version in ubuntu. I found the .deb package for debian in the experimental repositories, but couldn't find the same for ubuntu and wish to build the package myself. I'm able to compile and install Tinc from sources on ubuntu, but never created deb

Hi I have a simple hub and spoke topology where all my nodes connect to a central node. Below is tinc.conf for main node *tinc.conf* Name = main Interface = tun0 Forwarding = kernel and the remote nodes have same with ConnectTo = main. I have tried to apply a basic iptable policy on the main node but the traffic still seems to passthough and the nodes can communicate with each other. How do I

On Mon, Jan 16, 2017 at 12:29:59PM +0000, Guillermo Bisheimer wrote: > One more thing. I can run two tinc daemons one for each group, but I sill > need to communicate clients from one group to the other. > > Clients from group 2 (admin group) need to reach clients from group 1 > (remote server group), but clients from group 1 must not be able to reach > each other nor the

On 6 September 2017 at 10:47, Guillermo Bisheimer <gbisheimer at bys-control.com.ar> wrote: > Hi Etienne, > > I will try to reproduce the issue, as it not always happen. Just sometimes. Right, that matches my experience. > The TAP driver I have installed in the Tinc folder is version 9.0.0.8 > according to the .inf file included. > > Should I test with driver 9.0.0.9?

On Fri, Dec 30, 2016 at 11:38:51AM +0100, Etienne Dechamps wrote: > I believe the reason why you're experiencing this problem is because tinc > does not use the connection TCP port to determine which port to send UDP > packets to. Instead, it uses the port that is *advertised* by the other > node. That's correct, at least for the initial PMTU probes. If it receives packets

Hi to all. I've setup a Tinc VPN for a bunch of nodes divided in two groups: Group 1: IP Range 10.100.0.2 to 10.100.127.255 Group 2: IP Range 10.100.128.1 to 10.100.255.255 Server IP: 10.100.0.1 Every client connects only to the server. In the server I have the following tinc.conf: Name = server AddressFamily = ipv4 Interface = tun0 TunnelServer = yes Forwarding = kernel ListenAddress =

Can you post your Tinc configuration too? El lun., 30 ene. 2017 a las 11:42, Dave Albert (<dave.albert at gmail.com>) escribió: > Here is an extract of my current iptables that are not working: > > iptables -L -n -v > > Chain INPUT (policy DROP 8 packets, 1120 bytes) > pkts bytes target prot opt in out source > destination > 0 0