This looks like you did -inet6 after the session started; if so, that's too late, it wont't cancel an active IPV6CP. down+up should let it take effecct.
On 2011-03-15, Christophe Etcheverry <cetcheve+o...@omitufo.org> wrote: > On 22:14 Mon 14 Mar , Stuart Henderson wrote: >>> I use OpenBSD i386 -current on a Soekris net5501 as a gateway using >>> pppoe(4) to create only an ipv4 connection. I never had any problem but >>> since an upgrade last week, pppoe(4) try to create an ipv6 connection too. >> >> I don't see why this would be anything new - pppoe(4), or more specifically >> sppp(4), has supported v6 since 2007. > > Yes, my isp's warning surprised me too but the appearance of the ipv6cp > spamming the exact same day of my upgrade is kind of weird. > >> you can add -inet6 to the top of hostname.pppoe0 (or type "ifconfig pppoe0 >> -inet6") and sppp(4) no longer attempts IPV6CP. > > Thank you for this advice but even when I do that my gateway throw a lot > of ICPV6CP requests. > > # ifconfig pppoe0 -inet6 > # ifconfig pppoe0 > pppoe0: flags=28851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST,NOINET6> > mtu 1492 > priority: 0 > dev: vr0 state: session > sid: 0x82c PADI retries: 0 PADR retries: 0 time: 00:11:22 > sppp: phase network authproto pap authname "xxxxxxxxxx" > groups: pppoe egress > status: active > inet xx.xx.xx.xx --> xx.xx.xx.xx netmask 0xffffffff > > Here, we can see inet6 has been disabled on pppoe0. But I still get a > lot of IPV6CP requests on my logs : > > 07:59:10.825666 PPPoE-Session > code Session, version 1, type 1, id 0x082c, length 16 > IPV6CP: Configure-Request, Interface-ID=0000:0000:0000:0001 > 07:59:10.825736 PPPoE-Session > code Session, version 1, type 1, id 0x082c, length 16 > IPV6CP: Configure-Ack, Interface-ID=0000:0000:0000:0001 > > Any ideaB ?
