search for: bindtoaddress

...appily 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 2001:780:0:1e::60 Host 2: 2001:780:106::1 2001:780:106::f1 With the `BindToAddress' I have bound the daemon(s) to the addresses 2001:780:0:1e::1 and 2001:780:106::1. `netstat(8)' confirms this: tcp6 0 0 2001:780:0:1e::1:655 :::* LISTEN 5707/tincd udp6 0 0 2001:780:0:1e::1:655 :::* 5707/tincd The problem is that `BindToAddress' is only used for *...

Hello, First of all thank you very much for Tinc. I have been using 1.0.24 under Debian & Alpine Linux 32 bit using 'BindToAddress' in tinc.conf without any issues to bind to an IPv6 ULA Address. With 1.1pre10 'BindToAddress' in tinc.conf on the client machines fails with: ============================================================================== tincd 1.1pre10 (Jun 7 2014 21:38:38) starting, debug level 5...

...1.45, both TCP and UDP Port 656 forwarded to 192.168.1.51, both TCP and UDP Machine #1. ========== Local IP address on LAN = 192.168.1.45 Windows Firewall allows all incoming TCP and UDP traffic for the Tinc.TincVPN service. Tinc.conf: Name = Adam ConnectTo = Erika Interface = TincVPN BindToAddress = 192.168.1.45 655 Hosts/Adam: Address = XYZ.ddns.org [WAN IP address, of router] Port = 655 Subnet = 192.168.1.45 Hosts/Erika: As below Machine #2. ========== Local IP address on LAN = 192.168.1.51 Windows Firewall allows all incoming TCP and UDP traffic for the Tinc.TincVPN servi...

...d TCP traffic on all ports and IP addresses. Any idea on how can I debug this thing? Seems so close, but so far away. Appreciate all thoughts. Cheers, Adam From: Sven-Haegar Koch Sent: Tuesday, July 14, 2015 5:14 AM To: tinc at tinc-vpn.org Subject: Re: Please help debug Windows setup BindToAddress = 192.168.1.45 655 Subnet = 192.168.1.45 You should use different IP ranges for inside the VPN and outside of it - otherwise your OS does not now how to reach the destination IP correctly. So for example change the Subnet statements to 192.168.2.x Greetings Haegar On Mon, 13 Jul 2015, Donald P...

Is it possible to use different port numbers for UDP and TCP? I'd like to open the TCP connection to one port on the remote server and stream the UDP packets to a different port. I've tried specifying both as BindToAddress and Address lines but it always just uses TCP. On 2 May 2017 17:36, "Guus Sliepen" <guus at tinc-vpn.org> wrote: On Tue, May 02, 2017 at 09:53:15PM +0800, Bright Zhao wrote: > When tinc daemon get up on A(together with some manual scripts for destination to 8.8.8.8), the route...

...I am trying to set up a second VPN between two servers: gtdb and db2. Both servers are already part of separate VPNs: 10.1.0.0/24 and 10.0.0.0/24 These are my files: On server 1: db2 /etc/tinc/nets.boot # gainplus (this works fine, autostarts, etc) vpn1 /etc/tinc/vpn1/tinc.conf Name = db2 BindToAddress = 10.130.17.192 AddressFamily = ipv4 Port = 656 ConnectTo = gtdb Interface = tun0 /etc/tinc/vpn1/tinc-up #!/bin/sh # tinc-up ip addr add 10.3.0.50/24 dev $INTERFACE ip link set dev $INTERFACE up /etc/tinc/vpn1/hosts/gtdb Subnet = 10.3.0.51/32 Port = 656 -----BEGIN RSA PUBLIC KEY----- /etc/tinc/...

...at 05:40:40PM +0100, Peter Whisker wrote: > > > Is it possible to use different port numbers for UDP and TCP? I'd like to > > open the TCP connection to one port on the remote server and stream the > UDP > > packets to a different port. I've tried specifying both as BindToAddress > > and Address lines but it always just uses TCP. > > It's not directly supported by tinc, but maybe you can trick it to. Here > are some pointers: > > You can have multiple BindToAddress lines. For outgoing UDP packets, > tinc will *initially* use the first matching on...

Hi, I see there’re two configuration in tinc: In main configuration: BindToAddress = <address> [<port>] In host configuration: Port = <port> So, let’s say on svr1 /etc/tinc/test/tinc.conf: BindToAddress = ip_addr p1 BindToAddress = ip_addr p2 /etc/tinc/test/hosts/svr1: Port = p1 On the client side c1 /etc/tinc/test/tinc.conf: ConnectTo = svr1 /etc/tinc/test...

