On Mon, Mar 16, 2009 at 4:07 PM, Laurent CARON wrote:
> Henning Brauer wrote:
>
>> this is extremely stupid.
>>
>
> I know, I'm a very stupid guy ;)
You are not the first...
http://search.gmane.org/?query=stupid&author=henning&group=gmane.os.openbsd.misc&sort=relevance&DEFAULTOP=and&xP=Zstupid&
Henning Brauer wrote:
this is extremely stupid.
I know, I'm a very stupid guy ;)
: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Henning Brauer
Sent: 16 March 2009 13:29
To: OpenBSD
Subject: Re: HP Proliant DL385 with Squid at a Gigabit-switch - bad
network
performance
* Laurent CARON [2009-02-28 21:33]:
Steve Shockley wrote:
On 2/27/2009 8:43 AM,
On Mon, Mar 16, 2009 at 01:51:19PM -, Michal wrote:
| Sorry but I worked for a very successful company in the UK that didn't use
| auto neg's on Cisco switches and routers so I wouldn't call it evil AT all,
| please explain why manual is evil.
Manual is error-prone. If everything defaults to a
* Michal [2009-03-16 14:56]:
> Sorry but I worked for a very successful company in the UK that didn't use
> auto neg's on Cisco switches and routers so I wouldn't call it evil AT all,
> please explain why manual is evil.
because it leads to errors, sooner or later, that are hard to debug.
And not
half Of
Henning Brauer
Sent: 16 March 2009 13:29
To: OpenBSD
Subject: Re: HP Proliant DL385 with Squid at a Gigabit-switch - bad network
performance
* Laurent CARON [2009-02-28 21:33]:
> Steve Shockley wrote:
>> On 2/27/2009 8:43 AM, Laurent CARON wrote:
>>> - Forcing speed on
* Laurent CARON [2009-02-28 21:33]:
> Steve Shockley wrote:
>> On 2/27/2009 8:43 AM, Laurent CARON wrote:
>>> - Forcing speed on switch
>>> - Forcing speed on nic
>>
>> Why? This practice made sense when 10baseT gear from different vendors
>> wasn't compatible, but not for the last 15-20 years.
On 2/28/2009 4:45 PM, Brian Keefer wrote:
I've had problems with bge(4)s in IBM xSeries machines that required
forcing speed/duplex, else they would negotiate to 100/half.
Probably your switch was forced to 100/full... autonegotiation needs to
be enabled on both ends of the connection.
On Feb 28, 2009, at 12:28 PM, Laurent CARON wrote:
Steve Shockley wrote:
On 2/27/2009 8:43 AM, Laurent CARON wrote:
- Forcing speed on switch
- Forcing speed on nic
Why? This practice made sense when 10baseT gear from different
vendors wasn't compatible, but not for the last 15-20 years.
Steve Shockley wrote:
On 2/27/2009 8:43 AM, Laurent CARON wrote:
- Forcing speed on switch
- Forcing speed on nic
Why? This practice made sense when 10baseT gear from different vendors
wasn't compatible, but not for the last 15-20 years.
This practice still makes sense, at least with broad
On 2/27/2009 8:43 AM, Laurent CARON wrote:
- Forcing speed on switch
- Forcing speed on nic
Why? This practice made sense when 10baseT gear from different vendors
wasn't compatible, but not for the last 15-20 years.
http://www.ethermanage.com/ethernet/pdf/dell-auto-neg.pdf
Moreover, gigabi
Pete Vickers wrote:
The bge driver sucks for these cards - just chuck in an em(4) NIC and
you should see instant improvement.
Those cards have always been unreliable for me under Linux and OpenBSD.
On 2009/02/28 12:10, Pereresus ne Vlezaet Buggy wrote:
> On 28 February 2009 ?. 01:58:29 Stuart Henderson wrote:
> > On 2009-02-27, Pete Vickers wrote:
> > > The bge driver sucks for these cards - just chuck in an em(4) NIC
> > > and you should see instant improvement.
> > >
> > > 'netstat -I bge0
On 28 February 2009 G. 01:58:29 Stuart Henderson wrote:
> On 2009-02-27, Pete Vickers wrote:
> > The bge driver sucks for these cards - just chuck in an em(4) NIC
> > and you should see instant improvement.
> >
> > 'netstat -I bge0' will confirm the packet errors
>
> this was fixed a year ago.
Ma
On 2009-02-27, Pete Vickers wrote:
> The bge driver sucks for these cards - just chuck in an em(4) NIC and
> you should see instant improvement.
>
> 'netstat -I bge0' will confirm the packet errors
this was fixed a year ago.
On Fri, Feb 27, 2009 at 3:43 PM, Han Boetes wrote:
> cache_dir aufs xxx yyy
Thank you, I've switched to aufs, I hope it works ok on OpenBSD
(docs mention "POSIX threads").
The netstat actually doesn't show I/O errors:
afar...@ablprx01:squid> netstat -I bge0
NameMtu Network Address
I recommend you switch to:
cache_dir aufs xxx yyy
# Han
The bge driver sucks for these cards - just chuck in an em(4) NIC and
you should see instant improvement.
'netstat -I bge0' will confirm the packet errors
/Pete
On 27 Feb 2009, at 14:33, Alexander Farber wrote:
bge0 at pci3 dev 6 function 0 "Broadcom BCM5704C" rev 0x10, BCM5704 B0
(0x2100
Alexander Farber wrote:
Hello,
our web proxy for 400 users (actually at the moment less than 100,
but we are going to switch the others to use it soon) is slow.
It is a HP Proliant DL385 running OpenBSD 4.4-stable with
the squid-2.7.STABLE3 from packages (dmesg below).
Does anybody please have
Hello,
our web proxy for 400 users (actually at the moment less than 100,
but we are going to switch the others to use it soon) is slow.
It is a HP Proliant DL385 running OpenBSD 4.4-stable with
the squid-2.7.STABLE3 from packages (dmesg below).
Does anybody please have a good advice how to find
20 matches
Mail list logo
