Stefek Zaba wrote:
I've just brought 3.8-RELEASE up on an oldie-but-goody machine - ASUS
P3B-F - into which a total of 10 NICs have been thrust. 4 are on an
Adaptec AHA-62044, whose NICs get named sf0 .. sf3 (note that as per the
i386 info at http://www.openbsd.org/i386.html, these are recognised by
the GENERIC kernel but not by the one on the boot CD-ROM); 4 more are on
a D-LINK DFE 570TX, whose NICs get named dc0 .. dc3. (That's a minor
documentation bug in the i386 web page - it says the 570TX NICs will get
driven by the de(4) driver, but it's the dc(4) which does the job in
point of fact. The dc(4) and de(4) man pages get this right).
That's a whoops. Once, that was true. That was..uh..long ago. Fixed.
No massive stress tests done yet, but basic ping and nc of 10MB in
sensible barely-over-a-second time suggests basic functionality working
well. (Actual performance for nc sending a 10MB testfile is about 0.98
seconds on the dc ports of the 570TX, and more like 1.4 seconds on the
sf ports on the Adaptec; both going through one otherwise unloaded
switch to a Windows box.)
Hope that's encouraging/useful to anyone else setting up a multizone
setup with an OpenBSD box as the spider / hydra / Fat Controller /
piggy-in-the-middle / Network Policy Device / whatever you want to call
it...
dmesg sent to openbsd.org's 'dmesg' address, not appended here; shout if
you feel you must see it.
For a test, I once ... well, I'll just jump right to the punch line:
dc19 at pci7 dev 7 function 0 "DEC 21142/3" rev 0x41: irq 10, address
00:60:f5:08:54:27
lxtphy11 at dc19 phy 1: LXT971 10/100 media interface, rev. 1
Hardest part was finding which port was which so I could install the OS
on it. :)
Later, I found I had a six-PCI slot machine, but I never got around to
repeating the test... In case anyone is wondering, that was 3.6-beta,
from Aug. 2004.
Nick.
