Hello Jonathan,
2016-06-04 23:34 GMT+02:00 Jonathan Bennett <jbscienc...@gmail.com>:
> Franck, this looks really good. Looks like the recently used list has
> entries from your testing/use. Not a huge problem, just an fyi.
>
Thanks. I will fix this. A clean config.properties file is provided in the
target directory along with a fresh build and all the dependencies.
> It looks like you are calling the fwknop binary, rather than working
> directly with libfko, is that correct?
Yes, you are right.
> It's interesting to see the different approaches to solving some of the
> challenges to building an fwknop gui project.
>
In fact, relying on fwknop client binary is due to the following points:
* I think fwknop core team has done a great job and spent a lot of time on
the fwknop client binary in C. I did not want to create a new client and
struggle to add the same features that are already available.
* I wanted to provide a user interface that can be used during fwknop
development. Thus, the user can use the default fwknop client install on
his system or select the latest release he has rebuilt for test purposes.
* New features added to fwknop client and available through fwknoprc file
will be supported, for most of them, by adding maybe 6 lines of code to the
UI.
* No libfko wrapper needed
> Great work on this!
>
Thanks.
Regards,
--
Franck
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Fwknop-discuss mailing list
Fwknop-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fwknop-discuss
