Welcome to BNG Blaster Discussions!

[GIC-de]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[Jonix71]

Is there any support for custom variables to use for DHCP Op82 creation?

"access-line": {
    "agent-remote-id": "DEU.RTBRICK.{session-global}",
    "agent-circuit-id": "0.0.0.0/0.0.0.0 eth 0:{session-global}"
}

From config example {session-global} is used. I would like be able to simulate access switches to test our DHCP implementation at the same time we are running BNG Blaster.

ex: GigabitEthernet0/0/{port-nr} switchname{switch-nr}

Under each port-nr+switch-nr N-clients should be activated of types (Internet,VoIP,IPTV)
Possibility to configure port-range used 1-24, 1-48 and swith-nr 1-1000.

[GIC-de]

Currently only the variables {session} and {session-global} are supported, but {session} starts from 1 for every access interface / VLAN range. So you could configure the ARI/ACI under the access interface and create one access interface per ethernet interface 1000 VLAN's per access interface.

https://rtbrick.github.io/bngblaster/interfaces.html

The configuration attributes for username, agent-remote-id and agent-circuit-id support also some variable substitution. The variable {session-global} will be replaced with a number starting from 1 and incremented for every new session. where as the variable {session} is incremented per interface section.

[GIC-de]

{
    "access": [
        {
            "interface": "eth1",
            "agent-remote-id": "DEU.RTBRICK.{session-global}",
            "agent-circuit-id": "GigabitEthernet0/0/1 switchname{session}"
            "outer-vlan-min": 100,
            "outer-vlan-max": 199,
            "inner-vlan-min": 7,
            "inner-vlan-max": 7
        },
        {
            "interface": "eth1",
            "agent-remote-id": "DEU.RTBRICK.{session-global}",
            "agent-circuit-id": "GigabitEthernet0/0/2 switchname {session}"
            "outer-vlan-min": 200,
            "outer-vlan-max": 299,
            "inner-vlan-min": 7,
            "inner-vlan-max": 7
        }
    ]
}

[Jonix71]

Ok,
It works but will generate a large config file. Another question for DHCP part have you thought about adding possibility to send Option-60? Our BNG implementation uses Option-60 to classify clients and this also vill give client diffrent IP allocated from the DHCP server. So that would be a feature request.

[GIC-de]

The DHCPv4 option 60 is currently not supported but could be added. I would assume you need an option 60 which is different for each user with some iterators? Could you please open an issue/feature request. There you could also specify an example configuration that would fit your needs, this helps to better understand your request.

[onfirealot]

Is there any plans to add LAC into the testing at all? We're currently using Spirent testing, but have started to use BNG Blaster for PPPoE testing and finding it really useful.

[GIC-de]

I'm not sure if I understand the question correctly, but the BNG Blaster is already able to emulate L2TP LNS servers. The assumption is that the LAC is the device under test (DUT). We test our BNG LAC functionality in RtBrick FullStack software (RBFS) using BNG Blaster as well.

Here the BNG Blaster supports also RFC5515 CSUN and CSURQ.

[onfirealot]

Ah ok. We are currently testing the LTS functionality our BNG, so we are using a Spirent tester to act as a LAC. That way we can tunnel switch the incoming subscribers on the BNG onto another device.

[marthin-vandyk]

Hi guys,

Am looking to emulate a lot of pppoe sessions, but they must be in the same VLAN. Is there a way to do so without having the VLAN range?

thanks

[GIC-de]

You need to set VLAN mode to N:1, in this case the Blaster will not iterate VLAN's and creates multiple sessions per VLAN.

        {
            "interface": "eth1",
            "vlan-mode": "N:1"
            "inner-vlan": 128,
            "outer-vlan": 7,
        }

This works single tagged, double tagged, tripple tagged and even untagged.

[marthin-vandyk]

Many thanks Christian! I did find the setting in the docs, but was not sure how it applied to the topology and thus did not try it/overlooked it.

did try many other things :)

looking good thanks again

[GIC-de]

I created a documentation issue to improve documentation here:
#127

[girishpatoliya]

Does LNS mode support ppp over L2TP ?
I have tried to run an instance of bng blaster, but I don't see it listening on port 1701..

[girishpatoliya]

Challenge issue is resolved after changing secret to alpha-numeric.
However PPP/LCP config request is still not responded (ppp over l2tp)

[GIC-de]

I'm confused, your client should be in PPP authentication phase, waiting for PAP or CHAP authentication ACK. So would expect authentication request retries here rather than LCP configuration requests.

[girishpatoliya]

I have already tested ppp/lcp/chap/ipcp with openl2tp with same LAC, I wanted to test ipv6cp with BNG.
Sequece is : L2tp tunnel -> PPP LCP -> PAP|CHAP ->IPCP -> data packets. (attached pcap snap from test with openl2tp)

[girishpatoliya]

I added debug statement (last else) in bbl_l2tp.c: bbl_l2tp_data_rx()

 907     switch(l2tp->protocol) {
 908         case PROTOCOL_LCP:
 909             lcp_rx = (bbl_lcp_s*)l2tp->next;
 910             lcp_rx->padding = l2tp_session->tunnel->server->lcp_padding;
 911             if(lcp_rx->code == PPP_CODE_ECHO_REQUEST) {
 912                 lcp_rx->code = PPP_CODE_ECHO_REPLY;
 913                 bbl_l2tp_send_data(l2tp_session, PROTOCOL_LCP, lcp_rx);
 914             } else if(lcp_rx->code == PPP_CODE_TERM_REQUEST) {
 915                 l2tp_session->disconnect_code = 3;
 916                 l2tp_session->disconnect_protocol = 0;
 917                 l2tp_session->disconnect_direction = 1;
 918                 bbl_l2tp_send(l2tp_session->tunnel, l2tp_session, L2TP_MESSAGE_CDN);
 919                 bbl_l2tp_session_delete(l2tp_session);
 920             } else {
 921                     bbl_l2tp_tunnel_s *l2tp_tunnel = l2tp_session->tunnel;
 922                     LOG(L2TP, "**L2TP Info (%s) Tunnel (%u) from %s (%s) session (%u) not handling LCP CONF REQ**\n",
 923                                     l2tp_tunnel->server->host_name, l2tp_tunnel->tunnel_id,
 924                                     l2tp_tunnel->peer_name,
 925                                     format_ipv4_address(&l2tp_tunnel->peer_ip),
 926                                     l2tp_session->key.session_id);
 927             }
 
 Observed in logs when LCP received from LAC.
 ===============================
 
 Apr 28 07:17:40.048377 L2TP Debug (LNS1) Tunnel 1 state changed from Wait-Control-Connection to Established
Apr 28 07:17:40.049093 L2TP Info (LNS1) Tunnel 1 with testlac1 (192.168.13.100) established
Apr 28 07:17:40.061813 L2TP Info (LNS1) Tunnel (1) from testlac1 (192.168.13.100) session (1) established
Apr 28 07:17:40.629333 L2TP Info (LNS1) Tunnel (1) from testlac1 (192.168.13.100) session (1) **not handling LCP CONF REQ**
Apr 28 07:17:43.423148 L2TP Debug (LNS1) Tunnel 1 Session 1 deleted
Apr 28 07:17:43.424064 L2TP Debug (LNS1) Tunnel 1 state changed from Established to Received-StopCCN
Apr 28 07:17:49.033989 L2TP Debug (LNS1) Tunnel 1 state changed from Received-StopCCN to Terminated
 

Below is the topology I am using :

(LAC- 192.168.13.100) ------------------> (192.168.13.10 - BNG Blaster)

Config :

{
    "interfaces": {
        "network": [
            {
                "interface": "eth4",
                "address": "192.168.13.11/24",
                "gateway": "192.168.13.100"
            }
        ],
        "access": [
            {
                "interface": "dummy0",
                "outer-vlan-min": 1,
                "outer-vlan-max": 4000,
                "inner-vlan-min": 8,
                "inner-vlan-max": 8,
                "authentication-protocol": "CHAP"
            }
        ]
    },
    "ppp": {
        "mru": 1470,
        "authentication": {
            "username": "testlac1",
            "password": "testcal1",
            "timeout": 5,
            "retry": 60
        },
        "lcp": {
            "conf-request-timeout": 5,
            "conf-request-retry": 30,
            "keepalive-interval": 30,
            "keepalive-retry": 3
        },
        "ipcp": {
            "enable": true
        },
        "ip6cp": {
            "enable": true
        }
    },
    "l2tp-server": [
        {
            "name": "LNS1",
            "address": "192.168.13.10",
            "secret": "passwordc",
            "receive-window-size": 8
        }
    ],
    "session-traffic": {
        "autostart": true,
        "ipv4-pps": 1
    }
}

[GIC-de]

This is not needed for tests with BNG Blaster as client and server but we can extend. Currently I'm busy with other Blaster requests, so if you like, you can try yourself and open PR. Otherwise I will work on it as soon as possible.