> The modem code in ComOS 3.9b8 is the same modem code
> included in ComOS 3.8.2 for the PortMaster 3.
:-( But then, we knew this was going to be the case.
Does anybody have any rough idea as to when a 3.9 beta
with new modem code might come out? A couple of weeks?
Two months? Six months? I know Lucent cannot commit
to anything, but even a conservative guestimate would
be appreciated, if at all possible.
> No bugs have been fixed in ComOS 3.9b8.
-This- surprised me. :-( :-( Ah well. I won't be
loading this beta. I'll wait until a version gets
released with updated modem code, that's probably
my biggest concern at the moment. The new features
are cool, and definitely welcomed, but I'll leave
the beta testing to others for the moment. :-)
I am going to check with our telco to see if we can get
NFAS, though, I'd love to squeeze an extra B channel out
of our PRIs. But I'll probably wait until I've loaded
the updates for other reasons (like modem code), and others
have had a chance to beat on the beta a little.
> WARNING! The amount of nonvolatile ram (NVRAM) available for saving
> configurations has been reduced from 128KB to 64KB. PortMaster
> products with configurations greater that 64KB will lose some of
> their configuration. For this reason, be sure to backup your
> PortMaster configuration before upgrading to this release.
Is there any way to easily tell how large our configurations are?
I seriously doubt that we're anywhere near that, since we have a
fairly simple configuration, with RADIUS used for all user/dialin
control. Apart from the basic global configuration, we have a
small OSPF setup, and a few small filters, and I'd be very surprised
if we were over 64 KB with that! But it would be nice to have a
way to definitively know if a given configuration is going to be
too large.
Michael Bryan
pmu@ursine.com
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>