[MLB-WIRELESS] hardware of choice for a client.

[David Ashburner]

he he I've done the port but I'm pressed for time. I can let  you have it to 
try if you want.
Bigest problem I have had with the Minitar is lack of RAM - you loose 2MB to 
the kernel and another 3.5 to the RAMDISK. disen't leave much to run apps 
in. been looking at cramfs and NFS to free up some RAM

I have a pretty simple (read using it as a link device) ramdisk image almost 
ready to go if there is anyone who want's to collaborate on testing it out 
and maybee helping me finish hacking it into shape. Any takers?

>From: "Dan Flett" <conhoolio at hotmail.com>
>To: "'Steven Haigh'" <netwiz at crc.id.au>, <melbwireless at wireless.org.au>
>Subject: RE: [MLB-WIRELESS] hardware of choice for a client.
>Date: Wed, 1 Dec 2004 14:40:53 +1100
>
>Hi Steven...
>
>Minitar MNWAPB APs can do client connections, are cheap, easy to add PoE
>to, have 18dBm Tx output, and run Linux!  What more could you ask for?
>
>It would be excellent if someone could port Frottle to run on the
>Minitar.  It could be set up to automatically run in either client or
>master mode depending if the unit is in client or AP mode, respectively.
>This would make less convincing the argument against using Frottle
>because it is a Linux-only application.  A Frottle-enabled Minitar would
>allow a Windows or any other platform to take advantage of it's
>hidden-node-reduction ability.
>



To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message