similar to: Email etiquette

Displaying 20 results from an estimated 10000 matches similar to: "Email etiquette"

2016 Dec 29
0
Allow direct connection between some (but not all) nodes on the network (Guus Sliepen)
Guus Sliepen, I am working in a zeroconf setup for tinc called tzk, that could allow you to make this easily https://github.com/NebTex/tzk/ it will make better readme this weekend but you need a public machine with a public domain - subdomain pointed to it, the script will install tinc, consul (that is used for coordinate the vpn), and caddy a small reverse proxy for expose consul to the public
2016 Jul 25
0
How does tinc server handle the case one client's key file is removed after connection
Thanks Guus for the quick answer, I will give a try now. Рысь, In my case we don't want to restart tinc "server" at all, therefore what might happen is that the client is still connected to server while its public key was already removed from server. I will try the signal approach. Heng On Mon, Jul 25, 2016 at 12:42 PM, <tinc-request at tinc-vpn.org> wrote: > Send tinc
2015 Sep 24
0
tinc initialization (in both Red Hat and Debian families)
Would it not make more sense to have this on packagers responsiblity instead like you were saying adding it into the upstream repo. Maybe have a secondary repo that people can contribute to for distribution specific files and install scripts. On 24 September 2015 at 21:30, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: >
2016 Oct 09
2
make tinc as a reusable lib possible?
Just wait tinc be more lib style for some future days:) 2016-10-09 22:45 GMT+08:00 Guus Sliepen <guus at tinc-vpn.org>: > On Sun, Oct 09, 2016 at 10:40:12PM +0800, Cong Monkey wrote: > >> If release as libtinc possible, will that possible that you relicence >> TINC as LGPL to make commercial use possible? > > Both tinc and MeshLink are licensed under the GPL and will
2016 May 13
2
Bridge not forwarding multicast traffic to the tap interface
yes, ip_forward was turned on. iptables is defaulted to ACCEPT policy on all the 3 chains. On Sat, May 14, 2016 at 1:24 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sat, May 14, 2016 at 12:06:51AM +0800, Terry T wrote: > > > I have a Debian 8 64-bit machine set up as a server and apt-got the tinc > > package. I configured tinc as a bridge and everything seems
2017 Sep 04
0
[Announcement] Tinc versions 1.0.32 and 1.1pre15 released
Thanks Guus! Looking forward to trying out tinc 1.1pre15. Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Nirmal On Sat, Sep 2, 2017 at 1:47 PM Guus Sliepen <guus at tinc-vpn.org> wrote: > With pleasure we announce the release of tinc versions 1.0.32 and > 1.1pre15. > > Here is a summary of the changes in tinc 1.0.32: > > * Fix segmentation fault when using Cipher =
2017 Sep 04
0
[Announcement] Tinc versions 1.0.32 and 1.1pre15 released
Thanks Guus! Looking forward to trying out tinc 1.1pre15. Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Nirmal On Sat, Sep 2, 2017 at 1:47 PM Guus Sliepen <guus at tinc-vpn.org> wrote: > With pleasure we announce the release of tinc versions 1.0.32 and > 1.1pre15. > > Here is a summary of the changes in tinc 1.0.32: > > * Fix segmentation fault when using Cipher =
2015 May 21
0
IPv6 subnet routing
You have a typo in your routes: fd80:2015:2105:adcd::/6 abcd vs. adcd On 21 May 2015, at 19:35, Martin <martinmoen at gmail.com<mailto:martinmoen at gmail.com>> wrote: I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024
2014 Dec 28
1
Road for 1.1 (2.0) backward compatibility
And how distant are we from a 1.1.0? :) On Sun, Dec 28, 2014 at 10:49 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sun, Dec 28, 2014 at 10:33:47AM -0200, Raul Dias wrote: > > > I know this comes up from time to time. So it is time to update our > > expectations. > > > > Is there a roadmap for a 1.1 backward compatibility already? > > The roadmap
2015 Oct 19
1
Feasibility of Tinc vpn with my current setup.
Thanks for the reply Guss, So in my case the Amazon VPS server is behind a FULL CONE NAT(static NAT), so is that enough to hole punch other nodes. what all ports will should be opened up on the NAT device? Most of the other nodes are behind cg-nat, so I wont have any control over its nat. Thank you, Regards, Bobby Thomas. On Oct 19, 2015 1:45 AM, "Guus Sliepen" <guus at
2015 Oct 27
1
dns resolution behind proxy
Hello Guus, thanks for Your fast reply. Does it mean only socks is affected and http proxy should work? If this is the case then this may be a temp. solution. Thanks and regards! Uwe Am 27.10.2015 14:08:36, schrieb Guus Sliepen: > On Tue, Oct 27, 2015 at 12:33:35PM +0000, Uwe Werler wrote: > > > I wonder why tinc tries to resolve host names before connection even > > with
2017 Jan 26
1
Compression not working between 1.1pre11 and 1.1pre14
Guus, i wonder if you have had a moment to have a look at the compression issue? Thanks a lot! Peter -----Original Message----- From: tinc [mailto:tinc-bounces at tinc-vpn.org] On Behalf Of Guus Sliepen Sent: Thursday, December 29, 2016 1:15 PM To: tinc at tinc-vpn.org Subject: Re: Compression not working between 1.1pre11 and 1.1pre14 On Thu, Dec 29, 2016 at 12:47:15PM -0000, Peter Schulze
2017 May 10
1
If two identical host get up, what will happen?
Will the later one can't get onto the tinc domain, or either one may get disconnected? I may give a try later to validate this. Sent from iPhone > 在 2017年5月11日,上午1:46,Guus Sliepen <guus at tinc-vpn.org> 写道: > >> On Tue, May 09, 2017 at 05:28:43PM +0800, Bright Zhao wrote: >> >> I mean exactly the same configuration, including the pub-pri key. > > You
2014 Nov 24
1
Connection failing between 2 nodes with dropped packets error
Cipher is enabled with the default setting (Blowfish CBC) Digest is disabled Compression is disabled MACLength is the default (4 if I remember correctly) I suspect that the issue is related to the encryption. I tried disabling encryption and the issue wasn?t reproduced during an automated test run of 400 reconnections. Regards, Alexandre Beaulieu > On Nov 22, 2014, at 3:19 PM, Guus Sliepen
2016 Feb 14
2
Qts - L --mLock option
So as best practice running tinc I should include it ? Regards Yazeed Fataar <yazeedfataar at hotmail.com> On Sun, Feb 14, 2016 at 1:08 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sun, Feb 14, 2016 at 10:53:19AM +0300, Yazeed Fataar wrote: > > > Going through the options tinc has . Can someone explain exactly what the > > purpose is for -L option for the
2017 Jan 16
0
Firewall rules for TINC server
Thanks for the answer Guus, 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 server. If I'm not using TunnelServer and Forwarding, How can I setup
2016 Mar 13
1
Fwd: How to avoid friends of friends joining the vpn ?
Thanks I will look into StrictSubnets, while digging through the mailling list I came across this: https://github.com/siblynx/tinc-1.0.16_hostupd/blob/master/README.hostupd which is pretty close to what I need That looks to be a fork on its own, with no PR raises for addding that functionality to the main tinc, unless I missed it out. Are there any plans to bring that functionality in ? -azul
2018 Mar 20
1
Tinc deployments in the USA
I meant Tinc site-site VPN deployments in US business segments. Just references if any. On Tue, Mar 20, 2018 at 1:44 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Tue, Mar 20, 2018 at 12:53:55PM -0700, al so wrote: > > > Are there any Tinc deployments in the USA in Medium sized businesses and > > small Enterprises? > > Yes. However, VPNs are Virtual *Private*
2016 Mar 04
1
ipv6 default route from somewhere
On Fri, Mar 04, 2016 at 09:43:44PM +0100, Guus Sliepen wrote: > - On Linux, add "echo 0 >/proc/sys/net/ipv6/conf/$INTERFACE/accept_ra" > to tinc-up before any ifconfig or ip commands. Ah, if it's only the default route you don't want, then it's: echo 0 >/proc/sys/net/ipv6/conf/$INTERFACE/accept_ra_defrtr -- Met vriendelijke groet / with kind regards,
2015 Nov 07
1
dns resolution behind proxy
On Tue, Oct 27, 2015 at 02:08:36PM +0100, Guus Sliepen wrote: > > I wonder why tinc tries to resolve host names before connection even > > with configured (socks5) proxy which fails behind restrictive firewalls. > > [...] I'll try to change tinc so it will allow connections via SOCKS5 > even if it cannot resolve the hostname itself. I added the ability for tinc to