So, I'm with Virgin ADSL and it's terrible.
Moving swiftly on.
Quite regularly, the PPP session will drop. This is indicated by a red light on the supplied ADSL router. ADSL synch remains at this point. It does eventually reconnect, or I can force a connect via the web interface. Jolly good show.
I have swapped the supplied router for a cisco 877. It seems to hold synch much better, especially with an extra +3db of SNR margin but when the PPP session does eventually drops, it takes the synch with it. Is there a way to make the 877 NOT re-synch when PPP drops? Example of current drop below.
Moving swiftly on.
Quite regularly, the PPP session will drop. This is indicated by a red light on the supplied ADSL router. ADSL synch remains at this point. It does eventually reconnect, or I can force a connect via the web interface. Jolly good show.
I have swapped the supplied router for a cisco 877. It seems to hold synch much better, especially with an extra +3db of SNR margin but when the PPP session does eventually drops, it takes the synch with it. Is there a way to make the 877 NOT re-synch when PPP drops? Example of current drop below.
Code:
*Aug 20 16:06:04.787: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
[b]*Aug 20 16:06:04.787: Vi2 PPP: Authorization required[/b]
*Aug 20 16:06:04.787: Vi2 PPP: No remote authentication for call-out
tupac#
*Aug 20 16:06:04.791: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0
*Aug 20 16:06:05.787: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
tupac#
*Aug 20 16:06:05.851: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Aug 20 16:06:06.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
tupac#
*Aug 20 16:06:24.896: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Aug 20 16:06:25.896: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
tupac#
*Aug 20 16:06:32.045: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
*Aug 20 16:06:32.045: %DIALER-6-BIND: Interface Vi2 bound to profile Di0
tupac#
*Aug 20 16:06:32.045: Vi2 PPP: Using dialer call direction
*Aug 20 16:06:32.045: Vi2 PPP: Treating connection as a callout
*Aug 20 16:06:32.045: Vi2 PPP: Session handle[9D000052] Session id[160]
*Aug 20 16:06:32.045: Vi2 PPP: Authorization required
*Aug 20 16:06:32.045: Vi2 PPP: No remote authentication for call-out
tupac#
*Aug 20 16:06:34.530: Vi2 PPP: No authorization without authentication
*Aug 20 16:06:34.534: Vi2 CHAP: I CHALLENGE id 1 len 31 from "oxfd-bam-1"
*Aug 20 16:06:34.534: Vi2 CHAP: Using hostname from interface CHAP
*Aug 20 16:06:34.534: Vi2 CHAP: Using password from interface CHAP
*Aug 20 16:06:34.534: Vi2 CHAP: O RESPONSE id 1 len 51 from "[email protected]"
*Aug 20 16:06:34.754: Vi2 CHAP: I SUCCESS id 1 len 4
tupac#
*Aug 20 16:06:35.758: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up