All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Wangerin <post+050629@henning.wangerin.dk>
To: netfilter@lists.netfilter.org
Subject: Re: NAT problems forwarding from a routed subnet.
Date: Wed, 14 Jun 2006 00:47:52 +0200	[thread overview]
Message-ID: <1150238872.3585.3.camel@server.ltsp> (raw)
In-Reply-To: <448F0D00.50306@zoomnet.ro>

On Tue, 2006-06-13 at 22:07 +0300, Alexandru Dragoi wrote:
> You will do same as in 10.128.x.250->10.10.x.250, but on the next router
> (with nat capabilityes) to internet. 

Yeah.
The moment you call for help, the solution pops into ones face.

The natting on the client-box is done via scripts, and I counldn't
figure out witch parts to pick out.

It's up and running find.

> By the way, that link is not working.

Hmm. Should be.

Must have been a temporary outage of the old line :-(
That's one more reason the get the new setup running quickly!

-- 
Henning Wangerin <post+050629@henning.wangerin.dk>


      reply	other threads:[~2006-06-13 22:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 13:20 NAT problems forwarding from a routed subnet Henning Wangerin
2006-06-13 19:07 ` Alexandru Dragoi
2006-06-13 22:47   ` Henning Wangerin [this message]

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=1150238872.3585.3.camel@server.ltsp \
    --to=post+050629@henning.wangerin.dk \
    --cc=netfilter@lists.netfilter.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.