-
Notifications
You must be signed in to change notification settings - Fork 45
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
Comments
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. |
@ yanic did not use the It use the mac address of |
@freifunk-en Is this still an issue with the fix in yanic? |
@jplitza Sorry for the late reply, i didnt update yanic yet but i will do today and report back |
So, this issue basically is dead, as there are no users anymore, that can even confirm it? |
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. |
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
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
The text was updated successfully, but these errors were encountered: