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

ffwizard: individual texts for uplinks #625

Closed
SvenRoederer opened this issue Nov 19, 2018 · 6 comments
Closed

ffwizard: individual texts for uplinks #625

SvenRoederer opened this issue Nov 19, 2018 · 6 comments

Comments

@SvenRoederer
Copy link
Contributor

the wizard has some hardcoded texts which points to a specific uplink (eg VPN03 - freifunk-berlin/firmware-packages@eb9d6c4#diff-0019160469d0108641e7020d912d2336L45).
We should add a way to customize these text-blocks by the installed uplink.

I see 2 possible ways:

  • the uplink package provides some files which directly are read by the wizard
  • the uplink-package sets some uci-options during it's installation, which are evaluated by the wizard
@pmelange
Copy link
Contributor

I think it would be enough to have a proper description in the makefile for the different uplink packages. Then simply by updating the package lists, the description will be available. There will be no need to download the packages themself before they are needed.

Here is what we currently have (Hedy 1.0.X):

~# opkg list "freifunk-berlin-uplink*"
freifunk-berlin-uplink-notunnel-files - 0.0.5-1 - Freifunk Berlin files to setup a uplink without any
 tunnel.
 upstream traffic will be directly routed via your network
freifunk-berlin-uplink-tunnelberlin-files - 0.0.2-1 - Freifunk Berlin files to setup a tunnel to route all
 upstream traffic to these community-internet-gateways
freifunk-berlin-uplink-vpn03-files - 0.0.4-1 - Freifunk Berlin VPN03 files

We could change these text segments to be useful for the wizard.

This issue is related to #601

@SvenRoederer
Copy link
Contributor Author

This is not about a descriptive name for the uplink-type images. This issue is about having individual texts in the wizard oin place of the hardcoded stuff we have currently.
Why is the no-tunnel uplink having a text referencing "you need to get a certificate at ...."

@pmelange
Copy link
Contributor

@pmelange
Copy link
Contributor

Sorry, that is the diff you provided above (different commit id though). All references are anyhow removed. I still think it should be enough to have the needed info (and links) in the package description.

@SvenRoederer
Copy link
Contributor Author

There are still refeerences to "Zertifikate" which don not make sense for "no-tunnel" uplink or "tunneldigger".

@SvenRoederer
Copy link
Contributor Author

got it ... missed that the uplink.auth=x509 also disables the messagebox I had seen.

SvenRoederer added a commit to SvenRoederer/freifunk-berlin-firmware that referenced this issue Nov 10, 2020
22a5a22 quagga: update GCC10 patch
4f2528a opennds: Release 7.0.1
52be301 Merge pull request freifunk-berlin#625 from bluewavenet/master
068a061 Merge pull request freifunk-berlin#619 from neheb/qg
SvenRoederer added a commit to SvenRoederer/freifunk-berlin-firmware that referenced this issue Dec 1, 2020
22a5a22 quagga: update GCC10 patch
3e6059f quagga: fix dependency to libcares
4f2528a opennds: Release 7.0.1
52be301 Merge pull request freifunk-berlin#625 from bluewavenet/master
068a061 Merge pull request freifunk-berlin#619 from neheb/qg
330a0cc Merge pull request freifunk-berlin#618 from TDT-AG/pr20201009/quagga-libcares
SvenRoederer added a commit to SvenRoederer/freifunk-berlin-firmware that referenced this issue Dec 1, 2020
22a5a22 quagga: update GCC10 patch
3e6059f quagga: fix dependency to libcares
4f2528a opennds: Release 7.0.1
52be301 Merge pull request freifunk-berlin#625 from bluewavenet/master
068a061 Merge pull request freifunk-berlin#619 from neheb/qg
330a0cc Merge pull request freifunk-berlin#618 from TDT-AG/pr20201009/quagga-libcares
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

2 participants