Re: loss of connectivity after enabling vlan_filtering

2019-06-30 Thread vtolkm
On 30/06/2019 03:13, vto...@gmail.com wrote: > On 30/06/2019 02:37, vto...@gmail.com wrote: >> On 30/06/2019 01:23, vto...@gmail.com wrote: >>> On 30/06/2019 01:11, Andrew Lunn wrote: On Sun, Jun 30, 2019 at 01:04:50AM +0200, vto...@googlemail.com wrote: > On 30/06/2019 00:49, Andrew Lun

Re: loss of connectivity after enabling vlan_filtering

2019-06-29 Thread vtolkm
On 30/06/2019 02:37, vto...@gmail.com wrote: > On 30/06/2019 01:23, vto...@gmail.com wrote: >> On 30/06/2019 01:11, Andrew Lunn wrote: >>> On Sun, Jun 30, 2019 at 01:04:50AM +0200, vto...@googlemail.com wrote: On 30/06/2019 00:49, Andrew Lunn wrote: > On Sun, Jun 30, 2019 at 12:01:38AM +

Re: loss of connectivity after enabling vlan_filtering

2019-06-29 Thread vtolkm
On 30/06/2019 01:23, vto...@gmail.com wrote: > On 30/06/2019 01:11, Andrew Lunn wrote: >> On Sun, Jun 30, 2019 at 01:04:50AM +0200, vto...@googlemail.com wrote: >>> On 30/06/2019 00:49, Andrew Lunn wrote: On Sun, Jun 30, 2019 at 12:01:38AM +0200, vto...@googlemail.com wrote: > * DSA MV88E6

Re: loss of connectivity after enabling vlan_filtering

2019-06-29 Thread vtolkm
On 30/06/2019 01:11, Andrew Lunn wrote: > On Sun, Jun 30, 2019 at 01:04:50AM +0200, vto...@googlemail.com wrote: >> On 30/06/2019 00:49, Andrew Lunn wrote: >>> On Sun, Jun 30, 2019 at 12:01:38AM +0200, vto...@googlemail.com wrote: * DSA MV88E6060 * iproute2 v.5.0.0-2.0 * OpenWRT 19.0

Re: loss of connectivity after enabling vlan_filtering

2019-06-29 Thread vtolkm
On 30/06/2019 00:49, Andrew Lunn wrote: > On Sun, Jun 30, 2019 at 12:01:38AM +0200, vto...@googlemail.com wrote: >> * DSA MV88E6060 >> * iproute2 v.5.0.0-2.0 >> * OpenWRT 19.07 with kernel 4.14.131 armv7l > The mv88e6060 driver is very simple. It has no support for VLANs. It > does not even have

loss of connectivity after enabling vlan_filtering

2019-06-29 Thread vtolkm
* DSA MV88E6060 * iproute2 v.5.0.0-2.0 * OpenWRT 19.07 with kernel 4.14.131 armv7l ___ after # bridge v a dev {bridge} self vid {n} untagged pvid or with the device enslaved in the br # bridge v a dev {device} vid {n} untagged pvid I am hitting a roadblock when executing # sysctl -w /sys/