public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: elektra <onelektra@gmx.net>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] meshliunx
Date: Tue, 23 Jan 2007 13:45:25 +0100	[thread overview]
Message-ID: <45B60365.7010502@gmx.net> (raw)
In-Reply-To: <45B5EEB3.5040203@bb.banban.jp>

Hello Kazuki -
> I am so interested in meshlinux. Can I make any question?
> - Is meshlinux built on something well-known distribution, like 
> freifunk on openwrt?
Meshlinux is targeted at the re-use of PC hardware for wireless routers. 
Currently it is based on Slackware.  At the moment Meshlinux is nothing 
fancy. The philosophy behind Meshlinux is KISS, stability and 
flexibility. No webinterface, no fancy package management - yet. But 
b.a.t.m.a.n., bridge-utils, quagga (RIP, BGP, OSPF v2 and v3...) 
up-to-date OLSRD with fisheye & ETX, apache, nmap, ncftp, proftp, rsync, 
horst, ff-trace, serial terminal, openvpn etc. It installs from a 
bootable CD to a harddrive within approximately 2 minutes on a Pentium 
III. I'll make an image for CF-Cards also - so you could use it with a 
WRAP-Board or Soekris. There will be 3 versions - one with complete 
compiling/building environment (including kernel-sources) for HD-install 
or a chroot environment on your Desktop so you can compile/build 
anything that you think is missing (like the newest SVN-checkout of a 
driver or a special patch), and two stripped-down ones - one for HD 
install and the CF-Image.

The recommended wifi-cards of today for Linux are using the Atheros 
chipset. If you really want to have bandwidth you need a powerful CPU 
for these cards. A 200 MHz Mips-CPU will give you a maximum throughput 
of 1.28 MByte/sec over a direct link (tested with Netgear WGT634U). The 
same cards can do ~ 3 MByte/sec without turbo-mode on a faster host CPU.

If you want bandwidth and more than one interface you will be much 
better off with a router based on a PC and PCI-cards. Of course it will 
be quite bulky and consume more power than a little embedded device. 
Meshlinux may be a good choice for a core-router or server (http, ftp, 
sip, icecast ... you name it) for local content. Administrators of such 
routers may not miss a webinterface.

cu elektra









>
> - Does it depend on specific architecture and/or board, 
> mips-arm-broadcom-la-la-la?
> - Does it have a package manegement system,  like ipkg?
> - it seems b.a.t.m.a.n. takes account of multi wireless 
> module/interface, does meshlinux support multi radio?
> http://www.google.co.jp/search?hl=ja&q=multi+radio&btnG=Google+%E6%A4%9C%E7%B4%A2&lr= 
>
>
> Anyway, I'm so ready to see her(him?) ; )
>
> Best regards,
>
> Kazuki
>> from Nagasaki Japan
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>


  reply	other threads:[~2007-01-23 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22 10:46 [B.A.T.M.A.N.] hi all rcml
2007-01-23  9:45 ` Marek Lindner
2007-01-23 11:17   ` [B.A.T.M.A.N.] meshliunx ルマンド
2007-01-23 12:45     ` elektra [this message]
2007-01-23 13:03       ` Benjamin Henrion
2007-01-23 11:33 ` [B.A.T.M.A.N.] hi all Lui

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=45B60365.7010502@gmx.net \
    --to=onelektra@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox