Or you are using a third party-controlled server with direct internet access to make home IP accessible
1. No ISP firewall blocking unsolicited incoming traffic
Do you configure WG to use persistent keepalives
I have cable with a theoretically dynamic DNS but it's changed once in >4 years.
The point of the comment was that cannot just assume it never changed unless monitoring it contiuously.
If your DNS provider has an API, this is probably the very first example in the docs.
And that's really NAT, not a firewall, so nothing is "blocked".
You do get public IPv6 addresses from some ISPs, though.
Sure enough, look what appears on HN front page a few hours later...
https://news.ycombinator.com/item?id=22167627
People's home public IP addresses are not universally reachable/accessible^1 from the internet. It varies.
What does "reachable/accessible" mean. It means that transferring a file would be as easy as person A typing something like
nc -lnp [port] [person A home IP adddress] < file
nc -w1 -vvn [person A home IP address] [port] > file
Regardless of what anyone says in an HN comment, in the real world, people at home are sometimes behind firewalls, or other software that performs NAT, that are running on computers that do not belong to them and are not under their control.
That's why WG has persistent keepalives. No one answered that question.
Can you tell us anything about how you obtained one
1. No ISP firewall blocking unsolicited incoming traffic
You only get one, so you typically NAT everything, port 25 is blocked and often port 80 is as well, but that's about it.
I have run services on port 443 on Optimum and FiOS for years.
IP addresses don’t change frequently. Usually what happens is there will be some maintenance and you’ll end up with a new IP because you lost the lease in the interim. If you keep your equipment on though you can have the same reachable IP address for years.
I use a dynamic DNS service so this is rarely a big deal.
Not sure why this is so hard for you to grasp. You keep arguing, for what reason?
What is Optimum, FIOS.
WG does not work over TCP.
Try running a UDP-only DNS server from home on some random port. If you know the port can you reach it via UDP from the internet.
A TCP service listening on port 443 on an ISP customer's IP address in the US might be reachable from the internet. However, this topic is neither TCP nor port 443 nor is it restricted to just the US.
> Try running a UDP-only DNS server from home on some random port.
No reason to run DNS.
However, I run openvpn udp between three houses (fios, Comcast, cablevision) for nearly 15 years. It’s pretty common, works fine.
Again in the US... cable, fiber and dsl internet service comes with a public mostly unfiltered IPv4 address, the address is dynamic but in practice it is extremely stable.
End of story.
No idea why you’re acting like such an imbecilic tool in this thread. The whole time I have mentioned that this is the case for major US “landline” ISPs. Yes there are plenty of counterexamples, not sure what point you’re trying to prove.
Hmmm, it was a yes or no question. Are you suggesting it work would if you did.
I have no reason to run DNS on a home internet connection. What would a sane use case be? They don’t block it because it would be stupid to use it anyway.
Ports that are typically blocked include 67, 139, 161, 520, 547, etc.. ie dhcp, rip, smb, snmp... none of them are any great loss to those that want to run a vpn.
Running a VPN or ssh service is another story and it works fine both TCP and UDP.
I had a Time Warner cable modem for 15 years and the IP address would only change after a sustained power outage. Usually had the same IP for a year.
My AT&T Fiber IP address has not changed in 2 years and that is even after 2 power outages of about 12 hours.