I dunno how it is possible.. they're both Rockwell - perhaps something from
Rockwell? AFAIK K56 & V34 use different encoding and signalling things
though.. perhaps it was just lying to show that it connected fast then
showed the correct rate? Little rockwell "feature" ? :)
I've seen it happen more than once..
On Tue, Feb 03, 1998 at 03:17:52PM +0000, Chris Adams wrote:
> According to Paul White <pwhite@livingston.com>:
> >The second thing I would like to bring up is the fact that
> >K56Flex will not re-negotiate down to V.34 speeds. However It
> >will retrain to other PCM speeds. I recently saw a
> >post with a user stateing that after a long period of
> >idle time, his 48k connection would drop to 24k. This is
> >not possible - The connection would have hung up after
> >34k (Maybe he typo'd.)
>
> Well, I posted that I had seen it, and I did not typo. I have a Hayes
> Accura 56k external speakerphone modem. It has 1.12 firmware in it. It
> tends to retrain a lot (partially because my apartment has cruddy
> lines). If I just let it connect with the init string from the .INF
> file, it will connect at 50K most of the time, but retrain constantly
> during telnet connections. If I FTP a big file down, it will usually
> not retrain while the file is moving. It seems to train down when I
> type and try to train back up when it is idle.
>
> Anyway, to try to limit the retrains, I put a '+ms=,,,42000,,,' on the
> init string, which limits the PCM connects to 42K, and that is what it
> usually connects at. However, I have had it connect at 42K and train
> down to as low as 4800. I am checking speeds via SNMP on the PM3. I am
> pretty sure it really is 4800, as things go _really_ slow when this
> happens.
>
> I just went looking in my RADIUS records, and here is an example:
>
> Mon Jan 19 15:41:39 1998
> Acct-Session-Id = "0C003D57"
> User-Name = "someuser"
> NAS-IP-Address = someip
> NAS-Port = 14
> NAS-Port-Type = Async
> Acct-Status-Type = Start
> Acct-Authentic = RADIUS
> Connect-Info = "44000 LAPM/V42BIS"
> Service-Type = Framed-User
> Framed-Protocol = PPP
> Framed-IP-Address = someotherip
> Acct-Delay-Time = 0
> Timestamp = 885246099
>
> Mon Jan 19 15:48:23 1998
> Acct-Session-Id = "0C003D57"
> User-Name = "someuser"
> NAS-IP-Address = someip
> NAS-Port = 14
> NAS-Port-Type = Async
> Acct-Status-Type = Stop
> Acct-Session-Time = 402
> Acct-Authentic = RADIUS
> Connect-Info = "4800 LAPM/V42BIS"
> Acct-Input-Octets = 5434
> Acct-Output-Octets = 3024
> Acct-Terminate-Cause = Lost-Carrier
> Service-Type = Framed-User
> Framed-Protocol = PPP
> Framed-IP-Address = someotherip
> Acct-Delay-Time = 0
> Timestamp = 885246503
>
> There are quite a few examples of this in the RADIUS logs, and since I
> have had it happen to me several times, I don't think it is a cosmetic
> or reporting bug.
>
> Maybe it isn't _supposed_ to be possible, but it does look like it is
> happening.
> --
> Chris Adams - cadams@ro.com
> System Administrator - Renaissance Internet Services
> I don't speak for anybody but myself - that's enough trouble.
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
-- - Steve - Systems Manager - Community Internet Access, Inc. - Gallup and Grants, New Mexico - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.