I think there is a fundamental communications gap here. Note that the PM
keeps receiving the SAME request, over and over. We never once recieve an
ACK or a NAK despite all of the requests we've sent. And, we've ACK'd the
request each time, yet the Pipeline keeps making it.
It seems that the Pipeline is not seeing anything from the PM. The PM
is seeing it - but not the other way around. If you can I'd do a debug on
the Pipeline to see what, if anything, it is receiving back.
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
>Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
-MZ
-- <URL:mailto:megazone@megazone.org> Gweep, Discordian, Author, Engineer, me.. Join ISP/C Internet Service Providers' Consortium <URL:http://www.ispc.org/> "A little nonsense now and then, is relished by the wisest men" 781-788-0130 <URL:http://www.megazone.org/> <URL:http://www.gweep.net/> Hail Discordia! - 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/>