All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Poelzleithner <poelzi@poelzi.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Texas UML instances and OLSR+BATMAN tests
Date: Tue, 09 Oct 2007 11:11:10 +0200	[thread overview]
Message-ID: <470B45AE.40502@poelzi.org> (raw)
In-Reply-To: <200710090953.43820.axel@open-mesh.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Axel Neumann wrote:

>> I have tested the OpenVZ livecd with a small window manager (consumes
>> 128MB in RAM), and with 10 instances running batman or olsr, it works
>> fine with 512MB of RAM, but my problem is that the livecd does not
>> supports ebtables it seems, which I need to configure for avoiding
>> bridge shortcuts between the nodes.
>>
>> Does anybody has experience with ebtables? Does it needs a kernel
>> patch? Or it is just user-space?
> 
> If you follow the link in the above lines, you will find a line like:
> 
> ... patched again to fix a bug in the ebtables part of the 2.6.18 kernel 
> extracted from patch-2.6.18.8 from 
> http://www.kernel.org/pub/linux/kernel/v2.6/ and downloadable here...

in openvz usuall all ebtables and iptables modules are supported in the
0 instance. modules that can be used inside of virtuall instances have
to be prepared for this. but this shouldn't be a problem for your setup,
so i guess the problem may be somewhere else.

by the way, if you use reiserfs + raid + lvm you have to switch off the
4k stack patch or your system will run instable :)

kindly regards
 daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: GnuPT 2.7.2
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHC0Wuy/mkIQp7AD0RAqK3AKC5sVgI7aNVn3+DST8EgbvqTrGOoQCeNTcj
SMjDi5igzJtn45LbA7F+w70=
=9F1u
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-10-09  9:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 20:18 [B.A.T.M.A.N.] Texas UML instances and OLSR+BATMAN tests Benjamin Henrion
2007-06-08 22:08 ` Aaron Kaplan
2007-06-08 23:07   ` Benjamin Henrion
2007-06-09 11:57     ` Axel Neumann
2007-06-09 13:14       ` Aaron Kaplan
2007-06-09 22:35         ` zethix or something
2007-06-09 22:42           ` Aaron Kaplan
2007-10-01 17:56           ` Benjamin Henrion
2007-10-01 18:10             ` Aaron Kaplan
2007-10-02  8:59               ` Axel Neumann
2007-10-09  7:25                 ` Benjamin Henrion
2007-10-09  7:53                   ` Axel Neumann
2007-10-09  9:11                     ` Daniel Poelzleithner [this message]
2007-10-09 12:50                       ` Axel Neumann
2007-10-09 14:23                         ` Aaron Kaplan
2007-10-09 14:29                           ` Benjamin Henrion
2007-10-09 14:56                             ` Aaron Kaplan
2007-10-09 16:34                               ` Bernd Petrovitsch
2007-10-09 16:40                                 ` Aaron Kaplan
     [not found]                                   ` <20071009165849.GA27755@MAIL.13thfloor.at>
2007-10-09 17:30                                     ` Aaron Kaplan
2007-06-08 22:33 ` Axel Neumann

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=470B45AE.40502@poelzi.org \
    --to=poelzi@poelzi.org \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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.