search for: tincnet

On Tue, Apr 10, 2018 at 03:36:08PM +0200, Hans de Groot wrote: > hosta  <--> hostb  <-->  hostc > > Hosta and hostc are not directly connected via tinc. But both are conncted > via hostb (I called my network tincnet). This works fine I can ssh from > hosta to hostc and vice versa without any problems. > > hostc is in a whitelisted iprange at some service provider. > > I need hosta to talk to a certain ip (lets call it ipaddressx) via hostc. > > I added the iptables mangle rule to mark a...

...bly why traffic goes out via hostb when I do not have the specific subnet/ip at hostc Regards Hans de Groot configs at hosta tinc.conf Name = hosta Device =/dev/net/tun Hostnames = No connectto = hostb Mode = Router KeyExpire = 3600 PingInterval = 10 PingTimeout = 15 PrivateKeyFile = /etc/tinc/tincnet/rsa_key.priv ProcessPriority = high PMTUDiscovery = yes tinc-up #!/bin/bash ifconfig $INTERFACE 192.168.230.21 netmask 255.255.255.0 route add -net 192.168.230.0 netmask 255.255.255.0 gw 192.168.230.1 ip route add default via 192.168.230.160 dev tincnet table hostc ip rule add from 0.0.0.0/0 fwmar...

I have a three tinc server setup, similar to "4.3 How Connections Work" using the configuration mostly likehttp://ostolc.org/site-to-site-vpn-with-tinc.html The clients (Ubuntus, Debians and Windows 10s) can all ping (and SSH) to each other remotely. As far as that is concerned it's working great - thanks so much for some great software. However, on each of the Tinc servers (A and

...pull/166 > Regards > > Hans de Groot > > > configs at hosta > tinc.conf > Name = hosta > Device =/dev/net/tun > Hostnames = No > connectto = hostb > Mode = Router > KeyExpire = 3600 > PingInterval = 10 > PingTimeout = 15 > PrivateKeyFile = /etc/tinc/tincnet/rsa_key.priv > ProcessPriority = high > PMTUDiscovery = yes > > tinc-up > #!/bin/bash > ifconfig $INTERFACE 192.168.230.21 netmask 255.255.255.0 > route add -net 192.168.230.0 netmask 255.255.255.0 gw 192.168.230.1 > ip route add default via 192.168.230.160 dev tincnet table...

Hey there, So I have two Amazon EC2 instances (micro) running tincd. Each is running dnsmasq to provide a dhcp server for tinc users. Their configuration looks something like this: [tinc1:/etc/tinc/tincnet/tinc.conf] Name = tinc1 AddressFamily = ipv4 Interface = tun0 Mode = switch ConnectTo = tinc1 ConnectTo = tinc2 [tinc1:/etc/tinc/tincnet/hosts/tinc1] Address = 10.100.250.100 Subnet = 172.31.1.1/32 [tinc1:/etc/tinc/tincnet/tinc-up] #!/bin/sh ifconfig $INTERFACE 172.31.1.1 netmask 255.25...

Hello List, I have this setup: hosta  <--> hostb  <-->  hostc Hosta and hostc are not directly connected via tinc. But both are conncted via hostb (I called my network tincnet). This works fine I can ssh from hosta to hostc and vice versa without any problems. hostc is in a whitelisted iprange at some service provider. I need hosta to talk to a certain ip (lets call it ipaddressx) via hostc. I added the iptables mangle rule to mark all traffic to ipaddressx at port...