Navigation Menu

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

Add configuration wizard #139

Open
mrash opened this issue Nov 17, 2014 · 5 comments
Open

Add configuration wizard #139

mrash opened this issue Nov 17, 2014 · 5 comments
Assignees
Milestone

Comments

@mrash
Copy link
Owner

mrash commented Nov 17, 2014

It would probably be helpful for users to have a basic configuration wizard for both the client and server. For example, this could drive the client --save-rc-stanza functionality, but without requiring the user to understand all of the command line args to set up the .fwknoprc file.

@mrash mrash added this to the fwknop-2.8.0 milestone Sep 19, 2015
@mrash mrash self-assigned this Sep 19, 2015
@jp-bennett
Copy link
Collaborator

@mrash I could add a fwknopd wizard function to fwknop-gui. It would be similar to the openwrt interface. After running it, perhaps it would display the completed access.conf and fwknopd.conf so an end user could copy and paste the config as needed.

A command line version would also be helpful, I think.

@fjoncourt
Copy link
Contributor

I was thinking about a fwknop server user interface.

So far, I have set up a first a application (proof of concept) around two components:
  * a back-end server connected to a database
  * a front-end user interface that displays data from the back-end server as a web site

Technologies:
* back-end server runs with Apache / Tomcat / Java / PostgreSQL
* front end user interface runs with html / css / ...

What would be the use cases? I mean, what capabilities people would expect the administration user interface to provide?

For such an admin interface, I'd say it would be great to have the following:

  • access.conf stanza generation and validation
  • ability to create encryption and authentication keys
  • process status of existing fwknopd process
  • display of syslog messages from any running fwknopd instance? This could be extended to graph who is sending SPA packets and what services they are accessing over time for example.

@jp-bennett
Copy link
Collaborator

Related is #175 . Adding a database back end would make this much simpler. Also, I'd like to avoid Java for the official solution. My $.02

@fjoncourt
Copy link
Contributor

Then, what back-end technology would you choose/prefer/recommend?

2016-07-26 20:54 GMT+02:00 Jonathan Bennett notifications@github.com:

Related is #175 #175 . Adding a
database back end would make this much simpler. Also, I'd like to avoid
Java for the official solution. My $.02


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#139 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADFca2JXDGgM_0PBx-p5iLlr4kophKH4ks5qZlfmgaJpZM4C8f0v
.

@fjoncourt
Copy link
Contributor

Database management with Java is quite easy with hibernate/c3p0

  • No SQL query to write.
  • Session management is done with one file
  • Table mapping is done through annotations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants