From: Henning Wangerin <post+050629@henning.wangerin.dk>
To: netfilter@lists.netfilter.org
Subject: NAT problems forwarding from a routed subnet.
Date: Tue, 13 Jun 2006 15:20:09 +0200 [thread overview]
Message-ID: <1150204810.16144.39.camel@server.ltsp> (raw)
Hi!
I'm in control of a larger WLAN network, where we are connected via
a /30 network, and have a routed /28 network that we are going to
forward ip by by to some of our users.
Each location have an 10.128.x.1/24 network where eg 10.128.x.250 is
natted to 10.10.x.250 on my LAN.
That works fine. I can ssh from the WLAN-network to 10.128.x.250 and get
access to the desired server.
I need to get access the same way from the internet, so eg a.b.c.50 is
forwarded to 10.128.x.250.
I'tried multiple solutions, but nothing works.
Any tips/links on how to get it to work?
BTW the network is described here:
http://www.olsr-net.dk
--
Henning Wangerin <post+050629@henning.wangerin.dk>
next reply other threads:[~2006-06-13 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 13:20 Henning Wangerin [this message]
2006-06-13 19:07 ` NAT problems forwarding from a routed subnet Alexandru Dragoi
2006-06-13 22:47 ` Henning Wangerin
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=1150204810.16144.39.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox