Why does Wireguard no longer work when it is behind new router?

I have had a RPI set up for years behind a NAT where I lived, using dynamic DNS. If it matters, my ISP was Verizon. I moved, and am using a new router/cable modem combo (from Netgear). My ISP is now Comcast. My NAT dynamic address range changed from 192.168.1.* to 192.168.0.* , and I updated my client's DNS settings to reflect that (not that it matters for this question, per se). I set up port forwarding and a static IP for my RPI, and expected everything to Just Work™. Indeed, I can connect my device, and ping both ways to my server ( 10.7.0.1 ←→ 10.7.0.5 ), but from the client ping 8.8.8.8 n

Question by Nate on Super User, licensed CC BY-SA. We show a short excerpt and link to the original thread as credit.