On Tue, 15 Mar 2011 18:25:51 +1100, Olivier Mehani wrote:
Any idea ?
Ask you ISP to start offering IPv6 connectivity (;
However, maybe they did, and this is the reason you witnessed a
change
of behaviour.
They actually offer IPv6 connectivity since a few years now (so the
IPv6CP B+ spamming B; should have been noticed before). :)
But because of lack of time and laziness, I never asked them to setup
the IPv6 connectivity for my line.
According to the situation, I guess I will soon. It would solve the
problem but I'd rather be sure that there's no unexpected behavior in
the current pppoe(4) code before asking them to give me IPv6
connectivity.
(The fact that ifconfig -inet6 pppoe0 doesn't disable IPv6CP requests
seems weird for example).
--
Christophe
