>>
>>> -Original Message-
>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>> Sent: Wednesday, 19 February 2014 8:33 PM
>>> To: dev; Kishan Kavala
>>> Subject: Re: cidrs in acls
>>>
>>> Kishan,
>>>
>>>
: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Wednesday, 19 February 2014 8:33 PM
>> To: dev; Kishan Kavala
>> Subject: Re: cidrs in acls
>>
>> Kishan,
>>
>> Can you have a look at the branch acl-item-cidrs. I made some code to
>> handle the c
grade path to move existing cidrs to new
network_acl_item_cidr table
Regards,
kishan
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, 19 February 2014 8:33 PM
> To: dev; Kishan Kavala
> Subject: Re: cidrs in acls
>
> Kishan
Kishan,
Can you have a look at the branch acl-item-cidrs. I made some code to
handle the cidrs from a separate table. I hardly think this can be
enough and would like to create a checklist on what I need to do next.
(item one is use the new transaction model;)
thanks,
Daan
On Fri, Jan 17, 2014
That was what I thought as well. What was the retionale to join them
into one field?
On Fri, Jan 17, 2014 at 8:32 AM, Kishan Kavala wrote:
> Daan,
> Similar to firewall_rules_cidrs, separate table can be used to store acl
> cidrs. Maybe in network_acl_item_cidrs.
>
> Regards,
> kishan
>
>> ---
Daan,
Similar to firewall_rules_cidrs, separate table can be used to store acl
cidrs. Maybe in network_acl_item_cidrs.
Regards,
kishan
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Friday, 17 January 2014 1:05 AM
> To: Kishan Kavala
> Cc: dev
> Su
