All of lore.kernel.org
 help / color / mirror / Atom feed
From: striscio striscio@preciso.net
To: lartc@vger.kernel.org
Subject: [LARTC] NAT+portfw failure
Date: Wed, 28 Feb 2001 13:14:21 +0000	[thread overview]
Message-ID: <marc-lartc-98373940417065@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940417054@msgid-missing>

<PRE>On Tuesday 27 February 2001 04:12, Paul Wouters wrote:

On Tuesday 27 February 2001 04:12, you wrote:

I'm not sure I understood the problem, but I have a similar situation (an 
ADSL router with public address a.b.c.d that forwards everything coming in to 
a single host THOR with ip 172.17.32.91). The router can't reach other 
internal addresses (only 172.17.32.91).
This host THOR has a second network card (ip 172.18.32.99) and acts also as 
gateway for the LAN.
To make internal hosts reach adress a.b.c.d  I put an ip alias to the second 
eth on THOR that answers on the address a.b.c.d
In that way:
- external host talk to the router which forwards on the internal host THOR
- internal host try to connect to a.b.c.d and receive answer from THOR. 

If the router would be able to handle packets addressed to it and coming from 
internal network this werid trick wouldn't be necessary, but actually THOR 
would answer to internal and external call both in the actual situation and 
in the perfect world. 

Hope this may help you. If this soluiton has something wrong or can be done 
better, please help me.

         have a good day

         gianpaolo



</PRE>

  parent reply	other threads:[~2001-02-28 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27  3:12 [LARTC] NAT+portfw failure Paul
2001-02-27  8:53 ` Arthur
2001-02-27 17:56 ` Paul
2001-02-28  4:06 ` Largo
2001-02-28 13:14 ` striscio [this message]
2001-03-02 17:24 ` Paul

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-98373940417065@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.