---cut---
The following is just advice, which you're free to accept,
ignore, or modify as your own judgement suggests.
The below assumes you have 20 PortMasters (or anywhere between 8 and
250 PortMasters), that you assign all the user addresses from the
dynamic address assignment pools on the PortMasters, and that you're
using the 205.164.206.0 network for your ethernet.
PortMasters. All PortMasters must be running ComOS 3.1.2 (or later).
Proxy ARP is convenient for 7 or fewer PortMasters, but should be
avoided as you scale up. Instead, use your 205.164.206.1 network for
the ethernet, and carve your other networks up among the PortMasters,
with each network providing 30 addresses for the assigned pool of each
of 8 PortMasters.
For example, if you're using networks
205.164.207.0, 205.164.208.0, and 205.164.209.0 for your assigned pools,
then on EVERY PortMaster you would use the following commands:
set ether0 address 205.164.206.X (for some value of X)
set gateway 205.164.206.Y (where Y points at your Cisco gateway)
set authenticate 205.164.206.1
set accounting 205.164.206.1
set secret (whatever)
add netmask 205.164.207.0 255.255.255.224
add netmask 205.164.208.0 255.255.255.224
add netmask 205.164.209.0 255.255.255.224
set ether0 routing on
save all
Normally routes are collapsed on network boundaries (See RFC1058 for
an explanation). The Netmask Table collapses routes on the boundaries
specified, so that if say on one PortMaster you have an assigned Pool
starting at "set assigned 205.164.207.33" that instead of broadcasting
that it has a route to the 205.164.207.0" network, it would say that
it has a host route to 205.164.207.33 - the other PortMasters will see
that route, look in their OWN netmask table, and convert it back into
a subnet route to 205.164.207.33 through 205.164.207.62.
The Cisco doesn't support the netmask table, so you need to set a
static route on it for each of the 3 destination networks for your
assigned pools (205.164.207.0, 205.164.208.0, and 205.164.209.0),
pointing at ONE of the PortMasters. It will then forward the packets
to the proper PortMaster. If you were using an IRX running ComOS 3.2R
instead of a Cisco, you could set the netmask table on it, too, and
it listen to RIP from the PortMasters and route directly.
-- Carl Rigney Livingston Technical Support support@livingston.com 800-458-9966---cut---
-MZ
-- Although I work for Livingston Enterprises Technical Support, I alone am responsible for everything contained herein. So don't waste my managers' time bitching to them if you don't like something I've said. Flame me. Phone: 800-458-9966 support@livingston.com <http://www.livingston.com/> FAX: 510-426-8951 6920 Koll Center Parkway #220, Pleasanton, CA 94566