I can run sudo ip link set eth0 up as much as I want, and it still shows as down.
The output you posted contradicts this.
eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
ip link sets this ^^ not this ^
> ip link ...
To add to what @Ingo said, they actually have a third OUI now: E4-5F-01
Not sure why that happened either, but I have hardware with a MAC with that OUI.
I'd have commented that, but don't have enough reputation.
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 ...
As with pretty much any connector, search for "[connector name] breakout board", and you'll see tons of adapters from that connector to some sort of GPIO breakout. For example, here's an RJ-45 breakout board:
If the sensor only has two terminals of its rj45 port wired in, you can probably make a custom cable. Cut the end off of an ethernet cable and wire up the appropriate leads to gpio pins. Not as slick as you wanted, but worth a shot. IDK if the signaling voltage will be compatible, but there's tons of 3.3v and 5v logic out there, I reckon it's worth a try.
I just had the idea whether the problem is related to the Public vs Private categorization of your LAN Ethernet network within Windows: some features are configured differently for these. Mine for example, when used without a router on it, typically gets categorized as Public.
On Windows, open Powershell with administrator rights, and issue the following:
I solved this by getting a lead over at the Pi Forums. See Ethernet Problems. It turns out my Ethernet is only running at 10/100. The Broadcom Chipset on the Pi4 doesn't support fallback from Gigabit to Fast Ethernet. As such I bought a USB 3.0 to Gigabit Ethernet Adapter TU3-ETG, which does support fallback, and is supported by the upstream linux kernel, ...
I stumbled on this question after experiencing the same issue with my RPi 4 crashing my Asus router.
It turns out that my Pi's case fan was intermittently failing. When the fan stopped and the Pi got very warm, it also crashed the router. Replacing the case/fan and keeping an eye on the CPU temperature has helped: I haven't experienced any issues now that ...
Here's how I would do it - for multiple IP's you'll be creating a file in /etc/network/interfaces.d
lets create /etc/network/interfaces.d/wlan0 - name doesn't matter really
iface wlan0 inet manual
up ip address add 192.168.1.100/24 dev wlan0 label wlan0:0
up ip address add 192.168.1.101/24 dev wlan0 label wlan0:1
Clearly, you would use the ...