LEICHTER-JERRY@YALE.ARPA (07/21/87)
During the last upgrade of my DECSA & LAT software, I found, to my
horror, that calls made from ports with MODEM enabled were set up
as coming from DIALUP terminals.
Shock, horror!
Don't these guys in DEC know about terminal exchanges? The kind that
need modem signals to disconnect? LAT, as I understand it, means
L O C A L Area Transport. This ridiculous change, during a
maintenance upgrade, of all things, means that I have had to
revert to the previous bug ridden, crash-prone version. I use DIALUP
to exclude breakins from W I D E area access, for which it was intended.
[Later, Mr. Williams asks for "a patch for this stupid, STUPID change".]
My, my. Mr. Williams, welcome to the real world in which different people
have different configurations. It's impossible to make EVERYONE happy. There
are tons of people out there with real, live modems connected to their LAT
servers. Anyone connecting in through such a port SHOULD be classified as
DIALUP user.
It gets worse: What happens when you can dial in to the terminal switch, then
connect to the LAT - in addition to having local connections to the switch?
That's the case at this installation.... For this kind of configuration, not
even a LAT option that allowed you to set a port to DIALUP or not by hand
would help - there would literally be no way at all to tell if a connection
was local or remote, short of checking the switch to see where "the other
side" was connected to.
(It wasn't even in the bl**dy release notes!)
I don't have the release notes to look at, but it may have shown up as a bug
fix. (Yes, there were SPR's about the previous behavior.)
-- Jerry
-------