search for: aaa_vpnhub1

...og level 3) (huge amount == at least 3 or 4 per edge direction in the network) After extending the debug log messages a bit I can see that 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 ->...

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 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...

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 it, but I committed a fix anyway that makes > sockaddr2str() handle AF_UNSPEC addresses. It might just...

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...

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 might just have moved the problem though...