Hi. On Sat, 24 May 2014 18:27:28 +0200 Pascal Hambourg <pas...@plouf.fr.eu.org> wrote:
> Reco a écrit : > > > > To keep things simple. Two host can communicate with each other without > > third party (router) only if they have their IPs from the same network. > > No. Only if they share the same broadcast domain (link layer network), > regardless of IP addressing. Usually IP subnetting matches link layer > network divisions, but not always. A simplification always steps away from the truth. You're right, of course. Now, if only you could explain all this in simple words to the OP :) > > That can greatly simplify things if your ISP is using NAT with some > > kind of port redirection. Meaning, you obtain your IP as before, and > > they did all the job already. > > Huh ? NAT does not make things simpler but more complicated ! For the one who maintains it - it is definitely complicates things. For the common user network topology is irrelevant (as many other things do). For the specific task discussed in this thread (obtaining ssh access via the public IP) an appropriate network configuration at ISP's level (most probably including NAT for the end users) simplifies things for the OP. > What would be the benefit of using NAT here ? The obvious benefit for the ISP lies in not providing every ISP's customer with costly public IP while using network equipment coming straight from '80s. The benefit for the ISP's user lies in obtaining NATted IP (and stuff) via DHCP exactly the same way as before, yet 'magically' gaining access to the home network from certain ISP-provided public IP. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140524210332.94eb05cbf197f1ca40812...@gmail.com
