Date: Wed, 26 Dec 2001 16:29:40 -0800 From: "Peter/Los Angeles, CA" <peter@haloflightleader.net> To: <ulf@Alameda.net>, "Robert L Sowders" <rsowders@usgs.gov> Cc: "Allen Landsidel" <all@biosys.net>, <freebsd-stable@FreeBSD.ORG>, <owner-freebsd-stable@FreeBSD.ORG>, "Sam Drinkard" <sam@wa4phy.net>, <sthaug@nethelp.no> Subject: Re: 4.5 PRERELEASE - Call for testing Message-ID: <01dd01c18e6d$9847b420$245b1486@hhlaw.com> References: <OF30244549.1707EE30-ON88256B2E.00811810@wr.usgs.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
------=_NextPart_000_01D8_01C18E2A.847ADE60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Look, I'm not for flames myself, but I have to say it gets a whole lot =
more interesting when there's a forest fire going on. It's like a Jerry =
Springer show except it's really quiet.
Peter
----- Original Message -----=20
From: Robert L Sowders=20
To: ulf@Alameda.net=20
Cc: Allen Landsidel ; freebsd-stable@FreeBSD.ORG ; =
owner-freebsd-stable@FreeBSD.ORG ; Peter/Los Angeles, CA ; Sam Drinkard =
; sthaug@nethelp.no=20
Sent: Wednesday, December 26, 2001 3:44 PM
Subject: Re: 4.5 PRERELEASE - Call for testing
This should be moved to chat, hardware, hackers, you pick it.=20
Regardless of what the standard says, it has been my experience that =
if you have a connection that fails to autoneg to full duplex, then =
forcing the freebsd nic to 100 full will result in the expected behavior =
of a 100 full connection. During the negotiation phase the nic says I =
can only do 100 full and the switch responds with 100 full.=20
Recent experience with HP-Procurve and NBase Mega switches confirmed =
that they continually refused to autoneg 100 full until the nics were =
forced to 100 full. Subsequently turning the nics back to autoneg =
produced 100 full connections. Why this occurred is beyond me, but =
after three days of testing that was the fix.=20
It may be that this is not the experience of the other readers of this =
thread. That's fine, all I'm saying is, if you're having trouble with =
full duplex then try forcing the nic to full and see what happens, it =
works for me.=20
This really should be moved off stable now.=20
Ulf Zimmermann <ulf@Alameda.net>=20
Sent by: owner-freebsd-stable@FreeBSD.ORG=20
12/26/2001 02:29 PM=20
Please respond to ulf=20
=20
To: "Peter/Los Angeles, CA" =
<peter@haloflightleader.net>=20
cc: Sam Drinkard <sam@wa4phy.net>, Allen =
Landsidel <all@biosys.net>, sthaug@nethelp.no, =
freebsd-stable@FreeBSD.ORG=20
Subject: Re: 4.5 PRERELEASE - Call for testing=20
On Wed, Dec 26, 2001 at 02:22:15PM -0800, Peter/Los Angeles, CA wrote:
> Please correct me if I'm wrong, but isn't it kind of strange that
> auto-sensing/auto-negotiating must be enabled on both sides for the =
feature
> to work a bit strange?
>=20
> At home, I have a Netgear FS116, a 16-Port unmanaged switch. It is
> auto-sensing/full-duplex 10/100Mbits/sec switch. Therefore, we =
cannot
> control how it will behave.
>=20
> On the other hand, I have network cards on my computer which I can =
set to
> full/half/auto/10/100, whatever combination I like, and yet, the =
switch will
> continue to work.
>=20
> What I'm getting at is that just because one end is not set to
> auto-negotiate/auto-sense that there will be no communication at =
all. Say,
> that one end is set manually, and the other end is automatic. The =
automatic
> end will set itself to the parameters of the one that is manually =
set. This
> is how my network works. Thus, I don't believe that both ends, need =
to be
> set the same way in order to work in this scenario.
>=20
> The automatic will automatically negotiate/auto-sense to whatever =
can't be
> changed, as a result, they work. Or is this even what you folks are =
arguing
> about?
I do not know if this is written in the standard, but I have seen =
devices
where if you turn off AutoNeg, they won't respond at all to the =
packets.
But I have also seens devices which will still respond, but just to =
their
fixed setting. I personal prefer it that if I turn off autoneg, it =
won't
do anything, because that gives you a fixed point. Any production =
system
I always set switch and host to full 100.
--=20
Regards, Ulf.
---------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204
You can find my resume at: http://seven.Alameda.net/~ulf/resume.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------=_NextPart_000_01D8_01C18E2A.847ADE60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Look, I'm not for flames myself, but I =
have to say=20
it gets a whole lot more interesting when there's a forest fire going =
on. =20
It's like a Jerry Springer show except it's really quiet.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Peter</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Drsowders@usgs.gov href=3D"mailto:rsowders@usgs.gov">Robert =
L=20
Sowders</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dulf@Alameda.net=20
href=3D"mailto:ulf@Alameda.net">ulf@Alameda.net</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A title=3Dall@biosys.net=20
href=3D"mailto:all@biosys.net">Allen Landsidel</A> ; <A=20
title=3Dfreebsd-stable@FreeBSD.ORG=20
=
href=3D"mailto:freebsd-stable@FreeBSD.ORG">freebsd-stable@FreeBSD.ORG</A>=
; <A=20
title=3Downer-freebsd-stable@FreeBSD.ORG=20
=
href=3D"mailto:owner-freebsd-stable@FreeBSD.ORG">owner-freebsd-stable@Fre=
eBSD.ORG</A>=20
; <A title=3Dpeter@haloflightleader.net=20
href=3D"mailto:peter@haloflightleader.net">Peter/Los Angeles, CA</A> ; =
<A=20
title=3Dsam@wa4phy.net href=3D"mailto:sam@wa4phy.net">Sam Drinkard</A> =
; <A=20
title=3Dsthaug@nethelp.no =
href=3D"mailto:sthaug@nethelp.no">sthaug@nethelp.no</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, December 26, =
2001 3:44=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: 4.5 PRERELEASE - =
Call for=20
testing</DIV>
<DIV><BR></DIV><BR><FONT face=3Dsans-serif size=3D2>This should be =
moved to chat,=20
hardware, hackers, you pick it.</FONT> <BR><BR><FONT face=3Dsans-serif =
size=3D2>Regardless of what the standard says, it has been my =
experience that if=20
you have a connection that fails to autoneg to full duplex, then =
forcing the=20
freebsd nic to 100 full will result in the expected behavior of a 100 =
full=20
connection. During the negotiation phase the nic says I can only =
do 100=20
full and the switch responds with 100 full.</FONT> <BR><BR><FONT=20
face=3Dsans-serif size=3D2>Recent experience with HP-Procurve and =
NBase Mega=20
switches confirmed that they continually refused to autoneg 100 full =
until the=20
nics were forced to 100 full. Subsequently turning the nics back =
to=20
autoneg produced 100 full connections. Why this occurred is =
beyond me,=20
but after three days of testing that was the fix.</FONT> <BR><BR><FONT =
face=3Dsans-serif size=3D2>It may be that this is not the experience =
of the other=20
readers of this thread. That's fine, all I'm saying is, if =
you're having=20
trouble with full duplex then try forcing the nic to full and see what =
happens, it works for me.</FONT> <BR><BR><FONT face=3Dsans-serif =
size=3D2>This=20
really should be moved off stable now.</FONT> <BR><BR><BR><BR>
<TABLE width=3D"100%">
<TBODY>
<TR vAlign=3Dtop>
<TD>
<TD><FONT face=3Dsans-serif size=3D1><B>Ulf Zimmermann=20
<ulf@Alameda.net></B></FONT> <BR><FONT face=3Dsans-serif =
size=3D1>Sent=20
by: owner-freebsd-stable@FreeBSD.ORG</FONT>=20
<P><FONT face=3Dsans-serif size=3D1>12/26/2001 02:29 PM</FONT> =
<BR><FONT=20
face=3Dsans-serif size=3D1>Please respond to ulf</FONT> <BR></P>
<TD><FONT face=3DArial size=3D1> =
</FONT><BR><FONT=20
face=3Dsans-serif size=3D1> To: =
=20
"Peter/Los Angeles, CA"=20
<peter@haloflightleader.net></FONT> <BR><FONT =
face=3Dsans-serif=20
size=3D1> cc: =
Sam=20
Drinkard <sam@wa4phy.net>, Allen Landsidel =
<all@biosys.net>,=20
sthaug@nethelp.no, freebsd-stable@FreeBSD.ORG</FONT> <BR><FONT=20
face=3Dsans-serif size=3D1> Subject: =
=20
Re: 4.5 PRERELEASE - Call for=20
testing</FONT></TR></TBODY></TABLE><BR><BR><FONT face=3D"Courier New" =
size=3D2>On=20
Wed, Dec 26, 2001 at 02:22:15PM -0800, Peter/Los Angeles, CA =
wrote:<BR>>=20
Please correct me if I'm wrong, but isn't it kind of strange =
that<BR>>=20
auto-sensing/auto-negotiating must be enabled on both sides for the=20
feature<BR>> to work a bit strange?<BR>> <BR>> At home, I =
have a=20
Netgear FS116, a 16-Port unmanaged switch. It is<BR>>=20
auto-sensing/full-duplex 10/100Mbits/sec switch. Therefore, we=20
cannot<BR>> control how it will behave.<BR>> <BR>> On the =
other hand,=20
I have network cards on my computer which I can set to<BR>>=20
full/half/auto/10/100, whatever combination I like, and yet, the =
switch=20
will<BR>> continue to work.<BR>> <BR>> What I'm getting at is =
that=20
just because one end is not set to<BR>> auto-negotiate/auto-sense =
that=20
there will be no communication at all. Say,<BR>> that one end =
is set=20
manually, and the other end is automatic. The automatic<BR>> =
end will=20
set itself to the parameters of the one that is manually set.=20
This<BR>> is how my network works. Thus, I don't =
believe that=20
both ends, need to be<BR>> set the same way in order to work in =
this=20
scenario.<BR>> <BR>> The automatic will automatically=20
negotiate/auto-sense to whatever can't be<BR>> changed, as a =
result, they=20
work. Or is this even what you folks are arguing<BR>> =
about?<BR><BR>I=20
do not know if this is written in the standard, but I have seen=20
devices<BR>where if you turn off AutoNeg, they won't respond at all to =
the=20
packets.<BR>But I have also seens devices which will still respond, =
but just=20
to their<BR>fixed setting. I personal prefer it that if I turn off =
autoneg, it=20
won't<BR>do anything, because that gives you a fixed point. Any =
production=20
system<BR>I always set switch and host to full 100.<BR><BR>-- =
<BR>Regards,=20
=
Ulf.<BR><BR>-------------------------------------------------------------=
--------<BR>Ulf=20
Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: =
510-865-0204<BR>You can=20
find my resume at: http://seven.Alameda.net/~ulf/resume.html<BR><BR>To =
Unsubscribe: send mail to majordomo@FreeBSD.org<BR>with "unsubscribe=20
freebsd-stable" in the body of the=20
message<BR></FONT><BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_01D8_01C18E2A.847ADE60--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01dd01c18e6d$9847b420$245b1486>