At a loss figuring out if an IP is on LAN or INET

  • Thread starter Thread starter Terry Olsen
  • Start date Start date
I originaly thought about that, but then I thought about the fact that
the NAT we think about of multiple machines sharing the same IP is in
fact NAPT, whilst true NAT means that each machine could have a
different external IP whilst all being on the same internal network.

True, though in practice I think it would be awfully rare to have
multiple desktop machines behind "true NAT" firewalls.

The
only work around I could see was to have one client try to talk to the
other client internaly first to see if a connection could be found,
hence the use of the shared secrect. Think about it you probaly want two
shared secrects, one from A and one from B so that they both know they
are talking to the right machine, whilst in my first idea only A knew it
had the right computer, B does not (B could have connected to a random
computer that just accepted the connection).

Agreed.

Ideally you'd also want to handle situations where A can initiate a
connection with B, but B can't initiate a connection with A. But I
suspect this is all getting pretty far afield from the OP's needs, which
I don't think included server registration at all.
 
Back
Top