My origional message was:
>Hi,
> previously in this group managers have mentioned CAP(Columbia Appletalk
> Protocol). This is an excellent package that, in addition to many other
> capabilities, allows a UNIX file system to appear on an appletalk network.
>
> I have just completed the installation of CAP, to get CAP working properly
> I had to also use a companion package, Unix to Appletalk Router(UAR).
> Does this suggest there is a configuration problem with our departmental
> Cisco?. No one mentioned using UAR in any posting on the subject. Its taken
> me months to figure out what the problem was.
>
> I thought OSF supported Native Ethertalk. Was I wrong?.
>
>
It turns out that all I had to do was to answer yes to the configuration
question that asked if I wanted phase 2 Ethertalk. It works perfectly now.
That will teach me to READ the config options. <sigh>
BTW a number of resondents mentioned removing a reference to pfopen.o in the
makefile in ~[cap]/support/ethertalk/. There was no reference to pfopen.o in
this file.
I assume that patch 197(my current patch level) fixed this.
The responses are included below. Thanks especially to Paul Casteels whose
idiots guide helped figuree it out.
thanks again
boc
Thanks to All who replied.
-------------------------------------------------------------------------------
>From berrigan_at_kent.wednet.edu Thu Jun 20 02:53:31 1996
Hi Brian!
I use CAP over Cisco routers. I only use Native Ethertalk on my Digital Unix
machines and it works fine.
The Cisco interface to which the host is connected looks like this:
interface Ethernet0/3
ip address 111.111.111.111 255.255.255.248
appletalk cable-range 55377-55377 55377.98
appletalk zone EtherTalk
appletalk protocol eigrp
no mop enabled
bridge-group 1
Our appletalk zone name is "EtherTalk", but that is just what our network
person named it (in other words, it is not related to the proper working
of Native Ethertalk, I'm sure you have another name for your zone).
If you have any questions, feel free to ask.
Bob Berrigan
Kent School District
Kent, WA
berrigan_at_kent.wednet.edu
-------------------------------------------------------------------------------
>From scooter_at_kansas.gene.com Thu Jun 20 02:50:52 1996
Brian,
You certainly do not have to use UAR to get CAP to work. We're running
it on several 2100's and 8400's using Ethertalk. You should be using
CAP 6 patch level 197, and everything should work. Don't forget to configure
your kernel for PACKETFILTER support.
-------------------------------------------------------------------------------
>From jshen_at_kidsat.ucsd.edu Thu Jun 20 01:18:34 1996
It's possible that your Cisco router doesn't have Appletalk turned on.
Jay
-------------------------------------------------------------------------------
>From warren_at_atmos.washington.edu Thu Jun 20 01:00:41 1996
I am running native ethertalk and have had no problems. The only place I have even
considered UAR is on by dual network machines.
David Warren INTERNET: warren_at_atmos.washington.edu
(206) 543-0945 Fax: (206) 543-0308
University of Washington
Dept of Atmospheric Sciences, Box 351640
Seattle, WA 98195-1640
DECUS E-PUBS Library Committee representative
SeaLUG DECUS Chair
-------------------------------------------------------------------------------
>From nicolis_at_chiral.phys.univ-tours.fr Wed Jun 19 20:17:33 1996
Hi,
normally OSF does support Native Ethertalk. You should also, however,
have the PACKETFILTER option in the kernel (maybe some other too--I think
there's something to that effect in the FAQ). Keep in mind that OSF/1
works only if cap6.0 is patched up to level 196 (at least). You normally
don't need UAR (at least I didn't need it)--but then that depends on what
application you're after.
Hope this helps
Stam
-------------------------------------------------------------------------------
>From tono_at_goriz.sendanet.es Wed Jun 19 18:21:08 1996
Brian James O'Connor wrote:
<snip>
Hi Brian:
After a lot of time I made with th e following commands:
After you have applied the patches and configure them, you try:
1) edit the file support/ethertalk/makefile and remove the pfopen.o
2) make the makes like the manuals said and...
3) Check that your /sys/conf/YOURMACHINE has selected the option PACKETFILTER, else:
i) cd /dev
ii) MAKEDEV pfilt
iii) doconfig (after you have made a new /vmunix)
4) put on /etc/services:
at-rtmp 201/udp
at-nbp 202/udp
at-echo 204/udp
at-zis 206/udp
5) go to your cap directory and do:
./aarpd -D 20 pf/pfilt0 YOUR_APPLETALK_ZONE &
./atis -D 3 &
Now you can make getzones and view your available localtalk zones or atlook and see what computer are
in YOUR_APPLETALK_ZONE.
BYE.
-------------------------------------------------------------------------------
On Wed, 19 Jun 1996, Brian James O'Connor wrote:
<snip>
Hello,
OSF does support Native Ethertalk. There is no need to install UAR.
I include the steps I took to install CAP on our OSF machines.
Kind regards,
Paul Casteels casteels_at_uia.ac.be Tel: +32.3.8202455
Fax: +32.3.8202245
University of Antwerp Dpt.Physics
Universiteitsplein 1
B-2610 Wilrijk
Belgium
1/ apply the patches (fromm 101 .. 194) with
#!/bin/sh
for i in cap60.patches/cap60.patch*
do
patch -p0 -f -c < $i >> /tmp/pat 2>&1
done
2/ ./Configure
answer all the defaults,but select Native Ethertalk and support for
phase 2.
3/ ./gen.makes
4/ edit support/ethertalk/makefile : (remove pfopen.o)
5/ make include
make libsmade
make programs
make install (puts everuthing in /usr/local/cap)
6/ Make sure you have a vmunix with packetfilter enabled
(check in /sys/conf/NAME_OF_YOUR_MACHINE for options PACKETFILTER)
if not make a new /vmunix with doconfig and make the devices (check man
packetfilter)
MAKEDEV pfilt
6.1/ Check /etc/services :
at-rtmp 201/udp
at-nbp 202/udp
at-echo 204/udp
at-zis 206/udp
7/ Start it with e.g.
/usr/local/cap/aarpd -l /usr/local/cap/aarpd.log pf0 '*'
/usr/local/cap/atis -l /usr/local/cap/atis.log
/usr/local/cap/aufs -l /usr/local/cap/aufs.log
8/ check the man page for AUFS to make a connection to a directory.
Received on Thu Jun 20 1996 - 02:00:36 NZST