On 2023-04-29 10:13, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-04-28 19:36, Per Jessen wrote:
Carlos E. R. wrote:
On Friday, 2023-04-28 at 09:39 -0700, Lew Wolfgang wrote:
On 4/28/23 09:01, Per Jessen wrote:
Lew Wolfgang wrote:
* avoid problems when the ipv4 pool is exhausted.
But that's why God invented NAT!
NAT is a royal PITA. We accept it because there is, there wasn't, no alternative.
To be honest, I'm not sure whether to agree or not :-) I can't say I have ever had any unresolvable problems with NAT.
Oh, we had to solve them, so we did. For private individuals, it is harder.
I was going to ask you to list some of these harder problems, but it's wayyyy off topic and not overly interesting anyway.
Ver brief, then: private individuals are less likely to have fixed IPs, so we need "hacks" like dynamic dns servers out there. If we need the aid of some hack to traverse NAT (say stun) we have to use the server of somebody else, we can not do it ourselves.
For example, with IPv6 you can send email directly from your machine to somebody else direct, without any intermediate mail server collecting it.
Um, same with IPv4.
If you have routable addresses.
No, that is not necessary.
Technically, I can send a mail from my MUA here on 192.168.77.88 behind NAT directly to any mailserver on public IPv4. Of course, any semi-qualified mail admin will block that due to reverse lookup failure, but that applies to IPv6 too.
Technically, yes, but that is not what I'm suggesting. I'm suggesting sending to your friend "whatever" who is also behind NAT, without using a mail server outside. ...
You don't even need a directory, just type the IP address (I have not tried, it is theory). But I did do VoIP inside the LAN in that manner with IPv4.
Carlos, the same applies to public IPv4/5/6. Like above, I can initiate SIP from my telephone here on 192.168.77.89 behind NAT directly to any VoIP device (on port 5060) on public IPv4.
Yes, but you are using a stun server out there, and a directory out there. Or having to define virtual servers in the routers involved. I'm saying establishing a voip call without registering anywhere (non configured VoIP client software), just by telling the software the address of the other party, perhaps their user name inside that destination host machine.
<anecdote> Twelve-thirteen years ago, I had three people employed in home-office, in Bern, Basel and Solothurn, on their private ADSL lines. They each had a Linksys SPA921 phone - my Asterisk box was behind NAT. It worked exceptionally well (even if I had to dabble with traffic control to keep bandwidth reserved for VoIP). </anecdote>
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)