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

Do not override "interface" in the configuration file #236

Open
1 of 4 tasks
lonble opened this issue Mar 17, 2022 · 1 comment
Open
1 of 4 tasks

Do not override "interface" in the configuration file #236

lonble opened this issue Mar 17, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@lonble
Copy link

lonble commented Mar 17, 2022

I'm opening this issue because:

  • I have found a bug
  • I want to request a feature
  • I have a question
  • Other

I found a strange thing. When running qrcp for the first time, a config.json file is created, which holds the default software configuration. Everything looks normal except interface. interface does not hold the default like other options, but the interface I used the last time I ran qrcp. Every time I switch between ethernet and wifi I get Error: unable to find interface.
I tried setting interface to an empty string and the strange thing happened again. Whatever options are used on the command line will not overwrite the contents of the config.json file, except interface. I can only manually modify config.json every time I switch network environments.
I don't understand why qrcp store the value of interface by default, why overwrite the config file with the interface used the last time I ran qrcp. I think it should rescan available interfaces every time qrcp is run.

@claudiodangelis
Copy link
Owner

Hey, sorry for the huge delay! Yep, this seems to be a bug. However, I want to change the configuration file format from JSON to YAML in the next release, I will work on this too.

Thanks for reporting!

@claudiodangelis claudiodangelis added the bug Something isn't working label Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants