Very Computer

>'diald' warms up the link; 'pppd' agrees with everything, and I'm
>online. But how do I query the system to see how fast the modem is
right
>now? (Besides tacky brute force - pumping 57,600 bits through it and
>timing them?)

> >So I add 'speed 57600' to my 'diald.conf' to see what happens.
> >Historically, Window's fully integrated user interface has told me in
> >little tooltips that the modem was currently going at 38,400, so that's
> >what I started my Linux at, but now I want to see if my ISP's new 57k
> >modem pool works.

> >'diald' warms up the link; 'pppd' agrees with everything, and I'm
> >online. But how do I query the system to see how fast the modem is
> right
> >now? (Besides tacky brute force - pumping 57,600 bits through it and
> >timing them?)

> Someone who wishes to remain anonymous, to whom we will refer as "Joe
> Smulowicz", has pointed out that if you pass the Verbose option -v to
> 'chat' it will emit to the system log what the modem is saying as 'chat'
> replies to those items it recognizes. Then your modem might write a tiny
> snip of text reporting what rate and encoding it negotiated, such as
> "31200\ARQ".

> >So I add 'speed 57600' to my 'diald.conf' to see what happens.
> >Historically, Window's fully integrated user interface has told me in
> >little tooltips that the modem was currently going at 38,400, so that's
> >what I started my Linux at, but now I want to see if my ISP's new 57k
> >modem pool works.

> >'diald' warms up the link; 'pppd' agrees with everything, and I'm
> >online. But how do I query the system to see how fast the modem is
> right
> >now? (Besides tacky brute force - pumping 57,600 bits through it and
> >timing them?)

> Someone who wishes to remain anonymous, to whom we will refer as "Joe
> Smulowicz", has pointed out that if you pass the Verbose option -v to
> 'chat' it will emit to the system log what the modem is saying as 'chat'
> replies to those items it recognizes. Then your modem might write a tiny
> snip of text reporting what rate and encoding it negotiated, such as
> "31200\ARQ".

> Of course I also could have sampled the sounds of the various baud rate
> attempts leading up to the click and then manually decoded them...