[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: [ale] IPCHAINS
- From: jonathan at xcorps.net (Jonathan Rickman)
- Date: Tue, 29 May 2001 21:45:43 -0400 (EDT)
Without further details about your specific setup or skill level, I
suggest reading the man page for ipchains as well as ipmasqadm so that
you'll be ready to answer the questions that will probably be asked. Once
you're armed with that basic knowledge email me off-line and I'll give you
a quick class. We'll CC the pertinent stuff to the list. Or...if I totally
misunderstood you and you are a true kung fu master looking for a quick
tip, give this a shot.
after enabling ipforwarding...and assuming you have the mfw module.
ipchains -I forward -p tcp -d 192.168.0.1/32 -s 192.168.0.2/32 22
ipchains -I input -p tcp -y -s 0/0 -d 192.168.0.1/32 4000 -m 2
ipmasqadm mfw -I -m 2 -r 192.168.0.2 22
or something to that effect...that's off the top of my head so double
X Corps Security
On Tue, 29 May 2001, Jason Lynn wrote:
> Say I wanted to have all incomming ssh traffic to port 4000 on 192.168.0.1
> redirected to port 22 on 192.168.0.2...
> Is it possible to redirect to a port on another computer with IPCHAINS? If
> not, what is the best way to accomplish this task?
> Thanks again,
> Get your FREE download of MSN Explorer at http://explorer.msn.com
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.