Free ip services software for linux

Logging Services project is intended to provide cross-language logging services for purposes of application debugging and auditing.
We should also mention that thanks to the relentless efforts of many developers, we have a basic level of interoperability between the following projects:
- Log4Cxx (c++)
- Log4j
- Log4Net
- Log4Perl
- Log4PHP
- Log4PLSQL
- JDK1.4s util.logging framework
There is still much work ahead bringing in the various projects to work together within the Logging Services Project. The process is likely to take a little while. In the mean time, we will continue to do what we like best, that is developing open source software.
This is a project of the Apache Software Foundation (ASF). Like all Apache projects, we encourage a collaborative, consensus-based development process. We offer an open and pragmatic software license, and we strive to create software of the highest quality. The ASF is organized into several projects, which like Logging Services project may contain multiple sub-projects.

The QDS library allows Qt applications to access features provided in common desktop APIs in a portable way, without requiring dependencies on any desktop platform library.
This is especially useful for applications targeting the Unix desktops, because Qt/X11 is very generic and only provides features it can implement on all sub platforms. All library code is licenced under 2-clause BSD licence.
Service implementations are loaded from plugins which link to the respective desktop libraries. The plugin to use can be specified on the applications commandline, in the QDS configuration file or QDS can try to autodetect the currently running platform.
Enhancements:
- Autodetection to use GNOME plugin in case GNOME_DESKTOP_SESSION_ID is set
- Replaced the primitive example application with a simple but network aware text editor application
- Support for wildcards in mailcap entries

PHP P10 Oper Services project is a small IRCD operator services written in the PHP scripting language.
It supports levels, and it uses a database. It currently supports the IRCU P10+ IRC server and the PostgreSQL database.
Enhancements:
- PHP Oper Services Alpha 1 PL1 This is a very early release of PHP Services and note that it is an Alpha Release.

IRC Services are Services for IRC Networks (or just Services for short) provides for definitive nickname and channel ownership, automatic channel mode setting, memo (short message) storage and retrieval, and greater IRC operator control over the network.
Main features:
- Nickname management. Services allows users to "register" nicknames, and will prevent users other than the registrant from using them. Services also maintains information about each registered nickname, including the last time the nicks owner was online as well as a URL and E-mail address that can be set by the user.
- Channel management. Like nicknames, Services allows users to register channels as well. A channels owner can give privileges to other users of the channel, such as auto-opping or the ability to set various channel options, or conversely deny other users the ability to obtain channel operator privileges or even enter the channel altogether. Services will remember the topic on the channel even after the last user leaves, and can automatically set modes on the channel whenever a user joins it.
- Messages to offline users. Probably every IRC user has gone through the experience of waiting and waiting for someone to come online in order to pass a message along or ask a question. Services alleviates this with a "memo" system, allowing users to leave messages for other users even if the recipient is not online at the time; the recipient will be notified of the memo the next time they log on.
- Centralized network control. Services includes features which allow IRC operators greater control over the IRC network through a single point, and also defines multiple privilege levels for IRC operators with respect to Services itself. For example, IRC operators with sufficient privileges can use Services to set modes on any channel; it is also possible to ban users or groups of users from connecting to the network entirely, and such bans ("autokills" in Services terminology) will remain active even if a server, or Services itself, splits from the network.
Furthermore, each of these sets of features can be configured or disabled to match individual networks policies.
Whats New in 5.1pre4 Development Release:
- This release corrects various minor issues in the previous beta release and updates the ratbox protocol module to better support current versions of the ircd-ratbox server (note that versions earlier than 2.1 are no longer supported).
Whats New in 5.0.61 Stable Release:
- This release fixes a bug which allows users to crash Services on x86-64 (and potentially other non-x86) platforms.

Serlvers is a set of Erlang modules designed to help in the implementation of IP services (i.e. TCP/IP or Internet servers).

Serlvers consists of a set of behaviours to abstract the internals of each protocol, and other modules to help with the infrastructure.

