2

Since you mentioned incoming connections and in particular replies going the wrong way, it sounds like it might be enough to have packets sent with the source address 10.150.114.190 (eth2) use the routes that go via 10.150.114.191, and similarly for eth1. Policy-based (source) routing should be able to do that. It should basically boil down to something like:...


2

I think you're looking for (the Linux-only) SO_BINDTODEVICE. From man 7 socket: SO_BINDTODEVICE Bind this socket to a particular device like “eth0”, as specified in the passed interface name. If the name is an empty string or the option length is zero, the socket device binding is removed. The passed option is a variable-length ...


1

Your interface vmbr0 is configured with a default gateway in a different subnet (in other words another logical range) than the IP address. The gateway IP tells the system how to get to another subnet, and without it, packets won't leave the current subnet. For instance, the 192.168.42.0/24 subnet has the following range of usable IP addresses: 192.168.42.1 -...


1

Solved! I had two gateways defined in /etc/network/interfaces. Once I removed all but one, the error is corrected. # systemctl --failed 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.


1

It turns out NetworkManager tries to manage and assign an IP address to the veth* network bridge port (I am assuming this is related to the docker0 network bridge). All these veth* appear in the ifconfig list after I invoke docker run to start a Docker container. They have a different suffix label that is dynamic, but their prefix is always veth*. So the ...


1

Are you unloading the module first? I believe that you have to use modprobe -r i40e to remove it, then you can load it again with the parameters. I found this article helpful (it should be similar on Ubuntu): https://docs.fedoraproject.org/en-US/Fedora/14/html/Deployment_Guide/sec-Setting_Module_Parameters.html This will probably break your connection if you ...


1

Something which you could do is to set a fallback IP in your dhclient.conf so APIPA (automatic private IP addressing) doesn't come into play when your DHCP isn't available. however, this has to be set statically and is not linked to your last DHCP-Lease. Example: Post concerning this topic


Only top voted, non community-wiki answers of a minimum length are eligible