> But why? It's just another route.
There is much more to this than just another route. What you are doing is
asking the ethernet card to also support arp and other broadcast traffic
for the second Class C. ARP tables have to be larger, time to resolve an
address is longer etc., Which also complicates routing if you are using
anything but static routes. All this MAY require a tad more horsepower
than the 386/33 in the PM-2 is ready to deliver. Although it has "some"
of the qualities of a router, noone ever said the PM-2 was suited to that
purpose.
> This brings up a question I have about
> static addresses. On my Linux term servers, I've been too
> busy/overworked/lazy (pick one) to configure gated...so I have this nasty
> hack of routing an extra /24 out eth0 on our Cisco (internet gateway).
> Do I need to assign another /24 for this and subnet it into little tiny
> bits or just use addresses from our primary ethernet /24 for isdn static
> addresses? Neither of these is an appealing thought.
Well you can resolve this in many ways. The above will work in a fashion.
Or, you can wait for ComOS 3.5 which supports OSPF and VLSM. Then get
contiguous Class C's and supernet them together into a larger network. Or
you can plan out your network, start using a routing protocol, learn
gated, etc. Then your static network is not subnetted, but for static IP
gets advertised as a host route vice a network/subnet route. IMHO, you
are pushing static routes and proxy arp a bit hard if you have already
exceeded 255 hosts between your customers and internal net. If you set it
up right, you can not only simplify your network, but you can also lower
the amount of ARP broadcast traffic on your network, which is probably
high now. For example, we have over 275 modems (dynamic IP
split/subnetted over 2 Class C's), Our internal network is on another
Class C. Static IP customers are on another Class C, and virtual web
hosts are on another Class C.. The only Class C that needs host routing is
the static IP Class C. Our web server acts as the router/gateway to the
virtual hosts. Each portmaster/terminal server as the router to its
subnet of dynamic addresses. One problem with many hundreds of hosts on
one network is that when there is a power outage or whatever, there is a
huge broadcast storm as every machine tries to repopulate its arp cache.
Some intelligent switches/hubs will interpret this as a problem and
incorrectly shutdown traffic.