Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VPN recognition seems broken/flappin #25

Open
ghost opened this issue Nov 19, 2017 · 6 comments
Open

VPN recognition seems broken/flappin #25

ghost opened this issue Nov 19, 2017 · 6 comments

Comments

@ghost
Copy link

ghost commented Nov 19, 2017

Last month we did update all our communitys to use the lastest mesh-announce,
before we used alfred-announce from somewhere in 2015.

With the old alfred-announce we never had problems with announce/meshviewer to recognize vpn links.

Since we did install the new version with respondd it started flappin or not even show vpn links

image

We´re using:
Batman-adv 2013.4 (from git)
Tunneldigger
Gluon 2016.x / 2017.x
mesh-announce
ffrgb-meshviewer
yanic

batman interface > br0
client tunnel > bat0
site2site tunnel > bat0

I´ve noticed that the entire structure inside nodeinfo.d has changed, but what could cause this problem?

Edit: Maplink https://map.ff-en.de/enkreis/#/de/graph

Regards
Matthias

@jplitza
Copy link
Member

jplitza commented Jan 3, 2018

Interesting. We have an identical setup except we're using fastd instead of Tunneldigger and never experienced these problems.

Whether links are seen as VPN links AFAIK entirely depends on whether one of the end nodes has the nodeinfo.vpn attribute set. So when the data from that one VPN gateway cannot be received, all its links are recognized as regular links, but then again, it shouldn't have a name either.

So basically, I suspect this is caused by the technology switch "Alfred → respondd" and not by mesh-announce and could only be mitigated by yanic. But maybe @genofire can say more about the problem.

@genofire
Copy link
Contributor

genofire commented Jan 3, 2018

@ yanic did not use the nodeinfo.vpn attribute anymore for vpn detection, because a other community has an gateway with a real interface to there mesh-network.

It use the mac address of nodeinfo.mesh.{INTERFACE}.interfaces.tunnel on both sides.
(Maybe we have an bug, if the both nodes has there mac on different types - wifi or other)
@freifunk-en could you make a link to a link like this https://map.ff-en.de/enkreis/#/de/graph/0023abdead08-f4f26d49de86? Could i send respondd package from outside into your network?

@jplitza
Copy link
Member

jplitza commented Apr 28, 2018

@freifunk-en Is this still an issue with the fix in yanic?

@ghost
Copy link
Author

ghost commented May 18, 2018

@jplitza Sorry for the late reply, i didnt update yanic yet but i will do today and report back

@AiyionPrime
Copy link
Contributor

So, this issue basically is dead, as there are no users anymore, that can even confirm it?

@TobleMiner
Copy link
Member

Does this issue still exist? There have been major changes in mesh-announce and thus additional confirmation on this issue is required. This issue will be closed in a month if there is no further activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants