From: "Marcelo Moreira" <marcelom@qualitau.com>
To: James O'Gorman <james@netinertia.co.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: SSH and NAT
Date: Mon, 24 Mar 2003 17:08:19 -0800 [thread overview]
Message-ID: <037001c2f26b$05ef5a70$a828a8c0@qualitau.com> (raw)
In-Reply-To: 20030324224026.GN8391@netinertia.co.uk
> > The IP packet only contain some primitive information - if you wish to
deal
> > with names, then you have to use DNS. You can't store the name
information in
> > the packet header.
>
> Not quite sure what you mean by this? I've set up the DNS so that box1
> and box2 both point to an IP (albeit the same one as I only have the
> one) - an A record on the DNS server.
Ok. Let me see if I can explain this a little bit better.
An IP packet has only the numeric address information on it.
So essentialy, a ssh packet to box1 and another to box2 are
the same (except for time, sequence, flags, etc).
The DNS information is not on the IP header at all. It is just
another protocol that is used to map names to numeric addresses.
> > I can recommend that you read about IP headers if you wish to know more
about
> > the construction of these magic little packets :-)
>
> I understand bits of it, but obviously not enough. :)
> Guess I should get reading!
Yes, I guess you should also. In fact, get the definitive IP guide:
TCP/IP Illustrated, Vols I II and III. Author is Stevens.
Have fun on your reading...
Marcelo.
prev parent reply other threads:[~2003-03-25 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030324182922.GF8391@netinertia.co.uk>
2003-03-24 20:27 ` SSH and NAT Brad Morgan
[not found] ` <20030324203629.GH8391@netinertia.co.uk>
2003-03-24 22:14 ` Kim Jensen
[not found] ` <20030324224026.GN8391@netinertia.co.uk>
2003-03-25 1:08 ` Marcelo Moreira [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='037001c2f26b$05ef5a70$a828a8c0@qualitau.com' \
--to=marcelom@qualitau.com \
--cc=james@netinertia.co.uk \
--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