All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Jernej Kos <kostko@unimatrix-one.org>
Subject: Re: [B.A.T.M.A.N.] Migration to Batman
Date: Fri, 13 Apr 2012 09:43:23 +0200	[thread overview]
Message-ID: <20120413074323.GI7664@lunn.ch> (raw)
In-Reply-To: <CAKLmikN=yGHL8QZomD=GsaKYcZchd=r7kvsjsyxMCx2CYNjbzw@mail.gmail.com>

On Fri, Apr 13, 2012 at 09:29:27AM +0200, Mitar wrote:
> Hi!
> 
> On Fri, Apr 13, 2012 at 8:22 AM, Antonio Quartulli <ordex@autistici.org> wrote:
> > A little remark here. You MUST use interfaces that support ethernet frames
> > transmission. Therefore (IIRC) you can use tap interfaces but not tun ones.
> 
> L2TP tunnel is creates a L2 tun interface, no?

First, of, lets make sure we are all using tun/tap correctly. I know i
keep having the check which is which.

http://en.wikipedia.org/wiki/TUN/TAP

	TAP (as in network tap) simulates a link layer device and it
	operates with layer 2 packets such as Ethernet frames. TUN (as
	in network TUNnel) simulates a network layer device and it
	operates with layer 3 packets such as IP packets. TAP is used
	to create a network bridge, while TUN is used with routing.

So a tap interface can be added to BATMAN and become part of the L2
mesh.

tun cannot be added to batman. You need to perform L3 routing over the
interface.

Which implementation are you using of L2TP?

      Andrew

  reply	other threads:[~2012-04-13  7:43 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 10:26 [B.A.T.M.A.N.] Migration to Batman Mitar
2012-04-12 10:36 ` Gioacchino Mazzurco
2012-04-12 12:00   ` Antonio Quartulli
2012-04-12 15:13     ` Mitar
2012-04-12 15:36       ` Andrew Lunn
2012-04-12 17:12         ` Mitar
2012-04-12 18:12           ` Andrew Lunn
2012-04-12 19:49             ` 3zl Trizonelabs
     [not found]       ` <CAOaDhSRTgejL5tzAnAx6wBso1sjWn_7bVuT6P1_C1qcVu25McQ@mail.gmail.com>
2012-04-12 15:37         ` Jernej Kos
2012-04-12 17:19           ` Mitar
2012-04-12 21:08           ` Mitar
2012-04-12 21:15             ` Gioacchino Mazzurco
2012-04-13  5:59             ` Andrew Lunn
2012-04-13  7:58               ` Mitar
2012-04-13  8:15                 ` Andrew Lunn
2012-04-13  8:41                   ` Mitar
2012-04-13  9:24                     ` Andrew Lunn
2012-04-13 13:24                       ` Mitar
2012-04-14  2:26                     ` Nicolás Echániz
2012-04-14  9:06                       ` Mitar
2012-04-16 10:25               ` Mitar
2012-04-16 10:37                 ` Marek Lindner
2012-04-16 10:46                   ` Mitar
2012-04-16 10:58                     ` Marek Lindner
2012-04-16 12:32                       ` Mitar
2012-04-16 12:40                         ` Antonio Quartulli
2012-04-16 13:59                           ` Mitar
2012-04-16 18:28                             ` Marek Lindner
2012-04-16 18:30                         ` Marek Lindner
2012-04-16 11:03                     ` Antonio Quartulli
2012-04-16 12:37                       ` Mitar
2012-04-12 17:10     ` Mitar
2012-04-12 22:13       ` Marek Lindner
2012-04-12 17:05   ` Mitar
2012-04-12 22:17     ` Marek Lindner
2012-04-13  6:22       ` Antonio Quartulli
2012-04-13  7:29         ` Mitar
2012-04-13  7:43           ` Andrew Lunn [this message]
2012-04-13  7:51             ` Mitar
2012-04-13  8:26               ` Andrew Lunn
2012-04-13  8:35                 ` Mitar
2012-04-13  8:52           ` Christian Huldt
2012-04-13 13:32             ` Mitar
2012-04-13 13:50               ` Andrew Lunn
2012-04-13 13:53                 ` Mitar

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=20120413074323.GI7664@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=kostko@unimatrix-one.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.