On 12/2/21 08:41, Brian Hutchinson wrote:
Yup, I'm using systemd-networkd ... I think I have to in order to leverage 
network-online.target etc., and set up my network (bonding in this case) with 
.netdev and .network files in /etc/systemd/network.

You don't "have" to do anything.  It is a choice.  Other network managers you 
might consider include:
ConnMan
netctl
NetworkManager
Wicd

What kind of platform are you on?  PC, embedded?

Just Arch Linux on various PCs, but, if you are already running systemd, I 
don't expect that the hardware makes any difference.

Can you give an example of what this would look like?

I could, but, unless you want to abandon systemd-networkd for some reason, and 
also not consider some of the other popular network management systems, there 
would be no point.

... but I can also check carrier of my interfaces ...

The kernel bonding module is its own thing, and automatically monitors the 
state of its slave devices and manages the state of its virtual interface.  I 
don't know why you would want to bother with the carrier state of - presumably 
- an ethernet device, or whatever.  If there were a problem with the bonding 
module, that would be an entirely separate issue.

Of course, this all presupposes that you have actually selected and configured 
the correct options to the kernel bonding module, to provide the functionality 
you want with the hardware you are using.  But that is nothing to do with 
systemd or with ptp4l.

My issue is with systemd starting PTP before the bond is fully set up.

As I mentioned, I cannot help you with systemd-networkd.  I cannot find any 
author attributions in or to the systemd-networkd source, and none of the 
actual developers here appears to have volunteered any insight - and good luck 
with that.

Still, you might read here for clues:
 https://wiki.archlinux.org/title/Systemd-networkd
though, you will have to disregard the reference to "Wireless bonding", which was 
originally written by me, but is now quite obsolete, without updates, having been subsequently 
"vandalized" by a rather persistent inexperienced and arrogant user.

James

Reply via email to