Subject: Followup to ATM cabling question.
To: None <email@example.com>
From: Darren Reed <firstname.lastname@example.org>
Date: 03/15/2000 12:21:07
Note, this is not at all NetBSD-centric..
Last week I posted, asking about setting up ATM in a crossover.
Some said yes, some said no.
Well, I have now managed to get to FORE SBA-200 cards talking to
each other, running FORE's latest drivers with Solaris 2.6/7.
I did have to manually configure the ATM card addresses (NSAP?)
and have not used any VC's, high redundancy/failure, etc, options.
# ifconfig fa0
fa0: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 9188
inet 192.168.8.2 netmask ffffff00 broadcast 192.168.8.255
on the other host:
# ifconfig fa0
fa0: flags=843<UP,BROADCAST,RUNNING,MULTICAST> mtu 9188
inet 192.168.8.1 netmask ffffff00 broadcast 192.168.8.255
It is somewhat interesting to compare using FDDI with ATM (both in
a loopback setup between the two hosts):
# spray -c 100 -l 4100 192.168.6.1 -d 0
sending 100 packets of length 4100 to 192.168.6.1 ...
9 packets (9.000%) dropped by 192.168.6.1
1182 packets/sec, 4849737 bytes/sec
# spray -c 100 -l 4100 192.168.8.1 -d 0
sending 100 packets of length 4100 to 192.168.8.1 ...
33 packets (33.000%) dropped by 192.168.8.1
929 packets/sec, 3809140 bytes/sec
oh, the ifconfig for the FDDI card looks like this:
nf0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 4352
inet 192.168.6.2 netmask ffffff00 broadcast 192.168.6.255