macos: Repair community routing subject disappearing throughout safe boot

• MacMini with the most recent model of MacOS
• MacBook Professional with the most recent model of MacOS
• Raspberry Pi with Ubuntu 22.04
• Eero Wifi Community

• MacBook Professional can ping and ssh to Pi
• MacMini crashes with errors:

~ ping 192.168.5.77
PING 192.168.5.77 (192.168.5.77): 56 information bytes
ping: sendto: No path to host
ping: sendto: No path to host
Request timeout for icmp_seq 0

~ ssh -vvv (e mail protected)
OpenSSH_9.8p1, LibreSSL 3.3.6
debug1: Studying configuration information /Customers/pitosalas/.ssh/config
debug1: /Customers/pitosalas/.ssh/config line 2: Making use of choices for *
debug1: Studying configuration information /and so on/ssh/ssh_config
debug1: /and so on/ssh/ssh_config line 21: embody /and so on/ssh/ssh_config.d/* matched no information
debug1: /and so on/ssh/ssh_config line 54: Making use of choices for *
debug2: resolve_canonicalize: hostname 192.168.5.77 is tackle
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/Customers/pitosalas/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/Customers/pitosalas/.ssh/known_hosts2'
debug1: Authenticator supplier $SSH_SK_PROVIDER didn't resolve; disabling
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: coming into
debug1: Connecting to 192.168.5.77 (192.168.5.77) port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: join to deal with 192.168.5.77 port 22: No path to host
ssh: hook up with host 192.168.5.77 port 22: No path to host

• LanScan on Mac mini sees the IP tackle
• Trackers on Mac mini see IP tackle:

~ traceroute 192.168.5.77
traceroute to 192.168.5.77 (192.168.5.77), 64 hops max, 40 byte packets
 1  192.168.5.77 (192.168.5.77)  2.777 ms  2.407 ms  2.058 ms
~

• Booting MacMini in secure mode solves the issue
• Disable all startup objects after which boot usually: the issue reappears

• NOTE: For the primary few seconds after boot I can ping and ssh efficiently after which it begins failing. Which means that one thing at that time within the boot sequence is inflicting the issue.

Subsequent steps?

• Any options on easy methods to establish what’s inflicting the issue.