For the record, these systems run 3.7/i386 rock solid. Just forget
entirely about using the Software Assist RAID support on the motherboard
and use RAIDFrame instead.
In the BIOS, you can toggle it between RAID and NON-RAID mode, but it
makes no difference. The kernel probes it just the
Would anyone like to elaborate on the impacts of using keep state on
conjunction with pass rules that assign traffic to queues?
One might assume that inverted traffic flows would also be queued, however
that would break the traffic can only be queued egress an interface
rule...
There should
I'll double check this today and verify. Will the IPMI on the
motherboard only work with the onboard ethernet controllers, or will it
get its grubby little hands on any/all controllers it finds? If it only
The IPMI configuration screen gives you the option of configuring which
Interface to
On Wed, 19 Oct 2005, Theo de Raadt wrote:
Someone with one of these problematic cards should put it in the
It isn't so much a bug; more so a caveat of Dell's implenentation.
Maybe you can order PowerEdge 1850s w/o a hardware IPMI implementation,
but I don't think it's an issue that warrants
2005 11:28:24 -0400 (EDT)
From: Brian A. Seklecki [EMAIL PROTECTED]
To: Henning Brauer [EMAIL PROTECTED]
Cc: misc@openbsd.org, Tony Sarendal [EMAIL PROTECTED],
jared r r spiegel [EMAIL PROTECTED], Seamus Wassman [EMAIL PROTECTED]
Subject: Queing on Multiple Interfaces Revisited (WAS: Re
.
But you need a technique for queuing a shared ingress
~BAS
--
http://2suck.net/hhwl.html - http://www.bsws.de/
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
--
l8r* --
~ Brian A. Seklecki
From back in the heady days when 'Help Desk' meant
So have him send the message pre-formatted to the list? HTML?
How about just draw the diagram using ports/graphics/dia/* and export to
PNG, post the URL?
~BAS
On Fri, 2005-09-30 at 10:01, J.C. Roberts wrote:
On Fri, 30 Sep 2005 18:35:16 +0530, Manpreet Singh Nehra
[EMAIL PROTECTED] wrote:
What platform are you on? Are you compiling it from source?
It works just fine in 3.7/i386.
Just:
bash-3.00# cd /usr/ports/net/ntop make install clean
If you insist on source, try looking at /usr/ports/net/ntop/patches/*
Try reading about Ports in the FAQ.
~BAS
On Thu, 2005-09-29 at
On Mon, 29 Aug 2005, Vinicius Pavanelli Vianna wrote:
I'm currently using an OpenBSD 3.7 as a firewall for my network, since
this machines is a 1U rack I can't add an extra ethernet card to it, so
I was looking for an alternative solution to use redundancy, since there
are plenty of usb ports
On Sat, 23 Jul 2005, Hans-Joerg Hoexer wrote:
Hi,
On Fri, Jul 22, 2005 at 06:43:34PM -0400, Brian A. Seklecki wrote:
The URL:
http://digitalfreaks.org/~lavalamp/openbsd_ipsec_generic.png
Outlines the generic cookie-cutter configuration from vpn(8) with
addressing changes. A couple
The URL:
http://digitalfreaks.org/~lavalamp/openbsd_ipsec_generic.png
Outlines the generic cookie-cutter configuration from vpn(8) with
addressing changes. A couple of comments on that document:
*) The output of 'netstat -rn -f encap' should probably be included at the
end.
*)
Please confirm that the following are applicable:
* boot(8), biosboot(8), installboot(8), boot_i386(8) lack any
support for booting off RAIDFrame volumes (a 13 line patch 22
months ago fixed this on the b other side of the isleb (r)).
* No support is planned
The same behavior happens on Dell's serial console redirection. It
happens when you boot FreeBSD too. As soon as the kernel starts output
ANSI characters it goes dead.
Dell lets you toggle between VT100/220 mode and ANSI mode, but it's
unaffected. The kernel output just kills it.
Dell has an
201 - 213 of 213 matches
Mail list logo
