summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml')
-rw-r--r--doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml
index affbf39..0df2605 100644
--- a/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml
+++ b/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml
@@ -394,7 +394,7 @@ disable type: physical netflow-sampler: disable sflow-sampler: disable
394 <para>Since Fortigate VNF, which is acting as router and firewall, is 394 <para>Since Fortigate VNF, which is acting as router and firewall, is
395 configured to be the DHCP server for the LAN network, the device 395 configured to be the DHCP server for the LAN network, the device
396 interface connected to the uCPE LAN port has to be configured to get 396 interface connected to the uCPE LAN port has to be configured to get
397 dinamically assigned IPs. These IPs are in the 172.0.0.0/24 network for 397 dynamically assigned IPs. These IPs are in the 172.0.0.0/24 network for
398 Site1 and the 172.10.10.0/24 network for Site2. Therefore, site-to-site 398 Site1 and the 172.10.10.0/24 network for Site2. Therefore, site-to-site
399 connectivity can be checked (from Site1) as such:</para> 399 connectivity can be checked (from Site1) as such:</para>
400 400