search for: vxlan0

...would like to *add more physical nodes later* when I need the resources. This is what I have done so far: - Installed latest Ubuntu 18.04, with latest version of libvirt and supporting software from ubuntu's apt repo. - Each node can reach the other via its own eth0. - Each node has a working vxlan0, which can ping the other via its vxlan0, so it looks like the vxlan config is working. (I used *ip link add vxlan0 type vxlan...*) - Configured route on Host1 like so: *ip route add 192.168.2.0/24 <http://192.168.2.0/24> via 172.20.0.1* - Configured route on Host2 also: *ip route add 192.168...

...or me, I intend for each guest to be *"stationary" to each host*. Each node's *eth0* is connected via IPSec (unicast and transport mode) to the other. This is to encrypt the communication between all nodes because it travels over the internet. Additionally, each node currently has a *vxlan0* interface in the *172.20.0.0/24 <http://172.20.0.0/24>* network which allows them to be all on the same "LAN". I have attached a simple diagram illustrating this setup, also available here: https://i.imgur.com/jc7bc6b.png . I would *prefer* to use the DHCP that comes "built-in...

...nodes later* when I need the > resources. > > This is what I have done so far: > - Installed latest Ubuntu 18.04, with latest version of libvirt and > supporting software from ubuntu's apt repo. > - Each node can reach the other via its own eth0. > - Each node has a working vxlan0, which can ping the other via its vxlan0, > so it looks like the vxlan config is working. (I used *ip link add vxlan0 > type vxlan...*) > - Configured route on Host1 like so: *ip route add 192.168.2.0/24 > <http://192.168.2.0/24> via 172.20.0.1* > - Configured route on Host2 al...

...two tc filters. The first, an ingress filter that matches on packets received from VTEP1 and marks them using a fwmark (firewall mark). The second, an egress filter configured on the LAG interface connected to the host that matches on the fwmark and drops the packets. Example: # tc filter add dev vxlan0 ingress pref 1 proto all flower enc_src_ip $VTEP1_IP action skbedit mark 101 # tc filter add dev bond0 egress pref 1 handle 101 fw action drop Motivation ========== For each ES, only one VTEP is elected by the control plane as the DF. The DF is responsible for forwarding decapsulated BUM traffic...

...two tc filters. The first, an ingress filter that matches on packets received from VTEP1 and marks them using a fwmark (firewall mark). The second, an egress filter configured on the LAG interface connected to the host that matches on the fwmark and drops the packets. Example: # tc filter add dev vxlan0 ingress pref 1 proto all flower enc_src_ip $VTEP1_IP action skbedit mark 101 # tc filter add dev bond0 egress pref 1 handle 101 fw action drop Motivation ========== For each ES, only one VTEP is elected by the control plane as the DF. The DF is responsible for forwarding decapsulated BUM traffic...