Displaying 3 results from an estimated 3 matches for "haegar_tokamak".
2015 May 15
2
tinc 1.1 "Got ADD_EDGE ... which does not match existing entry"
...hat it is always
about the local_address field - essentially switching from an IP to
unknown back and forth.
Here unrelated node "vlad" connected to aaa_vpnhub1 and to igor, on
waehring I receive for the link tokamak<->igor:
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)
Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for haegar_tokamak
-> igor which does not match existing entry (Local address unknown !=
2.3.4.5)
Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for igor -&g...
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 1.1 nodes pass on the local_address,
> but the 1.0 nodes (as they don't know that field) do not - resulting in
> "unknown" in an ADD_EDG...
2015 May 15
2
tinc 1.1 "Got ADD_EDGE ... which does not match existing entry"
...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 address 2.3.4.5
> > != unknown)
> >
> > What I think may happen is that the 1.1 nodes pass on the local_address,
> > but the 1.0 nodes (as they don't know that field) do not - resulting in
> > &qu...