Re: Why does ssh keep hanging

Jorgen Grahn <grahn+nntp@xxxxxxxxxxxxxx> wrote:
It may hide part of the issue, but they still cannot run any servers,
use protocols which aren't made to work with normal IPv4 NAT, and so
on.

I was referring to the Split DNS scenario (having moved on from 1:1
NAT slightly), picking up your comment about it feeling strange to
have two addresses for the same host. From that perspective - and
ignoring many:1 NAT for a moment, I have to disagree with you about not
running servers. My web server here is 192.168.132.252 but you see it
as 188.222.203.136. In both instances we can use the same DNS name (www)
and it will work correctly.

In a corporate configuration this would be (should be) implemented with
1:1 NAT not many:1 NAT.

However, IMO this is getting rather off topic for the original subject
matter.

Cheers,
Chris
.

Relevant Pages

  • Re: Why does ssh keep hanging
    ... I was referring to the Split DNS scenario (having moved on from 1:1 ... NAT slightly), picking up your comment about it feeling strange to ... running servers. ...
    (comp.os.linux.networking)
  • Re: FW NAT and Keep State
    ... >> I have been told that with NAT there is no real need to have any ... >> inbound protection as NAT takes care of it. ... To his credit I think he was referring to incoming protection rather ... the local network. ...
    (comp.os.linux.networking)
  • Re: Slippery intruder -- please advise
    ... > It's a pet peeve that people keep referring to NAT as a firewall. ... To add to the confusion, there really are products that are ...
    (comp.security.misc)