CANLOOP(4)

πŸ“¦ version 11.0, in nixpkgs unstable

πŸ¦‹ CANLOOP(4) πŸ¦‹

okay bestie, welcome to the Kernel Interfaces Manual β€” this page is all about canloop, the software loopback CAN network interface ✨


🌸 NAME 🌸

canloop β€” a software loopback CAN network interface, periodt πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

pseudo-device canloop

✨ DESCRIPTION ✨

So the canloop pseudo interface is literally a loopback interface for the CAN layer. No cap. 🫢

It can be used as a destination by a CAN application when there is no CAN hardware available. It's giving "we make it work anyway" main character energy πŸ˜ŒπŸ’–

Other sockets bound to the same canloop interface β€” or not bound to any interface at all β€” will receive the frames. Yes, those sockets. They get the frames. iykyk πŸ¦‹

canloop interfaces can be created by using the ifconfig(8) create command. Slay. πŸ”₯


🌈 SEE ALSO 🌈

go read those too, bestie β€” they're iconic πŸ‘‘


πŸ’œ HISTORY πŸ’œ

The canloop device appeared in NetBSD 8.0. Not me being nostalgic for a whole release era πŸ˜­πŸ’€


source/version situation: Debian; date stamp: May 18, 2017 β€” that's the tea, bestie, bye fr fr πŸŽ€πŸ’–

πŸ“¦ where this page comes from