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

[Eduard Bloch <edi@gmx.de>]

#include <hallo.h>
* Vassilii Khachaturov [Mon, Sep 20 2004, 11:51:31AM]:

> > PS: I won't clone 265183, there are already enough bug reports to the
> > pppoe module problem.
> 
> But what about the routing loop problem I had mentioned in the original
> 265183 report? It is something pretty confusing for a new user.

Which loop? I do not know why your modem has an own IP, maybe it is a
router and not a modem? Why does it give your local systems DHCP
adresses? How are they related to whatever is connected there? Or maybe
it is not a usual PPPoE modem but this other weird
ip-route-over-fake-internal-network-with-dhcp-over-DSL system (*).

Or what t.f. is a "LAN duplex link"? Does not say anything to me. Maybe
a phantasy name from your ISP? If yes, what is in the real world terms?

Regards,
Eduard.

PS: (*) I am still looking for somebody to explain me how this
"technology" works and can provide a reliable step-for-step howto to add
support for it to pppoeconf. Or even patches. From time to time people
asked me to add support for their "DHCP DSL" but for real support more
is needed.
-- 
So, your "solution" is to ask "Should I break your system now or after
the next reboot?". Debconf is not an alternative to fixing the
problem. Such questions are still unacceptable bugs.
              -- asuffield in debian-devel about crazy linux-2.4 repackaging