9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rgr@sdf.lonestar.org (Rob Ristroph)
To: 9fans@cse.psu.edu
Subject: [9fans] NAT'ing a drawterm connection
Date: Sun, 24 Aug 2003 23:00:55 -0500	[thread overview]
Message-ID: <87oeyepers.fsf@rgristroph-austin.ath.cx> (raw)


I have a cpu/auth server on a private network, which is connected to
the internet via a Linux computer running iptables and masquerading or
NAT'ing as they call it now.

 From that linux box I can drawterm into my Plan 9 cpu/auth server.

I would like to forward the appropriate ports so that someone on the
internet at large can drawterm to my plan 9 machine.

Here was my first attempt:

# Port forwarding to try to make drawterm to Plan 9 machine work
/sbin/iptables -t nat -A PREROUTING -p tcp --dport 567 -i eth0 -j DNAT --to 192.168.1.18:567
/sbin/iptables -t nat -A PREROUTING -p tcp --dport 567 -i eth0 -j DNAT --to 192.168.1.18:17007
/sbin/iptables -t nat -A PREROUTING -p tcp --dport 567 -i eth0 -j DNAT --to 192.168.1.18:17008

However it doesn't work.

Has anyone set this up before ?

If the connections on 170xx are initiated from the Plan 9 side, I
don't need those last two lines, right ?  For simplicity let's presume
the client drawterm has a real IP address.

--Rob



             reply	other threads:[~2003-08-25  4:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25  4:00 Rob Ristroph [this message]
2003-08-25  4:04 ` andrey mirtchovski
2003-08-25  5:15   ` Rob Ristroph
2003-08-25  5:22     ` andrey mirtchovski
2003-08-25  5:26       ` andrey mirtchovski
2003-08-25 12:35         ` Bruce Ellis
2003-08-25 13:11           ` [9fans] " Jim Choate
2003-08-25 13:18             ` andrey mirtchovski
2003-08-25 14:00               ` Jim Choate
2003-08-25 15:24                 ` andrey mirtchovski
2003-08-25 15:46                   ` Scott Schwartz
2003-08-25 15:55                     ` andrey mirtchovski
2003-08-25 17:40                     ` Jim Choate
2003-08-25 16:05             ` matt
2003-08-25 17:37               ` Jim Choate
2003-08-26 11:22                 ` matt
2003-08-28  0:13                   ` Bruce Ellis
2003-08-28  8:21                     ` matt
2003-08-25 13:18           ` [9fans] " Russ Cox
2003-08-25 14:02             ` [9fans] " Jim Choate
2003-08-25 17:52             ` [9fans] " Bruce Ellis
2003-08-26  0:30               ` boyd, rounin
2003-08-28  3:23               ` Russ Cox
2003-08-29  4:32         ` Rob Ristroph
2003-08-29  4:50           ` andrey mirtchovski
2003-08-25 14:53     ` matt
2003-08-26  1:16 Skip Tavakkolian
2003-08-26  1:50 ` boyd, rounin
2003-08-26  4:25   ` Jim Choate
2003-08-26  4:17 ` Jim Choate
2003-08-29  4:39 YAMANASHI Takeshi

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=87oeyepers.fsf@rgristroph-austin.ath.cx \
    --to=rgr@sdf.lonestar.org \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).