public inbox for b.a.t.m.a.n@lists.open-mesh.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>
Subject: Re: [B.A.T.M.A.N.] batman-adv on different archs
Date: Wed, 20 Jan 2010 10:49:22 +0100	[thread overview]
Message-ID: <20100120094922.GH7844@lunn.ch> (raw)
In-Reply-To: <20100120092904.181520@gmx.net>

On Wed, Jan 20, 2010 at 10:29:04AM +0100, "Juha Yl?nen" wrote:
> 
> -------- Original-Nachricht --------
> > Datum: Wed, 20 Jan 2010 10:15:59 +0800
> > Von: Marek Lindner <lindner_marek@yahoo.de>
> >
> > Complete configuration means: brctl show, ifconfig, cat /proc/net/batman-
> > adv/interfaces (or batctl if) and ping output. 
> 
> Could be the first one in the list as brctl fails. CONFIG_BRIDGE is
> not configured in the device kernel. Is batman-adv dependent on
> this? I'll recompile the kernel and see what happens (it's a slow
> process), in the meanwhile, what other kernel configurations are
> needed for batman-adv?

Bridging is not a requirement. 

However many uses typically use bridging to build bigger
networks. They bridge bat0 with eth0 to form one big layer 2 network.

However you don't have to do this. I've run OSPF on the bat0 interface
and just routed traffic over it just like any other network link in
the network.

    Andrew

  parent reply	other threads:[~2010-01-20  9:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 14:58 [B.A.T.M.A.N.] batman-adv on different archs "Juha Ylönen"
2010-01-20  2:15 ` Marek Lindner
2010-01-20  9:29   ` "Juha Ylönen"
2010-01-20  9:42     ` Marek Lindner
2010-01-20  9:49     ` Andrew Lunn [this message]
2010-01-20  9:51     ` Sven Eckelmann
2010-01-20 13:12   ` "Juha Ylönen"
2010-01-20 22:32     ` Marek Lindner
2010-01-21 14:12       ` "Juha Ylönen"
2010-01-21 15:29         ` Sven Eckelmann
2010-01-21 17:17         ` Gus Wirth
2010-01-21 18:32           ` Sven Eckelmann
2010-01-22 18:26             ` Simon Wunderlich
2010-01-24 21:19               ` "Juha Ylönen"
  -- strict thread matches above, loose matches on Subject: below --
2010-01-24 21:17 "Juha Ylönen"
2010-01-24 22:03 ` Sven Eckelmann
2010-01-21 19:02 "Juha Ylönen"
2010-01-22 12:16 ` Sven Eckelmann
2010-01-18 11:27 "Juha Ylönen"
2010-01-18 11:39 ` Andrew Lunn
2010-01-18 13:29   ` "Juha Ylönen"
2010-01-18 13:38     ` Marek Lindner
2010-01-18 13:51       ` Andrew Lunn
2010-01-19  7:46         ` "Juha Ylönen"
2010-01-19  7:43       ` "Juha Ylönen"
2010-01-19 12:07         ` Marek Lindner
2010-01-19 14:51           ` "Juha Ylönen"
2010-01-19 15:11             ` Sven Eckelmann
     [not found]               ` <20100119153233.319500@gmx.net>
2010-01-19 17:12                 ` Sven Eckelmann
2010-01-19 19:37             ` Simon Wunderlich
2010-01-20 14:05               ` "Juha Ylönen"
2010-01-20 21:58                 ` Marek Lindner
2010-01-18 11:42 ` Marek Lindner

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=20100120094922.GH7844@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.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