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

Configuration concept #1

Open
2 of 5 tasks
dl1com opened this issue Jun 4, 2020 · 2 comments · Fixed by #51 · May be fixed by #59
Open
2 of 5 tasks

Configuration concept #1

dl1com opened this issue Jun 4, 2020 · 2 comments · Fixed by #51 · May be fixed by #59
Labels
moved from gitlab Moved from internal Gitlab
Milestone

Comments

@dl1com
Copy link
Contributor

dl1com commented Jun 4, 2020

Basically, we have two different categories of configuration parameters: Parameters directly related to the HNAP waveform and parameters which are related to the Pluto Linux system.
The basic system and network settings are originally handled within uboot's fw environment and presentet to the user by the config.txt file which is also accessible by the USB mass storage.
We'll not cancel this concept to avoid confusion. Therefore, our current decision is to provide the HNAP relevant settings in the hnap_config.txt and add our additional system related settings (network configuration) in the fw environment/config.txt as well.

Examples for HNAP Waveform Configuration parameters:

  • Loglevel
  • Frequency
  • Tx gain
  • Desired MCS
  • PTT Offset
    ...

Examples for Pluto System Configuration parameters:

  • Hostname
  • Callsign
  • Network settings (TAP IP, Subnet)
  • DHCP Server configuration
  • ...

To Dos

  • the HNAP config file will be renamed to hnap_config.txt to avoid confusion with the Pluto config.txt file
  • the HNAP config file will be stored to the jffs2 partition to enable persistence
  • we'll add the Tx and Rx gain setting to the HNAP config file
  • basestation autostart will read the config file instead of having hard-coded parameters (related to Binaries should load the default config file without providing the -c parameter #54)
  • define relevant parameters to set up various networking scenarios
@dl1com dl1com added the moved from gitlab Moved from internal Gitlab label Jun 4, 2020
@dl1com dl1com changed the title Retrieve configuration from environment variables Configuration concept Oct 16, 2020
@dl1com
Copy link
Contributor Author

dl1com commented Oct 23, 2020

I just came across another way of storing persistent storage: Since v0.32, the Pluto offers the JFFS2 partition (where it already stores the passwd and ssh keys), we could probably also use it to just put our config.txt there

@dl1com
Copy link
Contributor Author

dl1com commented Nov 5, 2020

Current state of this issue:

  • the HNAP config file will be renamed to hnap_config.txt to avoid confusion with the Pluto config.txt file
  • the HNAP config file will be stored to the jffs2 partition to enable persistence
  • we'll add the Tx and Rx gain setting to the HNAP config file
  • basestation autostart will read the config file instead of having hard-coded parameters

@dl1com dl1com linked a pull request Nov 16, 2020 that will close this issue
@dl1com dl1com added this to the 2.0.0 milestone Nov 20, 2020
@dl1com dl1com linked a pull request Nov 23, 2020 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
moved from gitlab Moved from internal Gitlab
Projects
None yet
1 participant