Bug#265183: pppoe workaround of the post-reboot problem

[Eduard Bloch <edi@gmx.de>]

severity 263224 serious
reassign 262941 modutils
severity 262941 serious
merge 262941 263224
thanks

#include <hallo.h>
* Vassilii Khachaturov [Fri, Aug 13 2004, 08:50:58AM]:
> The thing that happens as a by-product of pppoeconf that enables the
> pppoe to work later on is the loading of the pppoe module. So to have
> pppoe working after reboot, `modprobe pppoe' is needed before `pon
> dsl-provider'. I think pppoeconf should have done something differently
> transparent to the user. FWIW, here's the /etc/ppp/peers/dsl-provider it
> had generated. See this also in connection with the routing quirk
> described in the original report (that had to be worked around with the
> assigning of a static address).
> 
> Eduard: please feel free to fork #265183 to pppoeconf bugs (on the

As said to the previous bug reporters, it is simply not my job to load
_kernel_ modules for some other package. It would just additional
complexity while there are other places where it must be fixed. I agree
that this bug looks very shameful for a fresh Debian release so it
should be release critical. Especially when there is such a simple fix.

PS: I won't clone 265183, there are already enough bug reports to the
pppoe module problem.

Regards,
Eduard.
-- 
OpenBSD fails miserably in this respect, and makes for an example of how NOT
to work with the community on security issues.  Their approach is, roughly,
"we fixed this a while ago but didn't tell anyone, so you're vulnerable and
we're not, ha-ha-ha".