Hi Terry,

> > AFAICS Raspbian ships WireGuard already packaged which I would use
> > instead of adding a Debian Unstable package as that tutorial
> > suggests.
>
> I did try to install using apt before I ran through that tutorial, but
> got a 'not found'.

Not found, it hasn't heard of the package, or not found, it's heard of
it but has problems installing it?

> Since it's in there it seems a bit odd that it's not found.

Yes, I'd pursue fixing that rather than adding Debian Unstable.

> > For what to do then, https://wiki.archlinux.org/index.php/WireGuard
> > might be useful, even though you're not Arch Linux.  In particular,
> > I see it mentions kernel 5.6 versus earlier ones.  ‘uname -r’ shows
> > your kernel release.  It also says
>
> The default installation of Raspberry Pi OS installs kernel 4.9.

Current Debian is 10, Buster, which I assume Raspbian uses.
http://archive.raspbian.org/raspbian/dists/buster/main/binary-armhf/Packages.xz
contains

    Package: linux-image-4.9.0-6-rpi
    Package: linux-image-4.9.0-6-rpi-dbg
    Package: linux-image-4.9.0-6-rpi2
    Package: linux-image-4.9.0-6-rpi2-dbg
    Package: linux-image-rpi
    Package: linux-image-rpi-dbg
    Package: linux-image-rpi-rpfv
    Package: linux-image-rpi2
    Package: linux-image-rpi2-dbg
    Package: linux-image-rpi2-rpfv

so it seems correct to find you're running 4.9.  It's the largest I find
with

    $ lynx -dump -nolist http://archive.raspbian.org/raspbian/pool/main/l/ |
    > grep 'linux-[0-9]' |
    > sort -V
    linux-3.6/                                         13-Apr-2017 15:11
    linux-3.10/                                        13-Apr-2017 15:11
    linux-3.12/                                        13-Apr-2017 15:11
    linux-3.18/                                        28-Sep-2017 17:31
    linux-4.4/                                         14-Oct-2017 22:13
    linux-4.9/                                         13-Feb-2019 03:17
    $

On the other hand,
https://en.wikipedia.org/wiki/Raspbian#Version_history says 4.19 is
available.

> I subsequently did sudo apt full-upgrade and sudo rpi-update  to
> upgrade the firmware and that got me to 5.4.

I don't know how that happened.  The Raspbian Wikipedia page above
doesn't mention a 5.x.  Could it have been after something added
Debian's unstable into the mix?

https://www.raspberrypi.org/forums/viewtopic.php?t=269769
said in April ‘We are planning to move to the 5.4 kernel in the near
future’.

Oh, found the cause.

    
https://www.raspberrypi.org/documentation/raspbian/applications/rpi-update.md

    rpi-update is a command line application that will update your
    Raspberry Pi OS kernel and VideoCore firmware to the latest
    pre-release versions.

    WARNING: Pre-release versions of software are not guaranteed to
    work.  You should not use rpi-update on any system unless
    recommended to do so by a Raspberry Pi engineer.  It may leave your
    system unreliable or even completely broken.  It should not be used
    as part of any regular update process.

So don't do that.

You've enough problems and trouble ahead getting this working on a
stable Raspbian, don't deviate from that.  :-)

> The tutorial then downloads the linux headers, which ultimately
> (allegedly) gets the 5.6 modules installed, but the Pi still boots
> into the 5.4 kernel.
>
> >     systemd-networkd and NetworkManager both have native support for
> >     setting up WireGuard interfaces, they only require the kernel
> >     module.
>
> Which apparently I can't get.  I didn't see any errors, but perhaps I
> needed to install gcc?

No, I doubt that would help.  A 5.6 module with a 5.4 kernel sounds
wrong.

-- 
Cheers, Ralph.

-- 
  Next meeting: Online, Jitsi, Tuesday, 2020-07-07 20:00
  Check to whom you are replying
  Meetings, mailing list, IRC, ...  http://dorset.lug.org.uk
  New thread, don't hijack:  mailto:dorset@mailman.lug.org.uk

Reply via email to