From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Books for protocol development
Date: Tue, 25 Sep 2012 17:50:45 +0200 [thread overview]
Message-ID: <20120925155045.GA2270@grml> (raw)
In-Reply-To: <CA+CftcHdZZ_270uwxGYYzURvvVfjDURurW-PR0hoL=i0+rzUrg@mail.gmail.com>
Hi!
On 09:12 Tue 25 Sep , V.Ravikumar wrote:
> On Mon, Sep 24, 2012 at 9:03 PM,
> <michi1@michaelblizek.twilightparadox.com>wrote:
>
> > Hi!
> >
> > On 17:02 Mon 24 Sep , V.Ravikumar wrote:
> > > Hello all ,
> > >
> > > Could some body please suggest any books/links for Linux networking
> > > protocol development.
> > > Protocol development at L2/L3 layers.
> >
> > There is a book called "The Linux Networking Architecture: Design and
> > Implementation of Network Protocols in the Linux Kernel".
> >
> > Is there anything in particular you are looking for?
> >
> I need information specifically about VPN technology like MPLS and other
> related stuff.
> About their design & implementation at layer L2 level.
MPLS is not really a VPN, but rather a layer 2.5 encapsulation supposed to
combine the speed of switching with the flexibility of routing. It should be
possible to use MPLS to build VPNs, but I guess few people did this before.
Also, MPLS is probably not in widespread use by linux to begin with.
There are some "other" VPN technologies as well:
- ipsec: This is a standard which is implemented by most "hardware" firewalls
and it is quite popular in corporate networks. The linux implementation does
not do anything at layer 2 at all. Packet are captured before they are
passed to the layer 2 and encapsulated. They pass iptables twice. In
practice ipsec can be pretty weird/confusing.
- openvpn: cross platform free+open source project; It connects to the other
side with either udp or tcp. It creates a virtual network device. Everything
you send to this device will be sent to the other side as if the machines
were directly connected. On linux openvpn runs completely in userspace and
creates the virtual device via the tun/tap interface.
If you are interested in how to create such a virtual device in the kernel,
you can want to take a look at the ethos project. Its project site seems
down/gone, but you can get a copy here:
http://michaelblizek.twilightparadox.com/ethos.tar.gz
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2012-09-25 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:32 Books for protocol development V.Ravikumar
2012-09-24 15:33 ` michi1 at michaelblizek.twilightparadox.com
2012-09-25 3:42 ` V.Ravikumar
2012-09-25 15:50 ` michi1 at michaelblizek.twilightparadox.com [this message]
2012-09-24 15:39 ` Anuz Pratap Singh Tomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120925155045.GA2270@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).