Skip to content
This repository has been archived by the owner. It is now read-only.
Browse files

kvm: solve routing issues by using the same default bridge as CNI

When the kvm stage1 and the coreos stage1 are used on the same machine with a
flannel CNI configuration (and likely other configurations) without a specified
bridge name, different bridges will be constructed by each stage1 for the same
subnet -- cni0 and kvm-cni0 -- causing traffic intended for the
later-constructed bridge to be lost, as it is routed to the earlier-constructed

The normal workaround is to specify a bridge name in the CNI configuration, but
this fix avoids the issue altogether by making sure that cni0 is used in all
  • Loading branch information
celskeggs committed Feb 17, 2018
1 parent 4029349 commit 4ae50784b9f2c13c66b17b053f4aa13b1647cad2
Showing with 1 addition and 1 deletion.
  1. +1 −1 networking/kvm.go
@@ -43,7 +43,7 @@ import (

const (
defaultBrName = "kvm-cni0"
defaultBrName = "cni0"
defaultSubnetFile = "/run/flannel/subnet.env"
defaultMTU = 1500

0 comments on commit 4ae5078

Please sign in to comment.