From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Port Forwarding Problem
Date: Fri, 25 Apr 2008 14:49:47 -0500 [thread overview]
Message-ID: <481235DB.7070705@riverviewtech.net> (raw)
In-Reply-To: <4810DCB9.8070208@kiusys.com>
On 4/24/2008 2:17 PM, Ivan Hernandez wrote:
> On a LAN a set of computers in the range 192.168.1.x that have already
> assigned a default gw 192.168.1.1 run an application that must connect
> to an internet server 234.56.78.9 to the tcp port 4444 much like a
> telnet app.
>
> The 192.168.1.1 gw does no serves internet in any way so the
> 192.168.1.x network is isolated except for 1 computer, that has 2 nic's
> and is the computer running linux that i need to configure.
<snip>
Is there something preventing you from moving your Linux system to
192.168.1.1, i.e. a device that is already there?
If there is a device at 192.168.1.1 what sort of control do you have
over it? Can you configure it to use 192.168.1.2 as its default gateway?
I would make your Linux system be the default gateway for the
192.168.1.x network, either by being 192.168.1.1 or by having
192.168.1.1 use 192.168.1.2 as its default gateway.
This way, your client systems can use 192.168.1.1 as the default gateway
for the network, even if it is by way of 192.168.1.2.
Grant. . . .
next prev parent reply other threads:[~2008-04-25 19:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 19:17 Port Forwarding Problem Ivan Hernandez
2008-04-25 19:49 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-16 12:53 Port forwarding problem Carlos Mtz-Troncoso
2010-10-16 13:13 ` Pascal Hambourg
2010-10-16 13:19 ` Carlos Mtz-Troncoso
2010-10-16 13:37 ` Pascal Hambourg
2010-10-16 14:01 ` Carlos Mtz-Troncoso
2010-10-16 18:19 ` Pascal Hambourg
2005-07-18 5:17 Port Forwarding Problem George Esperanza
2005-04-15 10:36 Julian Labuschagne
2005-04-15 10:34 Julian Labuschagne
2005-04-15 8:40 ` Samuel Díaz García
2005-04-15 11:23 ` Julian Labuschagne
2005-04-15 14:32 ` Taylor, Grant
2005-04-15 14:40 ` Jason Opperisano
2003-02-25 18:06 Tom Smith
2003-02-25 20:14 ` Willi Dyck
2003-02-25 21:53 ` Tom Smith
2003-02-26 3:20 ` Arnt Karlsen
[not found] ` <3E5C3DEE.70104@openadventures.org>
2003-02-26 14:07 ` Arnt Karlsen
[not found] <001601c2d1fa$669894e0$990da8c0@..153.service>
2003-02-11 19:11 ` Port forwarding problem DarKRaveR
2003-02-11 19:14 ` Rob Sterenborg
2003-02-11 18:21 Danila Octavian
2003-01-29 0:56 port " Ian McBeth
2003-01-28 8:14 oarojo
2003-01-29 1:21 ` Arnt Karlsen
2002-11-14 4:29 Port " Tom Elsesser
2002-11-24 20:40 ` Joel Newkirk
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=481235DB.7070705@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox