Keep in mind that the IOS also eats a lot more RAM than ComOS, and the
room needed to store routes depends in large part of the format you store
them. You cannot compare the two directly.
>case current portmaster hardware is not capabable of dealing with such
>enormious routing tables let alone simply using 2 fully loaded T1 lines.
This is not true. IRX-112 and IRX-114 are routinely used with 2 T1s
maxed out and they handle it fine.
>seeing it (still waiting for pm2er30) my guess is that Livingston will have
>BGP4 running by the time it is ancient history, I'd rather see some effort
We already have it running internally.
>in ipv6 and the mysterious stuck-W1 bug (deny everything you want but it
>remains a comos bug)
We have seen almost no demand for IPv6. And looking at the industry it
seems to be almost studiously ignored. And looking at the IETF docs on it
I can see why - there is still much to be worked out before it is a useful
replacement for IPv4. And now we have splinter groups arguing that v6 is
flawed and proposing new specs for other systems. This flares up on the
IETF mailing list from time to time.
And *what* stuck W1 bug? The last W1 bug I was aware of was fixed several
revs ago, at 3.3.1. And everyone I know who had reported the bug with
the earlier code reported it fixed in the new code.
Are you running recent code?
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588