Re: port-shark/57613: Abysmal network performance on shark

[mlelstv%serpens.de@localhost (Michael van Elst)]

The following reply was made to PR port-shark/57613; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-shark/57613: Abysmal network performance on shark
Date: Tue, 12 Sep 2023 06:03:20 -0000 (UTC)

 herdware%sdf.org@localhost (=?X-UNKNOWN?Q?Bj=C3=B6rn_Johannesson?=) writes:
 
 >Perhaps it would be possible to turn off the possibility to enable 
 >full-duplex since it's so broken? (Other stuff connected to that switch 
 >runs fine full-duplex.)
 
 Machine and switch both need to use auto-negotation or both need to
 be statically configured to the same duplex mode. Mixing auto and
 static configuration does not work, and the default for an interface
 is to use auto negotiation.
 
 
 >The other problem that nfs-root hangs going multi-user turns out 
 >to be that /etc/rc.d/network flushes routes after setting (or not in this 
 >case) NIS/YP domain. Since this shark is on another subnet than the file 
 >server and the gateway the machine got from dhcpd got flushed things 
 >break.
 >Setting flushroutes=NO in rc.conf fixes the problem but is that the 
 >intended way? After network_start_domainname() flushes the route we can 
 >never reach network_start_defaultroute() which comes later.
 
 It would be smarter if /etc/rc.d/network knew how to handle NFS roots.