🚀 go-pugleaf

I have been given responsibility for many of our FastPaths here and,
after RTFM'ing as much as I can find, I have a question (or maybe
two).  I know that I need an IPTalk network port (N or H line)
configured in my atalkatab file for each FastPath that supports an
IPTalk-based CAP host.  This is clear and obvious.  I _think_ I do
_not_ need one for the FastPaths that will be doing IP encapsulation
across our IP-only backbone if they are not supporting CAP hosts.  Is
this correct?  For example, consider the following two FastPaths on a
subnetted class B network:

1.1 K	128.210.1.1 "PUCC-Local1"	# LocalTalk port
2.1 E	128.210.1.1 "PUCC-Ether1"   	# EtherTalk phase 1 port
    	<miscellaneous configuration details for this box>

1.2 K	128.210.2.1 "PUCC-Local2"   	# LocalTalk port on box 2
2.2 E	128.210.2.1 "PUCC-Ether2"   	# EtherTalk phase 1 port, box2
    	<miscellaneous configuration details for this box>

Assuming an IP-only network connects these two subnets, can Macs on
each network communicate with all others Macs on other networks or do
I need to add lines like:

3.1 H	128.210.1.1 "PUCC-IP1"	    	# IPTalk port
3.2 H	128.210.2.1 "PUCC-IP2"	    	# IPTalk port, box 2

Any help would be appreciated.

Thanks,
Scott M. Ballew
PUCC Networking