i’ve got a demo instance of iphive running, so if you want to see how it works feel free to email me and i can get you access to try it out. the demo is using the latest version of the code as of 2011.4.4 and is using private address space for the example database.
the next version is being written to accommodate IPv6, and will also have better user-accounting facilities to better track the who-does-what aspect of inventory management. at that time i’ll also be upgrading to the newest version of the mite framework, which will unlock a whole slew of possible enhancements and improvements.
fireverse is a stellar conquest civ-type webgame. the current version (alpha6.2011.1.21) is written on top of the mite framework in perl, and uses mysql for a backend data model.
graphics are generated dynamically in svg format, though png conversion is available for those browsers that don’t support svg yet.
mite isn’t so much a dedicated application as it is a collection of directory structures, modules, and implementation philosophy. Here are some of the basics of how it works, and why.
Continue reading “mite – basics – directory and server config”
Some people still deploy/use/support userdir sites. As tragic as this may be, managing those accounts has almost always sucked. This tool makes it suck slightly less.
This tool assumes a pureftpd and apache2 backend, and used mysql to manage all the accounts. With multiple IP addresses are used, it becomes possible use shortname logins as well.
dnsadmin is a web frontend/configuration script that allows for simple management of a bind authoritative server. All zone info is stored in a mysql database that is written into bind configuration and zone files by a cronjob.
pigeon is a mail system management tool. This allows for control over mail user accounts on mail systems that use mysql for domain and account management. Current deployments supported by this tool use postfix as an MTA/MDA and dovecot for POP3/IMAP access.
NB : The mydns project appears to be dead, and a new project has (sort of) taken its place (mydns-ng). With this in mind, the module discussed here should be considered of VERY limited use.
First of all, you need to go here so you have an idea of what this is about.
This is a perl module written to help manage a mydns based server.
The idea was to provide a simple and clean interface, which also means that there aren’t a lot of additional or optional things enabled or supported.
Still, this should get you by if you need to do a lot of bulk management duties.
note – this project was pretty much abandoned ones I put together my own dnsadmin system to manage bind rather than mydns. This isn’t to say bind is better than mydns, but rather that the environment I deployed these in preferred bind.
here is the pod2html output for the module :
here is the module itself :
iphive is an inventory management system for IPv4 addresses.
Consider a network with more than one /24 IP block present, and a need to divide that into smaller blocks for allocating to for arbitrary uses. In our use case we will assume that you want to divide that /24 into /29 blocks. Obviously being able to track which of those /29 blocks are in use and what they are being used for is helpful. This system allows you to do this.
iphive uses a mysql database to keep track of the supernets, blocks, and addresses. The web interface is based on the Mite web framework and also contains an auditing tool meant to be run directly on a command line. The auditing tool uses SNMP queries against a user-defined set of routers to check for routes and confirm IP usage on a network and the blocks sizes actually used.