Free diet router software for linux

Diet Tracker is a set of Perl codes to help you keep track of your diet progress. Diet Tracker uses a MySQl database to store and display your weight variations and calorie intake as you progress in your diet.
This software was inspired by Jeremy Zawodnys Excel spreadsheet that does almost the same thing. I wanted a web version that was simple and meant for single user and not finding any, wrote one.
Main features:
- Web based
- Track calorie intake per day
- Graphs to track weight and intake history
- Moving average calculation to even out jitters
- Automatic BMI calculation
- Clean interface

Net::BGP::Router is a BGP Router based on Net::BGP.

SYNOPSIS

use Net::BGP::Router;
# Constructor
$router = new Net::BGP::Router(
Name => My very own router!,
Policy => new Net::BGP::Policy
);
# Accessor Methods
$router->add_peer($peer,both,$acl);
$router->remove_peer($peer,both);
$router->set_policy($policy);
$router->set_policy($peer,in,$acl);
__top

This module implement a BGP router. It uses Net::BGP objects for the BGP sessions and a Net::BGP::RIB object to store the routes. Policy are handled using a Net::BGP::Policy object.

BitWise Routing Server allows multiple PCs behind a router to make direct connections.

The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.

As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.

The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).

The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.

The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.

Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.

In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.

If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.

Setting up the physical router

The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.

The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).

Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.

Configuring BitWise to use the Routing Server

In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).

Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.

Registration with the Routing Server

Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.

It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.

Using the Routing Server

Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.

The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.

diet libc contains the system call wrappers and the most commonly-used functions you expect from a libc.
diet libc can be used to create small, statically-linked binaries under x86, AMD64, SPARC, SPARC64, PPC, PPC64, ARM, MIPS, MIPS64, PA-RISC, S/390, S/390x (64-bit S/390), and Alpha-Linux.
Enhancements:
- Improvements to GCC 4 support. toascii, ustat, strnlen, clearenv, ngettext, dngettext, strdupa, and strndupa are provided.
- Extended attribute, thread, and misc. syscalls have been added.
- There are many general and platform-specific bugfixes.

File Beamer is an easy to use file transfer tool. The programm is platform independent. That means it runs with Windows 98/ME/2000/XP, Linux, Unix and MacOS X.

This is made possible by using Trolltechs Qt Library which provides an easy to use GUI toolkit, networking functions and a lot more.

File Beamer is free open source software and was released under the GPL license.

Usage:

Receiving files:

Click the "Receive" tab
If the receiver is behind a firewall or router, check "reverse connection" and enter the senders IP or host name. *
Click the "listen" button. The client can now receive files
When receving a file, a "Save as" dialog appears. Choose a place to safe the file.

Sending files:

Click the "Send" tab
If the receiver is behind a firewall or router check "reverse connection" *
Else input the target IP address or host name and port
Select a file to send either by typing the path or by clicking the "..." button
Click the "Send" button (target must be in listen mode)

Avis client library is a Java API for clients accessing Elvin event routers, including the open source Avis event router and the commercial Mantara Elvin product.
Avis is an event router service compatible with the commercial Elvin implementation developed by Mantara Software. Avis provides a fast, general-purpose publish/subscribe message bus.
Elvin event routers alllow arbitrary messages, known as notifications, to be exchanged via a publish/subscribe model. Elvin clients subscribe to messages published by other clients using expressions that match messages by their content.
The content-based routing approach used in Elvin routers differs from many other message bus systems that operate by selecting messages published on pre-defined channels, and has the advantage of promoting a much higher level of decoupling between producers and consumers of events.
The name "Avis" derives from the French word avis, meaning advice or notification.
Enhancements:
- This release marks a stable baseline for the Java client API.
- The core set of features required for an Elvin client library are now implemented and stable, including subscription, notification, security, close event notification, liveness checking, and router connection option support.