routing
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 163
Routing incoming ppp0
Routing incoming ppp0 is a netfilter firewall. more>>
Routing incoming ppp0 is a netfilter firewall.
Sample:
#!/bin/bash
# Load required modules
insmod ip_tables
insmod ip_conntrack
insmod iptable_nat
insmod ipt_MASQUERADE
# Then flush all rules
iptables -F
iptables -t nat -F
# In the NAT table (-t nat), Append a rule (-A) after routing
# (POSTROUTING) for all packets going out ppp0 (-o ppp0) which says to
# MASQUERADE the connection (-j MASQUERADE).
#iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
# Below means route 192.168.1.x
iptables -t nat -A POSTROUTING -d ! 192.168.1.0/24 -j MASQUERADE
iptables -A FORWARD -s 192.168.1.0/24 -j ACCEPT
iptables -A FORWARD -d 192.168.1.0/24 -j ACCEPT
iptables -A FORWARD -s ! 192.168.1.0/24 -j DROP
# Disallow NEW and INVALID incoming or forwarded packets from ppp0.
#iptables -A INPUT -i ppp0 -m state --state NEW,INVALID -j DROP
#iptables -A FORWARD -i ppp0 -m state --state NEW,INVALID -j DROP
# port 113 is evil ;)
iptables -A INPUT --protocol udp --source-port 113 -j DROP
iptables -A INPUT --protocol udp --destination-port 113 -j DROP
# Turn on IP forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
#iptables -A INPUT --protocol udp --source-port 113 -j DROP
# Route incoming ppp0 at port 80, to 192.168.1.18:80
iptables -A PREROUTING -t nat -p tcp -i ppp0 --dport 80 -j DNAT --to 192.168.1.18:80
# Route incoming ppp0 at port 21, to 192.168.1.18:21
iptables -A PREROUTING -t nat -p tcp -i ppp0 --dport 21 -j DNAT --to 192.168.1.18:21
<<lessSample:
#!/bin/bash
# Load required modules
insmod ip_tables
insmod ip_conntrack
insmod iptable_nat
insmod ipt_MASQUERADE
# Then flush all rules
iptables -F
iptables -t nat -F
# In the NAT table (-t nat), Append a rule (-A) after routing
# (POSTROUTING) for all packets going out ppp0 (-o ppp0) which says to
# MASQUERADE the connection (-j MASQUERADE).
#iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
# Below means route 192.168.1.x
iptables -t nat -A POSTROUTING -d ! 192.168.1.0/24 -j MASQUERADE
iptables -A FORWARD -s 192.168.1.0/24 -j ACCEPT
iptables -A FORWARD -d 192.168.1.0/24 -j ACCEPT
iptables -A FORWARD -s ! 192.168.1.0/24 -j DROP
# Disallow NEW and INVALID incoming or forwarded packets from ppp0.
#iptables -A INPUT -i ppp0 -m state --state NEW,INVALID -j DROP
#iptables -A FORWARD -i ppp0 -m state --state NEW,INVALID -j DROP
# port 113 is evil ;)
iptables -A INPUT --protocol udp --source-port 113 -j DROP
iptables -A INPUT --protocol udp --destination-port 113 -j DROP
# Turn on IP forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
#iptables -A INPUT --protocol udp --source-port 113 -j DROP
# Route incoming ppp0 at port 80, to 192.168.1.18:80
iptables -A PREROUTING -t nat -p tcp -i ppp0 --dport 80 -j DNAT --to 192.168.1.18:80
# Route incoming ppp0 at port 21, to 192.168.1.18:21
iptables -A PREROUTING -t nat -p tcp -i ppp0 --dport 21 -j DNAT --to 192.168.1.18:21
Download (MB)
Added: 2007-02-14 License: GPL (GNU General Public License) Price:
989 downloads
BitWise Routing Server 1.7
BitWise Routing Server allows multiple PCs behind a router to make direct connections. more>>
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.
<<lessThe 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.
Download (1.0MB)
Added: 2006-03-02 License: Freeware Price:
1331 downloads
BitWise Routing Server for Linux 1.7
allows you to accept BitWise connections to multiple computers behind a router. more>> 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).<<less
Download (1011KB)
Added: 2009-04-20 License: Freeware Price: Free
187 downloads
Internet Registry Routing Daemon 2.3.4
Internet Registry Routing Daemon (IRRd) is a freely available, stand-alone Internet Routing Registry database server. more>>
Internet Registry Routing Daemon (IRRd) is a freely available, stand-alone Internet Routing Registry database server. IRRd supports the RPSL and RPSLng Routing Policy Specification Language standards.
The IRRd package includes all required IRR support services, including: automated near real-time mirroring of other IRR databases, update syntax checking, authentication/security, and notification.
<<lessThe IRRd package includes all required IRR support services, including: automated near real-time mirroring of other IRR databases, update syntax checking, authentication/security, and notification.
Download (0.67MB)
Added: 2007-08-14 License: BSD License Price:
801 downloads
JOpt.SDK Vehicle Routing Component 2.0.0 (Tutorial)
JOpt.SDK library is a routing software for Java that uses specialized genetic algorithms. more>>
JOpt.SDK library is a routing software for Java that uses specialized genetic algorithms to calculate an optimized allocation of orders and stops to mobile resources.
The algorithm not only provides tours at minimum costs but also considers an arbitrary set of constraints for each tour. You may define your own constraints and optimization goals in order to customize JOpt.SDK to your specific planning needs or you decide to use one of our best practices addons in order to achieve a fast application of our optimization algorithms to selected industries.
JOpt.SDK can solve nearly any problem that can be classified by one of the following types:
TSP - Traveling Salesman Problem. JOpt.SDK finds the shortest or fastest path for your mobile resources
VRPTW - Vehicle routing problem with time windows - like TSP but for a set of vehicles. JOpt.SDK finds an optimal allocation of orders and stops within a vehicle fleet. It may also consider different constraints for vehicles, drivers and stops.
JOpt.SDK functionality can be accessed via Java API and thus fits seamlessly into any JAVA application. Software developers may integrate the JOpt.SDK component into their application in order to offer their customers a consistent solution including optimization of mobile workforce schedules.
Enhancements:
- The tutorial has been revised to reflect some major API changes introduced since JOpt 2.0.0.
<<lessThe algorithm not only provides tours at minimum costs but also considers an arbitrary set of constraints for each tour. You may define your own constraints and optimization goals in order to customize JOpt.SDK to your specific planning needs or you decide to use one of our best practices addons in order to achieve a fast application of our optimization algorithms to selected industries.
JOpt.SDK can solve nearly any problem that can be classified by one of the following types:
TSP - Traveling Salesman Problem. JOpt.SDK finds the shortest or fastest path for your mobile resources
VRPTW - Vehicle routing problem with time windows - like TSP but for a set of vehicles. JOpt.SDK finds an optimal allocation of orders and stops within a vehicle fleet. It may also consider different constraints for vehicles, drivers and stops.
JOpt.SDK functionality can be accessed via Java API and thus fits seamlessly into any JAVA application. Software developers may integrate the JOpt.SDK component into their application in order to offer their customers a consistent solution including optimization of mobile workforce schedules.
Enhancements:
- The tutorial has been revised to reflect some major API changes introduced since JOpt 2.0.0.
Download (MB)
Added: 2007-05-08 License: Free For Educational Use Price:
903 downloads
Linux Advanced Routing & Traffic Control HOWTO 1.0.0
Linux Advanced Routing & Traffic Control HOWTO is a document concerning iproute2, traffic control (shaping), and more! more>>
Linux Advanced Routing & Traffic Control HOWTO is a document concerning iproute2, traffic control (shaping), and more!
The LARTC-HOWTO describes many advanced ways of routing and shaping traffic.
Using the HOWTO, you will be able to shape traffic in myriad ways, which will help you lower latency for interactive use when others are downloading or uploading.
It will also teach you how to limit certain hosts/protocols bandwidth usage. It also explains many aspects of routing using the ip tool from the iproute2 suite.
<<lessThe LARTC-HOWTO describes many advanced ways of routing and shaping traffic.
Using the HOWTO, you will be able to shape traffic in myriad ways, which will help you lower latency for interactive use when others are downloading or uploading.
It will also teach you how to limit certain hosts/protocols bandwidth usage. It also explains many aspects of routing using the ip tool from the iproute2 suite.
Download (MB)
Added: 2006-10-06 License: Freeware Price:
652 downloads
Arping 2.05
Arping is an ARP level ping utility. more>>
Arping is an ARP level ping utility. Its good for finding out if an IP is taken before you have routing to that subnet. You can also ping MAC addresses directly.
Broadcasts a who-has ARP packet on the network and prints answers. VERY useful when you are trying to pick an unused IP for a net that you dont yet have routing to. Then again, if you have no idea what Im talking about then you prolly dont need it.
Arping is util to find out it a specific IP address on the LAN is taken and what MAC address owns it. Sure, you *could* just use ping to find out if its taken and even if the computer blocks ping (and everything else) you still get an entry in your ARP cache. But what if you arent on a routable net? Or the host blocks ping (all ICMP even)? Then youre screwed. Or you use arping.
<<lessBroadcasts a who-has ARP packet on the network and prints answers. VERY useful when you are trying to pick an unused IP for a net that you dont yet have routing to. Then again, if you have no idea what Im talking about then you prolly dont need it.
Arping is util to find out it a specific IP address on the LAN is taken and what MAC address owns it. Sure, you *could* just use ping to find out if its taken and even if the computer blocks ping (and everything else) you still get an entry in your ARP cache. But what if you arent on a routable net? Or the host blocks ping (all ICMP even)? Then youre screwed. Or you use arping.
Download (0.031MB)
Added: 2006-06-21 License: GPL (GNU General Public License) Price:
1269 downloads
YateAdmin 1
YateAdmin is a FREE powerful web interface which helps to set up the telephony engine Yate. more>>
YateAdmin is a FREE powerful web interface which helps to set up the telephony engine Yate.
You can use it to setup:
- Users lines
- Register to other servers
- Routes for gateways
- Fallback routing
- Call Detail Report
- Yate status
<<lessYou can use it to setup:
- Users lines
- Register to other servers
- Routes for gateways
- Fallback routing
- Call Detail Report
- Yate status
Download (0.058MB)
Added: 2006-10-04 License: GPL (GNU General Public License) Price:
1120 downloads
MUTE File Sharing 0.5.1
MUTE File Sharing is a peer-to-peer network that provides easy search-and-download functionality. more>>
MUTE File Sharing is a peer-to-peer network that provides easy search-and-download functionality while also protecting your privacy.
It compiles as a fast, native application for many platforms (no Java, no Python, etc.).
MUTE protects your privacy by avoiding direct connections with your sharing partners in the network. Most other file sharing programs use direct connections to download or upload, making your identity available to spies from the RIAA and other unscrupulous organizations.
MUTE is based on research, and experiments show that it works quite well. MUTEs ant-inspired routing is light-weight, robust, and adaptive. Results from experiments in real MUTE networks show that the collective behavior of MUTE nodes quickly finds the shortest (or fastest) routing path between two nodes on the network.
Enhancements:
- This release fixes bugs in MUTEs initial connection to the network upon startup.
- MUTE has also been upgraded to Crypto++ 5.4, so it should now compile using GCC 4.1.
<<lessIt compiles as a fast, native application for many platforms (no Java, no Python, etc.).
MUTE protects your privacy by avoiding direct connections with your sharing partners in the network. Most other file sharing programs use direct connections to download or upload, making your identity available to spies from the RIAA and other unscrupulous organizations.
MUTE is based on research, and experiments show that it works quite well. MUTEs ant-inspired routing is light-weight, robust, and adaptive. Results from experiments in real MUTE networks show that the collective behavior of MUTE nodes quickly finds the shortest (or fastest) routing path between two nodes on the network.
Enhancements:
- This release fixes bugs in MUTEs initial connection to the network upon startup.
- MUTE has also been upgraded to Crypto++ 5.4, so it should now compile using GCC 4.1.
Download (0.70MB)
Added: 2007-04-23 License: GPL (GNU General Public License) Price:
921 downloads
mrouted 3.9 Beta 3
mrouted project is a DVMRP multicast routing daemon. more>>
mrouted project is a DVMRP multicast routing daemon.
mrouted is an implementation of the DVMRP multicast routing protocol. It turns a UNIX workstation into a DVMRP multicast router with tunnel support, in order to cross non-multicast-aware routers.
Enhancements:
- IGMP could report membership in local-only groups (i.e. 224.0.0.X)
- IGMP could get confused by hearing its own new membership reports, thus a router would never perform fast leave.
- IGMP could reset timers for the wrong interface.
- mrouted put a bogus value in the maximum timeout field of IGMPv2 query packets.
- Non-querier mrouters would respond to IGMP leave messages
- mrouted was not performing fast leave properly
- If the last member goes away on a transit network, the upstream router would stop forwarding even if there are downstream members.
- Kernel hash function improved
- Eliminated possibility of panic(): timeout in cache maintenance
- Reordered resource allocation when sending upcall to handle failure properly
- some endian-ness bugs squashed in mrouted, probably more to go.
- Multicast traceroute could send a reply on a disabled interface.
<<lessmrouted is an implementation of the DVMRP multicast routing protocol. It turns a UNIX workstation into a DVMRP multicast router with tunnel support, in order to cross non-multicast-aware routers.
Enhancements:
- IGMP could report membership in local-only groups (i.e. 224.0.0.X)
- IGMP could get confused by hearing its own new membership reports, thus a router would never perform fast leave.
- IGMP could reset timers for the wrong interface.
- mrouted put a bogus value in the maximum timeout field of IGMPv2 query packets.
- Non-querier mrouters would respond to IGMP leave messages
- mrouted was not performing fast leave properly
- If the last member goes away on a transit network, the upstream router would stop forwarding even if there are downstream members.
- Kernel hash function improved
- Eliminated possibility of panic(): timeout in cache maintenance
- Reordered resource allocation when sending upcall to handle failure properly
- some endian-ness bugs squashed in mrouted, probably more to go.
- Multicast traceroute could send a reply on a disabled interface.
Download (0.10MB)
Added: 2007-03-12 License: Freely Distributable Price:
982 downloads
LooperNG 1.3
LooperNG is an intelligent event routing daemon. more>>
LooperNG is an intelligent event routing daemon. Primarily used for Network Management, this application can be used to accomplish a variety of tasks related to logging and alerting.
It is a modularised, rules-based event routing system that is flexible and easy to use. It is primarily deployed by network / security management groups as a central event gateway or an SNMP trap collection and forwarding station.
LooperNG events can be in the form of SNMP traps, Syslog Alerts, lines in a Log File, Sockets etc. Events can be received and generated such that an event can arrive in one form (e.g., SNMP) and forwarded in another form (e.g., Syslog). LooperNG can also receive events from systems like Nagios, Snort, Mon etc. and forward to other systems like a MySQL database, Netcool/OMNIbus, or just send an e-mail. Modules for new types of events can be easily written.
LooperNG was designed to improve on some of the limitations Looper (muthanna.com/looper). It is built completely from scratch with a cleaner more scalable architecture and is based on the Perl language.
Main features:
- SNMP Trap forwarding, exploding and rewriting (enhancing).
- Event generation for demos, debugging, troubleshooting etc.
- Event Enrichment and Escalation.
- Intelligent routing, rerouting and processing of events and alerts.
- Monitoring logfiles, syslog events, intrusion events etc.
- Forwarding alert history to databases, logfiles etc.
- Used as ad-hoc Netcool Probes.
- Used to replace HP Openview NNMs trap collection features.
- Centralize alerts in a LooperDB database.
<<lessIt is a modularised, rules-based event routing system that is flexible and easy to use. It is primarily deployed by network / security management groups as a central event gateway or an SNMP trap collection and forwarding station.
LooperNG events can be in the form of SNMP traps, Syslog Alerts, lines in a Log File, Sockets etc. Events can be received and generated such that an event can arrive in one form (e.g., SNMP) and forwarded in another form (e.g., Syslog). LooperNG can also receive events from systems like Nagios, Snort, Mon etc. and forward to other systems like a MySQL database, Netcool/OMNIbus, or just send an e-mail. Modules for new types of events can be easily written.
LooperNG was designed to improve on some of the limitations Looper (muthanna.com/looper). It is built completely from scratch with a cleaner more scalable architecture and is based on the Perl language.
Main features:
- SNMP Trap forwarding, exploding and rewriting (enhancing).
- Event generation for demos, debugging, troubleshooting etc.
- Event Enrichment and Escalation.
- Intelligent routing, rerouting and processing of events and alerts.
- Monitoring logfiles, syslog events, intrusion events etc.
- Forwarding alert history to databases, logfiles etc.
- Used as ad-hoc Netcool Probes.
- Used to replace HP Openview NNMs trap collection features.
- Centralize alerts in a LooperDB database.
Download (1.7MB)
Added: 2006-07-04 License: GPL (GNU General Public License) Price:
1211 downloads
Rodent 0.9.8-1
Rodent is an ident daemon that is capable of routing AUTH requests to other machines on your network. more>>
Rodent is an ident daemon that is capable of routing AUTH requests to other machines on your network.
Rodent is intended for routers or to be run on a machine behind a home router.
Rodent allows others to enjoy full ident without the limitations of port forwarding to a single machine.
<<lessRodent is intended for routers or to be run on a machine behind a home router.
Rodent allows others to enjoy full ident without the limitations of port forwarding to a single machine.
Download (0.051MB)
Added: 2007-07-27 License: GPL (GNU General Public License) Price:
820 downloads
YateClient 1.2.0
YateClient is a next-generation telephony engine. more>>
YateClient is a next-generation telephony engine.
While currently focused on Voice over Internet Protocol (VoIP) and PSTN, its power lies in its ability to be easily extended.
Voice, video, data, and instant messaging can all be unified under Yates flexible routing engine, maximizing communications efficiency and minimizing infrastructure costs for businesses.
Yate can be used as a:
- VoIP server
- VoIP client
- VoIP to PSTN gateway
- PC2Phone and Phone2PC gateway
- H.323 gatekeeper
- H.323 multiple endpoint server
- H.323SIP Proxy
- SIP session border controller
- SIP router
- SIP registration server
- IAX server and/or client
- IP Telephony server and/or client
- Call center server
- IVR engine
- Prepaid and/or postpaid cards system
<<lessWhile currently focused on Voice over Internet Protocol (VoIP) and PSTN, its power lies in its ability to be easily extended.
Voice, video, data, and instant messaging can all be unified under Yates flexible routing engine, maximizing communications efficiency and minimizing infrastructure costs for businesses.
Yate can be used as a:
- VoIP server
- VoIP client
- VoIP to PSTN gateway
- PC2Phone and Phone2PC gateway
- H.323 gatekeeper
- H.323 multiple endpoint server
- H.323SIP Proxy
- SIP session border controller
- SIP router
- SIP registration server
- IAX server and/or client
- IP Telephony server and/or client
- Call center server
- IVR engine
- Prepaid and/or postpaid cards system
Download (1.1MB)
Added: 2007-04-16 License: GPL (GNU General Public License) Price:
923 downloads
CheeseMusic Engine 1.0.1
The CheeseMusic engine is the core to most of the cheesetronic audio tools. more>>
The CheeseMusic engine is the core to most of the cheesetronic audio tools.
CheeseMusic Engine is a flexible and powerful set of components designed to aid in the programming of audio software.
Main features:
- Very fast fixed point mixing/resampling engine. (tops around 200 voices on my duron 850mhz)
- Support for custom Effect Buffers (and LADSPA too).
- Abstract DSP/MIDI layers with support for ALSA/JACK/OSS/Win32
- Support for synthesis helpers such as envelopes,LFOs,filters,ringbuffers,interpolators,declickers,etc
- GUI-Agnostic support thru "Property Bridges" with GTKmm and QT support (but most support is for Qt)
- Qt widgets for configuring many components, such as:
- Audio/Midi drivers.
- Resampler.
- Effect Buffers/Routing.
- Envelopes/LFO,etc.
- Midi-Input managers, with voice/bank/channel allocation and integration to the mixing engine
- Powerful framework for writing MIDI Synthesizers, as programming at voice level is only needed.
<<lessCheeseMusic Engine is a flexible and powerful set of components designed to aid in the programming of audio software.
Main features:
- Very fast fixed point mixing/resampling engine. (tops around 200 voices on my duron 850mhz)
- Support for custom Effect Buffers (and LADSPA too).
- Abstract DSP/MIDI layers with support for ALSA/JACK/OSS/Win32
- Support for synthesis helpers such as envelopes,LFOs,filters,ringbuffers,interpolators,declickers,etc
- GUI-Agnostic support thru "Property Bridges" with GTKmm and QT support (but most support is for Qt)
- Qt widgets for configuring many components, such as:
- Audio/Midi drivers.
- Resampler.
- Effect Buffers/Routing.
- Envelopes/LFO,etc.
- Midi-Input managers, with voice/bank/channel allocation and integration to the mixing engine
- Powerful framework for writing MIDI Synthesizers, as programming at voice level is only needed.
Download (0.45MB)
Added: 2005-12-02 License: GPL (GNU General Public License) Price:
1421 downloads
NLog 0.95
NLog is a .NET logging library designed with simplicity and flexibility in mind. more>>
NLog is a .NET logging library. NLog is designed with simplicity and flexibility in mind. With NLog you can process diagnostic messages emitted from any .NET language, augment them with contextual information, format them according to your preference and send them to one or more targets.
The API (application programming interface) is similar to log4net, and the configuration is very simple. NLog uses a routing table while log4net uses a logger hierarchy with attachable appenders. This makes NLogs configuration very easy to read and maintain.
NLog supports .NET, C/C++ and COM interop API so that all your application components including legacy modules written in C++/COM can send their messages through a common log routing engine.
The .NET API is very fast at filtering messages, so that you can keep your logging instructions in code and let NLog filter them out at runtime. NLog can filter out as many as 150 million logging instructions per second on a single-CPU 1.6 GHz laptop. Add that to asynchronous processing and other wrappers and youll get a very powerful and scalable logging tool.
Enhancements:
- This release adds a new Trace level, which is more verbose than the Debug level.
- It adds a new conditions language that lets you write powerful filtering conditions while keeping the syntax natural and readable.
- It adds a global log threshold and configurability at the config level.
- It adds support for variables in configuration files.
- It adds an infrastructure for compound targets and wrapper targets.
- It adds detailed documentation with examples for many targets, both on the Web site and in the help file.
<<lessThe API (application programming interface) is similar to log4net, and the configuration is very simple. NLog uses a routing table while log4net uses a logger hierarchy with attachable appenders. This makes NLogs configuration very easy to read and maintain.
NLog supports .NET, C/C++ and COM interop API so that all your application components including legacy modules written in C++/COM can send their messages through a common log routing engine.
The .NET API is very fast at filtering messages, so that you can keep your logging instructions in code and let NLog filter them out at runtime. NLog can filter out as many as 150 million logging instructions per second on a single-CPU 1.6 GHz laptop. Add that to asynchronous processing and other wrappers and youll get a very powerful and scalable logging tool.
Enhancements:
- This release adds a new Trace level, which is more verbose than the Debug level.
- It adds a new conditions language that lets you write powerful filtering conditions while keeping the syntax natural and readable.
- It adds a global log threshold and configurability at the config level.
- It adds support for variables in configuration files.
- It adds an infrastructure for compound targets and wrapper targets.
- It adds detailed documentation with examples for many targets, both on the Web site and in the help file.
Download (1.0MB)
Added: 2006-02-21 License: BSD License Price:
1344 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above routing search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
