On Thu, May 19, 2016 at 3:24 PM, Jan Scheurich wrote:
> Am 19.05.2016 um 22:47 schrieb pravin shelar:
>>
>> On Wed, May 18, 2016 at 9:41 AM, Jan Scheurich
>> wrote:
>> I agree current tunneling port check is bit arbitrary. It was designed to
>> handle most common tunneling setup. But I do not thi
Am 19.05.2016 um 22:47 schrieb pravin shelar:
On Wed, May 18, 2016 at 9:41 AM, Jan Scheurich wrote:
I agree current tunneling port check is bit arbitrary. It was designed
to handle most common tunneling setup. But I do not think we can allow
tunneling on any type of port. For example I doubt t
On Wed, May 18, 2016 at 9:41 AM, Jan Scheurich wrote:
> This patch enables user-space tunnels to work over internal (tap) ports other
> than
> the bridge LOCAL port. This feature can e.g. be used to implement tunnels over
> different VLANs on the same physical port by adding multiple internal por
This patch enables user-space tunnels to work over internal (tap) ports other
than
the bridge LOCAL port. This feature can e.g. be used to implement tunnels over
different VLANs on the same physical port by adding multiple internal ports
to the physical bridge as VLAN access ports:
ovs-vsctl add-
