MorningStar PPP
Scott Taylor
On OSR5.0.5a does anybody know where Morning Star 2.1.2a keeps it's
modem init string? I want it to be audible when dialing out.
I have a USR Courier V.everything connected to it and, according to
mstppp settings it is using atdialUSR. So what do I have to do to hear
it connecting.
Also, how can I see at which speed it connected at? The pppd.log says
Dialer connected at speed index 0, I think that's a Zero. The ISP has a
56K dialup connection, can mstppp connect at 56K? If so how, or is it?
Thanks.
Scott Taylor
larry
larry
Scott Taylor wrote in message <37F0ECCB...@home.NOT.com>...
Jean-Pierre Radley
| Hi all,
| On OSR5.0.5a does anybody know where Morning Star 2.1.2a keeps it's
| modem init string? I want it to be audible when dialing out.
|
| I have a USR Courier V.everything connected to it and, according to
| mstppp settings it is using atdialUSR. So what do I have to do to hear
| it connecting.
Why do you want that modem noise, when you can just tail the pppd.log?
Your atdialUSR defaults file is either in /usr/lib/uucp/defaults, or
better, in /etc/defaults (better because the first directory has 1000
files in it, and atdialer looks first in /etc/defaults anyhow).
| Also, how can I see at which speed it connected at? The pppd.log says
| Dialer connected at speed index 0, I think that's a Zero. The ISP has a
| 56K dialup connection, can mstppp connect at 56K? If so how, or is it?
Mstppp doesn't do any connecting; it uses the dialer you specified.
It connects at the highest possible speed negotiated by your modem and
the remote modem, but not higher than the speed you specified in
/usr/lib/mstppp/Devices. Try it manually using cu.
--
Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
Evan Hunt
Don't blame me, I voted for Scott Taylor <s.ta...@home.NOT.com>.
>Hi all,
>On OSR5.0.5a does anybody know where Morning Star 2.1.2a keeps it's
>modem init string? I want it to be audible when dialing out.
Two places: Either /usr/lib/uucp/default/*, or /usr/lib/mstppp/Dialers.
>I have a USR Courier V.everything connected to it and, according to
>mstppp settings it is using atdialUSR. So what do I have to do to hear
>it connecting.
Okay, that one's in /usr/lib/uucp/default/atdialUSR. You can modify
that file to remove the "M0" from the MDM_INIT line (and perhaps replace
it with "M1"),
or,
You can switch to one of the USR dialers in /usr/lib/mstppp/Dialers,
such as USR, USRv34Sportster, etc, none of which (as far as I know)
turns off the speaker.
--
Evan Hunt - evanh at sco dot com
"The wages of sin are death. But after taxes are taken out,
it's just a sort of tired feeling." - Paula Poundstone
Scott Taylor
Evan Hunt wrote:
>
> Don't blame me, I voted for Scott Taylor <s.ta...@home.NOT.com>.
> >Hi all,
> >On OSR5.0.5a does anybody know where Morning Star 2.1.2a keeps it's
> >modem init string? I want it to be audible when dialing out.
>
> Two places: Either /usr/lib/uucp/default/*, or /usr/lib/mstppp/Dialers.
>
> >I have a USR Courier V.everything connected to it and, according to
> >mstppp settings it is using atdialUSR. So what do I have to do to hear
> >it connecting.
>
> Okay, that one's in /usr/lib/uucp/default/atdialUSR. You can modify
> that file to remove the "M0" from the MDM_INIT line (and perhaps replace
> it with "M1"),
>
That is the file that I changed. However, it didn't have MDM_INIT but
it did have MDM_SETUP, so I added M1 to the string, still didn't produce
the results I wanted. And yes the volume works on the modem.
> or,
>
> You can switch to one of the USR dialers in /usr/lib/mstppp/Dialers,
> such as USR, USRv34Sportster, etc, none of which (as far as I know)
> turns off the speaker.
>
So I guess my next question is: how do you tell mstppp to use
/usr/lib/mstppp/Dialers instead of /usr/lib/uucp/default/atdialUSR ?
Is there some better documentation on setting up mstppp manually? The
stuff I read on it in the 'X' help documents wasn't allot of help and
there are no man pages, that I can find, for mstppp.
thanks
Evan Hunt
Don't blame me, I voted for Scott Taylor <s.ta...@home.com>.
>So I guess my next question is: how do you tell mstppp to use
>/usr/lib/mstppp/Dialers instead of /usr/lib/uucp/default/atdialUSR ?
>Is there some better documentation on setting up mstppp manually? The
>stuff I read on it in the 'X' help documents wasn't allot of help and
>there are no man pages, that I can find, for mstppp.
There are man pages... "man MST_PPP Dialers", for instance.
To answer your question, just use a different dialer name
in the Devices file. atdialUSR only exists in one of the two
places; USRv34Sporster only exists in the other one.
Scott Taylor
Evan Hunt wrote:
>
> Don't blame me, I voted for Scott Taylor <s.ta...@home.com>.
> >So I guess my next question is: how do you tell mstppp to use
>
> There are man pages... "man MST_PPP Dialers", for instance.
Thanks Evan, that'll help a lot.
For some reason, on my system, "man MST_PPP ppp.Dialers", "man -k MST"
shows these. Of course, I have only ever "tried man -k mstppp" and got
'nothing appropriate'. Now had I paid attention to "man -k ppp"... The
life of a groveling IT Manager.
These files make things much clearer. Well mostly anyhow. Still don't
know how to tell what speed I'm connected at. In pppd.log it says
"speed index 0" but I can not find anything in the man's for that. What
speed is index 0? In my /etc/gettydefs index 0 is B9600. I really
don't think my ISP would even allow a connection under 14.4 so this is
obviously not referring to the gettydefs speed index. So what is it
referring to?
Thanks again.
Evan Hunt
Don't blame me, I voted for Scott Taylor <s.ta...@home.NOT.com>.
>These files make things much clearer. Well mostly anyhow. Still don't
>know how to tell what speed I'm connected at. In pppd.log it says
>"speed index 0" but I can not find anything in the man's for that. What
>speed is index 0?
38400 baud, I believe. Isn't that nicely intuitive? :)
This comes from the UUCP dialer. See, originally, baud rates used
to go up to 19200 and stop. When the higher rates were added, about
four years ago, older applications that depended on the assumption
that there were exactly 16 baud rates and they could all fit inside
a four-bit number started showing up oddities. Atdialer is one
of them; it reports the connection speed as the low-order four bits
of its exit value, and the other four bits are used for other things,
so I can't easily fix it.
Fortunately, having speed index 0 or 1 or 2 show up doesn't cause too
much conflict, since nobody in his right mind would actually be *using*
a 0, 50 or 75 baud connection. So it's safe to just read it as if we'd
retired those useless low speeds and reused them for new fast ones.
The easy way to find out what the actual speed is, is establish a
connection and then run:
# stty -a < /dev/tty1A
(or whatever tty it is)
Scott Taylor
Evan Hunt wrote:
>
> Don't blame me, I voted for Scott Taylor <s.ta...@home.NOT.com>.
> >These files make things much clearer. Well mostly anyhow. Still don't
> >know how to tell what speed I'm connected at. In pppd.log it says
> >"speed index 0" but I can not find anything in the man's for that. What
> >speed is index 0?
>
> 38400 baud, I believe. Isn't that nicely intuitive? :)
>
> This comes from the UUCP dialer. See, originally, baud rates used
> to go up to 19200 and stop. When the higher rates were added, about
> four years ago, older applications that depended on the assumption
> that there were exactly 16 baud rates and they could all fit inside
> a four-bit number started showing up oddities. Atdialer is one
> of them; it reports the connection speed as the low-order four bits
> of its exit value, and the other four bits are used for other things,
> so I can't easily fix it.
Interesting.
>
> Fortunately, having speed index 0 or 1 or 2 show up doesn't cause too
> much conflict, since nobody in his right mind would actually be *using*
> a 0, 50 or 75 baud connection. So it's safe to just read it as if we'd
> retired those useless low speeds and reused them for new fast ones.
> The easy way to find out what the actual speed is, is establish a
> connection and then run:
>
> # stty -a < /dev/tty1A
> (or whatever tty it is)
Wow, wouldn't it be nice if the output of this command were true;
speed 115200 baud; ispeed 115200 baud; ospeed 115200 baud;
Ok, so now that I know the port speed, I still want to make sure I am
getting my $$$ worth from my ISP. This modem handles about 30 users
email requests and perhaps 3 or 4 users browsing (fortunately not heavy
users). I can't help it, the office is out in the bush and no high
speed connections out here. So you can see my concern for making sure I
get the best connection I can.
Well, thanks again Evan. Unless you can think of something else, I
guess I'll go back to listening to the handshake. :o)
Scott
Evan Hunt
Don't blame me, I voted for Scott Taylor <sta...@maaxwestco.ca>.
>Ok, so now that I know the port speed, I still want to make sure I am
>getting my $$$ worth from my ISP.
Oh! You wanted the actual speed the modem's running at; I thought you
wanted to know how fast the serial port was running. Two whole
different things.
If the modem reports the speed with "CONNECT 28800" or some such, then
you might be able to log that information, but otherwise I'm afraid
there's not much I can suggest; neither UUCP nor PPP keeps track of it.
You could probably spot-check throughput by timing the transfer of a
known-size file periodically, but that's all I can think of.