Thank you for the example! The default without any CAN filters does indeed receive all messages, with any ID. We found our problem, and I will share in case it saves someone else.
The ip linux utility brings up a CAN interface just fine, but when trying to bring up the interface with networkd, the interface comes up without any idication of error and has all the stats that it does using the ip utility, but something isn't configured correctly and there is no indication of what is different.
This configuration works.
/etc/systemd/network/10-acan.link:
[Match]
Path=platform-43ff8000.llce:llce_can6
Type=can
[Link]
Name=acan
/etc/systemd/network/10-acan.network:
[Match]
Name=acan
/usr/lib/systemd/system/acan-bitrate.service:
[Unit]
After=sys-subsystem-net-devices-acan.device
Description=Configure acan with appropriate bittiming
[Service]
Type=oneshot
ExecStart=sh -c '/sbin/ip link set acan down && /sbin/ip link set acan up type can tq 125 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1'
[Install]
WantedBy=sys-subsystem-net-devices-acan.device
This configuration brings up the interface without problem, allows transmission, but not reception of messages.
/etc/systemd/network/10-acan.link:
[Match]
Path=platform-43ff8000.llce:llce_can6
Type=can
[Link]
Name=acan
/etc/systemd/network/10-acan.network:
[Match]
Name=acan
[CAN]
TimeQuantaNSec=125
PropagationSegment=6
PhaseBufferSegment1=7
PhaseBufferSegment2=2
SyncJumpWidth=1