31 results found
We have a lot of IPv4 /27 and /26 public IP blocks. At our various locations we share VLANs and IP blocks between many servers. Each time we add a new server we have to manually add the server to many IP blocks. This is a tedious exercise. It's the most tedious exercise we do in SolusVM management. We would like to request some kind of better design. I think what would be better is if SolusVM had some higher level "grouping" of network blocks that you then assigned to servers in same VLAN. When we needed to add a…24 votes
We are handling an increasing number of migrations from one location to another, and it would be helpful to streamline this process for efficiency:
Next to the ADD button where we add a new IP, there would be a REPLACE MAIN IP button to click instead. It simply replaces the main IP and deletes the old one to make it available in the pool again.19 votes
A firewall system should be developed for virtual servers or virtual server groups. We have to block and allow certain ip and ports.15 votes
We would like to be able to give customers their own virtual network. Instead of adding them onto a global internal network we prefer to have something like Open vSwitch or similar. This allows for overlapping internal address scopes for example. It would improve the security of internal systems, e.g. a database server.15 votes
Add network rules for VPS DDoS protection in Network Rules in SolusIO13 votes
Ability to shape networking past 1000Mbps13 votes
The new VLAN feature from Hetzner requires an MTU of 1400. Because SolusVM automatically creates the network configuration on the VPS, it would be good if you could change the MTU value for the VPS network interface.11 votes
ability to add additional network interfaces to KVM VPSes9 votes
Please allow us to reserve certain IPs from the API8 votes
Add option to assign bulk IPv4 addresses to a VM (OVZ or KVM) instead of having to manually add one at a time which is time consuming and antiquated method.8 votes
It would be better to delete all DNS records associated with a VM when the VM has been deleted7 votes
It would be better if we disable the network of the VM from the SolusVM 2 panel. So an abusive VM network can be disabled and let the customers resolve their situation through VNC.6 votes
I through database to set kvm143 netspeed=2000 but it can't discriminate it
[root@localhost ~]# php /usr/local/solusvm/includes/trafficloader.php --mode=all --debug=1
MASTER RESULT RETURN ARRAY
[success] => 1
[nic] => br0
[nicspeed] => 10000
[vt] => kvm
[traffic] => 53,kvm138.0,138,0;IP|54,kvm139.0,139,600mbit;IP|58,kvm142.0,142,0;IP|59,kvm143.0,143,0;IP|60,kvm144.0,144,0;IP|62,kvm146.0,146,1000mbit;IP
REPLACE CORRECT VIFVM PREFIX FROM CONFIG
DELETING QDISC FROM br0
ADDING QDISC TO br0
DELETING QDISC FROM kvm138.0
DELETING QDISC FROM kvm139.0
ADDING QDISC TO kvm139.0
ADDING CLASS TO kvm139.0 WITH SPEED 600mbit CLASSID 2
ADDING QDISC TO kvm139.0 WITH HANDLE 2
ADDING CLASS TO br0 WITH SPEED 600mbit CLASSID 2
ADDING QDISC TO br0 WITH HANDLE…6 votes
It would be better to add this feature to have IPv6 Only VM.
Other Virtualization has this feature so it will be a good addition for SolusVM to have this.5 votes
We use SolusVM as our primary source for all our IP ranges. But we have physical machines too. To make sure these IP's are not used we reserve them in SolusVM.
It would be helpful if we can set a description for these IP addresses. Basically, we just need a description field for each IPv4 address and IPv6 subnet that we reserve.
I know you can set reverse DNS for IPv4 but you can't for IPv6 subnets. A single solution that covers all IP's is preferred, so that's why I suggest to add a description field.5 votes
Instead of assigning the lowest numbered IP, cycle through each IP in the range to ensure even usage.
This would allow a natural cooldown period from when an IP is last used to when it's assigned to a new VM, potentially improving situations where the previous user left a poor email reputation.4 votes
Add ability to add IP addresses for customers4 votes
IPv6 address as the main IP for VMs4 votes
We would like to request a new feature for when adding a new network block and IPs in SolusVM that there is a checkbox or option to add the IP's in a reserved state. We sometimes acquire RIPE addresses and actually preconfigure them in SolusVM before our network team partner has completed the actual network configuration. Occasionally we've had orders coincidentally come in the same moment we are adding additional network blocks and get provisioned on the new network blocks that are not yet reserved or fully set up.
Therefore we would like to be able to add network block…4 votes
- Don't see your idea?