As mentioned in the RatOS repo here, not having your /etc/networks/interfaces.d/can0 parsed will implicitly prevent the can0 from coming up as expected, even if you follow all other instructions to the letter.
I was able see the CAN device appear in kernel logs, I saw the device in lsusb output, I saw the actual interface appear in ifconfig output, but with status DOWN and queue of only 10.
While stumbleshooting I found a post where someone was able to manually bring the interface up with ip link set up can0 type can bitrate 1000000, which did work to bring the can0 interface link UP.
I worked backwards from there.
Summary: /etc/network/interfaces must contain
# Include files from /etc/network/interfaces.d:
source /etc/network/interfaces.d/*
for the /etc/networks/interfaces.d/can0 to be correctly parsed as the instructions expect.
As mentioned in the RatOS repo here, not having your /etc/networks/interfaces.d/can0 parsed will implicitly prevent the can0 from coming up as expected, even if you follow all other instructions to the letter.
I was able see the CAN device appear in kernel logs, I saw the device in
lsusb
output, I saw the actual interface appear inifconfig
output, but with status DOWN and queue of only 10.While stumbleshooting I found a post where someone was able to manually bring the interface up with
ip link set up can0 type can bitrate 1000000
, which did work to bring the can0 interface link UP.I worked backwards from there.
Summary:
/etc/network/interfaces
must containfor the /etc/networks/interfaces.d/can0 to be correctly parsed as the instructions expect.