Inconsistant connection over ethernet

hello, i am trying to ssh into my jetson AGX xavier over ssh using just an ethernet cable.

ssh over wifi when the board is connected to the lan works great.

i need to control the board over ethernet however.

when i have a host machine plugged into the board with the cable, they seem to only be connected some of the time.

i connect the two computers and then try
$ ping xavieragx.local
but this is only successful about 25% of the time

same story with
$ ssh user@xavieragx.local

anyone know what makes this happen? i’ve seen on some raspberry pi forums that the interface can go into sleep mode which produces this behavior, perhaps something similar causes this issue with the xavier? any help would be greatly appreciated.

Which jetpack release are in use?

Have you checked other linux devices? I mean other linux device to replace that host.

the Jetson in use is running JetPack 4.6.0(rev 3)

the host that is ssh’ing into it is a windows laptop.

i have tried several windows laptops using the command
$ ping xavieragx.local

and about 3/4 of the time the command yields:
Ping request could not find host xavieragx.local. Please check the name and try again.

the other 1/4 of the time it pings it successfully and in sub millisecond time

Pinging XavierAGX.local [fe80::axxc:cxx2:bxx:b33xxxx] with 32 bytes of data:
Reply from fe80::axxc:cxx2:bxx:b33xxxx: time=1ms
Reply from fe80::axxc:cxx2:bxx:b33xxxx: time<1ms
Reply from fe80::axxc:cxx2:bxx:b33xxxx: time<1ms

Ping statistics for fe80::axxc:cxx2:bxx:b33xxxx:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

by plugging in a monitor to the jetson while also SSHing into it via ethernet i noticed that every once and awhile a notification would appear saying “Disconnected wired connection”

upon looking in the settings for the wired connection and messing around i set the ipv4 and ipv6’s method to “shared to other computers”

this seems to have fixed the problem and the board and computer have maintained a 10+ minute long ssh connection over ethernet now.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.