We have a user that is trying to connect to a PM3 running 3.7.2 on a PRI
with a Digi Datafire U card in a 95 box.
When checking out the debugging on the PM3, the following is what is
displayed:
---snip!---
(all looks good up until this point)
Sending LCP_CONFIGURE_REQUEST to port S15 of 14 bytes containing:
01 05 00 0e 05 06 eb ac de 9c 03 04 c0 23
Sending LCP_CONFIGURE_REQUEST to port S20 of 14 bytes containing:
01 05 00 0e 05 06 a2 1a 4d b9 03 04 c0 23
ppp_recv (S20): Bad PPP Address
ppp_recv (S15): Bad PPP Address
ppp_recv (S20): Bad PPP Address
ppp_recv (S15): Bad PPP Address
ppp_recv (S20): Bad PPP Address
ppp_recv (S15): Bad PPP Address
---unsnip!---
...and this goes on ad-infinitum until the PM3 times out and hangs up the
line. The connection is obviously unsuccessful. :)
None of us here has ever seen the "Bad PPP Address" before... Can anyone
shed any light on this situation?
Thanks Much!
Christopher Beck
Network Engineer
OneNet Communications, Inc.
513.554.1638 - cpbeck@one.net
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.