hey @heynnema and @slangasek thanks so much for your help in this area. i was able to get it working great it appears, here are my steps, please let me know if this makes sense: gist.github.com/ylluminate/1a7a791202beb0d1b4fb81253ada75ac

the only thing that bothers me slightly is that i feel as though the iptables rules may not be robust enough or are doing something not quite right. so many other tutorials and mentions i see for this kind of forwarding seem to be tremendously more complicated... so i'm hoping this is correct and not creating some kind of a problem - somehow...

so far it seems to be resilient and able to deal with isp outages and reboots

@ylluminate Good job! The only thing that I see is that you define too many DNS servers. The limit is 3. Your .yaml is very similar to mine. But I couldn't have figured out all of the routing stuff :-)

Do you still need to add my code for the wireless wlan0?

Right, I thought it might be 3 but I was just curious about it and didn't look it up again yet. Yes, I'm going to add the wlan0 today if possible - I'm just out of time on this and so if I run into any hiccups I might have to deploy as-is until more time comes up later.

FYI, I found a handy working script that emails IP address changes out: github.com/begleysm/ipwatch

Made sure to have wpasupplicant installed and then did a sanity check with rfkill list and iwconfig (apt install wireless-tools; iwlist wlan0 scan|grep ESSID), saw that things were looking alright and then limited the netplan conf and did a netplan --debug generate; netplan apply; systemctl daemon-reload). curl https://wtfismyip.com/text/ip showed what I wanted to see at that point as did ip addr so it looks solid.