similar to: client slow or never reconnects to different second address of server.

Hello, I have tried for days on end with no success on this, so I thought I would post it here and see if someone can help me at all. *Here's the scenario:* I have 1 PC with a Static IP/Domain (a dyndns.org account - myserver.homeip.net) connected to a router, which in turn is the gateway to the internet. It also has a static local IP (192.168.1.2). I will call this the "server"

I have now got the tinc demons (on network OFFICES) on BranchB and BranchA talking to each other, and I have been able to access services (like AFP, Apple file sharing) between the two hosts (in both directions), but not beyond the local network connected to BanchA. I am unclear which routing can be provided by tinc and which routing would I have to add manually. The aim is: BranchB is a

i have a switched and bridged tincd node with two addresses, each with a different port. Address = 37.70.156.168 28655 Address = 192.168.2.228 655 i was having trouble reliably connecting to it / thru it and noticed that a log from a remote tincd node indicated it may have mixed up the ports. It doesn't appear to use the 28655 port that would be needed for remote access. Before i

https://bugzilla.netfilter.org/show_bug.cgi?id=903 Summary: Second rule is not getting executed when we give different timeouts for the same ip address. Product: iptables Version: unspecified Platform: i386 OS/Version: Ubuntu Status: NEW Severity: normal Priority: P5 Component: iptables

How does one specify two different ports in the same host file? When lapops are hardwired versus when mobile on a totally different lan. address0 71.17.72.27 address1 192.168.2.27 port0 22755 port1 655

Hi Who concern, I setup TINC VPN follow these. 192.168.1.x / 24 (Client groups) | 192.168.1.1 (eth1) (GW1) 202.44.34.206 (eth0) || Internet || 202.44.45.14 (eth0) (GW2) 192.168.2.1 (eth1)

Hello, I've had this same model CyberPower connected to a linux server and a freebsd server. [root at sensor003 menon]# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus

I've noticed some inconsistent performance with some of my tunnels and thought I would take some of the spare free time I have over the holidays to try to figure out what the cause of that may be. My environment in this case is my home LAN. Please forgive my use of the terms "server" and "client" in this email, I only use these terms to simply explanation. I statically

Hi, Thank you Guus, I think the /16 solution is the easier to apply so I modified my tinc-up in host A to be like #!/bin/sh ifconfig $INTERFACE 192.168.10.1 netmask 255.255.0.0 a route -a from HOST A shows: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 178.62.128.1 0.0.0.0 UG 0 0 0 eth0 10.129.0.0

Hi, after trying for days I ended up with a working tinc configurazion of 2 subnets, now my goal is to add 2 more subnets and comunicate. I might seem dumb at this point but honestly I don't work in IT or Networking stuff, and so I dont have that deep knowledge. A little explanation of my configuration is HOST A (VPN server) Public IP: 1.2.3.4 tun0 Subnet = 192.168.10.0/24 tun0 IP =

Would it be extremely difficult to do multicast over tinc? How about reliable multicast over tinc? This would be more traffic than multicast dns, but not _necessarily_ a great deal more. It would be for syncing some information among freeipa domain controllers. Would the tinc nodes need to be in all in switch or maybe even hub mode? EthernetOverIP over tinc?

[This email is either empty or too large to be displayed at this time]

Very last. If you use one of these Citrix Virtual Delivery Agent (VDA) for Windows Desktop OS 7.x Citrix Receiver for Windows Then do check this link also. https://support.citrix.com/article/CTX216312 Greetz, i'm off2home. Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba > Verzonden:

You might want to try with https://github.com/gsliepen/tinc/pull/120 - that said, this bug probably doesn't explain everything because tinc is supposed to log a message from setup_vpn_in_socket() anyway, but there's no such message in your log. In addition, I really don't see any way the "Received UDP packet from unknown source" message could be logged if the UDP socket

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.

Hello, I'm a long term samba user through many different flavors from FreeBSD to Linux. My latest is using Ubuntu 16.04 with its older version of the 4.2 series of samba as an AD DC and separate 4.2 series file server. In my small test environment the Samba 4.2 AD DC and the Samba 4.2 file server are different LXC containers on the same host. I've worked through many of the

Have anything to do with firewall locations, meaning home vs work vs public vs lockdown. Probably not it at all. On Jul 13, 2016 3:22 PM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > That's strange. Can you post a detailed log from the affected node (run > tincd -d5 -D), especially the initialization phase? > > On 13 July 2016 at 16:17, Petr Man <petr

Since Fedora is pushing NSS SSL instead of OpenSSL, has someone tested tinc-vpn against NSS? As i recall, a single machine can not have OpenSSL and mod_nss installed at the same time anymore. So if you have apache running, you _may_ have problems running tinc? The nss api is supposed to mostly similar to openssl api, but there are some things openssl supports and somethings nss supports. Is

Currently, i have nodes with PMTUDiscovery =yes and ClampMSS = yes. When the server does not receive a PMTU request back from one of the clients even when the packet size is very small (say 164), then it reverts to TCP. Should i turn off PMTUDiscovery or should it be ok to leave on? It takes a very long time to do simple pings (1 second or so), so i wonder what else i can do?

ping times to ConnectTo machine are often over a second or at least 300 milliseconds. Hundreds or thousands of times slower than other nodes from same physical location.