The DE4X5 drivers don't do "insl()", and *should* work out-of-the-box, if
you've got the latest from Dave Davies. They work just fine here, with our
1.2.8-based kernels... :-)
> Oh, and if you use OSF/1 telnet, you'll notice that out-of-band data
> doesn't work with OSF/1 binaries (^C in a telnet session will freeze the
> session, and you'll have to exit telnet with ^]). I haven't looked into
> it, but I suspect it's due to different definitions for SO_OOBINLINE, so
> socket options aren't set the way the OSF/1 binaries expect. I'll
> probably make this binary compatible with OSF/1 as well but I wanted to
> release 1.3.7 before starting on looking into this.
This is also true of our natively built "telnet" as well... :-(
> ttcp gives reasonable numbers for both tcp and udp transfers, but they
> certainly aren't stellar. Probably because the linux networking isn't
> _that_ fast, not so much any axp-specific stuff. Anyway, it's not due
> to alignment issues: the way things are set up now, almost all normal
> networking headers will be automatically aligned, and unaligned traps
> are pretty rare.
Our "ttcp" numbers for the DE4X5 were over 1MB/sec, and that with my
admittedly SLOW checksum routines; I think it depends greatly on the
quiescence (is this a word? :-) of the net, and the speed of the sender
and recipient (I got my numbers using a DEC 3000/400 as the other end).
> I haven't done any _extensive_ tests of the networking, and quite
> frankly some of the 1.3.x networking stuff is pretty experimental (even
> on the i386), but early indications are that things seem to work ok.
Yes, after making the "unsigned long" to "u32" translations in 1.2.8, and
implementing checksumming, it has worked *marvelously*: we've got most of
the daemons up now; inetd/tcpd/ftpd/rlogind/fingerd/rshd/telnetd. The hardest
one was "ftpd", as an OSF-built one will have the password encoding from
the OSF libc, and not work with a LINUX /etc/passwd... :-( :-(
> Oh, to get networking up and running, you'll need axp versions of the
> linux "route" and "ifconfig". Those are reasonably simple: make sure
> you have the new kernel header files and check your linker flags (-N
> doesn't seem to be that good an idea) and they should compile more or
> less out of the box. I guess I should make my binaries available, duh.
We need to coordinate the new syscall numbers with the libc implementations;
any chance you'd like to make it public, or is it already "in there"?
--Jay++
-------------------------------------------------------------------------------
American Non Sequitur Society: we don't make sense, but we do like pizza...
Jay A Estabrook Alpha Migration Tools
Mailstop: TAY1-2 (DTN) 227-4202
Digital Equipment Corp. (external) (508) 952-4202
151 Taylor Street enet: jestabro@amt.tay1.dec.com
Littleton, MA 01460-1407 decnet: tallis::jestabro
-------------------------------------------------------------------------------