debmon/rinetd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Bump

Browse Source
This commit is contained in:
Mario Fetka 2017-04-22 12:14:51 +02:00
parent 9a2ad0d01a
commit 651d338340
3 changed files with 46 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CHANGES
View File

@ -52,4 +52,10 @@ arrays correctly when reallocating memory to
accommodate more connections. Thanks to
Sam Hocevar.
Version 0.62+syslog: added logging to syslog
support (SuSE)
Version 0.62+syslog+bind: added optional
sourceaddress column in configuration file to bind
to a specific local address for outgoing connections
(Lutz Pressler, <lp@SerNet.DE>)

2
debian/changelog vendored
View File

@ -1,4 +1,4 @@
rinetd (0.62.1sam-1) unstable; urgency=high
rinetd (0.62.1sam-2) unstable; urgency=high
* New upstream release.
* This release fixes memory initialisation issues causing erratic

43
rinetd.8
View File

@ -12,7 +12,7 @@
.Sh SYNOPSIS
.Nm /usr/sbin/rinetd
.Sh VERSION
Version 0.62, 04/14/2003.
Version 0.62+syslog+bind, 04/14/2003.
.Sh DESCRIPTION
.Nm rinetd
redirects TCP connections from one IP address and port to another. rinetd
@ -34,7 +34,7 @@ another file is specified using the -c command line option.
Most entries in the configuration file are forwarding rules. The
format of a forwarding rule is as follows:
.Pp
bindaddress bindport connectaddress connectport
bindaddress bindport connectaddress connectport [sourceaddress]
.Pp
For example:
.Pp
@ -64,6 +64,9 @@ service names are defined in the file /etc/services.
Both IP addresses and hostnames are accepted for
bindaddress and connectaddress.
.Pp
The optional sourceaddress can be used to bind to a specific local
address for the outgoing connection.
.Pp
.Sh ALLOW AND DENY RULES
Configuration files can also contain allow and deny rules.
.Pp
@ -111,8 +114,9 @@ is prohibitive. Since rinetd is a single process server, all other
connections would be forced to pause during the address lookup.
.Pp
.Sh LOGGING
rinetd is able to produce a log file in either of two formats:
tab-delimited and web server-style "common log format."
rinetd is able to produce a log output in three ways:
tab-delimited , web server-style "common log format." both are file-based
or as syslog output.
.Pp
By default, rinetd does not produce a log file. To activate logging, add
the following line to the configuration file:
@ -146,6 +150,34 @@ To activate web server-style "common log format" logging,
add the following line to the configuration file:
.Pp
logcommon
to activate syslog output enter the following line to the
configuration file:
syslog facility priority
Example1:
syslog local0 info
in this case all output is logged to the destination configured
in your syslogd config for facility local0 and priority info
Example2:
syslog
in this case everything goes to daemon info
Example3:
syslog wrongfacility wrongpriority
logging to default: daemon info
.Pp
If configured, the local source address is given in square brackets
after the "listening host" entry.
.Sh COMMAND LINE OPTIONS
The -c command line option is used to specify an alternate
configuration file.
@ -187,6 +219,9 @@ IS EXPRESSED OR IMPLIED. USE THIS SOFTWARE AT YOUR OWN RISK.
.Sh CONTACT INFORMATION
See http://www.boutell.com/rinetd/ for the latest release.
Thomas Boutell can be reached by email: boutell@boutell.com
.Pp
Logging to syslog added by SuSE.
Sourceaddress extension added by Lutz Pressler <lp@SerNet.DE>.
.Sh THANKS
Thanks are due to Bill Davidsen, Libor Pechachek, Sascha Ziemann, the
Apache Group, and many others who have contributed advice