search for: bindtointerface

Albi Rebmann wrote: > Hallo, > > sorry to say again, but BindToInterface = interface [experimental] still > does not work here (tinc 1.08). I use SuSE Linux 8.0, 2.4 Kernel. > If I add a missing device I get an error, but I add ppp2 (my external > device) and tinc still listens on 0.0.0.0 > I hope you have an idea how I can bind tinc to only one ip address...

...zdesign.com wrote: > Oops, I got it to work only after putting the WAN on port 656 so it > did not interfere with port 655 for the LAN. You should not need to have two tinc daemons just because you have a WAN and a LAN interface. By default (ie, if you don't specify BindToAddress and/or BindToInterface), tinc listens on all interfaces, and the kernel should normally take care of selecting which outgoing interface to use for tinc's packets. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachme...

...============================================== Central Node (10.0.0.1) configurations: ============================================================================== --------------------------------------- tinc.conf --------------------------------------- Name=central Mode=router AddressFamily=any BindToInterface=eth0 MaxTimeout=333 KeyExpire=888 PingInterval=88 PingTimeout=4 #Forwarding=kernel TunnelServer=yes --------------------------------------- hosts/central --------------------------------------- Compression=10 PMTUDiscovery=yes Subnet=10.0.0.0/28 Subnet=0.0.0.0/0#10 =============================...

Hello, I set up a tinc vpn network with tinc 1.0pre5 on Mandrake 8.1 Please take note of the following troubles i noticed 1) In the config files, the name of the variables are case sensitive 2) the BindToInterface seems to be faulty. I removed the line, now everything work, except the security aspect.. 3) I HAD to add a Subnet=<full address of the local tinc device> in the hosts file, or i get a message : cannot route packet to < address of the distant tinc device (set up in tinc-up with ifconfig)&g...

...it. 2) CLIENT_01, CLIENT_02 - nodes are located in the same LAN. 3) CLIENT_03 - remotely located node. === VPNGATE === tinc/vpn/hosts/vpngate tinc/vpn/hosts/client_01 tinc/vpn/hosts/client_02 tinc/vpn/hosts/client_03 ... tinc.conf: AddressFamily = ipv4 BindToAddress = x.x.x.x (public IP address) BindToInterface = eth0 Name = vpngate Device = /dev/net/tun PrivateKeyFile = /etc/tinc/vpn/rsa_key.priv Mode = switch === CLIENT_0X === tinc/vpn/hosts/vpngate tinc/vpn/hosts/client_0X ... tinc.conf: AddressFamily = ipv4 Name = client_0X ConnectTo = vpngate Interface = tinc.vpn PrivateKeyFile = C:\Program Files\...

...Oops, I got it to work only after putting the WAN on port 656 so it >> did not interfere with port 655 for the LAN. > > You should not need to have two tinc daemons just because you have a WAN > and a LAN interface. By default (ie, if you don't specify BindToAddress > and/or BindToInterface), tinc listens on all interfaces, and the > kernel should normally take care of selecting which outgoing interface > to use for tinc's packets. > > > > _______________________________________________ > tinc-devel mailing list > tinc-devel at tinc-vpn.org > http://w...

No parameters using DNS. - tinc.conf content Name = sito1 AddressFamily = ipv4 BindToAddress = <IPPUB>:665 BindToInterface = int Device=/dev/net/tun Interface = vpndrif Mode = router PingInterval = 60 PingTimeout = 5 ProcessPriority = normal - host/sito1 content Address = <IPPUB>:665 Subnet = <IPLOCAL>/<NETMASK> Port = 655 -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- Excuse me...

...uggestions to get more throughput, e.g. do you think it is worthwhile to try and compile the latest, pre-release version of tinc, or maybe apply some kernel tuning options when running inside a VM? Many thanks, J?rgen my configs: ========== tinc.conf ------------- Name = bob AddressFamily = ipv4 BindToInterface = eth1 DirectOnly = yes Mode = switch Broadcast = no Forwarding = off LocalDiscovery = yes Interface = tun0 ConnectTo = alice # I also tried a minimal config, with only ?Name?, ?AddressFamily? and ?Interface? - it did not make any difference hosts/alice --------------- Address = 10.128.x.y Subnet...

....x port 655) failed: Resource temporarily unavailable Dec 5 11:36:32 frank tinc.vpn[6620]: Closing connection with zappa (x.x.x.x port 655) Dec 5 11:36:32 kfrank tinc.vpn[6620]: Trying to re-establish outgoing connection in 120 seconds D zappa# cat /usr/local/etc/tinc/vpn/tinc.conf name = zappa BindToInterface = eth0 device = /dev/tun MaxTimeout = 60 privateKeyFile = /usr/local/etc/tinc/vpn/rsa_key.priv frank# cat /usr/local/etc/tinc/vpn/tinc.conf name = frank BindToAddress = 212.43.131.10 connectTo = zappa device = /dev/tun MaxTimeout = 60 privateKeyFile = /usr/local/etc/tinc/vpn/rsa_key.priv all host...