...rface [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. Use BindToAddress. Ivo -- Software isn't released, it's allowed to escape. Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/

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----- [h182:] Subnet = 172.16.1.2/32 -----BEGIN RSA PUBLIC KEY----- *** -----END RSA PUBLIC KEY----- [h183:] Subnet = 172.16.1.3/32 -----BEGIN RSA PUBLIC KEY----- *** -----END RSA PUBLIC KEY----- *tinc.conf files:* [tinc.conf h181:] Name = h181 Device = /dev/net/tun BindToAddress = 0.0.0.0 AddressFamily = ipv4 [tinc.conf h182:] Name = h182 Device = /dev/net/tun ConnectTo = h181 BindToAddress = 0.0.0.0 AddressFamily = ipv4 [tinc.conf h183:] Name = h183 Device = /dev/net/tun ConnectTo = h181 BindToAddress = 0.0.0.0 AddressFamily = ipv4 *tinc-up Files:* [tinc-up h181:] #!...

...:08AM -0500, md at rpzdesign.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 -----------...

...ddresses. Any idea on how can I debug this thing? Seems so close, but so far away. Appreciate all thoughts. Cheers, Adam From: Sven-Haegar Koch Sent: Tuesday, July 14, 2015 5:14 AM To: tinc at tinc-vpn.org<mailto:tinc at tinc-vpn.org> Subject: Re: Please help debug Windows setup BindToAddress = 192.168.1.45 655 Subnet = 192.168.1.45 You should use different IP ranges for inside the VPN and outside of it - otherwise your OS does not now how to reach the destination IP correctly. So for example change the Subnet statements to 192.168.2.x Greetings Haegar On Mon, 13 Jul 2015, Donald P...

...solution, while the central node does not. Any points as to why the central tinc is not doing / able to do the ARP request? tinc.conf on the central node: Device = /dev/tap1 Name = centralnode Mode = switch DirectOnly = yes TunnelServer = yes PingInterval = 60 PingTimeout = 15 ReplayWindow = 0 BindToAddress = 192.168.50.82 BindToAddress = 192.168.50.84 BindToAddress = 192.168.50.83 tap1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=80000<LINKSTATE> ether 42:00:00:00:00:00 inet 192.168.51.1 netmask 0xffffff00 broadcast 192.168.51.255 Opened by PID 51917...

...ious compiler hardening flags by default. * Added support for a "conf.d" configuration directory. * Fix tinc-gui on Windows, also allowing it to connect to a 32-bits tincd when tinc-gui is run in a 64-bits Python environment. * Added a "ListenAddress" option, which like BindToAddress adds more listening address/ports, but doesn't bind to them for outgoing sockets. * Make invitations work better when the "invite" and "join" commands are not run interactively. * When creating meta-connections to a node for which no Address statement is specifi...

...ious compiler hardening flags by default. * Added support for a "conf.d" configuration directory. * Fix tinc-gui on Windows, also allowing it to connect to a 32-bits tincd when tinc-gui is run in a 64-bits Python environment. * Added a "ListenAddress" option, which like BindToAddress adds more listening address/ports, but doesn't bind to them for outgoing sockets. * Make invitations work better when the "invite" and "join" commands are not run interactively. * When creating meta-connections to a node for which no Address statement is specifi...

...ne #1. > > ========== > > Local IP address on LAN = 192.168.1.45 > > Windows Firewall allows all incoming TCP and UDP traffic for the > Tinc.TincVPN service. > > > > Tinc.conf: > > Name = Adam > > ConnectTo = Erika > > Interface = TincVPN > > BindToAddress = 192.168.1.45 655 > > > > Hosts/Adam: > > Address = XYZ.ddns.org [WAN IP address, of router] > > Port = 655 > > Subnet = 192.168.1.45 > > > > Hosts/Erika: > > As below > > > > Machine #2. > > ========== > > Local IP address o...

...ERFACE -net fd16:dcc0:f4cc::2:0:0/96 fd16:dcc0:f4cc::1:0:1 All those route commands are unnecessary. The ifconfig command already ensures there is a route for fd16:dcc0:f4cc::/80 to tinc's interface. > This is tinc.conf on machine A: > > Name = A > ConnectTo = B > BindToAddress = <public-ipv4> > BindToAddress = <public-ipv6> > Device = /dev/tap0 Hm, what if you use Device = /dev/tun0 instead? If this still doesn't work, then try to find out what happens with the packets you are sending. Run tinc in the foreground (use the options -d5 -D), a...

On Tue, May 02, 2017 at 05:40:40PM +0100, Peter Whisker wrote: > Is it possible to use different port numbers for UDP and TCP? I'd like to > open the TCP connection to one port on the remote server and stream the UDP > packets to a different port. I've tried specifying both as BindToAddress > and Address lines but it always just uses TCP. It's not directly supported by tinc, but maybe you can trick it to. Here are some pointers: You can have multiple BindToAddress lines. For outgoing UDP packets, tinc will *initially* use the first matching one for a given address family (IPv...

With pleasure we announce the release of version 1.0.17. Here is a summary of the changes: * The DeviceType option can now be used to select dummy, raw socket, UML and VDE devices without needing to recompile tinc. * Allow multiple BindToAddress statements. * Decrement TTL value of IPv4 and IPv6 packets. * Add LocalDiscovery option allowing tinc to detect peers that are behind the same NAT. * Accept Subnets passed with the -o option when StrictSubnets = yes. * Disabling old RSA keys when generating new ones now also works proper...