About:
Qolyester is a C++ implementation of the OLSR protocol for mobile wireless ad hoc networks. It is meant to be enhanced with QoS features from the QOLSR research group.

Author:
Ignacy Gawedzki [contact developer]

Rating:	reset 1 2 3 4 5 6 7 8 9 10
(not rated)

Homepage:
http://qolsr.lri.fr/
Tar/GZ:
http://qolsr.lri.fr/code/qolyester-20080613.tar.gz
Tar/BZ2:
http://qolsr.lri.fr/code/qolyester-20080613.tar.bz2

Trove categories: [change]

[Development Status]		2 - Pre-Alpha
[License]		OSI Approved :: GNU General Public License (GPL)
[Network Environment]		IP :: IPv4, IP :: IPv6
[Operating System]		Unix
[Programming Language]		C++
[Topic]		Communications, Internet, System :: Networking, System :: Systems Administration, Utilities

Dependencies: [change]
No dependencies filed

 Branches

Branch	Version	Last release	License	URLs
Default	20080613	11-Jul-2008	GNU General Public License (GPL)

 Comments

[»] Wrong author, wrong description and wrong latest release.
by Ignacy Gawedzki - Jan 31st 2004 04:36:15

I happen to be the author. =)

The description is: Qolyester is an implementation for Linux kernels 2.4.x (haven't tested with 2.6.x yet) (this will change as someone contributes other versions on the system interface) in C++ of the OLSR (Optimized Link-State Routing) protocol, RFC 3626. The implementation's main purpose is to be a testbed for QoS algorithms, but can be used as a routing daemon for any mobile ad hoc network. The Default branch is devoid of any QoS feature, but a QoS branch is to be released later when these algorithms become mature.

The latest version, at the time of writing is 20040130.

[reply] [top]

[»] Re: Wrong author, wrong description and wrong latest release.
by jeff covey - Feb 10th 2004 08:44:24


> I happen to be the author.

So why don't you claim ownership of the listing and fix it?

--
vs lbh pna ernq guvf, lbh'er n trrx.

[reply] [top]

---

[»] Re: Wrong author, wrong description and wrong latest release.
by imipak - Apr 16th 2005 18:21:47

I'm sympathetic - no, really, I am. An incorrect record entry can produce confusion and result in people who would benefit from the software not doing so. I would add, though, that it is no different for record entries that are incorrect because they aren't being actively maintained. Nobody is going to use a project they don't know about. Maybe Freshmeat should have some "professional" record maintainers who do nothing but update genuinely abandoned records for actively developed software.

[reply] [top]

---