New distribution: WISP-Dist
[Posted June 1, 2002 by corbet]
From: Vladimir Ivaschenko <vi@maks.net>
To: lwn@lwn.net
Subject: WISP-Dist announcement
Date: Thu, 30 May 2002 22:17:40 +0300
Hi All,
I made the first public release of WISP-Dist available
(description below). Homepage is at http://www.hazard.maks.net/wisp-dist .
About WISP-Dist
WISP-Dist is an embedded Linux distribution created for wireless
routers, but can be used for other purposes as well. Entire system
fits in 8 MB flash/16 MB RAM. The goal is to create an open,
customizable and easy to use solution for wireless routers.
Development was sponsored by [1]ThunderWorx.
Highlights:
* Completely open system based on Linux kernel 2.4 and LEAF Bering
* Entire distribution fits in 8 MB flash, of which 1.2MB are
currently free for additional packages
* Works on 16 MB RAM
* Simple to use menu-based configuration system for basic
functionality
* Command-line access for advanced configuration
* Local access via console or serial port
* Remote access via SSH
* Statistics available via SNMP
* OSPF, RIPv2 dynamic routing support integrated; networks built
this way are much easier to debug and tune than bridging-based
networks
* NAT
* Bandwidth shaping
* VLAN trunking support: service several customers from one CPE
connected to a switch
* Access Point support for Prism2, Prism2.5
* MAC filter (access list) support for AP
* Advanced network diagnostics: NTOP, tcpdump
* Remotely upgradable
* Modular: you can add/remove packages
* Can log all system events to remote system via SYSLOG protocol
* checkping: system will reboot if some of the specified hosts are
unreachable (useful when radios get stuck)
* Easy to service: all files are stored on standard FAT partition
* Compatible with LRP (LEAP) packages
Drawbacks:
* No integrated bridging support (I don't count this as a drawback).
It is not needed if you use RIP/OSPF routing, which is very easy
to setup. However all the components are inside to make bridging
on Prism2 boards; you can do it by editing scripts manually.
Full-fledged bridging is not possible on other cards as drivers do
not support WDS. A workaround is possible if somebody develops an
L3 (IP) bridging solution similar to the one used by Teletronics
CPR images; however it won't be reliable solution anyway (you get
various problems if you mix routing & bridging).
Supported (tested) platforms:
* Teletronics CPR motherboards
* Nagasaki MS-2100 mini-servers
Supported wireless cards:
* Aironet LMC352
* Lucent/Avaya WaveLan
* Prism2-based cards (Teletronics, Zcomax, D-Link, LinkSys ...)
Generally, all modern hardware is supported.
References
1. http://www.thunderworx.com/
--
Best Regards,
Vladimir
Certified Linux Engineer (RHCE)
(
Log in to post comments)