daan.hoogl...@gmail.com]
> Sent: Tuesday, May 26, 2015 8:09 AM
> To: =SMTP:dev@cloudstack.apache.org
> Subject: Re: support for /31 Networks
>
> Devender, do you have a test possibility? Wilder made a fix for master
> which I backported to 4.4:
> https://github.com/DaanHoo
Sent: Tuesday, May 26, 2015 8:09 AM
> To: =SMTP:dev@cloudstack.apache.org
> Subject: Re: support for /31 Networks
>
> Devender, do you have a test possibility? Wilder made a fix for master
> which I backported to 4.4:
> https://github.com/DaanHoogland/cloudstack/tree/4.4
> If y
Hi Daan ,
It"s worked grate, a big thanks for your support
Devender
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Tuesday, May 26, 2015 8:09 AM
To: =SMTP:dev@cloudstack.apache.org
Subject: Re: support for /31 Networks
Devender, do you have a
Original Message-
>> From: Wilder Rodrigues [mailto:wrodrig...@schubergphilis.com]
>> Sent: 22 May 2015 18:23
>> To: dev@cloudstack.apache.org
>> Subject: Re: support for /31 Networks
>>
>> Hi guys,
>>
>> We found when it was changed and the reason why:
gt; Devender
>
> -Original Message-
> From: Wilder Rodrigues [mailto:wrodrig...@schubergphilis.com]
> Sent: 22 May 2015 18:23
> To: dev@cloudstack.apache.org
> Subject: Re: support for /31 Networks
>
> Hi guys,
>
> We found when it was changed and the reason why:
>
>
Hi ,
Can I get patch file to use /31 subnet in 4.4.2
Devender
-Original Message-
From: Wilder Rodrigues [mailto:wrodrig...@schubergphilis.com]
Sent: 22 May 2015 18:23
To: dev@cloudstack.apache.org
Subject: Re: support for /31 Networks
Hi guys,
We found when it was changed and the
c/rfc3021.txt).
This is widely supported on network gear, and in modern operating
systems.
- Si
From: Remi Bergsma mailto:r...@remi.nl>>
Sent: Thursday, May 21, 2015 10:31 AM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subje
1, 2015 10:31 AM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: Re: support for /31 Networks
Hi,
This question was answered here as well:
http://markmail.org/message/m7vi342uwm4zr5iv
Support was removed as /31 has no available ip addresses.
Regards,
Remi
2015-05-21 16:
1.txt).
> >
> > This is widely supported on network gear, and in modern operating
> systems.
> >
> > - Si
> >
> >
> > From: Remi Bergsma
> > Sent: Thursday, May 21, 2015 10:31 AM
> > To: dev@cloudstack
defined in RFC 3021 (http://www.ietf.org/rfc/rfc3021.txt).
> >
> > This is widely supported on network gear, and in modern operating
> systems.
> >
> > - Si
> >
> >
> > From: Remi Bergsma
> > Sent: Thursday, M
_
> From: Remi Bergsma
> Sent: Thursday, May 21, 2015 10:31 AM
> To: dev@cloudstack.apache.org
> Subject: Re: support for /31 Networks
>
> Hi,
>
> This question was answered here as well:
> http://markmail.org/message/m7vi342uwm4zr5iv
>
> Support was removed as /3
Interesting enough, there is some info on it:
Using 31-Bit Prefixes on IPv4 Point-to-Point Links
https://tools.ietf.org/html/rfc3021
Perhaps we should restore support? I can imagine that since we are short on
ipv4 addresses, it's a waste to throw two of them away in each network. Any
thoughts?
R
: Thursday, May 21, 2015 10:31 AM
To: dev@cloudstack.apache.org
Subject: Re: support for /31 Networks
Hi,
This question was answered here as well:
http://markmail.org/message/m7vi342uwm4zr5iv
Support was removed as /31 has no available ip addresses.
Regards,
Remi
2015-05-21 16:42 GMT+02:00 Ian Southam
Hi,
This question was answered here as well:
http://markmail.org/message/m7vi342uwm4zr5iv
Support was removed as /31 has no available ip addresses.
Regards,
Remi
2015-05-21 16:42 GMT+02:00 Ian Southam :
> Hi Devender,
>
> You have started quite a discussion in our office about using the .0 and
Hi Devender,
You have started quite a discussion in our office about using the .0 and
putting a host on the cast address …...
Just as a matter of interest, why do you do this - we are presuming it does
actually work ;)
—
Grts!
Ian
> On 21 May 2015, at 10:29, Singh, Devender wrote:
>
> Hi Cl
Hi Cloudstack Team,
We had no problems building and using /31 networks on 4.2.0, but after our
upgrade to 4.4.2 we are no longer able to add new ones.
We have a lot of them already in place. As an example I pasted some output
from cloudmonkey on a link that is already established and working.
Hi Devender,
IIRC some changes have been made in this area in recent releases. So first
ip address in the cidr would not be treated as valid ip address for
assignment since it is a network id. So /31 would not have sufficient ips
to deploy vm.
Thanks,
Sanjeev
On Thu, May 14, 2015 at 10:15 PM, Si
Hello,
We had no problems building and using /31 networks on 4.2.0, but after our
upgrade to 4.4.2 we are no longer able to add new ones.
We have a lot of them already in place. As an example I pasted some output
from cloudmonkey on a link that is already established and working.
Does anyone ha
18 matches
Mail list logo
