On 19.07.2014 08:48, Baptiste Jonglez wrote:
Hi,
Two packages provide the proto l2tp netifd protocol: xl2tpd [1] in the
new packages feed, and l2tpv3tun [2] in oldpackages.
The config are totally different, the problem is really a name clash.
It seems they are doing things differently
Steven Barth wrote:
I renamed the xl2tpd netifd protocol to l2tpv2 and kept the l2tpv3 as
l2tp as documented in the wiki.
Thanks :)
On Mon, Jul 21, 2014 at 08:47:58AM +0200, Dirk Neukirchen wrote:
The config are totally different, the problem is really a name clash.
It seems they are
Hi,
Two packages provide the proto l2tp netifd protocol: xl2tpd [1] in the
new packages feed, and l2tpv3tun [2] in oldpackages.
The config are totally different, the problem is really a name clash.
What is the recommended way to deal with name clashes in netifd protocols,
without breaking
Hi Baptiste,
thanks for the report.
I renamed the xl2tpd netifd protocol to l2tpv2 and kept the l2tpv3 as
l2tp as documented in the wiki.
Cheers,
Steven
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
