no way to skip an interface when access concentrator found on it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pppoeconf (Debian) |
Incomplete
|
Undecided
|
Unassigned | ||
pppoeconf (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Binary package hint: pppoeconf
With multiple network interfaces, when pppoeconf finds an access concentrator on an interface, it will not allow a user to continue searching for others on other interfaces. As a result, a user may be unable to configure pppoe internet access via pppoeconf.
Real life example: 4 network interfaces on a pc, one wireless (ath0), three wired (eth[0-2]). Wireless interfaces was auto-configured by network-manager on boot and connected to some random unprotected wireless access point. Pppoeconf starts it's search for access concentrators on ath0 and finds one there. User has the choice between configuring for that pppoe access concentrator (to which user has no access, i.e. no valid username/password or that cannot be trusted) or quitting pppoeconf. The proper pppoe access meanwhile is via one of the wired interfaces that are not yet probed simply because their names come later in the alphabet than the wireless interface.
When multiple network interfaces are available, pppoeconf needs the option to skip an interface and keep looking for an access concentrator on the remaining interfaces, instead of forcing a user to the first one found. Currently, the only way around this is to disable the other interfaces, and then run pppoeconf so that the proper access concentrator is found - far from 'user-friendly'.
Kubuntu feisty with pppoeconf 1.12ubuntu1. Bug also exists in gutsy tribe 4.
Is this symptom still reproducible in 8.10 beta or later?