From de07ac33b856e90f7fbc8dce1928b7d728337395 Mon Sep 17 00:00:00 2001
From: Christian Giese <christian@rtbrick.com>
Date: Wed, 25 May 2022 16:01:10 +0000
Subject: [PATCH] update IPoE docu

---
 docsrc/sources/access/l2bsa.rst |  7 ++--
 docsrc/sources/quickstart.rst   | 59 ++++++++++++++++++++++++++++++++-
 2 files changed, 61 insertions(+), 5 deletions(-)

diff --git a/docsrc/sources/access/l2bsa.rst b/docsrc/sources/access/l2bsa.rst
index cbe15d9a..b5885e79 100644
--- a/docsrc/sources/access/l2bsa.rst
+++ b/docsrc/sources/access/l2bsa.rst
@@ -51,13 +51,12 @@ upstream direction (from U to A10-NSP interface). Those headers allow the wholes
 the actual U interface for traffic received on the A10-NSP interface. This functionality is referred to 
 as the intermediate agent functionality.
 
-
 The BNG Blaster A10NSP interface emulates such a layer two provider interface. This interface type accepts 
-all PPPoE sessions received to verify forwarding and PPPoE header enrichment. 
+all DHCPv4 and PPPoE sessions received to verify forwarding and header enrichment.
 
 .. note:: 
-    It is also planned to emulate a lightweight DHCPv4 and DHCPv6 server
-    to verify IPoE forwarding and header enrichment. 
+    It is also planned to emulate a lightweight DHCPv6 server
+    to verify IPv6 forwarding and header enrichment for IPoE. 
 
 Following a basic PPPoE/A10NSP configuration example which is
 detailed explained in the configuration section.
diff --git a/docsrc/sources/quickstart.rst b/docsrc/sources/quickstart.rst
index 0dbeb7ee..b805e863 100644
--- a/docsrc/sources/quickstart.rst
+++ b/docsrc/sources/quickstart.rst
@@ -45,7 +45,7 @@ one more :ref:`traffic stream <streams>` bound to the sessions.
             ],
             "access": [
                 {
-                    "__comment__": "PPPoE",
+                    "__comment__": "PPPoE Client",
                     "interface": "veth1.2",
                     "type": "pppoe",
                     "outer-vlan-min": 1,
@@ -193,6 +193,63 @@ You can also try other :ref:`commands <api>` to get familiar with the API.
 After the test has stopped, you can also check the final JSON report (``jq . report.json``),
 log, and PCAP files. 
 
+DHCP
+----
+
+Let's repeat all the steps from the PPPoE example before but with the following
+IPoE DHCP configuration.
+
+**dhcp.json:**
+
+.. code-block:: json
+
+    {
+        "interfaces": {
+            "a10nsp": [
+                {
+                    "__comment__": "DHCP Server",
+                    "interface": "veth1.1"
+                }
+            ],
+            "access": [
+                {
+                    "__comment__": "DHCP Client",
+                    "interface": "veth1.2",
+                    "type": "ipoe",
+                    "ipv6": false,
+                    "outer-vlan-min": 1,
+                    "outer-vlan-max": 4000,
+                    "inner-vlan": 7,
+                    "stream-group-id": 1
+                }
+            ]
+        },
+        "access-line": {
+            "agent-remote-id": "DEU.RTBRICK.{session-global}",
+            "agent-circuit-id": "0.0.0.0/0.0.0.0 eth 0:{session-global}"
+        },
+        "dhcp": {
+            "enable": true,
+            "broadcast": false
+        },
+        "session-traffic": {
+            "ipv4-pps": 1
+        },
+        "streams": [
+            {
+                "stream-group-id": 1,
+                "name": "S1",
+                "type": "ipv4",
+                "direction": "both",
+                "priority": 128,
+                "length": 256,
+                "pps": 1,
+                "a10nsp-interface": "veth1.1"
+            }
+        ]
+    }
+
+
 ISIS
 ----