Please sign in to comment.
Add advanced routing configuration option to routed_bridge
Context ------- Virtualization host with several mixed guests (kvm, lxc, docker, podman) Multiple network interfaces on different networks Multiple ip subnets served through a single nic (like OVH vrack setup) Bridged setup to provide network connectivity to guests Issue ----- Depending on guest subnet, network traffic must be routed through the correct gateway Solution -------- iproute2 provides multiple routing tables features OpenSVC interaction ------------------- When private backend networks are used across the cluster, each routing table must be aware of private ip segments Example ------- eth1@hypervisor <=> br0 <=> veth1 <=> eth1@container1 10.0.0.0/24 [routing table custom1] <=> veth2 <=> eth2@container2 18.104.22.168/24 [routing table custom2] Considering the private network below : [network#backend1] type = routed_bridge network = 10.11.0.0/16 ips_per_node = 1024 tunnel = always tables = main custom1 custom2 agent will manage network routes configuration for routing tables main, custom1, custom2 root@node:~# ip route show table custom1 default via 10.0.0.1 dev br0 10.11.0.0/22 dev obr_backend1 scope link 10.11.4.0/22 dev tun6023548126 scope link src 10.11.0.1 root@node:~# ip route show table custom2 default via 22.214.171.124 dev br0 10.11.0.0/22 dev obr_backend1 scope link 10.11.4.0/22 dev tun6023548126 scope link src 10.11.0.1
- Loading branch information...
Showing with 41 additions and 20 deletions.