We have an issue where hosts are configured with the public facing
nework interface as the ovirtmgmt network and it's default route is
added to a ovirt created table but not to the main routing table. From
my searching I've found this snippet from https://www.ovirt.org/develop
/release-management/features/network/multiple-gateways/ which seems to
explain why I can't ping anything or communicate with any other system
needing a default route.
"And finally, here's the host's main routing table. Any traffic coming
in to the host will use the ip rules and an interface's routing table.
The main routing table is only used for traffic originating from the
I'm seeing the following main and custom ovirt created tables.
# ip route show table main
10.0.0.0/8 via 10.4.16.1 dev enp3s0.106
10.4.16.0/24 dev enp3s0.106 proto kernel scope link src 10.4.16.15
220.127.116.11/24 dev PUBLICB proto kernel scope link src
18.104.22.168 169.254.0.0/16 dev enp6s0 scope link metric 1002
169.254.0.0/16 dev enp3s0 scope link metric 1003
169.254.0.0/16 dev enp7s0 scope link metric 1004
169.254.0.0/16 dev enp3s0.106 scope link metric 1020
169.254.0.0/16 dev PRIVATE scope link metric 1022
169.254.0.0/16 dev PUBLIC scope link metric 1024
# ip route show table 1138027711
default via 22.214.171.124 dev PUBLIC
126.96.36.199/24 via 188.8.131.52 dev PUBLIC
If I manually execute the following command to add the default route as
well to the main table I can ping ouside of the local network.
ip route add 0.0.0.0/0 via 184.108.40.206 dev PUBLIC
If I attempt to modify the /etc/sysconfig/network-scripts/route-PUBLIC
ad reboot the server ad one would think this file is recreated by vdsm
What I'm looking for is the correct way to setup a default gateway for
the main routing table so the hosts can get OS updates and communicate
with the outside world.
Users mailing list