pppoe(4): unexpected IPV6CP requests

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

pppoe(4): unexpected IPV6CP requests

Christophe Etcheverry-2
Hello,

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.
Indeed, a tcpdum gives me a lot of these logs :

21:30:14.142040 PPPoE-Session
        code Session, version 1, type 1, id 0x04e6, length 6
        IPV6CP: Configure-Request, Unknown IPV6CP code 0x0
21:30:16.133589 PPPoE-Session
        code Session, version 1, type 1, id 0x04e6, length 16
        IPV6CP: Configure-Request, Interface-ID=0000:0000:0000:0001
21:30:16.133663 PPPoE-Session
        code Session, version 1, type 1, id 0x04e6, length 16
        IPV6CP: Configure-Ack, Interface-ID=0000:0000:0000:0001

The connection works just fine though and I wouldn't have noticed the
problem if my ISP hadn't contacted me to warn me that its logs were full
of IPV6 errors.

I just tried with the last snapshot but the problem remains the same.

Is there a way to make those requests stopB ?

Here is my /etc/hostname.pppoe0:

inet 0.0.0.0 255.255.255.255 NONE \
pppoedev vr0 authproto pap \
authname 'xxxxxxxxxx' authkey 'xxxxxxxxxx' up
dest 0.0.0.1
!/sbin/route add default -ifp pppoe0 0.0.0.1

Here is my dmesg:

OpenBSD 4.9 (GENERIC) #671: Wed Mar  2 07:09:00 MST 2011
    [hidden email]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 434 MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
real mem  = 268005376 (255MB)
avail mem = 253489152 (241MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 20/70/03, BIOS32 rev. 0 @ 0xfac40
pcibios0 at bios0: rev 2.0 @ 0xf0000/0x10000
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0xa800
cpu0 at mainbus0: (uniprocessor)
amdmsr0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
io address conflict 0x6100/0x100
io address conflict 0x6200/0x200
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 6 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address 00:00:24:cc:1a:34
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
vr1 at pci0 dev 7 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 5, address 00:00:24:cc:1a:35
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
vr2 at pci0 dev 8 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 9, address 00:00:24:cc:1a:36
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
vr3 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12, address 00:00:24:cc:1a:37
ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
glxpcib0 at pci0 dev 20 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio
gpio0 at glxpcib0: 32 pins
pciide0 at pci0 dev 20 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <SanDisk SDCFH-4096>
wd0: 4-sector PIO, LBA, 3919MB, 8027712 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 21 function 0 "AMD CS5536 USB" rev 0x02: irq 15, version 1.0, legacy support
ehci0 at pci0 dev 21 function 1 "AMD CS5536 USB" rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS
gpio1 at nsclpcsio0: 29 pins
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
biomask e5c5 netmask ffe5 ttymask ffff
mtrr: K6-family MTRR support (2 registers)
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
root on wd0a swap on wd0b dump on wd0b

--
Christophe

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Stuart Henderson
On 2011-03-14, Christophe Etcheverry <[hidden email]> 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.

you can add -inet6 to the top of hostname.pppoe0 (or type "ifconfig pppoe0
-inet6") and sppp(4) no longer attempts IPV6CP.

while reading if_spppsubr.c on a related but different reason I came across
this gem which I just thought I'd share with misc@:

static u_short interactive_ports[8] = {
        0,      513,    0,      0,
        0,      21,     0,      23,
};

wow. ugh.

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Christophe Etcheverry-2
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 ?

--
Christophe

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Olivier Mehani
On Tue, Mar 15, 2011 at 08:02:38AM +0100, Christophe Etcheverry wrote:
> Any ideaB ?

Ask you ISP to start offering IPv6 connectivity (;

However, maybe they did, and this is the reason you witnessed a change
of behaviour.

--
Olivier Mehani <[hidden email]>
PGP fingerprint: 4435 CF6A 7C8D DD9B E2DE  F5F9 F012 A6E2 98C6 6655

[demime 1.01d removed an attachment of type application/pgp-signature]

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Christophe Etcheverry-2
 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

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Kevin Chadwick-2
On Tue, 15 Mar 2011 10:26:04 +0100
Christophe Etcheverry wrote:

>  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
>

I remember having trouble getting rid of ipvshit messages, but I'm not
convinced whether it was user ppp, kernel ppp or both, I do remember
reading that the messages didn't mean it was actually trying to
negotiate ipvshit. Anyway my logs are clean so removing ipvshit from
your kernel should fix it but obviously not help finding any potential
bug.

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Stuart Henderson
In reply to this post by Christophe Etcheverry-2
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 <[hidden email]> 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 ?

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Christophe Etcheverry-2
On 00:44 Wed 16 Mar     , Stuart Henderson wrote:
> 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.

Thanks for your answer but even when I restart the session (down+up or
a network restart with -inet6 in my hostname.pppoe0) I keep sending
IPv6CP requests.

I finally asked my ISP to enable IPv6 connectivity on my line but even
in this case I went on spamming its logs with the same messages as
before (the "IPV6CP: Configure-Request, Unknown IPV6CP code 0x0" message
seems weird by the way) still traduced by lot of "No interface
identifier in IPV6CP request" in its logs.
Besides, I wasn't able to configure a working IPv6 connection.

As a temporary solution, I fell back to the userland pppoe(8). I really
would rather use the kernel one, but with pppoe(8) my ISP is not spammed
anymore by IPv6CP requests and I have working IPv4 and IPv6 connections.

--
Christophe

Reply | Threaded
Open this post in threaded view
|

Re: pppoe(4): unexpected IPV6CP requests

Claudio Jeker
In reply to this post by Christophe Etcheverry-2
On Tue, Mar 15, 2011 at 08:02:38AM +0100, Christophe Etcheverry 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 ?
>

-inet6 does not turn off IPV6CP in sppp(4). This could be considered a
bug. Anyone willing to fix this?

--
:wq Claudio