From ea2a3266924fb04ea0aa90b151b4d4084b036c07 Mon Sep 17 00:00:00 2001 From: Christian Giese Date: Wed, 2 Nov 2022 14:27:01 +0000 Subject: [PATCH] update github pages --- docs/_sources/access/traffic.rst.txt | 53 +++++++++--------- .../configuration/interfaces_lag.rst.txt | 3 + docs/_sources/interfaces.rst.txt | 16 +++--- docs/_sources/streams.rst.txt | 16 +++--- docs/_sources/troubleshooting.rst.txt | 10 +++- docs/access/traffic.html | 53 +++++++++--------- docs/configuration/index.html | 8 ++- docs/configuration/interfaces_lag.html | 8 ++- docs/interfaces.html | 24 ++++---- docs/objects.inv | Bin 1206 -> 1209 bytes docs/searchindex.js | 2 +- docs/streams.html | 16 +++--- docs/troubleshooting.html | 8 ++- 13 files changed, 122 insertions(+), 95 deletions(-) diff --git a/docs/_sources/access/traffic.rst.txt b/docs/_sources/access/traffic.rst.txt index b28e016b..67693c10 100644 --- a/docs/_sources/access/traffic.rst.txt +++ b/docs/_sources/access/traffic.rst.txt @@ -57,32 +57,33 @@ for session traffic. .. code-block:: none Session Traffic (Global): - -------------------------------------------------------------- - Config: - IPv4 PPS: 1 - IPv6 PPS: 1 - IPv6PD PPS: 1 - Verified Traffic Flows: 6/6 - Downstream IPv4: 1 - Downstream IPv6: 1 - Downstream IPv6PD: 1 - Upstream IPv4: 1 - Upstream IPv6: 1 - Upstream IPv6PD: 1 - Violations (>1s): 0 - Downstream IPv4: 0 - Downstream IPv6: 0 - Downstream IPv6PD: 0 - Upstream IPv4: 0 - Upstream IPv6: 0 - Upstream IPv6PD: 0 - First Sequence Number Received: - Downstream IPv4 MIN: 1 ( 1.00s) AVG: 1 ( 1.00s) MAX: 1 ( 1.00s) - Downstream IPv6 MIN: 1 ( 1.00s) AVG: 1 ( 1.00s) MAX: 1 ( 1.00s) - Downstream IPv6PD MIN: 1 ( 1.00s) AVG: 1 ( 1.00s) MAX: 1 ( 1.00s) - Upstream IPv4 MIN: 1 ( 1.00s) AVG: 1 ( 1.00s) MAX: 1 ( 1.00s) - Upstream IPv6 MIN: 1 ( 1.00s) AVG: 1 ( 1.00s) MAX: 1 ( 1.00s) - Upstream IPv6PD MIN: 1 ( 1.00s) AVG: 1 ( 1.00s) MAX: 1 ( 1.00s) + ------------------------------------------------------------------------------ + Config: + PPS IPv4: 1 + PPS IPv6: 1 + PPS IPv6PD: 1 + Verified Traffic Flows: 96000/96000 (100.00%) + Downstream IPv4: 16000 + Downstream IPv6: 16000 + Downstream IPv6PD: 16000 + Upstream IPv4: 16000 + Upstream IPv6: 16000 + Upstream IPv6PD: 16000 + Violations: >1s >1s-2s >2s-3s >3s + Downstream IPv4: 12278 ( 12.79%) 3071 3040 6167 + Downstream IPv6: 12252 ( 12.76%) 3185 2900 6167 + Downstream IPv6PD: 12306 ( 12.82%) 3123 2978 6205 + Upstream IPv4: 12314 ( 12.83%) 3104 3033 6177 + Upstream IPv6: 12252 ( 12.76%) 3184 2891 6177 + Upstream IPv6PD: 12361 ( 12.88%) 3178 2957 6226 + Total: 73763 ( 76.84%) 18845 17799 37119 + First Sequence Received: MIN AVG MAX + Downstream IPv4 1 ( 1.00s) 9 ( 9.00s) 64 (64.00s) + Downstream IPv6 1 ( 1.00s) 9 ( 9.00s) 64 (64.00s) + Downstream IPv6PD 1 ( 1.00s) 9 ( 9.00s) 64 (64.00s) + Upstream IPv4 1 ( 1.00s) 9 ( 9.00s) 64 (64.00s) + Upstream IPv6 1 ( 1.00s) 9 ( 9.00s) 64 (64.00s) + Upstream IPv6PD 1 ( 1.00s) 9 ( 9.00s) 64 (64.00s) The ``First Sequence Number Received`` is used to measure the forwarding diff --git a/docs/_sources/configuration/interfaces_lag.rst.txt b/docs/_sources/configuration/interfaces_lag.rst.txt index 13922cad..ecf9a72a 100644 --- a/docs/_sources/configuration/interfaces_lag.rst.txt +++ b/docs/_sources/configuration/interfaces_lag.rst.txt @@ -25,6 +25,9 @@ * - `lacp-system-id` - LACP system identifier - 02:ff:ff:ff:ff:00 + * - `lacp-min-active-links` + - Define the minimum number of active links + - 0 * - `lacp-max-active-links` - Limit the maximum number of active links - 255 diff --git a/docs/_sources/interfaces.rst.txt b/docs/_sources/interfaces.rst.txt index b53eeaf1..6cb303f7 100644 --- a/docs/_sources/interfaces.rst.txt +++ b/docs/_sources/interfaces.rst.txt @@ -130,8 +130,8 @@ Link Aggregation (LAG) ~~~~~~~~~~~~~~~~~~~~~~ The BNG Blaster supports link aggregation (LAG) with and without -LACP. The created LAG interface can be used as link for all kinds -of interface functions. +LACP. The created LAG interface can be used as the parent interface link +for all kinds of interface functions. .. include:: configuration/interfaces_lag.rst @@ -171,16 +171,16 @@ of interface functions. Multithreaded Interfaces ~~~~~~~~~~~~~~~~~~~~~~~~ -The BNG Blaster handles all traffic sent and received (IO) in the main thread per default. +The BNG Blaster handles all traffic sent and received (I/O) in the main thread per default. With this default behavior, you can achieve between 100.000 and 200.000 PPS bidirectional traffic in most environments. Depending on the actual setup, this can be even less or much more, which is primarily driven by the single-thread performance of the given CPU. -Those numbers can be increased by splitting the workload over multiple IO worker threads. -Every IO thread will handle only one interface and direction. It is also possible to start +Those numbers can be increased by splitting the workload over multiple I/O worker threads. +Every I/O thread will handle only one interface and direction. It is also possible to start multiple threads for the same interface and direction. -The number of IO threads can be configured globally for all interfaces or per interface link. +The number of I/O threads can be configured globally for all interfaces or per interface link. .. code-block:: json @@ -215,10 +215,10 @@ at least 4 TX threads to verify all prefixes of a BGP full table for example. The configured traffic streams are automatically balanced over all TX threads of the corresponding interfaces but a single stream can't be split over multiple threads to prevent re-ordering issues. -Enabling multithreaded IO causes some limitations. First of all, it works only on systems with +Enabling multithreaded I/O causes some limitations. First of all, it works only on systems with CPU cache coherence, which should apply to all modern CPU architectures. It is also not possible to bundle (Link Aggregation) multithreaded interfaces. It is also not possible to capture traffic -streams send or received on threaded interfaces. All other traffic is still captured even on threaded +streams send or received on threaded interfaces. All other traffic is still captured on threaded interfaces. .. note:: diff --git a/docs/_sources/streams.rst.txt b/docs/_sources/streams.rst.txt index a8a907bd..d8bbf0fa 100644 --- a/docs/_sources/streams.rst.txt +++ b/docs/_sources/streams.rst.txt @@ -217,7 +217,7 @@ working. After the first packet is received for a given flow, for every further if there is a gap between the last and new sequence number which is then reported as a loss. The ``rx/tx-accounting-packets`` are all packets that should be counted in the session volume -accounting of the BNG, meaning session rx/tx packets excluding control traffic. +accounting of the BNG, meaning session RX/TX packets excluding control traffic. Each flow can be queried separately using jsonpath expression with name and direction or flow-id. @@ -302,11 +302,11 @@ Alternatively, all the session and stream traffic (including RAW streams) can be started or stopped globally using the ``traffic-start`` and ``traffic-stop`` commands. +.. _bbl_header: + BNG Blaster Traffic ~~~~~~~~~~~~~~~~~~~ -.. _bbl_header: - *Blaster Header and Fast Decode Signature* The 48 Byte fixed size BNG Blaster Header is added to all data packets @@ -319,7 +319,7 @@ IPv4 multicast traffic. Unicast Session Traffic ^^^^^^^^^^^^^^^^^^^^^^^ -The 64 bit session key is used for all traffic from access (upstream) +The 64-bit session key is used for all traffic from access (upstream) and to access (downstream) interfaces to identify the corresponding session which has sent or should receive the packet. @@ -387,7 +387,7 @@ Multicast Traffic BNG Blaster Magic Sequence ^^^^^^^^^^^^^^^^^^^^^^^^^^ -The 64 bit magic sequence is the word ``RtBrick!`` decoded as ASCII: +The 64-bit magic sequence is the word ``RtBrick!`` decoded as ASCII: .. code-block:: none @@ -399,13 +399,13 @@ of blaster traffic. Flow Identifier ^^^^^^^^^^^^^^^ -The 64 bit flow identifier is a globally unique number that identifies +The 64-bit flow identifier is a globally unique number that identifies the flow. Flow Sequence Number ^^^^^^^^^^^^^^^^^^^^ -The 64 bit flow sequence number is a sequential number starting with 1 +The 64-bit flow sequence number is a sequential number starting with 1 and incremented per packet primary used to identify packet loss. This number 0 means that sequencing is disabled. @@ -413,7 +413,7 @@ This number 0 means that sequencing is disabled. Nanosecond Send Timestamps ^^^^^^^^^^^^^^^^^^^^^^^^^^ -The 64 bit nanoseconds send timestamp is used for optional latency and +The 64-bit nanoseconds send timestamp is used for optional latency and jitter calculations. .. code-block:: none diff --git a/docs/_sources/troubleshooting.rst.txt b/docs/_sources/troubleshooting.rst.txt index 69103a55..b47ada77 100644 --- a/docs/_sources/troubleshooting.rst.txt +++ b/docs/_sources/troubleshooting.rst.txt @@ -6,18 +6,18 @@ 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 to files using the argument +Those events could be also logged into files using the argument ``-L ``. Per default, only events classified as `info` or `error` are logged. The following list shows all supported logging options. * ``debug``: debug events +* ``info``: informational events * ``error``: error events * ``igmp``: igmp events with join and leave time * ``io``: interface input/output events * ``pppoe``: pppoe events -* ``info``: informational events (enabled per default) * ``pcap``: PCAP related events * ``ip``: log learned IP addresses * ``loss``: log traffic loss with sequence number @@ -26,6 +26,8 @@ The following list shows all supported logging options. * ``isis``: log ISIS events * ``bgp``: log BGP events * ``tcp``: log TCP events +* ``lag``: log link aggregation (LAG) events +* ``dpdk``: log DPDK events .. code-block:: none @@ -56,6 +58,10 @@ include (default behavior) or exclude traffic streams from capture. } } + +Traffic streams send or received on threaded interfaces will be also not captured. +All other traffic is still captured on threaded interfaces. + Wireshark Plugin ~~~~~~~~~~~~~~~~ diff --git a/docs/access/traffic.html b/docs/access/traffic.html index 41110ac7..7ef03cb9 100644 --- a/docs/access/traffic.html +++ b/docs/access/traffic.html @@ -182,32 +182,33 @@ option in the corresponding access configuration.

