2
Today I replaced my old router with a new faster router in my home. However, this event appears to have migrated me to carrier-grade NAT'ing by my ISP. I tried with my old router but the same holds true. Along with the change are some annoying aspects, such as DNS resolution appears to be slower. Before the change I used 8.8.8.8 on my router, but no longer appears to be respected as DNS is now handled by my ISP's resolver.
But an even bigger issue now is that my local dev/test environment is impacted networking-wise. For example, my virtualbox VMs that were on a bridge networked all have multiple IPv6 addresses, and internet connectivity is broken. Another strange observation is that even if I power off all my VMs (which were on 10.0.x.x networks), I can ping, and even SSH to a number of 10.0.x.x servers. None of which appear to be mine.
I've read a few posts about people setting up VPN to get control back, and I may setup an openvpn server in my Azure environment. But is there another way? Am I no longer able to use the NAT'ing features of my wireless router?
Thanks for the tips. I did do some more troubleshooting earlier today and came up with a solution I just posted. Not ideal, but I dont care to spend any more time with the TP-link router. – omencat – 2016-07-01T04:51:57.963