Serlverss goal is that when making a server, you only need worry about how to store, handle, process, etc. the information instead of the internals of each protocol (to save countless hours of RFC reading).

Installation:

SCons is used to compile and install this package.
First check out the variables you need to set by running:
scons --help

Youll need to set PREFIX, the prefix directory (where Erlang is installed, it contains something like: bin erts-5.4.13 Install lib misc releases usr) and at the same time you set it, itll compile.

Then run:

scons install

to install. You might need sudo or su to reach superuser capabilities.

For example:

$ scons PREFIX=/usr/lib/erlang
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
erl -noshell -run edoc_run files ["src/launcher.erl","src/gen_echo.erl","src/gen_chargen.erl","src/gen_daytime.erl","src/gen_time.erl"] [{dir, "doc/"}] -run init stop
erlc -o src/ src/gen_chargen.erl
erlc -o src/ src/gen_daytime.erl
erlc -o src/ src/gen_echo.erl
erlc -o src/ src/gen_time.erl
erlc -o src/ src/launcher.erl
scons: done building targets.
$ sudo scons install
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
Install file: "src/gen_chargen.beam" as "/usr/lib/erlang/lib/serlvers-0.1.0/ebin/gen_chargen.beam"
Install file: "src/gen_daytime.beam" as "/usr/lib/erlang/lib/serlvers-0.1.0/ebin/gen_daytime.beam"
Install file: "src/launcher.beam" as "/usr/lib/erlang/lib/serlvers-0.1.0/ebin/launcher.beam"
Install file: "src/gen_chargen.erl" as "/usr/lib/erlang/lib/serlvers-0.1.0/src/gen_chargen.erl"
Install file: "src/gen_daytime.erl" as "/usr/lib/erlang/lib/serlvers-0.1.0/src/gen_daytime.erl"
Install file: "src/launcher.erl" as "/usr/lib/erlang/lib/serlvers-0.1.0/src/launcher.erl"
scons: done building targets.
$

IP Traffic Meter is a traffic counter for IPv4 addresses. It uses the DB4 database from Berkeley to keep its counters, the pcap library for monitoring, and the gd library from Boutel to create graphics. The results are displayed in JPEG graphics on an HTML webpage.
Enhancements:
- With ipmeter you can monitor the traffic made by some IPs. It produces daily, weekly, monthly and yearly statistics into jpg graphics. It uses db4 database from Berkeley to keep its internal counters, and gd library from Boutell to create jpg graphic.

Preview is a simple image viewer for GNUstep. It is designed to be easy to use and support GNUstep features such as image design, pasteboard/services, printing, and layout.

Configuration with no services supported script is for a single host firewall configuration with no services supported by the firewall machine itself.

Sample:

# USER CONFIGURABLE SECTION

# The name and location of the ipchains utility.
IPTABLES=iptables

# The path to the ipchains executable.
PATH="/usr/local/sbin"

# Our internal network address space and its supporting network device.
OURNET="10.5.0.0/24"
OURBCAST="10.5.0.255"
OURDEV="eth0"

# The outside address and the network device that supports it.
ANYADDR="0/0"
ANYDEV="ppp0"

# The TCP services we wish to allow to pass - "" empty means all ports
# note: comma separated
TCPIN="ssh,ftp,ftp-data"
TCPOUT="smtp,www,ssh,telnet,ftp,ftp-data,irc,http"

# The UDP services we wish to allow to pass - "" empty means all ports
# note: comma separated
UDPIN="domain"
UDPOUT="domain"

# The ICMP services we wish to allow to pass - "" empty means all types
# ref: /usr/include/netinet/ip_icmp.h for type numbers
# note: comma separated
ICMPIN="0,3,11"
ICMPOUT="8,3,11"

# Logging; uncomment the following line to enable logging of datagrams
# that are blocked by the firewall.
# LOGGING=1

