Troubleshooting
Logging
The BNG Blaster can log events to the standard output
or the logging window of the interactive courses interface.
Those events could be also logged into files using the argument
-L <file>
.
Per default, only events classified as info or error are logged. The following list shows all supported logging options.
debug
: debug eventsinfo
: informational eventserror
: error eventsigmp
: igmp events with join and leave timeio
: interface input/output eventspppoe
: pppoe eventspcap
: PCAP related eventsip
: log learned IP addressesloss
: log traffic loss with sequence numberl2tp
: log L2TP (LNS) eventsdhcp
: log DHCP eventsisis
: log ISIS eventsbgp
: log BGP eventstcp
: log TCP eventslag
: log link aggregation (LAG) eventsdpdk
: log DPDK eventspacket
: log packet eventshttp
: log HTTP events
$ sudo bngblaster -C test.json -L test.log -l ip -l isis -l bgp
PCAP
You can start the BNG Blaster with the argument -P <file>
to capture all traffic sent and received by the BNG Blaster
into a single PCAP file. This file includes all traffic from all
interfaces in use with proper meta header to filter by interface
names.
This helps to verify if traffic is received or how it has been received. Some network interfaces drop the most outer VLAN which can be easily verified using the capture file.
The configuration option capture-include-streams
allows to
include or exclude (default behavior) traffic streams from capture.
{
"interfaces": {
"capture-include-streams": true
}
}
Traffic streams send or received on threaded interfaces will be also not captured. All other traffic is still captured on threaded interfaces.
Wireshark Plugin
Traffic streams generated with the BNG Blaster include the BNG Blaster Header which can be analyzed with the Wireshark BNG Blaster Header Dissector.
Download the LUA dissector script bbl_header.lua and start Wireshark as shown below from the directory where the script is placed.
$ wireshark -X lua_script:bbl_header.lua