From: David A. Bandel david@pananix.com
To: lartc@vger.kernel.org
Subject: [LARTC] routing
Date: Wed, 03 Jan 2001 12:37:31 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416817@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416816@msgid-missing>
<PRE>Spyros Dimas wrote:
><i>
</I>><i> Hello and Happy New Year!
</I>><i> We have a LAN with 2 interfaces. One is configured with addresses
</I>><i> 192.168.0.x (pseudo-addresses) and other one with real addresses, so we
</I>><i> use ip-masquerade. But we would like one of workstation witch has a
</I>><i> address 192.168.0.5 to have a real address, such us 194.219.85.4, on the
</I>><i>
</I>><i> first interface or on the second. Could you tell us how we can do it. Or
</I>><i> if you have
</I>><i> another idea. Thanks.
</I>
This is really an issue for your firewall/masquerade software. If you
are masquerading using Linux and either ipchains (2.2.x) or iptables
(2.4.x) it's easy.
In either case, your firewall/masquerade server needs to have
194.219.85.4 aliased on the external interface, then:
2.2.x:
get ipmasqadm and set up a portforward from the masq server to the
workstation. Assuming you want to forward only port 80, the following
will work:
ipmasqadm portfw -a -P tcp -L 194.219.85.4 80 -R 192.168.0.5 80
better:
2.4.x:
use iptables and runthe following:
iptables -t nat -A PREROUTING -d 194.219.85.4 -p tcp --dport 80 -j DNAT
--to-destination 192.168.0.5:80
With iptables you can easily omit the port stuff so everything passes
(just like the workstation is on the Internet) or qualify your matches
with -m multiport and select several individual ports or a range (or
ranges) of ports.
Ciao,
David A. Bandel
--
Focus on the dream, not the competition.
-- Nemesis Racing Team motto
*** sent via a Linux 2.4.0-test12 system ***
</PRE>
next prev parent reply other threads:[~2001-01-03 12:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 11:13 [LARTC] routing Spyros
2001-01-03 12:37 ` David [this message]
2001-01-05 12:25 ` Junus
2001-01-05 12:33 ` Junus
2001-07-06 14:03 ` [LARTC] Routing Dave Miller
2001-07-06 15:01 ` Arthur van Leeuwen
2001-07-06 15:18 ` Dave Miller
2001-07-07 6:33 ` Deepak singhal
2001-07-07 18:24 ` Arthur van Leeuwen
2001-07-07 18:33 ` Dave Miller
2001-07-07 18:37 ` Arthur van Leeuwen
2001-12-25 4:58 ` [LARTC] routing Daniel Wittenberg
2001-12-25 12:16 ` bert hubert
2002-10-30 12:57 ` [LARTC] Routing Jose Sebastiao Martins
2002-10-30 15:57 ` Martin A. Brown
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-98373940416817@msgid-missing \
--to=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.