@ylluminate hi, so in your `ip output gist.github.com/ylluminate/6435840c37edc01e82c047c61f4c071b I see that eth1, which I understood to be your primary ISP, is "up" but has only a local ipv6 address. Is that correct? Is your DSL router currently not functional?

also the ip route definitely shows that the default route via 192.168.0.1 is being added to your eth0, which is marked as being your LAN (implies, has no Internet) - so that's consistent with your netplan yaml, and I think this yaml is wrong for the config you're trying to achieve. But to know what additional config (if any) you need on eth1, would need to see what the DHCP server there provides when it's working

@slangasek correct - since i'm not onsite the primary eth1 is not up and i'm mostly interested in testing and making sure eth2 is working which is the usb tether since that is going to be the main fallback and really the most important connection ultimately as such.

so right now i have a local lan plugged into eth1 that should be giving a dhcp lease from a 192.168.0.0 subnet

hmm, but you are right, it doesn't seem to be pulling an ip from dhcp

ok, whereas you do have 192.168.0.0 routes being provided on eth0. I think you should drop the 0.0.0.0 route from eth1 (which I guess is not actually in use anyway - the default route you currently have via 192.168.0.1 comes via dhcp). also you currently have two ips assigned to eth0 in the 192.168.0.0 subnet - you have 192.168.0.137 which is assigned by the dhcp server, and 192.168.0.1 which is statically assigned in the netplan config...

but the dhcp server on that interface is handing out a default route with 192.168.0.1 as the gateway, which is wrong if your server is supposed to be 192.168.0.1. So you probably should have this interface configured with a static address only and disable dhcp

so i commented out the parts on eth1 (pardon the crud floating around due to all of my fiddling): p153.p0.n0.cdn.getcloudapp.com/items/kpuLGbbl/…

i'm now getting ipv4 ip on eth1 and eth2

so @slangasek are you saying i need to have something more along the lines of this for the yml and ip output?: gist.github.com/ylluminate/1a3c21f127bfe3d4c93fa79effc097c6

i seem to then need to add some routes - but i'm not clear yet on what is correct for netplan in this regard

hello

dhcp4: false, and dhcp6: false, are the defaults, so you don't need them in the .yaml unless you need to set one to true.

Also, you only have ONE .yaml file in /etc/netplan, yes?

i figured as much, just a sanity check due to him saying it was pulling dhcp4 for it as well

ah, there is a default 50-cloud-init.yaml which could be the problem

before your "fiddling" didn't you get ipv4 on eth1 and eth2

i got caught up in following some instructions i found re: the other file that i left that

OH! TWO .yaml files. No wonder stuff didn't work.

What's in 50-cloud-init?

default server install: gist.github.com/ylluminate/990c81a1004739319424962080bbf879

so i've blown that away now

good. as two yaml files get merged during generate/apply

in fact, you should do generate/apply/reboot now

no kidding. <sigh> i should have thought about that but due to the "cloud" in the name and not grok'ing netplan fully yet, i never dreamed of looking in there - assuming ubuntu / canonical wanted it for something else. -.-

i did that: netplan --debug generate; netplan apply; reboot

Yeah, there's something on servers that I don't fully understand... that has to do with cloud-init.

do u have appropriate IP addresses now?

I noticed on your last comment to slangasek, you forgot the @slangasek, so he may not have seen your last comment... and may be quiet... waiting for you to respond. I'd send another comment to him so he'll get notified.

so now i'm looking at the following: gist.github.com/ylluminate/1a3c21f127bfe3d4c93fa79effc097c6

@slangasek ^

I see ipv4 addresses on all eth interfaces... am I wrong? Remove all of the false lines.

Gonna bug out now. Hopefully Steve will come back and work with you more.

oopsy, thanks, i'm in the middle of a meeting so i keep hopping back and forth