> Just set up a Livingston Router. It was shipped with obsolete software
> that didn't work with the LMI protocol, and can NOT have more than one
> subnet mask type. This is a FATAL flaw. My frame relay service provider
> had to provide me with an entire class C address just so they could have
> a dedicated circuit to our Livingston router. IE:
> Insinc (frame relay service provider) netmask (router-router) was
> 255.255.255.252. Perfect, gate the routers their own little net - 1,2
> for the routers and 0 and 3 for network and broadcast address. The
> Livingston IRX portmaster could not do this as I required a netmask of
> 255.255.255.0 for my internal network.
> In short, I needed the frm1 interface to have a netmask of 255.255.255.252.
> I needed my ether0 interface to have a netmask of 255.255.255.0.
> The Livingston portmaster could not handle this. Yuck.
Funny thing, I just replaced my Livingston with Cisco 2500, the Livingston
was grabbing my internal packets and bouncing it off the router at my service
provider. What I actually had to do was create permanent arp entries in my
bastion host to get around this problem.
Granted I have had the Cisco for about an hour but it seems to be handling
the routing much better.
Manager, System & Architecture
Prentice Hall Legal & Financial Services