update

README.md

@@ -44,7 +44,7 @@ Similar to VLANs, each VXLAN network identifier (VNI) uniquely identifies a Laye
 
 ### VTEP Discovery
 
-VxLAN is essentially a tunnelling scheme. Unlike other tunnels, a VXLAN builds a 1 to N network, not just point to point. VXLAN does not provide a control plane and VTEP discovery and address learning is performed either dynamically, in a manner similar to a learning bridge, or using statically-configured forwarding entries. The VTEP discovery [strategies](https://vincent.bernat.ch/en/blog/2017-vxlan-linux) include:
+VxLAN is essentially a tunnelling scheme but it is not limited to point to point tunnels. VXLAN does not provide a control plane to discover other VTEPs in the network, instead address learning is performed either dynamically, in a manner similar to a learning bridge, or using statically-configured forwarding entries. The VTEP discovery strategies include:
 
 - BUM (broadcast, unknown unicast, and multicast) flooding and address learning
 - Static L2/L3 entries
@@ -58,12 +58,13 @@ These labs use FRRouting (FRR) to deploy VxLAN in several scenarios where each s
 
 ![VTEP](img/vtep.png)
 
-
 FRR does not manage network interfaces directly. Instead it learns about the interface configuration from the Linux kernel. Therefore, the configuration of the bridge and the VxLAN interface shown in the figure must be handled by Linux.
 
-## Usefull Links
+## Useful Links
 
 - [FRRouting documentation](https://docs.frrouting.org/en/latest/index.html)
 - [Linux ip command manual](https://man7.org/linux/man-pages/man8/ip.8.html)
 - [Linux brctl command manual](https://man7.org/linux/man-pages/man8/brctl.8.html)
 - [Containerlab](https://containerlab.dev/)
+- [VxLAN & Linux](https://vincent.bernat.ch/en/blog/2017-vxlan-linux)
+- [VxLAN: BGP EVPN with FRR](https://vincent.bernat.ch/en/blog/2017-vxlan-bgp-evpn)

pim/README.md

@@ -18,9 +18,9 @@ pimd=yes
 
 The router configuration files are in the *-frr.conf files. The files include the interface and OSPF configurations for each router. All router-facing interfaces belong to OSPF area 0. The OSPF distributes routes to all connected networks, including the loopback interfaces, which are used by the VxLAN.
 
-Note that PIM must be enabled on all interfaces facing multicast sources or multicast receivers, as well as on the interface where the RP address is configured. IGMP is also enabled on the same interafces.
+Note that PIM must be enabled on all interfaces facing multicast sources or multicast receivers, as well as on the interface where the RP address is configured. IGMP is also enabled on the same interfaces.
 
-The VxLAN configuration reside in the setup-vxlan.sh script files. The configuration is mostly similar to other labs with the excption of the following command, which specifies the multicast group address and the physical interface used as the endpoint for the VXLAN tunnel. The TTL must be increased the default 1 to allow VxLAN packets to traverse the network.
+The VxLAN configuration reside in the setup-vxlan.sh script files. The configuration is mostly similar to other labs with the exception of the following command, which specifies the multicast group address and the physical interface used as the endpoint for the VXLAN tunnel. The TTL must be increased the default 1 to allow VxLAN packets to traverse the network.
 
 ```
 docker exec -it clab-pim-r1 ip link add vxlan100 type vxlan id 100 dstport 4789 local 1.1.1.1 group 239.1.1.1 dev eth1 ttl 5