@Sunshine 

Here you go, I added tracert just in case

PS C:\Users\Hus> ping 192.168.1.120

Pinging 192.168.1.120 with 32 bytes of data:
Reply from 192.168.1.120: bytes=32 time=2ms TTL=64
Reply from 192.168.1.120: bytes=32 time=4ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.120:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 4ms, Average = 2ms
PS C:\Users\Hus> tracert 192.168.1.120

Tracing route to 192.168.1.120 over a maximum of 30 hops

  1     1 ms     2 ms     1 ms  192.168.1.120

Trace complete.


PS C:\Users\Hus> ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 6ms, Average = 3ms

Pinging the router from inside the Pi:

klipper@mainsailos:~ $ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.52 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.20 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.08 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.49 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.86 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.89 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.83 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.23 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.31 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=2.75 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2.82 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=2.51 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=3.28 ms
^C
--- 192.168.1.1 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12016ms
rtt min/avg/max/mdev = 1.833/2.675/3.524/0.569 ms

klipper@mainsailos:~ $ traceroute 192.168.1.1
traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  5.984 ms  6.122 ms  6.391 ms

Pinging when my computer is not connected to the repeater, I also pinged it on the mDNS address just to check if it's reachable, but it wasn't:

PS C:\Users\Hus> ping 192.168.1.120

Pinging 192.168.1.120 with 32 bytes of data:
Reply from 192.168.1.101: Destination host unreachable.
Request timed out.
Reply from 192.168.1.101: Destination host unreachable.
Reply from 192.168.1.101: Destination host unreachable.

Ping statistics for 192.168.1.120:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
PS C:\Users\Hus> tracert 192.168.1.120

Tracing route to 192.168.1.120 over a maximum of 30 hops

  1     *     Hus-Asus [192.168.1.101]  reports: Destination host unreachable.

Trace complete.
PS C:\Users\Hus> ping mainsailos.local

Pinging mainsailos.local [fe80::32da:a4b6:a60c:aac3%18] with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for fe80::32da:a4b6:a60c:aac3%18:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PS C:\Users\Hus> tracert mainsailos.local

Tracing route to mainsailos.local [fe80::32da:a4b6:a60c:aac3%18]
over a maximum of 30 hops:

  1     *        *     Destination host unreachable.

Trace complete.

  @Sunshine Any updates on this?

Still having these issues