bircoph wrote:
What I can't understand is why l2tpconfig and config parser from openl2tpd are using different code to read effectively the same config files.
l2tpconfig is designed for interactive use. It supports tab completion for keywords, so has its own parser. It builds up RPC commands from each command line input provided by the user. It used to be the only way to configure openl2tpd.
Some users wanted a way to configure openl2tpd without RPC. So the config file parser was added to openl2tpd for this, and we chose the same syntax as l2tpconfig. As a result, there are two methods for configuring openl2tpd.