no way to skip an interface when access concentrator found on it

[jcfp]

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.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 beta or later?

[jcfp (jcfp)]

Yup. In intrepid it doesn't even show tell on which interface the ac is found on but just proceeds to use it as soon as one is found; the user can only bail out by saying the config file shouldn't be modified which causes pppoeconf to exit.

[xteejx (xteejx)]

Marking Confirmed, still a problem in Intrepid, setting Medium Importance - moderate impact on core application.
Would it be at all possible for you to try and reproduce this in Jaunty, I am unable to as I only have 1 network interface. Thank you.

[jcfp (jcfp)]

Still exists on jaunty.

[xteejx (xteejx)]

Thanks for the update. In Jaunty can you run "apport-collect 132188" and allow it full access to pull info into the bug report? Thank you.

[jcfp (jcfp)]

Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia ath_hal
Package: pppoeconf 1.18ubuntu1
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy kqemu lpadmin netdev plugdev powerdev sambashare scanner syslog vboxusers video

[xteejx (xteejx)]

Thank you for providing the info, marking Confirmed.

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for pppoeconf (Ubuntu) because there has been no activity for 60 days.]