4/26 I have one IP address on my DSL line. I have three computers
on my LAN. I want to be able to telnet into any of these from
an outside IP address. How do I do this? [Question re-phrased]
[Does anyone know of a product that can route more than one domain
on one ip? I know this is possible with virtual hosting. Im trying
to set up three computers I can telnet to on my DSL line, which only
comes with one static ip.]
\_ This question makes no sense. What you've seen is web virtual
hosting but given that your DSL provider only provided you one
IP address you cannot create 3 new IP addresses visible to the
outside world. The best you can do is create a subnet
(192.168.*.*) and have a computer (Linux IPmasq, NAT, WinGate,
whatever) perfrom some sort of network translation. The reason
why web server virtual hosting works is because it's really
using the same IP address but the URL that the web browser sends
to the server hints to which directory to look at. For example,
suggest NAT software in which the telnet remaps are
if I have a web page at http://www.dnai.com/~jondoe I can request that
dnai set up virtual hosting so that when a browser asks for
http://www.jondoe.com it will actually return to the browser
http://www.dnai.com/~jondoe instead (although the person surfing the
web can tell this). How that's done is simply adding a DNS entry
and reconfiguring the web serer. But most services don't do
that. You cannot map a host name to an internal firewall's IP's
port. For example, you cannot create a DNS entry called
<DEAD>ssh-to-scotch.berkeley.edu<DEAD> to map to <DEAD>scotch.berkeley.edu<DEAD>:22.
If you want to be able to telnet to your three internal
computers protected by the firewall, you can setup portforwarding
which is supported by many OS's. So you can have a port listenig
on port 1234 of your firewall so that when you do a
> telnet <DEAD>mydslline.com<DEAD> 1234
it will send all the packets to your internal computer.
\_ I know Win2K server can do this, because I have it working now
with your situation. Incidentally, I asked the same question
on the motd half a year ago and the responses I got were
the equivalent of "huh, fux0r?" and "fux0r me".
\_ Win2K isn't magic - any NAT software can do this, but
you'll have to map different ports to different hosts
(i.e. telnet NAT 23 goes to host a, telnet NAT 123 to
host b, telnet NAT 223 to host c)
\_ Yeah, but Win2K has it nicely dumbed down. Please
suggest software in which the telnet remaps are
easy with the matching OS name. Thanks! =)
\_ uh, the "product" that can "route" more than one domain to
one IP is called "DNS", and that doesn't stand for "Digital
Nervous System" you stooge. -tom
\_ tom, as you've pointed out, the question has some problems.
Nevertheless, you can set up Win2K server to route
telnets to your single DSL IP to an IP in your internal LAN.
\_ the question is stupid and will be deleted in about 20 minutes.
\_ Don't be a doofus. The guy just wants to know how to do
NAT. Just because he doesn't know the exact right question
to ask doesn't make it a stupid question. If he knew
what NAT was he probably wouldn't have had to ask how to
do it.
\_ No he doesn't you doofus. You cannot solve this with
NAT, because he stated he has ONE IP ADDRESS globally.
You need a reverse-proxy, or plug-gw, on a
real operating system.
\_ A real OS, NAT, and DNS and he's fine. WTF's your
problem? _I_ wasn't the one talking about win2k.
\_ Win2K is a real OS. Oh shit, no it isn't. Sorry.
his requirements with NAT.
You might want to actually READ the requirements
this time.
\_ Person A is mad about other people being mad;
Person B is mad about "NAT" term usage.
\_ how about a home gateway? 2 Wire is suppose to come out
with something this spring: http://www.2wire.com
\_ Please tell me of inexpensive, easy port forwarding software
for Windoze|Linux|Slowaris. Thx.
\_ http://coombs.anu.edu.au/ipfilter does a nice job.
Otherwise, freebsd comes with ipfw and natd. Linux
I believe comes with some weird ipmasq stuff. I've
found ipfilter (comes with a component called ipnat)
to be pretty fast and straightforward. -John
\_ Thanks, John! Now if only there weren't so many
root kits lying around for all the Unix boxes.
\_ Did you plan on installing and out-of-date UNIX
base system, with all of the default software
turned on, so one of these rootkits would actually
be a problem?
\_ But of course, you'll be forwarding to port 22, since you
should use ssh instead of telnet. |
http://csua.com/feed/