[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD53P8CY9SFvsrhiZqpxT=P5PtjbqL4LG1tf3O8jpU0yrychUw@mail.gmail.com>
Date: Sun, 19 May 2013 18:31:40 +0300
From: Boian Bonev <bbonev@...cct.com>
To: netdev@...r.kernel.org
Subject: RFC EOIP Tunnel
Hi,
EOIP is a proprietary ethernet over IP tunneling protocol introduced
by MikroTik's commercial product RouterOS. It uses GRE as protocol id
but with non-standard header.
Unlike EtherIP (RFC 3378) that is documented but not used, EOIP is not
documented but used for transparent Layer2 over wireless links and in
providing Layer2 services through multiple management domain networks
where pure L2 is as hard as near to impossible.
Long story short: my primary motivation behind doing this work was to
reduce the number of points of failure in a Linux+RouterOS and many
RouterOS endpoints setup. Old RouterOS endpoints do not support any
standard ethernet tunneling (upgrading is not an option) while Linux
does not support the EOIP protocol. On the other hand RouterOS cannot
be as flexible as Linux can be for routing and magic.
Judging from the existence of at least two separate opensource
projects doing this tunneling in userspace
(https://github.com/katuma/eoip and
https://code.google.com/p/linux-eoip/) I believe that this will be
useful for people using Linux in networked setups.
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.
With best regards,
b.
ps. https://github.com/bbonev/eoip contains 3.2.x patches + somehow
working but quite crappy config tool
--
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