----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> f66ba4ab
@REPLY: <op.19k6jruea3w0dxdave@hodgins.homeip.net>
21527421
@REPLYADDR William Unruh <unruh@invalid.ca>
@REPLYTO 2:5075/128 William Unruh
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References: 1@dont-email.me>
1@dont-email.me> 1@dont-email.me>
<op.19k6jruea3w0dxdave@hodgins.homeip.net>
@TZUTC: -0000
@PID: slrn/1.0.3 (Linux)
@TID: FIDOGATE-5.12-ge4e8b94
On 2023-08-12, David W. Hodgins <
dwhodgins@nomail.afraid.org> wrote:
> On Sat, 12 Aug 2023 18:46:02 -0400, William Unruh <
unruh@invalid.ca> wrote:
>
>> And of course just after I sent that out, the systems suddenly started
>> working again. Not at all clear what happened.
>
> Does "ip -s link" show any errors?
>
> Regards, Dave Hodgins
On Serv:
2: enp4s0:
mtu 1500 qdisc fq_codel
state UP mode DEFAULT group default qlen 1000
link/ether f8:32:e4:70:14:5b brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
69357175201 558088800 0 37942 0 15654970
TX: bytes packets errors dropped carrier collsns
1395857318948 985313209 0 0 0 0
On Client:
2: enp3s0: mtu 1500 qdisc fq_codel
state UP mode DEFAULT group default qlen 1000
link/ether 20:cf:30:90:5c:cb brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
715899055 1004543 0 1095 88 83900
TX: bytes packets errors dropped carrier collsns
379358269 614341 0 0 0 0
I have no idea what time span those results cover, and the mount
problems occured abot 5 days ago.
--- slrn/1.0.3 (Linux)
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5015/255 5019/40 5020/715 848
1042 4441 12000 5030/49 1081
SEEN-BY: 5075/128
@PATH: 5075/128 5020/1042 4441