The final report includes detailed information for session traffic.

Session Traffic (Global):
---------------------------------------------------------------
-Config:
-    IPv4    PPS:           1
-    IPv6    PPS:           1
-    IPv6PD  PPS:           1
-Verified Traffic Flows: 6/6
-    Downstream IPv4:          1
-    Downstream IPv6:          1
-    Downstream IPv6PD:        1
-    Upstream IPv4:            1
-    Upstream IPv6:            1
-    Upstream IPv6PD:          1
-Violations (>1s): 0
-    Downstream IPv4:          0
-    Downstream IPv6:          0
-    Downstream IPv6PD:        0
-    Upstream IPv4:            0
-    Upstream IPv6:            0
-    Upstream IPv6PD:          0
-First Sequence Number Received:
-    Downstream IPv4    MIN:      1 ( 1.00s) AVG:      1 ( 1.00s) MAX:      1 ( 1.00s)
-    Downstream IPv6    MIN:      1 ( 1.00s) AVG:      1 ( 1.00s) MAX:      1 ( 1.00s)
-    Downstream IPv6PD  MIN:      1 ( 1.00s) AVG:      1 ( 1.00s) MAX:      1 ( 1.00s)
-    Upstream IPv4      MIN:      1 ( 1.00s) AVG:      1 ( 1.00s) MAX:      1 ( 1.00s)
-    Upstream IPv6      MIN:      1 ( 1.00s) AVG:      1 ( 1.00s) MAX:      1 ( 1.00s)
-    Upstream IPv6PD    MIN:      1 ( 1.00s) AVG:      1 ( 1.00s) MAX:      1 ( 1.00s)
+------------------------------------------------------------------------------
+  Config:
+    PPS IPv4:                    1
+    PPS IPv6:                    1
+    PPS IPv6PD:                  1
+  Verified Traffic Flows:    96000/96000 (100.00%)
+    Downstream IPv4:         16000
+    Downstream IPv6:         16000
+    Downstream IPv6PD:       16000
+    Upstream IPv4:           16000
+    Upstream IPv6:           16000
+    Upstream IPv6PD:         16000
+  Violations:               >1s             >1s-2s   >2s-3s      >3s
+    Downstream IPv4:      12278 ( 12.79%)     3071     3040     6167
+    Downstream IPv6:      12252 ( 12.76%)     3185     2900     6167
+    Downstream IPv6PD:    12306 ( 12.82%)     3123     2978     6205
+    Upstream IPv4:        12314 ( 12.83%)     3104     3033     6177
+    Upstream IPv6:        12252 ( 12.76%)     3184     2891     6177
+    Upstream IPv6PD:      12361 ( 12.88%)     3178     2957     6226
+    Total:                73763 ( 76.84%)    18845    17799    37119
+  First Sequence Received:  MIN                AVG               MAX
+    Downstream IPv4           1 ( 1.00s)         9 ( 9.00s)       64 (64.00s)
+    Downstream IPv6           1 ( 1.00s)         9 ( 9.00s)       64 (64.00s)
+    Downstream IPv6PD         1 ( 1.00s)         9 ( 9.00s)       64 (64.00s)
+    Upstream IPv4             1 ( 1.00s)         9 ( 9.00s)       64 (64.00s)
+    Upstream IPv6             1 ( 1.00s)         9 ( 9.00s)       64 (64.00s)
+    Upstream IPv6PD           1 ( 1.00s)         9 ( 9.00s)       64 (64.00s)

The First Sequence Number Received is used to measure the forwarding diff --git a/docs/configuration/index.html b/docs/configuration/index.html index 505430b2..3f9998a8 100644 --- a/docs/configuration/index.html +++ b/docs/configuration/index.html @@ -310,11 +310,15 @@ for interface links referenced by interface functions.

LACP system identifier

02:ff:ff:ff:ff:00

-

lacp-max-active-links

+

lacp-min-active-links

+

Define the minimum number of active links

+

0

+ +

lacp-max-active-links

Limit the maximum number of active links

255

-

mac

+

mac

LAG interface MAC address

02:ff:ff:ff:ff:<id>

diff --git a/docs/configuration/interfaces_lag.html b/docs/configuration/interfaces_lag.html index e325b551..3961d856 100644 --- a/docs/configuration/interfaces_lag.html +++ b/docs/configuration/interfaces_lag.html @@ -112,11 +112,15 @@

LACP system identifier

02:ff:ff:ff:ff:00

-

lacp-max-active-links

+

lacp-min-active-links

+

Define the minimum number of active links

+

0

+ +

lacp-max-active-links

Limit the maximum number of active links

255

-

mac

+

mac

LAG interface MAC address

02:ff:ff:ff:ff:<id>

diff --git a/docs/interfaces.html b/docs/interfaces.html index 9cbe301a..f31c84f4 100644 --- a/docs/interfaces.html +++ b/docs/interfaces.html @@ -354,8 +354,8 @@ for interface links referenced by interface functions.

Multithreaded Interfaces

-

The BNG Blaster handles all traffic sent and received (IO) in the main thread per default. +

The BNG Blaster handles all traffic sent and received (I/O) in the main thread per default. With this default behavior, you can achieve between 100.000 and 200.000 PPS bidirectional traffic in most environments. Depending on the actual setup, this can be even less or much more, which is primarily driven by the single-thread performance of the given CPU.

-

Those numbers can be increased by splitting the workload over multiple IO worker threads. -Every IO thread will handle only one interface and direction. It is also possible to start +

Those numbers can be increased by splitting the workload over multiple I/O worker threads. +Every I/O thread will handle only one interface and direction. It is also possible to start multiple threads for the same interface and direction.

-

The number of IO threads can be configured globally for all interfaces or per interface link.

+

The number of I/O threads can be configured globally for all interfaces or per interface link.

{
     "interfaces": {
         "rx-threads": 2,
@@ -475,10 +479,10 @@ the actual configuration and setup. This allows starting 1 million flows with 1
 at least 4 TX threads to verify all prefixes of a BGP full table for example.

 
The configured traffic streams are automatically balanced over all TX threads of the corresponding
 interfaces but a single stream can’t be split over multiple threads to prevent re-ordering issues.

-
Enabling multithreaded IO causes some limitations. First of all, it works only on systems with
+
Enabling multithreaded I/O causes some limitations. First of all, it works only on systems with
 CPU cache coherence, which should apply to all modern CPU architectures. It is also not possible
 to bundle (Link Aggregation) multithreaded interfaces. It is also not possible to capture traffic
-streams send or received on threaded interfaces. All other traffic is still captured even on threaded
+streams send or received on threaded interfaces. All other traffic is still captured on threaded
 interfaces.

 

 
Note

diff --git a/docs/objects.inv b/docs/objects.inv
index 97a69791f9b08a7fa48eb64c18e68922ce7c1d59..2cb5db93f414d80c2b7cc9aefb9bdcf0ab0fec3a 100644
GIT binary patch
delta 641
zcmV-{0)G9r3AqWd>H&W?&rkUVv%A3lSK+AwPLq2wQq{x(qo{Fp_?FrRm5BO!Y
z7?#Tp?XRZG*0>Ru=YUab-NLINZ~0e|hps0lgzcb=qay=2SJQJw=v7lL@F#DAz|V(e
ziJuP<5%){rdt(Cb*WudfFP?q)yKxN@ost3`08i2>niBdBX^{a@lVAcNHxjY$jR`o}
z#P=o$9N=#@@0Qgai%J^y9?1jqwXmda5=o>)hQdptI7)XCq34X#4`8GXY^Op?lehvM
zIWqLBgseXffx2N4m?k?!^?W)ebH^YkVTen9(mUc6gwcdZMfJhJ29V-j+bzS$Y7ndFQ
z`ss6qQFtt*c~^S(xgfbZD5~!BRmRRE5b539N;za_PpT0^8T0mwfIB(+O+cNd{VE_!
zmGu32mUWO33-c%4ox%JyXH4;|U@R!I(&CLaY!|HszmBLpvwPHAZy>W(Fn`Rbrx8^!
z>)~{_tQ&bHO@i>R_>mc1poMjsL*5$dD0aU)mP6_blkqTR-hm)lS8x1gDD$PmLHJ~s
z@lovd*#JRbHcorYZR)j#`wLLROeVFJnQq*3G&2o5N%yfQknpS&Cvo{+7%hCbegEij
bSlStntX*vg;ah2p<+#+CmNEMum4|j#^vFD9

delta 672
zcmV;R0$=^P3APEa>H&XNnF=or?a4?{Tk9ZW;kbD!vXZnXRF6I2SI=TtE<2FFnl4-8
zMqHHxMy++{u7bS9UPT_do}3W2Lokkx4B%Wu&l#atO}W6Iya@t7AC@J4K14*^d+&Q=
z0`9lq+UYNzefTSJ4HKP`0v-TQ$tju=`VMK4Ka-?6G+i2lI!Tjr0vLbNuJ4TrIJv|3
zCI}qhZ#M6iRT+y)8ulK^1M{`8q;AScq(p|oOQJYRcha8cjMEQbqz!DRvP!3iYibTQ
zK^%1tIygmUDeR4+^QwfbHV%O*VG)=nJ4E$jkrgO-f`Eujba@NQ
zqCLS_mP0dFT6Ln5zg-T3S>l)!QQ0U`)m7*89+MaYDu1oo^l#>+Xali%e#$qPH9u_L
zs2wQ4*hX@bQsX~F{x-qJ>Sj1wT8OZkc4v{b84<4XUx+q*Z}R=fBEP3uxJGcR0;3mp
z2n%OmlE~^psyKyrjkM{fy1B9h)GeOdIj4i32AsM^ou#~5TW6>Vy5H`zxzBc0=T4hp
zMX#-!A%7oByBW$FZB{^}2kMTM1^K$Jd)9f&etZ4&Im0MC7Sg;co%&pmTpbiu_pBvh
z=MjkX?ro(UvX3X#h@p&myZ?75XTJcb)3o0JWT}$AKhLrbGGbx=q`Nbizvhf79ubTM
zMOIq8(T44!wcytgm1lO3dh5kwwhHEt8TB-x3V&ujobHx&qohd?{uMtmqYJdKPIJgx
zLmkELcgJ!_ePJ@5q0BoFB@q%z-98&2=*z}whPh3>&2WDKYM9BS
zwldR=dyZzNVJGQ6?F15@mEt5W-wUIK4>#){Jq}Ad
 
The rx/tx-accounting-packets are all packets that should be counted in the session volume
-accounting of the BNG, meaning session rx/tx packets excluding control traffic.

+accounting of the BNG, meaning session RX/TX packets excluding control traffic.

 
Each flow can be queried separately using jsonpath expression with name and direction or flow-id.

 
$ sudo bngblaster-cli run.sock session-streams session-id 1 | jq '."session-streams".streams[] | select(.name == "BE" and .direction == "downstream" )'
 

@@ -519,8 +519,8 @@ can be started or stopped globally using the traffic-stop commands.
-

BNG Blaster Traffic

-

Blaster Header and Fast Decode Signature

+

BNG Blaster Traffic

+

Blaster Header and Fast Decode Signature

The 48 Byte fixed size BNG Blaster Header is added to all data packets for traffic validation and fast decoding. The header is expected on the last 48 bytes of the packet.

@@ -528,7 +528,7 @@ last 48 bytes of the packet.

IPv4 multicast traffic.

Unicast Session Traffic

-

The 64 bit session key is used for all traffic from access (upstream) +

The 64-bit session key is used for all traffic from access (upstream) and to access (downstream) interfaces to identify the corresponding session which has sent or should receive the packet.

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
@@ -592,7 +592,7 @@ stored in host byte order for faster processing

BNG Blaster Magic Sequence

-

The 64 bit magic sequence is the word RtBrick! decoded as ASCII:

+

The 64-bit magic sequence is the word RtBrick! decoded as ASCII:

0x5274427269636b21
@@ -601,18 +601,18 @@ of blaster traffic.

Flow Identifier

-

The 64 bit flow identifier is a globally unique number that identifies +

The 64-bit flow identifier is a globally unique number that identifies the flow.

Flow Sequence Number

-

The 64 bit flow sequence number is a sequential number starting with 1 +

The 64-bit flow sequence number is a sequential number starting with 1 and incremented per packet primary used to identify packet loss.

This number 0 means that sequencing is disabled.

Nanosecond Send Timestamps

-

The 64 bit nanoseconds send timestamp is used for optional latency and +

The 64-bit nanoseconds send timestamp is used for optional latency and jitter calculations.

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html
index 3556f425..37d21b18 100644
--- a/docs/troubleshooting.html
+++ b/docs/troubleshooting.html
@@ -91,17 +91,17 @@
 
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 to files using the argument
+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 events
    • 
+
  • info: informational events
    • 
 
  • error: error events
    • 
 
  • igmp: igmp events with join and leave time
    • 
 
  • io: interface input/output events
    • 
 
  • pppoe: pppoe events
    • 
-
  • info: informational events (enabled per default)
    • 
 
  • pcap: PCAP related events
    • 
 
  • ip: log learned IP addresses
    • 
 
  • loss: log traffic loss with sequence number
    • 
@@ -110,6 +110,8 @@ The following list shows all supported logging options.
    
 
  • isis: log ISIS events
    • 
 
  • bgp: log BGP events
    • 
 
  • tcp: log TCP events
    • 
+
  • lag: log link aggregation (LAG) events
    • 
+
  • dpdk: log DPDK events
    • 
 

 
$ sudo bngblaster -C test.json -L test.log -l ip -l isis -l bgp
 

@@ -134,6 +136,8 @@ include (default behavior) or exclude traffic streams from capture.

 }
+

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