At the moment the gateway VM in qemu has only 1 network interface - eth0, instead of the two network interfaces needed in the future (one for external traffic, one to the network switch with the nodes). This is works-as-designed until #9 is implemented.
The problem at the moment is that the homek8s gateway ansible role configures a static ip address for eth0 , at least with the current hosts.qemu file. There eth0 is the interface to the dedicated network switch (to the nodes) and the ansible role assigns the ip address 192.168.2.10 to it.
This breaks the qemu default networking as this uses a qemu DHCP service to give the gateway VM an ip address of 10.0.2.15 - which we override with the static ip.
This problem will be solved when #9 is implemented and we give the gateway the 2 network interfaces it needs. Or we could temporarily just alter the network interface names in hosts.qemu so that eth0 is the external network interface (there we don't set a static ip but receive it via DHCP).
herzogf
commented
4 years ago
At the moment the gateway VM in qemu has only 1 network interface - eth0, instead of the two network interfaces needed in the future (one for external traffic, one to the network switch with the nodes). This is works-as-designed until #9 is implemented.
The problem at the moment is that the homek8s gateway ansible role configures a static ip address for eth0 , at least with the current hosts.qemu file. There eth0 is the interface to the dedicated network switch (to the nodes) and the ansible role assigns the ip address 192.168.2.10 to it. This breaks the qemu default networking as this uses a qemu DHCP service to give the gateway VM an ip address of 10.0.2.15 - which we override with the static ip.
This problem will be solved when #9 is implemented and we give the gateway the 2 network interfaces it needs. Or we could temporarily just alter the network interface names in hosts.qemu so that eth0 is the external network interface (there we don't set a static ip but receive it via DHCP).