-
Notifications
You must be signed in to change notification settings - Fork 33
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
upgrading a remote node will not make it connecting to the BBB again (tunneldigger) #690
Comments
This issue has been discussed at the weekly cbase meeting and various proposals have been discussed. Additionally, if the node uses the openvpn variety (luckily there are only about 12 users of this old service left) to connect to the bbb-vpn and notunnel or tunneldigger image is used, the same problem arises. |
In fact that's something which that closely relates to the flavors of images prebuilt. Probably the attendedsysupgrades, mentioned in #22 (comment), are a smart solution. |
This addresses issue #690 where a node which has been set up to use the bbbdigger package cannot connect to the bbb-vpn server after a firmware upgrade.
This has been implemented in #701 but is also dependant on freifunk-berlin/firmware-packages#189 |
Bug report
An upgraded node is missing the tunneldigger package
When upgrading a remote node via BBB-VPN was working painless with pre-Hedy releases. As the required OpenVPN packages have been included in all images a remote updated node was reconnecting to BBB-VPN by itself.
Since we switched to modular uplinks and an optional alternative BBB-VPN via tunneldigger the old situation can only be archived when using a matching "tunneled uplink" package. When using a no-tunneled image the BBB-VPN link can only be restored after a site-visit an installing tunneldigger / OpenVPN manually.
It would be great to have a working BBB-VPN connection after an update.
The text was updated successfully, but these errors were encountered: