Happy with 3.x - Sad with 4.x - Help me

[altomarketing]

Hi ! i have 10 happy servers with Proxmox 3.x , I basically have 50 PUBLIC ips, and on every new Proxmox 3.x server i did only this:

on 3.x : Setup proxmox with one public ip >> Add CT >> Routed mode with a new public ip >> Thats all ! I repetead this with every CT each one with one unique public IP (10 times) and start selling VPS

on Proxmox 4.0 I can not just did it, i just want to add LXC container with a new public ip. I read all about Network Model, bridge, venet, veth, .... but proxmo ask me now when i create a CT for a ipv4/cidr range when i create a new container, why can i not put just one ip like route in 3.x version ?

Im not an expert you can notice it, but there is on 4.0 a SIMPLE way to add a new CT with a new public IP like i did in 3.x version ?

 

[wirelessrouter]

I have the same problem.

 

[manu]

Hi
While creting a container, the cidr is your subnet mask, but written in CIDR notation.

Most probably, you should check the subnet mask of your host as show in the gui. convert this value to CIDR notation, and put this in Network tab when creating your container.

 

[altomarketing]

Hi
While creting a container, the cidr is your subnet mask, but written in CIDR notation..

Sorry but i dont understand.

all ips are 190.228.48.xxx - 255.255.255.240 and gateway 190.228.48.160 for all my ips
proxmox is 190.228.48.182
i need a container with 190.228.48.183

I try to add 190.228.48.183/32 (using http://www.subnet-calculator.com/cidr.php ) but error: is
Parameter verification failed. (400)

net0: invalid format - format error at /usr/share/perl5/PVE/JSONSchema.pm line 529 net0.ip: invalid format - value does not look like a valid ipv4 network configuration

 

[jim.bond.9862]

Sorry but i dont understand.

all ips are 190.228.48.xxx - 255.255.255.240 and gateway 190.228.48.160 for all my ips
proxmox is 190.228.48.182
i need a container with 190.228.48.183

I try to add 190.228.48.183/32 (using http://www.subnet-calculator.com/cidr.php ) but error: is
Parameter verification failed. (400)

net0: invalid format - format error at /usr/share/perl5/PVE/JSONSchema.pm line 529 net0.ip: invalid format - value does not look like a valid ipv4 network configuration

shouldn't it be "190.228.48.183/20" ?
as per the calculator CIDR for 255.255.255.240 is 20

 

[altomarketing]

shouldn't it be "190.228.48.183/20" ?
as per the calculator CIDR for 255.255.255.240 is 20

Sorry , i meant 255.255.255.224 , how do you calc for it ? and if there is any online tool to calc all my ips , better.

 

[jim.bond.9862]

Sorry , i meant 255.255.255.224 , how do you calc for it ? and if there is any online tool to calc all my ips , better.

even with the correction it still should be xxx.xxx.xxx.xxx/27 not 32
the calculator you are using have an option "[h=2]CIDR Netmask[/h]" you should choose the one you need and it will give you the needed value in "Mask Bits"

 

[altomarketing]

shouldn't it be "190.228.48.183/20" ?
as per the calculator CIDR for 255.255.255.240 is 20

Does it create a containter with only 190.228.48.183 ?

ok, to clarify can someone how to add a single ip that we used to do every CT we creat in proxmox 3.x , but in proxmox 4.x in the new format CIDR ?

it dont know what mask bits are.

 

[jim.bond.9862]

the mask bit is a representation on the subnet notation.
before CIDR gain speed we used notation like 192.168.x.x / 255.255.xxx.xxx to define IP/Subnet
no you can represent the 255.255.xxx.xxx subnet notation using numbers from 1 to 32
where 1 represent 128.0.0.0 and 32 represent 255.255.255.255

I am not too big on this my self as I never can calculate the number properly, but thank god we have the calculators to do this for us . we just need to put the right info in and get the result.

remember in old versions you would have an additional feald for subnet or
in IP box you would put 192.168.x.x/255.255.xxx.xxx well now you need to use
the 192.168.x.x/xx notation (CIDR) to represent the same thing. we can not substitute the IP
but subnet is more or less static set of values that can be represented in this way

 

[wbumiller]

The pendings updates will allow using /32 cidrs which will allow the opening poster's setup to work again.

 

[jim.bond.9862]

The pendings updates will allow using /32 cidrs which will allow the opening poster's setup to work again.

i think the OP issue was not that /32 CIDR is not working in Proxmox but that the IP/bitmask combination was/is wrong.

the IP was not part of the bitmask range choosen.
as I pointed out earlier the OP used IP address which corresponds to /27 bitmask but put in /32

 

[wbumiller]

i think the OP issue was not that /32 CIDR is not working in Proxmox but that the IP/bitmask combination was/is wrong.

the IP was not part of the bitmask range choosen.
as I pointed out earlier the OP used IP address which corresponds to /27 bitmask but put in /32

That wouldn't have triggered the described «Parameter verification failed. (400)» error message, that's due to the /32.

 

[jim.bond.9862]

ok, I am not sure if it would trigger the error or not as I had never used /32 subnet. infact for all my setups I never stray from /24 or /8 subnets

I just pointed out that OP used the wrong subnet to begin with (!!! based on the information he/she provided in the post !!!) so the setup would probably not worked anyway and might have created more issues in a long run.

that's all.

 

[altomarketing]

Ok, but no one is helping-answering my question , what should I add in ipv4/cidr field for create a containers.

My CT will use 190.228.48.183 - ny network uses = 255.255.255.224 , my gateway is 190.228.48.160.

I will create 20 CT more like xx.xx.xx.184 .. 185 .186 and so on...

 

[jim.bond.9862]

see my post earlier, it should be 190.228.48.183/27.

your subnet is 255.255.255.224 which translates to /27 in CIDR notation.
in old way you would enter 190.228.48.183/255.255.255.224 in the single field or split that up into two fields
using the new way you enter 190.228.48.183/27 replacing the full subnet mask with a bitmask value instead

keep in mind that your subnet range have only 30 address 190.228.48.160 - 190.228.48.191
29 actually since .160 is already used for your gateway.