[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 21 May 2013 22:20:22 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Boian Bonev <bbonev@...cct.com>
Cc: netdev <netdev@...r.kernel.org>
Subject: Re: RFC EOIP Tunnel
Rather than burdening the kernel maintainers with a proprietary
protocol that is non-standard. Why not just clean up the user space
implementation, and use tun like OpenVPN etc.
IMHO Mikrotik is violating GPL by having modules that claim to be GPL
and not releasing source. Plus modifying GRUB to do license
enforcement violates the intent of GPL as well.
On Tue, May 21, 2013 at 5:29 PM, Boian Bonev <bbonev@...cct.com> wrote:
> Hi,
>
>> Actually, I does get used in BSD land. I have seen several setups some time
>> ago where gif interfaces got added to a bridge interface, which behaves like
>> EtherIP then. Prior to FreeBSD 8 they reversed the bytes of the version field
>> so they still have to provide knobs for backwards compatibility.
>
> In FreeBSD the same thing is implemented as netgraph node...
>
>>> Before going in technical details and submitting patches I want to
>>> know opinions if this work is suitable for merging upstream or is
>>> better to be kept as a side kernel patch project.
>>
>> If the side kernel patch has matured and you are fine with it just propose it
>> to get merged.
>
> It is mature enough for the 3.2 series kernels (but obviously this is
> not ok for submitting). Since then tunnels have got refactored to have
> common code in a single place used by all tunnels and also GRE GSO
> support was added. I am not very confident if I can get the GSO part
> the right way and properly test it...
>
> Thanks for the pointers - will follow your advice and submit a patch.
>
>>> ps. https://github.com/bbonev/eoip contains 3.2.x patches + somehow
>>> working but quite crappy config tool
>>
>> Configuration should be done by iproute.
>
> This is my plan. The config tool is more like a proof of concept thing.
>
> With best regards,
> b.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists