Hi, Oliver,
On 02.04.2018 18:28, Oliver Hartkopp wrote:
> Hi Kirill, Marc,
>
> I checked the code once more and added some debug output to the other parts
> in CAN notifier code.
>
> In fact the code pointed to by both of you seems to be obsolete as I only
> wanted to be 'really sure' that no
Hi Kirill, Marc,
I checked the code once more and added some debug output to the other
parts in CAN notifier code.
In fact the code pointed to by both of you seems to be obsolete as I
only wanted to be 'really sure' that no leftovers of the CAN filters at
module unloading.
Yes, this one
On 06.03.2018 13:26, Oliver Hartkopp wrote:
> - DaveM
>
> Hi Kirill,
>
> On 03/05/2018 04:22 PM, Kirill Tkhai wrote:
>
>> Thanks for the explanation, and module unloading should be nice. Just to
>> clarify,
>> I worry not about rules, but about netdevices.
>>
>> unshare -n ip link add
- DaveM
Hi Kirill,
On 03/05/2018 04:22 PM, Kirill Tkhai wrote:
> Thanks for the explanation, and module unloading should be nice. Just to
> clarify,
> I worry not about rules, but about netdevices.
>
> unshare -n ip link add type vcan
>
> This command creates net ns, adds vcan there
Hi, Oliver,
thanks for your reply.
On 05.03.2018 16:59, Oliver Hartkopp wrote:
> Hi Kirill,
>
> On 03/01/2018 04:53 PM, Kirill Tkhai wrote:
>
>> I'm converting/reviewing pernet_operations either they allow several net
>> namespaces
>> to be created/destroyed in parallel or not. Please, see
Hi Kirill,
On 03/01/2018 04:53 PM, Kirill Tkhai wrote:
> I'm converting/reviewing pernet_operations either they allow several net
> namespaces
> to be created/destroyed in parallel or not. Please, see the details in my
> recent
> patches in net-next.git, if your are interested.
Thanks for
