altair4 wrote:mike acker wrote:
(1) ping command
my earlier analysis of this showed that I was not always able to ping the remote computer:
would sometimes succeed and sometimes fail.
It should never have succeeded. You have it backwards:
In my view it should have never succeeded: "local." -- means "on this computer " not "in this local net "
You have that backwards as well. "local" does not mean "on this computer". ".local" is an mDNS qualifier denoting a private network.
macOS and Linux uses this by default. After a long wait Windows uses it as well - but only in Windows 10.
In any event I'm relieved you got things sorted out.
thanks for your help and especially your patience!! I'll continue to work on this. I have no doubt that I'm making some stupid errors here myself.
I'm beginning to suspect some of my trouble may be related to timeouts
in this morning's tests I wanted to connect "lmderesearch" to "acker4"
after fussing around with the DNS setting in the "Network Settings" box -- using 192.168.1.1 -- i did get connected. but, after changing the DNS back to <blank> -- i was still getting connected.
frustration, obviously: I still haven't "tweaked the right wire"
as I continued tweaking though I think I may have found a time related pattern:
at times, I'd get a sequence like this:
Code: Select all
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
PING acker4.local (192.168.1.228) 56(84) bytes of data.
64 bytes from acker4 (192.168.1.228): icmp_seq=1 ttl=64 time=1.83 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=2 ttl=64 time=2.36 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=3 ttl=64 time=440 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=4 ttl=64 time=464 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=5 ttl=64 time=690 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=6 ttl=64 time=2.29 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=7 ttl=64 time=1.82 ms
^C
--- acker4.local ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6007ms
rtt min/avg/max/mdev = 1.820/229.122/690.344/272.312 ms
initially the ping is rejected but on retry it succeeds. and this was repeatable,.... for a while... and then:
Code: Select all
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local -W 5
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
mike@lmderesearch ~ $ ping acker4.local
ping: unknown host acker4.local
continuous rejections
however, reflecting on earlier results I went to the "acker4" box and switched the network interface off and then back on
retest: link active, again:
Code: Select all
mike@lmderesearch ~ $ ping acker4.local
PING acker4.local (192.168.1.228) 56(84) bytes of data.
64 bytes from acker4 (192.168.1.228): icmp_seq=1 ttl=64 time=30.8 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=2 ttl=64 time=1.97 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=3 ttl=64 time=1.88 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=4 ttl=64 time=171 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=5 ttl=64 time=294 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=6 ttl=64 time=2.19 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=7 ttl=64 time=1.67 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=8 ttl=64 time=159 ms
64 bytes from acker4 (192.168.1.228): icmp_seq=9 ttl=64 time=182 ms
^C
--- acker4.local ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9011ms
rtt min/avg/max/mdev = 1.672/93.966/294.436/103.312 ms
mike@lmderesearch ~ $
as i see it the indications here are a timing problem of some sort. the ASUS router offers a list of connected clients,-- and the list is dynamic: it updates periodically with clients being added/deleted at times
I'm going to get into the manual on this router and see if i can find any specs; i didn't see anything promising just poking around in the menus....