On 2016-09-08 04:03, Toshiaki Makita wrote:
> On 2016/09/08 3:22, Michal Soltys wrote:
> ...
>> 4.7.2
>> git describe on that commit suggests it's been available since 4.6.x
>>
>> What I did in details:
>>
>> ip li add name port1b type veth peer name port1e
>> ip li add br0 type bridge
>> ip li s
On 2016/09/08 3:22, Michal Soltys wrote:
...
> 4.7.2
> git describe on that commit suggests it's been available since 4.6.x
>
> What I did in details:
>
> ip li add name port1b type veth peer name port1e
> ip li add br0 type bridge
> ip li set dev br0 type bridge vlan_default_pvid 0
> ip li set d
On 2016-09-07 02:44, Toshiaki Makita wrote:
> On 2016/09/07 6:59, Michal Soltys wrote:
>> Consider following scenario:
>>
>> - create vlan aware bridge (say br0)
>> - setup br0's vlans, e.g.
>>
>> bridge vlan add dev br0 vid 10 self
>>
>> This will add necessary fdb entries directing appropriate
On 2016/09/07 6:59, Michal Soltys wrote:
> Consider following scenario:
>
> - create vlan aware bridge (say br0)
> - setup br0's vlans, e.g.
>
> bridge vlan add dev br0 vid 10 self
>
> This will add necessary fdb entries directing appropriate traffic to the
> bridge itself.
>
> - create appropr
Consider following scenario:
- create vlan aware bridge (say br0)
- setup br0's vlans, e.g.
bridge vlan add dev br0 vid 10 self
This will add necessary fdb entries directing appropriate traffic to the
bridge itself.
- create appropriate vlan interfaces on top of it, for example:
ip li add link
