>I don't see the problem with his answer. If it is a MP connection then
>the PPP debug output (0x51) and the ISDN debug output is obviously most
>relevant to tracking down what is going on. I don't see how saying that
>it is an MP connection, where you are dropping a channel and bringing it
>back up somehow cancels out the need for us to see the the debugging
>output from the PM. Yes, we do make the box--that is why we need to see
>OUR *own* debugging output--obviously that is the most useful and readable
>output from our standpoint.
The problem here sounds suspiciously like the problem I've reported using
Ascend Pipes. The bottom line (in my situation) was that BACP is broken
in it's current state on the PM3. A 2 channel connection will come up
fine, but if the second channel is dropped for any reason the dialing,
BACP-enabled router will NOT be able to reconnect it. Of course this is a
beta, so you can't really complain... nevermind it's been in beta for
months and months with no end in sight.
jon
(I run b13, but have seen no mention of BACP fixes in any versions since,
and don't feel like subjecting myself to modem issues with later betas.)
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>