From: Fabian Gervan <fabian1@inter-k.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] routing with 2.4 kernel
Date: Fri, 26 Oct 2001 11:45:09 +0000 [thread overview]
Message-ID: <marc-lartc-100411065110257@msgid-missing> (raw)
Hello
I am new with 2.4 kernel an have trouble to setup routing as I had in
2.2 kernel:
My setup:
server1 eth0:200.47.43.240 (FTP SERVER)
server2 eth0: 200.47.43.241 (MASQ BOX)
eth1: 10.2.0.1
client1: 10.2.0.2
client2: 10.2.0.3
clientN: 10.2.0.nnn
I want to clients 10.2.0.0/16 connect to my FTP server with 10.2 IP (no
internet IP).
200.47.43.240 is a linux 2.2 kernel, it already have a right setup for
routing to 10.2.0.0/16 clients, I have trouble with 200.47.43.241
(linux 2.4).
My actual setup: (in 200.47.43.241)
iptables -A FORWARD -s 10.2.0.0/16 -d 200.47.43.240 -j ACCEPT //it
doesn't work)
iptables -t nat -A POSTROUTING -s 10.2.0.0/16 -j MASQUERADE
--
Saludos,
Fabian Gervan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-10-26 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 11:45 Fabian Gervan [this message]
2001-10-27 1:54 ` [LARTC] routing with 2.4 kernel Greg Scott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-100411065110257@msgid-missing \
--to=fabian1@inter-k.com.ar \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.