> > Ya know, I like Livingston a lot. But what is this sorry piece of excuse
> > for code doing on your site? I made the mistake of "upgrading" one of our
> > boxes(thank god *only* one) with this. Now, the portmaster is exhibiting
> > all sorts of weird behaviour, like, taking a couple of BRI's out of
> > service, the inability to ping("unable to submit request?",) customers not
> > being able to get connected, and a myriad of other odd behaviour. I have
> > tried re-installing with similar results.
>
> I basically had an opposite experience. I was running 3.1.4 until I got
> bit by the 0.0.0.0 bug. I upgraded to 3.3.2, and things seemed fine for
> a few weeks except for the idle timeout. One day, the Portmaster started
> dropping every call as soon as it was answered, and power cycling didn't
> help.
>
> I upgraded to 3.3.2c1 right away, and things have been fine since.
> 3.3.2c1 also fixed the idle timeout problem.
Well turns out the problem was bad flash memory. So I have gone from an
almost working box(had the BRI bug that lost one BRI out of the 5) to
having a the machine RMA'd as a result of an attempted upgrade.
Frankly, I am a bit scared to try again lest we have to RMA all of our
Portmasters.
While I understand that hardware can and does go bad, what I fail to
understand is why some type of error detection isn't implemented when
attempting to upgrade, or if it is why it doesn't seem to work too well.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Patrick Greenwell (510) 943-5769 voice
Systems Administrator (510) 210-2000 modem
Value Net, Inc. (510) 943-1708 fax
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/