# END USER CONFIGURABLE SECTION
####################################
# Flush the Input table rules
echo -n Flushing forward... && {
$IPTABLES -F FORWARD
} && echo done

# We want to deny incoming access by default.
# echo -n Denying incoming access... && {
# $IPTABLES -P FORWARD drop
# } && echo done

# Drop all datagrams destined for this host received from outside.
echo -n Dropping incoming datagrams... && {
$IPTABLES -A INPUT -i $ANYDEV -j DROP
} && echo done

# SPOOFING
# We should not accept any datagrams with a source address matching ours
# from the outside, so we deny them.
echo -n Preventing spoofing... && {
$IPTABLES -A FORWARD -s $OURNET -i $ANYDEV -j DROP
} && echo done

# SMURF
# Disallow ICMP to our broadcast address to prevent "Smurf" style attack.
echo -n Preventing SMURFs... && {
$IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET -j DROP
} && echo done

# We should accept fragments, in iptables we must do this explicitly.
echo -n Accepting fragments... && {
$IPTABLES -A FORWARD -f -j ACCEPT
} && echo done

# TCP
# We will accept all TCP datagrams belonging to an existing connection
# (i.e. having the ACK bit set) for the TCP ports were allowing through.
# This should catch more than 95 % of all valid TCP packets.
echo -n Accepting valid incoming tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -d $OURNET --dports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done
echo -n Accepting valid outgoing tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -s $OURNET --sports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done

# TCP - INCOMING CONNECTIONS
# We will accept connection requests from the outside only on the
# allowed TCP ports.
echo -n Accepting incoming tcp connections on allowed ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $ANYDEV -d $OURNET --dports $TCPIN --syn -j ACCEPT
} && echo done

# TCP - OUTGOING CONNECTIONS
# We will accept all outgoing tcp connection requests on the allowed TCP ports.
echo -n Accepting outgoing traffic on allowed tcp ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $OURDEV -d $ANYADDR --dports $TCPOUT --syn -j ACCEPT
} && echo done

# UDP - INCOMING
# allow UDP datagrams in on the allowed ports and back.
echo -n Allowing UDP datagrams in on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -d $OURNET --dports $UDPIN -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -s $OURNET --sports $UDPIN -j ACCEPT
} && echo done

# UDP - OUTGOING
# We will allow UDP datagrams out to the allowed ports and back.
echo -n Allowing UDP datagrams out on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -d $ANYADDR --dports $UDPOUT -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -s $ANYADDR --sports $UDPOUT -j ACCEPT
} && echo done

# ICMP - INCOMING
# We will allow ICMP datagrams in of the allowed types.
# echo -n Allowing ICMP datagrams in of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET --icmp-type $ICMPIN -j ACCEPT
# } && echo done

# ICMP - OUTGOING
# We will allow ICMP datagrams out of the allowed types.
# echo -n Allowing ICMP datagrams out of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $OURDEV -d $ANYADDR --icmp-type $ICMPOUT -j ACCEPT
# } && echo done

# DEFAULT and LOGGING
# All remaining datagrams fall through to the default
# rule and are dropped. They will be logged if youve
# configured the LOGGING variable above.
#

# DoS
# enabling Syn-flood protection
echo -n Enabling Syn-flood protection... && {
iptables -A FORWARD -p tcp --syn -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling Furtive port scanner protection
echo -n Enabling Furtive port scanner protection... && {
iptables -A FORWARD -p tcp --tcp-flags SYN,ACK,FIN,RST RST -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling ping of death protection
echo -n Enabling ping of death protection... && {
iptables -A FORWARD -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT
} && echo done


if [ "$LOGGING" ]
then
# Log barred TCP
$IPTABLES -A FORWARD -m tcp -p tcp -j LOG
# Log barred UDP
$IPTABLES -A FORWARD -m udp -p udp -j LOG
# Log barred ICMP
$IPTABLES -A FORWARD -m udp -p icmp -j LOG
fi
#
# end.