...Internet. We are experiencing very slow network speed using Tinc. Between 2 nodes, we have 150 Mbit/s network speed without Tinc (public IPv4 to public IPv4 using iperf), and only 3 Mbit/s using Tinc (private IPv4 to private IPv4). Here is the configuration of Tinc we use : AddressFamily = ipv4 BindToInterface = vmbr1 Broadcast = mst DecrementTTL = no DirectOnly = no Forwarding = internal GraphDumpFile = /tmp/tinc-graph LocalDiscovery = no Mode = switch MACExpire = 30 Name = host1 PrivateKeyFile = /etc/tinc/my_tinc_network/rsa_key.priv ProcessPriority = high And for each host : Address = XXX.XXX.XXX.XX...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gus & Tinc-VPN List: It looks like I need to run 2 instances of tincd on each server. 1 instance of tincd will responsible for running a VPN over the LAN on eth1. This means Class C addresses from 10.0.1.10 -> 10.0.1.250 Another instance of tincd will be responsible for running a VPN over the WAN on eth0. This means Class C addresses from

Hi, I've stumbled upon a problem which I can't solve easily with the available options in tinc - at least as far as I see. If enlightenment is all I need, I'll happily accept pointers ;) I try to establish a connection between two hosts. Each host has multiple addresses assigned to it's internet interface. A stripped down list would be: Host 1: 2001:780:0:1e::1

...pint[413140]: Increase in PMTU to sllm1 (192.168.0.200 port 655) detected, restarting PMTU discovery What do I have to look for in this file ? Host config contains only Address, Cipher, Digest and MACLength; but I think that 3 last are rewritten by sptps. Tinc config is : AddressFamily = ipv4 #BindToInterface = vmbr1 Broadcast = mst ConnectTo = host1 ConnectTo = host2 ConnectTo = host3 ConnectTo = host4 ConnectTo = host5 ConnectTo = host6 ConnectTo = sllm1 Forwarding = internal GraphDumpFile = /tmp/tinc-graph Mode = switch Name = sllm2 PrivateKeyFile = /etc/tinc/coppint/rsa_key.priv ProcessPriority = hi...

I know i'm new to the list but i'd like to propose something for tincd daemon. I'd like to mark all sockets established by a tincd process with a mark passed as an argument in the command line. What could be the purpose of this new option? The goal of this option is to be able to have several tincd process running at the same time using the same port but using different ip. In

...work only after putting the WAN on port 656 so it >>> did not interfere with port 655 for the LAN. >> >> You should not need to have two tinc daemons just because you have a WAN >> and a LAN interface. By default (ie, if you don't specify BindToAddress >> and/or BindToInterface), tinc listens on all interfaces, and the >> kernel should normally take care of selecting which outgoing interface >> to use for tinc's packets. >> >> >> >> _______________________________________________ >> tinc-devel mailing list >> tinc-devel...

First off, thanks to all who have made tinc possible and continue to work developing it. I hope perhaps in time I can become a useful part of this community. :) I'm having an interesting issue with tincctl and was hoping someone could shed some light on it. Everything seems to work correctly when I build for OSX; however on linux and windows builds, I always receive connection