stakanov wrote:
In data venerdì 25 agosto 2017 15:20:29 CEST, Per Jessen ha scritto:
stakanov wrote:
I should have internet only on eth0 (which was wrongly renamed eth1 for reasons that I do not understand. It is the eth of the mainboard.
Enumeration of network interfaces follows the sequence in which their drivers are loaded. You can change it with YaST or by directly editing /etc/udev/rules.d/70-persistent-net.rules
I then have a eth1 pci-e card that handles only internal traffic and should be set to inner zone (no restrictions). Traffic on that card should have no possibility to access the internet. It will be handled by a little dedicated router. The bridge is there for kvm and should allow the virtualized systems to access the internet via eth0.
Okay.
So, first I looked for sudo route and got that I had the default route that was on the network not branched to the router. So I found out about the naming and renamed the whole thing. Then I tried to set up the bridge for KVM and linked it to eth0. However then, when I do this I have no default route any more.
In that setup, eth0 does not have the address, br0 will - but you'll have to enable dhcp for br0.
If I just have the two cards it seems that for reasons I do not understand, eth1 is preferred over eth0.
What do you mean by "preferred" ? Actually you answered that above. As the driver for the pci-e was loaded before, the eth0 was attributed from mainboard to pci-e and the default route pointed to ... the internal network without internet.
Yes, when you have two interfaces that both use DHCP, you need to specify which one gets to set the default route. See DHCLIENT_SET_DEFAULT_ROUTE in the network config. -- Per Jessen, Zürich (26.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org