Hi, just as an addition to this year old bug. I have seen this happening myself with GPRS connections which sometimes happen to not reply lcp echo requests. This is a CLEAR violation of RFC1661 and your provider is to blame not ppp. Typically lcp echo request/reply is a good thing to do to detect a hung/dead line and the pppd to disconnect and probably to redial/hang up. As a Carrier Network Staff member i have seen commercial RAS boxes using up all their resources due to the lack of lcp echos and non detected hung DSL sessions.
The claim "the user will notice that the line's down anyway, when he won't be able to get any traffic accross" is bogus as its of no help if you are on the wrong side of the link (Physically) and cant reach your homebox because it has not detected the failed link and redialled. Here is a excerpt from RFC1661 http://www.ietf.org/rfc/rfc1661.txt ------------------------------------------------------------------- 5.8. Echo-Request and Echo-Reply Description LCP includes Echo-Request and Echo-Reply Codes in order to provide a Data Link Layer loopback mechanism for use in exercising both directions of the link. This is useful as an aid in debugging, link quality determination, performance testing, and for numerous other functions. Upon reception of an Echo-Request in the LCP Opened state, an Echo-Reply MUST be transmitted. Echo-Request and Echo-Reply packets MUST only be sent in the LCP Opened state. Echo-Request and Echo-Reply packets received in any state other than the LCP Opened state SHOULD be silently discarded. ------------------------------------------------------------------------- Sending LCP Echo Requests is a "Good thing to do". Flo -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Heisenberg may have been here.
signature.asc
Description: Digital signature
