Displaying 20 results from an estimated 400 matches similar to: "tinc 1.1 "Got ADD_EDGE ... which does not match existing entry""
2015 May 15
2
tinc 1.1 "Got ADD_EDGE ... which does not match existing entry"
On Fri, 15 May 2015, Guus Sliepen wrote:
> On Fri, May 15, 2015 at 10:26:46PM +0200, Sven-Haegar Koch wrote:
>
> > Another strange and difficult to understand thing - seems like all the
> > easy bugs in 1.1 are gone ;)
> [...]
> > Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for haegar_tokamak
> > -> igor which does not match existing entry (Local
2015 May 15
0
tinc 1.1 "Got ADD_EDGE ... which does not match existing entry"
On Fri, May 15, 2015 at 10:26:46PM +0200, Sven-Haegar Koch wrote:
> Another strange and difficult to understand thing - seems like all the
> easy bugs in 1.1 are gone ;)
[...]
> Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for haegar_tokamak
> -> igor which does not match existing entry (Local address 2.3.4.5
> != unknown)
>
> What I think may happen is that the
2015 May 16
1
tinc 1.1 "Got ADD_EDGE ... which does not match existing entry"
On Sat, 16 May 2015, Guus Sliepen wrote:
> On Sat, May 16, 2015 at 12:09:52AM +0200, Sven-Haegar Koch wrote:
>
> > This change is not so good:
> >
> > Connection with aaa_vpnhub1 (1.2.3.4 port 443) activated
> > Error while translating addresses: ai_family not supported
> >
> > (And then the tinc process exists)
>
> Hm, I couldn't reproduce
2015 May 16
0
tinc 1.1 "Got ADD_EDGE ... which does not match existing entry"
On Sat, May 16, 2015 at 12:09:52AM +0200, Sven-Haegar Koch wrote:
> This change is not so good:
>
> Connection with aaa_vpnhub1 (1.2.3.4 port 443) activated
> Error while translating addresses: ai_family not supported
>
> (And then the tinc process exists)
Hm, I couldn't reproduce it, but I committed a fix anyway that makes
sockaddr2str() handle AF_UNSPEC addresses. It
2018 Dec 11
3
subnet flooded with lots of ADD_EDGE request
Hello,
We're suffering from sporadic network blockage(read: unable to ping
other nodes) with 1.1-pre17. Before upgrading to the 1.1-pre release,
the same network blockage also manifested itself in a pure 1.0.33
network.
The log shows that there are a lot of "Got ADD_EDGE from nodeX
(192.168.0.1 port 655) which does not match existing entry" and it
turns out that the mismatches
2005 Dec 13
1
strange tinc error with many nodes
Hello,
we currently set up a large tinc network with 2 central Nodes (these nodes connecting to each other).
All satellites (ca 40) connect to these both machines. All containing two ConntectTo fields (for backup)
e.g. (satellite)
Name = nfp_hy
Device = /dev/tun
PrivateKeyFile = /etc/tinc/nfp_hy/rsa_key.priv
ConnectTo = nfp_f_vpn
ConnectTo = nfp_c_vpn
If the count of satellites reaches
2018 Dec 18
0
subnet flooded with lots of ADD_EDGE request
On Tue, Dec 11, 2018 at 02:36:18PM +0800, Amit Lianson wrote:
> We're suffering from sporadic network blockage(read: unable to ping
> other nodes) with 1.1-pre17. Before upgrading to the 1.1-pre release,
> the same network blockage also manifested itself in a pure 1.0.33
> network.
>
> The log shows that there are a lot of "Got ADD_EDGE from nodeX
>
2016 Nov 10
1
static configuration
Hello,
I am tying to create tinc vpn for the ~1000 nodes and was thinking why meta connections are
needed at all if I only need static configuration where every node knows addresses of other hosts
and due to the amount of traffic any indirect connections will not work, so DirectOnly=yes is a must
and then passing around routing information is not needed, right? Currently I have 10 nodes
2015 May 13
2
tinc 1.1 never seems to accept UDP packets from 1.0.24 hosts
Hallo,
I have a couple of tinc hosts in the same network, some using the latest
tinc 1.1 git and some using 1.0.24.
It seems like traffic between 1.1 and 1.0 nodes is always transfered
using TCP (and an intermediate node, if not directly connected), never
with UDP.
Viewed from host W (tinc 1.1):
(All after successfully pinging an IP behind the remote side to trigger
UDP path probing, and
2005 Apr 08
1
TrustedNodes option in TINC
Hi,
We want to deploy a tinc VPN, with more than 50 sites connected all
arround the world. But we cannot trust all our sites with the same
level, so the tinc solution (automatic full mesh) is "too automatic" for
us : *any* node can add a new node which will be connected directly to
others.
A solution could be TLS (signing public keys), but create a PKI is
another issue for us.
2014 Aug 06
1
State graph of UDP data-connections
Hi,
I'm using Tinc in a scenario where round-trip time matters.
I've multiple nodes behind firewalls (with and without NAT) and a single
public server node.
How do I can get the current state of UDP data-connections between my
firewall'd nodes?
According to the docs:
- 'dump connections' give me all TCP meta-connections of the current
node
- 'dump edges' give me
2010 Sep 17
1
friend of a friend type darknets
Hi!
here a little patch for darknet functionality, i hope it does what its
intended for sufficiently ... but it seems to work :).
what should it do?
imagine your friend-network. A trusts B and C. B trusts D and E, D trust
F, C trusts G. All trust relationships are mutal
A <---> C <---> G
^
\
\-----> B <---> D <---> F
^
\
\---> E
2008 Jan 25
3
Bug#462468: nut: megatec_usb ups not detected since 2.2.1 update anymore
Hi Sven,
2008/1/25, Sven Koch <haegar at sdinet.de>:
> Package: nut
> Version: 2.2.1-1
> Severity: normal
>
> I am using a Mustec PowerMust 1000 USB, connected with a USB cable to
> the PC.
>
> With nut 2.2.0-2.1 everything works without problems - but since the
> 2.2.1-1 update the "upsdrvctl start" from the init script just fails,
> executing the
2013 Jul 21
2
Possible improvements to LocalDiscovery
LocalDiscovery works by sending some of the MTU probe packets to the
broadcast address (255.255.255.255). If the destination node receives
one of these packets, it will update its UDP cache and reply, thus the
two nodes will start using their local addresses to communicate.
Now, I see two problems with this approach:
- In case the two nodes are behind the same NAT and can reach other
*but*
2009 May 27
2
New NUT user with HP R3000XR problem
Greetings,
I've just installed nut-2.4.1 on a Solaris 10 x86 machine to monitor a
HP R3000XR UPS.
SunOS babylon4 5.10 Generic_138889-08 i86pc i386 i86pc Solaris
First of all, I encountered a single problem during the build. After
configuring, drivers/Makefile ends up containing the following line:
LIBNETSNMP_LDFLAGS = -R../lib -L/usr/sfw/lib -lnetsnmp -lgen [...]
This is clearly
2017 Feb 27
2
multithreading, subnet weights, logging info
Multiple questions here, thinking one email is less annoying (sorry if
not). Running tinc 1.0.31
1. Could anyone give an explanation (or point to documentation) of the
differences between Connections, Nodes, and Edges in the USR1/2 logging,
and the various information in there?
2. Connections appears to match the list of ConnectTo hosts in the main
config file -- does this mean this node can
2011 May 17
1
rails render_to_string problem
Hi
I`m trying to test my controller with rspec and always get an error.
The error is in the render_to_string method call (without it test
works fine). So could u please help me with that?
users_controller.rb:
def update
@user.update_attributes!(params[:user])
redirect_to @user, :status => 202, :text =>
render_to_string(:partial => "users/show", :type =>
2017 Oct 10
1
UDP connections on tinc
Hello,
We are using tinc 1.0.24 with switch mode. Some questions regarding to the
UDP connections on tinc.
As far as I understand tinc is building meta connections with "ConnectTo",
and "ADD_EDGE" packet. With the help of EDGE info two nodes who don't have
direct meta connection are able to communicate through direct UDP
connection.
I understand we can dump the meta
2014 Sep 25
1
Tinc1.1pre10 on Windows 8.1?
Hello tincers,
I run a small tinc mesh using version 1.1pre10 on mostly linux (debian) hosts. In the past, I was able to successfully join my windows machine to the tinc network, when I was running an earlier version of tinc (throughout the mesh). However, with 1.1pre10, I have had no success. Is this a known error, a misconfiguration on my part, or some other issue? I currently have no tinc-up
2017 Jan 13
2
tinc behind CISCO ASA 5506
Hi there
I have the following setup
Home - Main Tinc server with public IP running on PfSense
work - tinc client running behind a CISCO ASA firewall with public IP
running on Windows 10
offsite - tinc client running on tomato router behind a double NAT
Home & offsite connect & i can see all PCs & devices & connect to them
easily, on either side
work to Home or offsite connects