I’m attempting to determine if the message came from the host or the Jetson since ssh involves both…if the message occurs prior to reaching the Jetson login, then it comes from the host; at some point during login (right before the command prompt is available) messages are from the Jetson. If you use “sudo dmesg | tail” on both host and Jetson there may be a log message to show the origin of the message.
Additionally, you can ssh from your host to your host to see purely host messages. You can also ssh into the Jetson, and from that prompt, ssh from Jetson to Jetson to isolate Jetson messages.
Note that network interfaces and device special files are often renamed via udev rules after the device or interface is created. Some applications make assumptions about unchanging device/interface names and fail to consider udev renaming. Udev itself can also fail due to less common issues (such permissions or disk space issues).