Re: disabling mediaopts for if_wm(4)

2017-05-22 Thread Paul Goyette
On Thu, 11 May 2017, Paul Goyette wrote: FWIW, the re(4) situation is worse - very much worse! The re(4) negotiates 100BaseTX with no mediaopts at all, neither full nor half, and no flow-control. It took a couple of minutes before dhcpcd could configure the interface and even then it was

Re: ifconfig xx0 -mediaopt flowcontrol (was Re: disabling mediaopts for if_wm(4))

2017-05-11 Thread Paul Goyette
Well, I tried to explicitly configure the speed to 100baseTX, which (according to all other reports) will disable all auto-negotiation. That actually makes things worse, as it causes 50% reduction in the "speed test" download results (from 50Mb/sec reduces to 24Mb/sec), with no change in the

Re: disabling mediaopts for if_wm(4)

2017-05-10 Thread Paul Goyette
With no manual media or mediaopt setting at all -- just the default settings, full-auto, I see 100-full negotiated (with media options flowcontrol, rxpause, txpause) but still see 3-5Mb/sec performance? ... I also did a tcpdump while the speed-test was running, and saw lots of TCP SACK options,

Re: disabling mediaopts for if_wm(4)

2017-05-10 Thread Brian Buhrow
Hello. You only disable autonegotiation on copper ports if you set speed or duplex to 10 or 100 mbits/sec. Setting the speed to 1000-mbits/sec simply removes 10 or 100 mbits/sec choices from the autonegotiation process and NetBSD will only offer 1000-mbits/sec as a negotiable choice. But,

Re: disabling mediaopts for if_wm(4)

2017-05-09 Thread Paul Goyette
On Wed, 10 May 2017, Paul Goyette wrote: ISTR that wm(4) has one or more bugs concerning flow control. It's possible that when flow control is negotiated, the MAC is not set up to respect flow control signals, so it keeps sends frames to the peer after it is asked to pause. With all buffers

Re: disabling mediaopts for if_wm(4)

2017-05-09 Thread Paul Goyette
On Tue, 9 May 2017, David Young wrote: On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote: Well, I got a little bit of a problem... My new fiber-to-the-home router only has one RJ45 port available, so I had to get a switch to connect all of the hard-wired network devices. It all

Re: disabling mediaopts for if_wm(4)

2017-05-09 Thread David Young
On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote: > Well, I got a little bit of a problem... > > My new fiber-to-the-home router only has one RJ45 port available, so > I had to get a switch to connect all of the hard-wired network > devices. It all seems to work, except for one

Re: disabling mediaopts for if_wm(4)

2017-05-09 Thread Thor Lancelot Simon
On Tue, May 09, 2017 at 11:05:19PM -0400, Thor Lancelot Simon wrote: > On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote: > > > > So, what is the magic incantation to set the interface to 100TX FDX, but > > with flow/pause disabled? > > You can't. Or, more rightly, you can't do it

Re: disabling mediaopts for if_wm(4)

2017-05-09 Thread Thor Lancelot Simon
On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote: > > So, what is the magic incantation to set the interface to 100TX FDX, but > with flow/pause disabled? You can't. Or, more rightly, you can't do it the way you probably want to. If you explicitly set a speed and duplex, you will

disabling mediaopts for if_wm(4)

2017-05-09 Thread Paul Goyette
Well, I got a little bit of a problem... My new fiber-to-the-home router only has one RJ45 port available, so I had to get a switch to connect all of the hard-wired network devices. It all seems to work, except for one problem... In the uplink direction, I can only push about 3.5Mb/sec,