Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!rutgers!aramis.rutgers.edu!athos.rutgers.edu!rapatel
From: rapatel@athos.rutgers.edu ( Rakesh Patel)
Newsgroups: comp.protocols.appletalk
Subject: CAP and Dual interfaced machines.
Message-ID: <488@athos.rutgers.edu>
Date: 22 Dec 87 04:23:00 GMT
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 82
Cc: rapatel



	We have an unusual problem. Has anyone tried running CAP on a
dual interfaced machine? We have two kboxes running KIP 0987, one on
each of two subnets. The machine having the problem is connected
to both the subnets.  The host in question has addresses:

128.6.5.46
128.6.4.4

And the kboxes are:

128.6.4.240
128.6.5.108

The problem is that I can set up atalk.local as follows:

# mynet mynode myzone 
55.5 46 LCSR5
# bridgenet bridgenode bridgeIP
55.4 240 128.6.4.240

This entry makes CAP services accessible on the appletalk network hooked to
the kbox on subnet 4. The CAP services are NOT accessible from the
appletalk connected to the subnet 5 kbox ( i.e. not found under
chooser). The next entry reverses the accessability:

# mynet mynode myzone 
55.4 4 LCSR4
# bridgenet bridgenode bridgeIP
55.5 108 128.6.5.108

In this case, the CAP services are only accessible from the appletalk on the
subnet 5 kbox. CAP services are NOT accessible from anywhere when
attempting to use the following:

# mynet mynode myzone 
55.4 4 LCSR4
# bridgenet bridgenode bridgeIP
55.4 240 128.6.4.240


or 

# mynet mynode myzone 
55.5 46 LCSR5
# bridgenet bridgenode bridgeIP
55.5 108 128.6.5.108



Here is what our atalkatab looks like:

55.5	N1	128.6.5.0	LCSR5		#lcsr
55.4	N1	128.6.4.0	LCSR4		#lcsr

56.1	KC	128.6.4.240	CCISA1		#LCSR admin
	I128.6.4.255	I128.6.5.58		#ipbroad ipname
	I128.6.5.58	L0			#ipdebug ipfile
	L0 L0 L0 L0	S0 S0			#ipother unused unused
	L0		S0	S14		#flags ipstatic ipdynami
	S56.1	S55.4	"CCISA1"		#atneta atnete zonea

56.2	KC	128.6.5.108	LCSRA1		#LCSR admin
	I128.6.5.255	I128.6.5.58		#ipbroad ipname
	I128.6.5.58	L0			#ipdebug ipfile
	L0 L0 L0 L0	S0 S0			#ipother unused unused
	L0		S0	S9		#flags ipstatic ipdynami
	S56.2	S55.5	"LCSRA1"		#atneta atnete zonea



The reason why we made all the zones different was to keep broadcasts
at a minimum on our fairly busy ethernets. Anyone have any ideas as to
why the strange behavior, or better yet, how to fix the problem?
Atalkad is run on 128.6.5.58 if that matters. Note that all our
other machines have worked fine. The only difference being that this
one happens to be dual interfaced to the two ethernet segments that we
use as shown above.



							Rakesh Patel.