Aaron Conole writes:
> Aaron Conole writes:
>> Daniele Di Proietto writes:
>>> On 26/01/2017 12:35, "Ansis Atteka" wrote:
On 26 January 2017 at 21:24, Aaron Conole wrote:
Aaron Conole writes:
> Daniele Di Proietto writes:
>
>> On 26/01/2017 12:35, "Ansis Atteka" wrote:
>>>
>>>
>>>On 26 January 2017 at 21:24, Aaron Conole
>>> wrote:
>>>
>>>Daniele Di Proietto
Daniele Di Proietto writes:
> On 26/01/2017 12:35, "Ansis Atteka" wrote:
>>
>>
>>On 26 January 2017 at 21:24, Aaron Conole
>> wrote:
>>
>>Daniele Di Proietto writes:
>>
>>> On 25/01/2017 00:01, "Ansis
On 26 January 2017 at 04:03, Daniele Di Proietto
wrote:
>
>
>
>
>
> On 25/01/2017 00:01, "Ansis Atteka" wrote:
>
> >
> >
> >On Jan 25, 2017 4:22 AM, "Daniele Di Proietto"
> wrote:
> >
> >Current SELinux policy in RHEL and
On 26 January 2017 at 21:24, Aaron Conole wrote:
> Daniele Di Proietto writes:
>
> > On 25/01/2017 00:01, "Ansis Atteka" wrote:
> >
> >>On Jan 25, 2017 4:22 AM, "Daniele Di Proietto"
> wrote:
> >>
>
Daniele Di Proietto writes:
> On 25/01/2017 00:01, "Ansis Atteka" wrote:
>
>>On Jan 25, 2017 4:22 AM, "Daniele Di Proietto" wrote:
>>
>>Current SELinux policy in RHEL and Fedora doesn't allow the creation of
>>TAP devices.
On 25/01/2017 00:01, "Ansis Atteka" wrote:
>
>
>On Jan 25, 2017 4:22 AM, "Daniele Di Proietto" wrote:
>
>Current SELinux policy in RHEL and Fedora doesn't allow the creation of
>TAP devices.
>
>A tap device is used by dpif-netdev to create
On Jan 25, 2017 4:22 AM, "Daniele Di Proietto"
wrote:
Current SELinux policy in RHEL and Fedora doesn't allow the creation of
TAP devices.
A tap device is used by dpif-netdev to create internal devices.
Without this patch, adding any bridge backed by the userspace
Current SELinux policy in RHEL and Fedora doesn't allow the creation of
TAP devices.
A tap device is used by dpif-netdev to create internal devices.
Without this patch, adding any bridge backed by the userspace datapath
would fail.
This doesn't mean that we can run Open vSwitch with DPDK under