All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Requesting Help Setting up Private Network
Hello folks,
I need your help.
I had a dedicated server running few KVM VPs using Virtualizor to manage it. Bridge network is setup using their guide (https://www.virtualizor.com/docs/admin/kvm-bridge/) and it has been working without any issue. I setup and internal network to be use between those KVM VPs on the same server (intbr0). Recently I got a new server and set it up as well using Virtualizor, everything working fine as far as creating new VPS concern.
Issue: Both servers have 10G private network between each other (As per host, directly connected to each other on 10G network). They told me to setup any private IP (same subnet) on them and it should work fine
So I setup Server A --> 192.168.100.2
Server B --> 192.168.100.3
But I can not ping Server A from B or Server B from A.
According to my host, my internal networking (i.e. using KVM by Virtualizor) is causing issue and I need to fix it myself. I am not sure what I am doing wrong here. I did everything exactly as they asked me to.
[root@server A ~]# ip route show
default via 131.x.x.x dev viifbr0 proto static metric 425
131.x.x.x/29 dev viifbr0 proto kernel scope link src 131.x.x.x metric 425
192.168.1.0/24 dev intbr0 proto kernel scope link src 192.168.1.1 metric 426
192.168.100.0/24 dev enp94s0f0 proto kernel scope link src 192.168.100.2 metric 100
[root@server B ~]# ip route show
default via 185.52.53.105 dev viifbr0
185.x.x.0/24 dev viifbr0 proto kernel scope link src 185.x.x.x
192.168.1.0/24 dev intbr0 proto kernel scope link src 192.168.1.1 metric 425
192.168.100.0/24 dev enp1s0f0 proto kernel scope link src 192.168.100.3 metric 100
I understand 192.168.1.X only works between KVM VPs (VPS within Server A can communicate with each other and VPS within Server B can communicate with each other using that range. They can not connect across server. I would want to make them work across servers but it is okay for now).
I need 192.168.100.2 and 192.168.100.3 talking to each other using 10G network so I can transfer between the main servers. How can I get that working?? They can not ping to each other right now.
Do I need to remove intbr0 ? Do I need to add some special routing to get that working?
Ideally, I would want to use the private network (Between Server-A and Server-B ) to use as Internal Network within KVM VPS as well. But I am stuck at Step 1 of getting the private network Between those dedicated server working.
Kindly help with it. Really appreciate that.
Thanks
Comments
Anyone here who can help me with this ??
If I can get this private network up and running quickly, my life would get a lot easier as I have to move large files between the servers tonight.
Any help here ?? I am sure many people have internal network setup that works across servers as well.
Forget anything I said above. Here is current scenario.
Server A (2nd NIC (etha2) for Internal Network)
Server B (2nd NIC (ethb2) for Internal Network)
etha2 and ethb2 are directly connected with 10GB link.
I need help to know how to setup KVM Internal Private Network between the two servers. that can be used across servers.
(A VPS on Server A can connect to a VPS on server B using this private network using above etha2 and ethb2 connection)
Any Private IP range can be used.
Happy to pay for the help.
it doesn't look too complicated.
did you try to setup a dummy server on one and see if it can reach the other?
paste your interface setup, also if there is a firewall rules thats needs to allow private class etc..
Thank you so much for your help.
Private Interface Server A
intbr0 On server A
Private Interface Server B
intbr0 on Server B
I can not even ping 192.168.1.100 from 192.168.1.200
I can not ping private IP of a VPS From ServerA to any Private IP on ServerB
There is no firewall on server A or Server B. Iptables is empty.
On Server A
On Server B
what is the output of "ip a" ?
on both machines
route add 192.168.1.0/24 dev intbr0and try to ping
Isn't that route already there ?? In ip route show command ??
I still added it
But still no ping from 100 to 200 or the other way.
Do I need to add a gateway IP somewhere ?? 192.168.1.1 ?
you can try.
Where and how would I add that ??
this is my manual code when i do briding
here is another example using the interface file from proxmox
last comment i can add is don't forget forwarding has to be enabled.
echo 1 > /proc/sys/net/ipv4/ip_forwardmake it permanent by adding to /etc/sysctl.conf
net.ipv4.ip_forward = 1@ehab
First of all, Thank you so much for help me out.
ip forwarding is enabled. (Double checked in on both servers)
I think the issue is, ServerA is trying to use the default gateway (i.e. Public Interface) to find the private IP of ServerB (and other way around)
(ServerA intbr has IP 192.168.1.100) But see what it's doing
This is the interesting part.
enp94s0f0 is the private NIC. (not the public one)
If I add
It takes server down (i.e. public IP stops responding)
So here is the situation So far (Using the above configuration I posted for both servers)
ServerA can ping VPA1, VPSA1 can ping VPSA2 (all three can ping each other fine)
ServerB can ping VPB1, VPSB1 can ping VPSB2 (all three can ping each other fine)
But still the situation .. 192.168.1.100 can not ping 192.168.1.200 (or the other way)
VPSA1/VPSA2 can not ping VPSB1/VPSB2
Any ideas ???
i can't know for sure without access. I can check them but will request to install Debian 11 and need root access. Also if you offer some amount per hour in pm would be good to know in advance.
Try to turn off rp_filter on all interfaces. If it would not help, send here outputs of next commands from both servers (to see them all in 1 message):
ip a
ip r
brctl show