Anyone running Server on a Raspberry Pi 4?
Tom H
tomh0665 at gmail.com
Fri Jul 24 18:42:39 UTC 2020
On Fri, Jul 24, 2020 at 5:36 PM Liam Proven <lproven at gmail.com> wrote:
> On Wed, 22 Jul 2020 at 13:34, Oliver Grawert <ogra at ubuntu.com> wrote:
>> you just wipe /et/netplan and create:
>
> OK...
>
> So I had working wifi, but I experimentally rebooted today and the
> wifi does not acquire an IPv4 address. I thought I'd try your "modern"
> way.
>
> (I feel a bit like regular list members Gene Heskett and Douglas
> Pollard complaining about how Ubuntu's networking is all different
> these days! Gents, I apologise. I take it all back. I know just how
> you feel now.)
>
> First: I took you to mean a config file called /etc/netplan (i.e. that
> /et/ was a typo, which it was).
>
> It isn't. /etc/netplan/ is a directory. In it there is a file called
> 50-cloud-init.yaml
To be fait, Oliver G said "wipe out /etc/netplan", but he then cat-ed
a file inside that directory. So misunderstanding that "/etc/netplan"
is a file is rather weird.
> I thought this would not help me as I have disabled and removed
> cloud-init, but I tried anyway.
Your initial yaml was created by cloud-init. And, IIRC, if you hadn't
removed cloud-init, it would've been recreated.
> I ran ``netplan apply`` without changing anything and it ran. OK, fine.
>
> So I added the "wifis" section from your example, inserted my values,
> and ran ``netplan apply`` again.
>
> Presto, wlan0 had an IPv4 address. So, I rebooted, and it did after a
> reboot, too! \o/
BTW, the config generated by netplan'll be in
"/run/NetworkManager/system-connections" if you're using
NetworkManager and in "/run/systemd/network" if you're using networkd.
> In preliminary testing, it seems like I still get pauses when I am
> connected to the wired Ethernet port's IP address. Maybe a little less
> bad. But if I connect to the wireless port, I do not seem to see the
> pauses, so far.
More information about the ubuntu-users
mailing list