On 21 Jan 2001, at 18:19, Mike Noyes wrote:
> Is rinted usefull?
>
> >Date: Sat, 20 Jan 2001 13:12:22 -0800
> >From: John Wenger <[EMAIL PROTECTED]>
> >To: Linux Router Project <[EMAIL PROTECTED]>
> >Subject: [LRP] rinetd - a TCP port redirector: High Performance Holes
> >through Firewalls for Internal Servers
It was probably quite useful with Linux 2.0, but not with Linux 2.2
with ipmasqadm:
# ipmasqadm portfw -h
Usage: portfw -a -P PROTO -L LADDR LPORT -R RADDR RPORT
[-p PREF] add entry
portfw -d -P PROTO -L LADDR LPORT [-R RADDR RPORT]
delete entry
portfw -f clear table
portfw -l list table
portfw <args> -n no names
PROTO is the protocol, can be "tcp" or "udp"
LADDR is the local interface receiving packets to be forwarded.
LPORT is the port being redirected.
RADDR is the remote address.
RPORT is the port being redirected to.
PREF is the preference level (load balancing, default=10)
#
However, the general principle has proved to be quite useful here:
recently replaced an overpowered and potentially insecure firewall
system (full Red Hat install) with a simpler and smaller system
(Oxygen). The security gains were tremendous, but now the
former "servers" located on the firewall system are behind the
firewall - so I just port-forward to the old system. Nice.
--
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
