From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Speaking of routing....
Date: Thu, 13 Feb 2003 11:52:23 -0500 [thread overview]
Message-ID: <200302131652.h1DGqNM22144@augusta.math.psu.edu> (raw)
I have a question. I have have a CPU server with two interfaces, one
mounted on /net, the other on /net.alt. They're connected to two
networks; on internal, and the other the Internet. I want users who
login to the CPU server to be able to connect to either network
seamlessly; without jumping through hoops. Is that possible? (I know
this question is sort of vague, and I apologize for that, but I'm
pressed for time at the moment).
That is, when they connect somewhere, they shouldn't have to say,
``telnet /net.alt/tcp!foobar''; ``telnet tcp!foobar'' should work
for hosts internal and external. Is that possible? I'm afraid I
haven't looked at the code, as the machine is currently powered down,
and my laptop's battery is dead, and the charger is at home. :-(
- Dan C.
next reply other threads:[~2003-02-13 16:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 16:52 Dan Cross [this message]
2003-02-13 17:03 ` andrey mirtchovski
2003-02-13 17:13 ` Skip Tavakkolian
[not found] <20030213095533.L50666@ >
2003-02-13 22:16 ` Dan Cross
2003-02-13 22:24 ` andrey mirtchovski
2003-02-13 22:27 ` David Gordon Hogan
2003-02-13 23:14 ` Dan Cross
2003-02-13 23:23 ` northern snowfall
2003-02-13 23:24 ` David Gordon Hogan
2003-02-13 23:46 ` Dan Cross
2003-02-14 0:11 ` Russ Cox
2003-02-14 0:17 ` Dan Cross
2003-02-14 0:21 ` David Presotto
2003-02-14 0:29 ` northern snowfall
2003-02-14 0:31 ` Dan Cross
2003-02-14 0:34 ` David Presotto
2003-02-14 0:32 ` David Presotto
2003-02-14 0:44 ` Dan Cross
2003-02-14 0:48 ` David Presotto
2003-02-14 0:50 ` Dan Cross
2003-02-14 0:52 ` David Presotto
2003-02-14 0:57 ` Dan Cross
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=200302131652.h1DGqNM22144@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).