Bug #3963
closed
PPPoE client interface status wrong while attempting to connect
Added by Chris Buechler almost 11 years ago. Updated over 9 years ago.
0%
Description
PPPoE-type WAN interfaces show their status as "up" when they aren't actually. To replicate, just set an interface to PPPoE on a network without a PPPoE server. It's trying to connect, but down, and Status>Interfaces shows "up".
Updated by Chris Buechler almost 11 years ago
this also applies to PPP, likely the same root cause
Updated by Chris Buechler almost 11 years ago
To clarify - eventually it goes to "down" status, after failing for quite a while. The issue is it shows "up" while going through connection failures and not being connected, like the following failure showed as "up" during all 50+ reconnection attempts.
Oct 27 23:13:22 ppp: [opt1_link0] Link: reconnection attempt 37 in 3 seconds Oct 27 23:13:25 ppp: [opt1_link0] Link: reconnection attempt 37 Oct 27 23:13:25 ppp: [opt1_link0] PPPoE: Connecting to '' Oct 27 23:13:25 ppp: PPPoE: rec'd ACNAME "cmbvmw-inet-rtr.cmb.localdomain" Oct 27 23:13:25 ppp: [opt1_link0] PPPoE: connection successful Oct 27 23:13:25 ppp: [opt1_link0] Link: UP event Oct 27 23:13:25 ppp: [opt1_link0] LCP: Up event Oct 27 23:13:25 ppp: [opt1_link0] LCP: state change Starting --> Req-Sent Oct 27 23:13:25 ppp: [opt1_link0] LCP: SendConfigReq #113 Oct 27 23:13:25 ppp: [opt1_link0] PROTOCOMP Oct 27 23:13:25 ppp: [opt1_link0] MRU 1492 Oct 27 23:13:25 ppp: [opt1_link0] MAGICNUM 10e213a0 Oct 27 23:13:25 ppp: [opt1_link0] LCP: rec'd Configure Request #140 (Req-Sent) Oct 27 23:13:25 ppp: [opt1_link0] PROTOCOMP Oct 27 23:13:25 ppp: [opt1_link0] MRU 1492 Oct 27 23:13:25 ppp: [opt1_link0] MAGICNUM 54cbb170 Oct 27 23:13:25 ppp: [opt1_link0] AUTHPROTO PAP Oct 27 23:13:25 ppp: [opt1_link0] LCP: SendConfigAck #140 Oct 27 23:13:25 ppp: [opt1_link0] PROTOCOMP Oct 27 23:13:25 ppp: [opt1_link0] MRU 1492 Oct 27 23:13:25 ppp: [opt1_link0] MAGICNUM 54cbb170 Oct 27 23:13:25 ppp: [opt1_link0] AUTHPROTO PAP Oct 27 23:13:25 ppp: [opt1_link0] LCP: state change Req-Sent --> Ack-Sent Oct 27 23:13:25 ppp: [opt1_link0] LCP: rec'd Configure Ack #113 (Ack-Sent) Oct 27 23:13:25 ppp: [opt1_link0] PROTOCOMP Oct 27 23:13:25 ppp: [opt1_link0] MRU 1492 Oct 27 23:13:25 ppp: [opt1_link0] MAGICNUM 10e213a0 Oct 27 23:13:25 ppp: [opt1_link0] LCP: state change Ack-Sent --> Opened Oct 27 23:13:25 ppp: [opt1_link0] LCP: auth: peer wants PAP, I want nothing Oct 27 23:13:25 ppp: [opt1_link0] PAP: using authname "pppoe1asdfadsf" Oct 27 23:13:25 ppp: [opt1_link0] PAP: sending REQUEST #1 len: 28 Oct 27 23:13:25 ppp: [opt1_link0] LCP: LayerUp Oct 27 23:13:25 ppp: [opt1_link0] PAP: rec'd NAK #1 len: 20 Oct 27 23:13:25 ppp: [opt1_link0] MESG: Login incorrect Oct 27 23:13:25 ppp: [opt1_link0] LCP: authorization failed Oct 27 23:13:25 ppp: [opt1_link0] LCP: parameter negotiation failed Oct 27 23:13:25 ppp: [opt1_link0] LCP: state change Opened --> Stopping Oct 27 23:13:25 ppp: [opt1_link0] LCP: SendTerminateReq #114 Oct 27 23:13:25 ppp: [opt1_link0] LCP: LayerDown Oct 27 23:13:25 ppp: [opt1_link0] LCP: rec'd Terminate Request #141 (Stopping) Oct 27 23:13:25 ppp: [opt1_link0] LCP: SendTerminateAck #115 Oct 27 23:13:25 ppp: [opt1_link0] LCP: rec'd Terminate Ack #142 (Stopping) Oct 27 23:13:25 ppp: [opt1_link0] LCP: state change Stopping --> Stopped Oct 27 23:13:25 ppp: [opt1_link0] LCP: LayerFinish Oct 27 23:13:25 ppp: [opt1_link0] PPPoE: connection closed Oct 27 23:13:25 ppp: [opt1_link0] Link: DOWN event Oct 27 23:13:25 ppp: [opt1_link0] LCP: Down event Oct 27 23:13:25 ppp: [opt1_link0] LCP: state change Stopped --> Starting Oct 27 23:13:25 ppp: [opt1_link0] LCP: LayerStart Oct 27 23:13:25 ppp: [opt1_link0] Link: reconnection attempt 38 in 1 seconds
Updated by Renato Botelho almost 11 years ago
- Status changed from Confirmed to Feedback
After doing somo analysis, my understanding is 'Status' is supposed to be up, since interface exists on operating system and is UP.
The field below is PPPOE and it is now using the same value as Status, what is wrong, but just changing it to down will make the Connect button to show up, what is not a good idea when mpd is already running.
IMO we should show it as 'Connecting...' when mpd is running but pppoe is down, and 'Down' when it's stopped. Thoughts?
Updated by Chris Buechler almost 11 years ago
- Subject changed from PPPoE client interface status wrong in 2.2 to PPPoE client interface status wrong while attempting to connect
Yeah it really should say "Connecting", how difficult would it be to make that happen? I don't think this is a regression on further evaluation, but if it's easily fixed let's take care of it. Otherwise, let's push it off for later review.
Updated by Chris Buechler almost 11 years ago
- Priority changed from High to Normal
- Assignee changed from Renato Botelho to Chris Buechler
- Target version deleted (
2.2) - Affected Version deleted (
2.2)
not the issue it initially appeared to be, assigned to me for review in the future. behavior is no diff than previous releases.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Closed