On 16/06/17 22:26, Julien Gomes wrote:
> On 06/15/2017 06:00 AM, Nikolay Aleksandrov wrote:
>> On 15/06/17 14:44, Nikolay Aleksandrov wrote:
>>> On 15/06/17 14:33, Nikolay Aleksandrov wrote:
On 15/06/17 00:51, Julien Gomes wrote:
> Hi Nikolay,
>
> On 06/14/2017 05:04 AM, Nikolay
On 06/15/2017 06:00 AM, Nikolay Aleksandrov wrote:
> On 15/06/17 14:44, Nikolay Aleksandrov wrote:
>> On 15/06/17 14:33, Nikolay Aleksandrov wrote:
>>> On 15/06/17 00:51, Julien Gomes wrote:
Hi Nikolay,
On 06/14/2017 05:04 AM, Nikolay Aleksandrov wrote:
> This has been on
On 15/06/17 14:44, Nikolay Aleksandrov wrote:
> On 15/06/17 14:33, Nikolay Aleksandrov wrote:
>> On 15/06/17 00:51, Julien Gomes wrote:
>>> Hi Nikolay,
>>>
>>> On 06/14/2017 05:04 AM, Nikolay Aleksandrov wrote:
>>>
This has been on our todo list and I'm definitely interested in the
On 15/06/17 14:33, Nikolay Aleksandrov wrote:
> On 15/06/17 00:51, Julien Gomes wrote:
>> Hi Nikolay,
>>
>> On 06/14/2017 05:04 AM, Nikolay Aleksandrov wrote:
>>
>>> This has been on our todo list and I'm definitely interested in the
>>> implementation.
>>> A few things that need careful
On 15/06/17 00:51, Julien Gomes wrote:
> Hi Nikolay,
>
> On 06/14/2017 05:04 AM, Nikolay Aleksandrov wrote:
>
>> This has been on our todo list and I'm definitely interested in the
>> implementation.
>> A few things that need careful consideration from my POV. First are the
>> security
>>
Hi Nikolay,
On 06/14/2017 05:04 AM, Nikolay Aleksandrov wrote:
> This has been on our todo list and I'm definitely interested in the
> implementation.
> A few things that need careful consideration from my POV. First are the
> security
> implications - this sends rtnl multicast messages but
On 13/06/17 20:08, Julien Gomes wrote:
> Currently, all ipmr/ip6mr cache reports are sent through the
> mroute/mroute6 socket only.
> This forces the use of a single socket for mroute programming, cache
> reports and, regarding ipmr, IGMP messages without Router Alert option
> reception.
>
> The
