search for: schopen

Am Freitag, den 25.09.2015, 22:45 +0200 schrieb Marcus Schopen: > Hi Guus, > > Am Freitag, den 25.09.2015, 17:46 +0200 schrieb Marcus Schopen: > > Hmmm ... I've tried "LocalDiscovery = yes" > > in /etc/tinc/mytunnel/tinc.conf already, but that didn't help. Config on > > client A is: > > > > -----------...

Hi Guus, Am Freitag, den 25.09.2015, 17:04 +0200 schrieb Guus Sliepen: > Ok, that means by default the UDP NAT timeout on the Cisco is extremely > short. > > > I check the manual of the the Cisco NAT for any TCP/UDP > > timeout settings, but there is no way to modify anything like "keeps > > TCP/UDP connections alive". > > It wouldn't be called

Hi, I'm running some tinc clients behind a NAT (masquerading, Cisco Router) connecting to a host outside on a public IP in a different network. The tunnels get unstable every few minutes and I see packet loss when pinging the clients on their internal tunnel IPs from the host side. Before putting the tinc clients behind the NAT they were running on public IPs too (clients and host in

Hi Guus, Am Freitag, den 25.09.2015, 09:36 +0200 schrieb Guus Sliepen: > On Fri, Sep 25, 2015 at 08:41:06AM +0200, Marcus Schopen wrote: > > > I'm running some tinc clients behind a NAT (masquerading, Cisco Router) > > connecting to a host outside on a public IP in a different network. The > > tunnels get unstable every few minutes and I see packet loss when > > pinging the clients on their int...

Hi, Am Samstag, den 26.09.2015, 15:45 +0200 schrieb Marcus Schopen: > Hi, > > Am Samstag, den 26.09.2015, 12:20 +0200 schrieb Marcus Schopen: > > Last Problem seems to be the local UFW Firewall on the clients whichs > > seems to block the Broadcast for LocalDiscovery = yes. Need to check the > > logs here. > > Puzzeling around wi...

On Fri, Sep 25, 2015 at 08:41:06AM +0200, Marcus Schopen wrote: > I'm running some tinc clients behind a NAT (masquerading, Cisco Router) > connecting to a host outside on a public IP in a different network. The > tunnels get unstable every few minutes and I see packet loss when > pinging the clients on their internal tunnel IPs from the...

On Fri, Sep 25, 2015 at 04:51:22PM +0200, Marcus Schopen wrote: > > Maybe the timeout for UDP NAT mappings is a bit short on your Cisco. Try > > adding PingInterval = 30 to the tinc.conf on those clients, perhaps that > > will help. > > Thanks for pushing me into the right direction. I disabled "TCPOnly = > yes" on...

Hi Guus, Am Freitag, den 25.09.2015, 17:46 +0200 schrieb Marcus Schopen: > Hmmm ... I've tried "LocalDiscovery = yes" > in /etc/tinc/mytunnel/tinc.conf already, but that didn't help. Config on > client A is: > > --------------- > Name = clienta > AddressFamily = ipv4 > Interface = tun0 > ConnectTo = host > PingInterval =...

Hi, Am Samstag, den 26.09.2015, 12:20 +0200 schrieb Marcus Schopen: > Last Problem seems to be the local UFW Firewall on the clients whichs > seems to block the Broadcast for LocalDiscovery = yes. Need to check the > logs here. Puzzeling around with UFW firewall. What ports need to be open on the clients to get "LocalDiscovery = yes" working? I...

Hi, I'm using LocalDiscovery = yes to let tinc clients connect directly behind a NAT. Problem is that clients only start to talk directly after pinging each client from each client. Is there way to force direct connection after starting the tunnel. Ciao!

Hi, I use Samba's root preexec funktionality to create dynamic logon scripts: root preexec = /usr/local/samba/install/bin/make_logon_script '%m' '%U' '%a' '%g' '%L Who do I check in the by make_logon_script generated logon .bat script, which is executed on the windows clients, if a drive letters is already occupied by novell. The logon.bat script should

Hi, in the logfile of one of my WinXP SP3 clients I see this message once a second and thousands over the day [2012/01/20 17:27:22, 2] lib/access.c:check_access(323) Allowed connection from (xxx.xxx.xxx.xxx) The client is in the same internal subnet with the PDC. I checked the client and access to the shares, roaming profile and printing works fine. After restarting the client the logging