macos – Troubleshoot community routing drawback which disappears on protected boot

0
17
macos – Troubleshoot community routing drawback which disappears on protected boot


  • MacMini working newest MacOS
  • MacBook Professional working newest MacOS
  • Raspberry Pi working Ubuntu 22.04
  • Eero Wifi Community
  • MacBook Professional is ready to each ping and ssh to Pi
  • MacMini fails with errors:
~ ping 192.168.5.77
PING 192.168.5.77 (192.168.5.77): 56 knowledge bytes
ping: sendto: No path to host
ping: sendto: No path to host
Request timeout for icmp_seq 0

~ ssh -vvv [email protected]
OpenSSH_9.8p1, LibreSSL 3.3.6
debug1: Studying configuration knowledge /Customers/pitosalas/.ssh/config
debug1: /Customers/pitosalas/.ssh/config line 2: Making use of choices for *
debug1: Studying configuration knowledge /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 recordsdata
debug1: /and so on/ssh/ssh_config line 54: Making use of choices for *
debug2: resolve_canonicalize: hostname 192.168.5.77 is deal with
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 handle 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 deal with
  • tracers on Mac mini sees the IP deal with:
~ 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 protected mode solves the issue
  • Turning off each startup merchandise after which booting regular: the issue reapears

enter image description here

  • NOTE: Through the first few seconds after boot up I can efficiently ping and ssh after which it begins failing. Which suggests that one thing at that time within the boot sequence causes the issue

Subsequent Steps?

  • Any suggestion on the right way to determine what’s inflicting the issue

LEAVE A REPLY

Please enter your comment!
Please enter your name here