let's find it to put in 4.4.4. unless there was a better reason then this to put it in.
Op do 21 mei 2015 om 21:42 schreef Remi Bergsma <rberg...@schubergphilis.com >: > Exactly! > Left my mail in outbox and missed your reply ;-) > > @Sanjeev, since you answered the original mail.. Do you know when/where > this check was added? Or else I’ll search for it. Let’s open an issue and > resolve it. > > Thanks, > Remi > > > On 21 May 2015, at 19:28, Simon Weller <swel...@ena.com> wrote: > > > > You can assigned the network address as a valid ip address from a /31, > and this is 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 <r...@remi.nl> > > 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 /31 has no available ip addresses. > > > > Regards, > > Remi > > > > 2015-05-21 16:42 GMT+02:00 Ian Southam <isout...@schubergphilis.com>: > > > >> 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 <dsi...@virtela.net> wrote: > >>> > >>> 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. > >>> Does anyone have a workaround, or can point me in the right direction > >> for a patch? > >>> (local) > list networks id=e044c442-48f7-4bae-8c5d-530423a249f7 > >>> count = 1 > >>> network: > >>> id = e044c442-48f7-4bae-8c5d-530423a249f7 > >>> name = VLAN180 > >>> acltype = Domain > >>> broadcastdomaintype = Vlan > >>> broadcasturi = vlan://180 > >>> canusefordeploy = False > >>> cidr = 202.90.43.0/31 > >>> displaynetwork = True > >>> displaytext = VM-UTILITY-2 > >>> dns1 = 4.2.2.1 > >>> domain = ROOT > >>> domainid = 8acf0368-e5b1-11e2-b5cf-2ef4cf18a6ae > >>> gateway = 202.90.43.0 > >>> ispersistent = False > >>> issystem = False > >>> netmask = 255.255.255.254 > >>> networkofferingavailability = Optional > >>> networkofferingconservemode = False > >>> networkofferingdisplaytext = private-guest1_switch > >>> networkofferingid = 0b63d457-5f5e-426f-a81e-8797e522eb8c > >>> networkofferingname = private-guest1_switch > >>> physicalnetworkid = cf4c2846-2418-4ba4-b307-6a6405860799 > >>> related = e044c442-48f7-4bae-8c5d-530423a249f7 > >>> restartrequired = False > >>> service: > >>> specifyipranges = True > >>> state = Setup > >>> strechedl2subnet = False > >>> subdomainaccess = True > >>> tags: > >>> traffictype = Guest > >>> type = Shared > >>> vlan = 180 > >>> zoneid = 88066cb4-64ab-4c54-83a9-3279a1e030cb > >>> zonename = UTILITY-ZONE-1 > >>> > >>> (local) > list nics nicid=e062922f-c0ea-4f8a-beca-b86146dee622 > >> virtualmachineid=842054e6-c379-49fe-92f9-e2fdefa6779f > >>> count = 1 > >>> nic: > >>> id = e062922f-c0ea-4f8a-beca-b86146dee622 > >>> deviceid = 0 > >>> gateway = 202.90.43.0 > >>> ipaddress = 202.90.43.1 > >>> isdefault = True > >>> macaddress = 06:ca:b4:00:00:20 > >>> netmask = 255.255.255.254 > >>> networkid = e044c442-48f7-4bae-8c5d-530423a249f7 > >>> virtualmachineid = 842054e6-c379-49fe-92f9-e2fdefa6779f > >>> (local) > > >>> > >>> Devender Kumar Singh > >> > >> > >
