2022-03-30 23:47:00 +02:00
|
|
|
Troubleshooting
|
|
|
|
|
===============
|
|
|
|
|
|
|
|
|
|
Logging
|
|
|
|
|
-------
|
|
|
|
|
|
2022-10-27 16:31:25 +00:00
|
|
|
The BNG Blaster can log events to the standard output
|
|
|
|
|
or the logging window of the interactive courses interface.
|
2022-11-02 14:01:16 +00:00
|
|
|
Those events could be also logged into files using the argument
|
2022-03-30 23:47:00 +02:00
|
|
|
``-L <file>``.
|
|
|
|
|
|
2022-10-27 16:31:25 +00:00
|
|
|
Per default, only events classified as `info` or `error` are logged.
|
2022-03-30 23:47:00 +02:00
|
|
|
The following list shows all supported logging options.
|
|
|
|
|
|
|
|
|
|
* ``debug``: debug events
|
2022-11-02 14:01:16 +00:00
|
|
|
* ``info``: informational events
|
2022-03-30 23:47:00 +02:00
|
|
|
* ``error``: error events
|
|
|
|
|
* ``igmp``: igmp events with join and leave time
|
|
|
|
|
* ``io``: interface input/output events
|
|
|
|
|
* ``pppoe``: pppoe events
|
|
|
|
|
* ``pcap``: PCAP related events
|
|
|
|
|
* ``ip``: log learned IP addresses
|
|
|
|
|
* ``loss``: log traffic loss with sequence number
|
|
|
|
|
* ``l2tp``: log L2TP (LNS) events
|
|
|
|
|
* ``dhcp``: log DHCP events
|
|
|
|
|
* ``isis``: log ISIS events
|
|
|
|
|
* ``bgp``: log BGP events
|
|
|
|
|
* ``tcp``: log TCP events
|
2022-11-02 14:01:16 +00:00
|
|
|
* ``lag``: log link aggregation (LAG) events
|
|
|
|
|
* ``dpdk``: log DPDK events
|
2022-03-30 23:47:00 +02:00
|
|
|
|
|
|
|
|
.. code-block:: none
|
|
|
|
|
|
|
|
|
|
$ 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>``
|
2022-10-27 16:31:25 +00:00
|
|
|
to capture all traffic sent and received by the BNG Blaster
|
2022-03-30 23:47:00 +02:00
|
|
|
into a single PCAP file. This file includes all traffic from all
|
|
|
|
|
interfaces in use with proper meta header to filter by interface
|
|
|
|
|
names.
|
|
|
|
|
|
2022-10-27 16:31:25 +00:00
|
|
|
This helps to verify if traffic is received or how it has been received.
|
2022-03-30 23:47:00 +02:00
|
|
|
Some network interfaces drop the most outer VLAN which can be easily
|
2022-04-06 23:02:38 +02:00
|
|
|
verified using the capture file.
|
|
|
|
|
|
|
|
|
|
The configuration option ``capture-include-streams`` allows to
|
2022-11-08 21:42:47 +00:00
|
|
|
include or exclude (default behavior) traffic streams from capture.
|
2022-04-06 23:02:38 +02:00
|
|
|
|
|
|
|
|
.. code-block:: json
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
"interfaces": {
|
2022-11-08 21:42:47 +00:00
|
|
|
"capture-include-streams": true
|
2022-04-06 23:02:38 +02:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2022-11-02 14:01:16 +00:00
|
|
|
|
|
|
|
|
Traffic streams send or received on threaded interfaces will be also not captured.
|
|
|
|
|
All other traffic is still captured on threaded interfaces.
|
|
|
|
|
|
2022-04-06 23:02:38 +02:00
|
|
|
Wireshark Plugin
|
|
|
|
|
~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
|
|
Traffic streams generated with the BNG Blaster include the
|
2022-10-27 16:31:25 +00:00
|
|
|
:ref:`BNG Blaster Header <bbl_header>` which can be analyzed
|
2022-04-06 23:02:38 +02:00
|
|
|
with the Wireshark BNG Blaster Header Dissector.
|
|
|
|
|
|
|
|
|
|
Download the LUA dissector script
|
|
|
|
|
`bbl_header.lua <https://github.com/rtbrick/bngblaster/tree/main/wireshark>`_
|
2022-10-27 16:31:25 +00:00
|
|
|
and start Wireshark as shown below from the directory where the script is placed.
|
2022-04-06 23:02:38 +02:00
|
|
|
|
|
|
|
|
.. code-block:: none
|
|
|
|
|
|
|
|
|
|
$ wireshark -X lua_script:bbl_header.lua
|
|
|
|
|
|
