BNG Blaster not responding to PADO about bngblaster HOT 6 CLOSED

The outer VLAN is often not captured as explained in the FAQ:
https://rtbrick.github.io/bngblaster/faq.html

Some interface drivers drop the outer VLAN header. The BNG Blaster tries to recover the VLAN from kernel headers but will not change the packets stored in the PCAP file.

You can start BNG Blaster with -l pppoe -l debug -L test.log to get more details but I guess I know the issue.

By default, the BNG Blaster send's an empty service-name TAG. This means to accept any service from the BNG. But the BNG Blaster always expects to include a service name in the PADO from the BNG.

The RFC is not concrete about how to handle empty service-name tags. In our own BNG implementation, we respond with service-name access if PADI does not include a service-name otherwise, we respond with the service-name from PADI. This showed us the best compatibility with the different client implementations and CPE devices.

You can send a service-name from BNG Blaster with the following configuration to get your setup up and running.

{
    "pppoe": {
        "service-name": "access"
    }
}

Actually, it's the second time seeing this bug, so will think about changing the default behavior of BNG Blaster to send a service name per default or accept an empty service name in the PADO.

from bngblaster.

Hi,

Setting the service name worked.

Normally we use a Spirent for testing our BNGs. The Spirent also sends empty service-name TAG by default, and our BNG (Juniper MX10K3) responds with the PADO without a service name. (We have the BNG set to permit any service). The Spirent accepts an empty service name in the PADO.

from bngblaster.

I will address this in the next release.

from bngblaster.

This issue is fixed in version 0.7.2. Now, PADO with an empty service-name will be accepted if PADI is also send with empty service name.

Please verify and close the issue if the solution is accepted!

from bngblaster.

Thank you, will get that tested today.

from bngblaster.

All working. Thank you .

from bngblaster.