[PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch
Enrico Mioso
mrkiko.rs at gmail.com
Thu Dec 1 05:33:52 PST 2022
My 2 cents here.
My (very possibly wrong) impression, this seems the same way of thinking followed in commit db19efee951231b38573cffaadb15fad8f9c058d .
I can understand this is a strong way to convince people to care about specific issues. Still, this seems a bit rude to me.
On the other side, I can understand this problem can have pretty much security consequences, so both point of views make sense to me.
On Thu, Dec 01, 2022 at 12:52:29PM +0100, Petr Štetiar wrote:
> Uwe Kleine-König <uwe+openwrt at kleine-koenig.org> [2022-12-01 12:17:31]:
>
> Hi Uwe,
>
> > On 12/1/22 10:52, Petr Štetiar wrote:
> > > Several users have reported, that devices using mv88e6176 switch are
> > > seriously broken, basically turning that switch into a hub. Until fixed
> > > those devices should be disabled.
> >
> > I wonder if disabling is a sane thing to do here.
>
> IMO it's a serious issue, so we've just following sane options:
>
> * fix it
> * remove support for those devices and make everyone aware
>
> > People running 22.03.2 won't be able to update
>
> Indeed, bummer, we're sorry about that, but the idea here is to make everyone
> aware and prevent more users from upgrading those devices to latest 22.03
> release.
>
> > Isn't that worse than a slow network configuration?
>
> Quoting from https://github.com/openwrt/openwrt/issues/10997
>
> "After upgrade from 21.02 eth switch start to forward all incoming traffic to
> all ports. I can see ALL traffic using tcpdump on computer connected to one
> port and all eth traffic leds are blinking always simultaneously. Same
> configuration on 21.02 works ok - VLANs and individual traffic are isolated."
>
> Cheers,
>
> Petr
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
More information about the openwrt-devel
mailing list