I found that there was an entry for our external IP, which may well be the problem. I thankfully had the ability to change the external IP our internal postfix server NATs to to something else, and voila! the messages go through just fine. I know not everyone has that flexibility to select another IP

Theoretically you could assign an address from your servers public IPv6 prefix directly to the client so no NAT would be necessary. This would be the ideologically "correct" way to do IPv6, but may be problematic to do when your servers prefix regularly changes.

The diagram raises an interesting question which you may not have thought about before. How does all the information from the internet get to the right device inside the network? If you visit howtogeek.com on your laptop how does it end up on your laptop and not your son’s desktop if the public-facing IP address is the same for all devices? Advertisement pagespeed.lazyLoadImages.overrideAttributeFunctions();tmntag.cmd.push(function(){tmntag.adTag('purch_Y_C_0_1', false);}); This is thanks to a wonderful bit of routing magic known as a Network Address Translation (NAT).

Since onion services can receive incoming connections even if they are behind a router doing network address translation (NAT), TorChat does not need any port forwarding to work.

Network round-trip latency

ntarily made to Thomas R. Gray, in the prison where he was confined. and acknowledged by him to be such when read before the Court of Southampton, with the certificate, under seal, of the Court convened at Jerusalem, November 5, 1831, for his trial. Al