September 17, 20223 yr Do bear with me a little as I explain how I eventually get to this state where FCP show warning that I assigned 2 nics to the same network. "Multiple NICs on the same IPv4 network" I started off with only 1 nic and everything was working fine. I am able to connect to all my dockers and VMs(RDP) as long as it under the same network. My only concern at that time was the read speed in my 2.5g network setup. I have a nvme cache and I create a share which use only nvme cache. I am able reach a write speed of 280MB/s~ however the read speed is cap at 140MB/s~. I did an iperf3 test on both direction between both the server and client and the result is exactly what I explain above. I have a docker running LibreSpeed Speedtest and I am able to reach 2400Mb/s~ both upload and download. After some research, I manage to solve it by turning off the Bridge Mode for eth0. Now I am able to get the blazing fast 280MB/s~ read write from my nvme cache share. This is where the problem come, I will need to reconfig all my dockers to use Custom:br0 and assign back their individual IP I set previously. All dockers runs fine. However my VMs wont start as it state that br0 is not longer available and I have to use virbr0 for all my VMs. This result in my VMs will be in different network. I will not be able to RDP to my VMs on my computer which I need. At this moment I grab a USB C network adapter lying on my desk to test some concept. I was trying to use this second eth1 and enable Bridge Mode which give me br1 to assign to my VMs. Now I am able to maintain that 280MB/s read write from my nvme cache share and still able to access my VMs from any machine within the same network. So I am not to sure if I should ignore the warning or there is a better way of achieving what I need?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.