Network issues after reboot

You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : Network issues after reboot

Threaded Mode | Print

Network issues after reboot (2 Replies, Read 20194 times)

trueorbit	# May 1, 2020, 7:50 pm
Group: Member Post Group: Newbie Posts: 1 Status:	Background: - I have 1 master running Virtualizor along with VMs hosted on the same machine. - I have a /29 IP block the master/panel is on, also a /26 for additional IPs Everything was up and running prior to failure of the network card. We replaced the network card and on reboot the server came back online with the main IP only pinging, no other IP address is available. Also, when I SSH to the next IP after the panel (which is assigned to a VM), it ssh's to the main root and not the VM itself. The entire /29 IP block does this, and the /26 IP range is completely unavailable. I have had this issue in the past with SolusVM (using OpenVZ) before switching and am not sure what could be the cause of the problem, any ideas? The main device enp94s0f1 is connected, also this is setup properly in Config->Slaves->Network as it should (was the same before the issue), and the bridge is also connected. Any thoughts on what to check?
IP: --

Network issues after reboot

wolke	# May 4, 2020, 7:42 am \| Post: 1
Group: NOC Post Group: Elite Member Posts: 437 Status:	Sounds like a libvirtd issue. try the following: 1. create a file with the following content: Code #!/bin/bash /sbin/iptables -A FORWARD -m physdev --physdev-is-bridged -j ACCEPT service libvirtd restart 2. make it executable with chmod +x 3. run the file after reboot or firewall restart. We are using the same solution, just with csf firewall. So you can also use the code in a csfpost.sh file, which runs after starting/restarting csf. Edited by wolke : May 4, 2020, 7:42 am
IP: --

Network issues after reboot

jevingala	# May 18, 2020, 1:13 pm \| Post: 2
Group: Virtualizor Team Post Group: Super Member Posts: 773 Status:	Hi, The firewall rule does not seems to be a solution in this case. I think the entire range must be added on server's NIC instead of a single ip. If the issue is ongoing then please open a ticket with access details so that we can check if there is anything in which Virtualizor can do to help you out. ----------------------- Regards, Virtualizor Team. http://virtualizor.com/
IP: --

« Previous Next »

Threaded Mode | Print

Jump To :

Users viewing this topic
	1 guests, 0 users.

All times are GMT. The time now is May 2, 2025, 2:48 am.

Powered By AEF 1.0.8 © 2007-2008 Electron Inc.

Queries: 10 | Page Created In:0.303