From: "Peter V. Saveliev" <peet@altlinux.org>
To: lartc@vger.kernel.org
Subject: [LARTC] ncsh: alpha release
Date: Sat, 20 Oct 2007 18:23:26 +0000 [thread overview]
Message-ID: <200710202223.26770.peet@altlinux.org> (raw)
...
Hello!
An alpha-mature code of the Connexion project is available:
http://www.radlinux.org/
http://www.radlinux.org/download/connexion-0.4.4.tar.bz2 [171Kb]
docs:
* en: http://www.radlinux.org/docs/static/en/
* ru: http://www.radlinux.org/docs/static/ru/
See docs/INSTALL for quick start-up howto (strictly speaking, installation
isn't required, it can work out-of-box -- if all dependencies are provided).
config samples:
* in the tarball, interfaces/console/testing/*
* event handling: http://www.radlinux.org/connexion/wiki/Connexion/Samples
...
In general, Connexion is a framework that provides an easy way to create and
combine system configuration modules. The 0.4.4 is shipped with modules:
* ncsh: basic network setup (ethernet, vlan, bridging, pptp, pppoe controls),
shaping (tbf,htb) (including class-factory for massive shaping)
* events: snmp traps and netlink events handling
* base dictionary
...
System requirements: GNU/Linux (2.6.13 and above tested; older kernels are not
tested but should work, except, maybe, netlink events), glibc (uclibc is not
tested, may not work in events handling), python2.4, iproute2, vlan-utils and
other ip stuff.
Possible problems: netlink module uses ctypes and operates on very low level.
It may have arch-related bugs, 'cause it is tested only on PC ia32 and amd
x86_64
Additional python modules (may be installed, but are not necessary):
* egenix-mx-experimental -- for UID(); if absent, uuidgen will be used
* pysnmp 4.x
* pyasn1
* pysnmp-mibs -- for SNMP traps
* ctypes -- for netlink events
So, without event handling, the Connexion project may work with python2.4
only, w/o any additional packages (ip related utils are still needed, but if
one works with network setup, he already has these utils)
...
I hope that the project will be useful. Any comments are appreciated. If
anyone want to help the project with coding/testing/docs -- you are welcome.
--
Peter V. Saveliev
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2007-10-20 18:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200710202223.26770.peet@altlinux.org \
--to=peet@altlinux.org \
--cc=lartc@vger.kernel.org \
/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