Here's how to create a direct ethernet connection, presuming the interface is up (if not ip link set enp8s0 up):1
ip addr add 10.0.42.1/24 dev enp8s0
ip route add 10.0.42.2 dev enp8s0 src 10.0.42.1
That's one side; the configuration is symmetrical, meaning doing the other side is exactly the same except you swap 42.1 for 42.2 and vice versa. You don't have ...
There are a few other errors that happen prior to this but I'm not sure if they're relevant
They're actually an hour previous (dunno if you noticed this).
The bit after the hostname, if it isn't kernel, is a process name and PID (eg. bluetoothd. The kernel stuff there isn't an error except for the note about dhcpcd (which is something that is spit out ...
RaspiOS Buster (the official Raspberry Pi operating system based on Debian 10) uses dhcpcd to configure network interfaces, both eth0 and wlan0. The use of /etc/network/interfaces is obsolete and there is not a way to configure a static IP address alias into /etc/dhcpcd.conf. It is possible however to create an user defined hook script following the dhcpcd-...
Option 1 - Using nohook wpa_supplicant
The /etc/dhcpcd.conf configuration file of dhcpcd can be edited to define which wireless interfaces need wpa_supplicant.
For each identified interface, dhcpcd executes all scripts (hooks) found in /lib/dhcpcd/dhcpcd-hooks in lexical order. One of the scripts is 10-wpa_supplicant, which starts wpa_supplicant. It can be ...
Starting with the question:
Is there a reason this process would work for eth0 but not wlan0?
There is a difference in how the eth0 interface treats packets compared to wlan0. A comment on a blog post poses a plausible explanation:
I read somewhere that wireless doesn't work because frames coming in are then found to have a 'wrong' mac address. The frames ...
This is an XY problem.
You have decided (for whatever reason) that you "need" multiple IP addresses for the same interface and are diving more deeply into that rabbit hole (mixing incompatible networking systems without understanding either).
It may be possible to achieve your primary goal, but first you have to clearly define exactly what you are ...
So it turns out it was a hardware issue rather than a software issue. Looking at my question again, I recalled that 2.4 GHz wireless connections are well known for dropping due to any kind of interference of other devices that give off the 2.4GHz noise frequency while 5GHz doesn't have that problem. One of the things I failed to mention earlier in the ...
create a file in /etc/network/interfaces.d - lets call it eth0 - doesn't matter what the name is.
In this file add the following
iface eth0 inet manual
up ip link add link eth0 name eth01 address 02:00:00:00:00:01 type macvlan
up ip link add link eth0 name eth02 address 02:00:00:00:00:02 type macvlan
Now restart networking
sudo systemctl ...