[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: how to Port Forward



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Shahzad Chohan wrote:

|I'll also like to add to my previous mail.
|
|The only reason I'm not going to use NAT is becuase I believe that you
|can't use NAT to port forward on the same subnet, i.e port forward a
|host with ip 192.168.1.1 22 to 192.168.1.2 22.
|
|If I am wrong then can someone please show me how to do it with NAT.
|
|Thanks
|Shaz
|
|On 6/9/05, Alexander Dalloz <ad+lists uni-x org> wrote:
|
|>Am Do, den 09.06.2005 schrieb Shahzad Chohan um 13:41:
|>
|>>I'd like to port forward the ssh port from one internal machine to
|>>another, is there a way to do this with iptables without using NAT?
|>
|>>Shaz
|>
|>You may look for SSH's own possibility too port forward. google for "ssh
|>port forward" and you get many hints.
|>
|>Alexander
|>
|>
|>--
|>Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
|>legal statement: http://www.uni-x.org/legal.html
|>Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.27_FC2smp
|>Serendipity 15:39:22 up 16 days, 14:17, load average: 0.04, 0.09, 0.13
|>
|>
|>BodyID:41521057.2.n.logpart (stored separately)
|>
|>
|
No, you have to use ipnatctl to perform the functions you want.  NAT.
iptables does not support this from the HOWTO information online.

Why can't you just tell everyone that you need to use 192.168.1.2
instead of the 192.168.1.1 they were using before.  This would
eliminate the need to NAT the internal addresses (which is also
possible to do).

James

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCqFDhkNLDmnu1kSkRAu7vAJ9+D3v5D/cIM2k0QOAFDZYY+ALxcgCfU6xS
i6Sa37+Die1eFaXYI8TmyWA=
=idRN
-----END PGP SIGNATURE-----



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]