The DHCP set up is done by a dhcp client program, and not "the kernel". That dhcp program is typically run by a network management subsystem.

Which network managment are you using?

What's the output of pgrep -a dhcp ?

Do you have a firewall set up?

Would you mind drop the outputs of two commands:

# ls /sys/class/net
# ip link

That should provide exact information of the link level, and possibly point to where a problem might be.

Yes, "crickets" is a meaningful outcome. The follow-on testing would be

a) try running /usr/sbin/expressvpnd as root (I failed to highlight that before). 

Then b) look into the end of the file /var/log/syslog for traces of that run; esp. if there is anything near a good statement of why it is failing. In particular, if it's an apparmor issue, then it would show up there I think.

Also b2), check whether there might be a dedicated log file for expressvpn in /var/log.

The init script you installed is fine, but there is obviously a problem for the expressvpnd daemon program.

Try running /usr/sbin/expressvpnd from the command line; it may tell you why it fails to start.

Perhaps you are using apparmor restrictively and it needs some permissions set up?

When setting up a bluetooth speaker it got set up as a USB device, and I had to manually chwon /dev/bus/usb/001/002  to me in order gain access to it; maybe you have the same issue?

Yeah, I've read many threads here and still haven't worked out any regular formula for when "advice to search" is administered.

There obviosuly should be a constent rule for it as otherwise any poster might feel left out or fingered; especially those that do search first and don't get any credit for that, as well as those who don't search first and thus suffer an amount of face loss.

I don't use this feature myself, but I have a private stash of useful information. Esp, some "random documentation" that says (far down):

That is, the entry would then look like the following

&%%(diary-float t 4 2) time for my shower

Perhaps that works?

Perhaps this was due to the service pkginfo.devuan.org not being available on ipv6, which now it is.

That device, 054c:094b, does not appear to yet be listed among known devices, but it might work by identifying it explicitly for jmtpfs, i.e. if your mount point is /media/camera you'd use:

jmptfs -d 001,003 /media/camera

Perhaps jmtpfs works for you.

@bbatten: iptables on beowulf (or buster, really) doesn't require arptables or ebtables, but it recommends nftables.

Upon installation, it gets set up to use the iptables-nft alternative implementation and then it provides syntax transparency via /usr/sbin/xtables-nft-multi so as to use the "traditional" iptables rules language for manipulating and reviewing the rules.

It also gives you the option to change it to use the iptables-legacy implementation through update-alternatives.

Doesn't that work for you?

💁 ... someone just made this forum full utf8... enjoy
https://unicode.org/emoji/charts/full-emoji-list.html