In our setup, we have vlans on separate interfaces for ip address ranges. Using VMWare, it is relatively easy to create a new interface for each vlan. The first issue is when the default route for the customer ips is different than the primary interface for the server. We had to use the "ip rule" command with a separate route to have the OS (Centos) select the correct route for the 2nd interface. In addition, the /etc/wacct.conf file required modification to set the Device appropriate for the interfaces.
The problem comes with the next vlan. We don't see how we can manipulate the code to use another set of ips on another interface and the same time as the existing interface. The "ip rule" can be set as we did for the existing interface, but the ipaliases will not connect to the correct interface. The "simple" solution for the user is to have the system ask for the default route and interface when adding ips. This will allow the cPanel to do things in a "standard" and documented manner.
I like this idea 
Ok, I've raised a support ticket to see if they could help me implement this but they pointed me back in this direction. They said it is impossible to do at the time.
As a server administrator, and business owner, I expect to be able to provide my customers with dedicated IPs. I also chose what I believe to be the best cloud platform to host my cPanel servers, Amazon AWS. Sadly, I learnt that they have a very limited amount of IPs you can add to each network interface. For a medium instance that would be 6 IP addresses max. But a medium instance could host many more clients. So what they offer is to connect more NICs (up to 3) and that would up the server's limit to 18, which would be much better.
I believe that cPanel and Amazon AWS are a super great combination. But this issue restricts a very important feature. Maybe this has kept away some potential cPanel clients.
Ok, I've raised a support ticket to see if they could help me implement this but they pointed me back in this direction. They said it is impossible to do at the time.
As a server administrator, and business owner, I expect to be able to provide my customers with dedicated IPs. I also chose what I believe to be the best cloud platform to host my cPanel servers, Amazon AWS. Sadly, I learnt that they have a very limited amount of IPs you can add to each network interface. For a medium instance that would be 6 IP addresses max. But a medium instance could host many more clients. So what they offer is to connect more NICs (up to 3) and that would up the server's limit to 18, which would be much better.
I believe that cPanel and Amazon AWS are a super great combination. But this issue restricts a very important feature. Maybe this has kept away some potential cPanel clients.
This makes even more sense when you put IPv6 on another VLAN and provision a new NIC through KVM tagged with that VLAN.
This makes even more sense when you put IPv6 on another VLAN and provision a new NIC through KVM tagged with that VLAN.
We use PFSense firewall. I'd like to block all ports but the standard 80 /443 on the webserver but use some advanced geo based ip rules on pfsense to allow advanced and admin access. The PFsense route is a second nic interface and so requirese something like this.
We use PFSense firewall. I'd like to block all ports but the standard 80 /443 on the webserver but use some advanced geo based ip rules on pfsense to allow advanced and admin access. The PFsense route is a second nic interface and so requirese something like this.
At this time, this isn't something we plan to add to the product so I'm marking this as "not planned"
At this time, this isn't something we plan to add to the product so I'm marking this as "not planned"
Replies have been locked on this page!