Final 6.2.1 update causing LAN instability/sluggishness

Only have experience with RN516, so I wouldn't know about ARM versions. But at this point I would wait and see what Netgear comes back with. And avoid running the risk of having both servers giving you problems. "If it ain't broken, don't fix it". At least not till more is know what exactly is the problem.

Forum members have narrowed down the problem a lot already and given Netgear plenty of information to start investigating with and are offering support. Should be enough to find and fix the problem, I would say.

OptimusPrime wrote:
I think so far looks like fritzbox + ipv6 + new connman might be the root cause

@Optimus, you're talking like dsnpevl and _frantic_ are the only two users affected.

I'm running a DrayTek 2130Vn (not FritzBox) for my router with an RN314. UPnP is on. IPv4/IPv6 are both in operation. The RN314 has a static IP (v4) address.

I have a Motorola SB6580 gateway modem... Issues with RN314 6.2.1 locking it up... So its various types of routers/gateways. Not 1 specific brand

Like I mentioned earlier: I would not be supprised if you might find that this only occurs for a certain version of some chipset used in certain routers.

The specialized chipsets that router vendors use are likely to come from one of only a few chip manufacturers. So even in different brands of routers, IP traffic might go through the same brand and type of chipset. This is very similar what you find in computers. Two common chipset and CPU brands there are Intel and AMD. These chipsets show up in many brands of computers, as you may know.

So it's up to Netgear to figger out if a common chipset is used in the mentioned makes and models.

But starting with a spefic model, that is known to give problems and you have access to, would also be the approach I would take. The fix that is found for RN connman, in combination that specific router would most likely apply to all makes and models with the same chipset. But I'm making a lot of assumptions here. Let's wait what Netgear comes back with. Meanwhile, use this forum to make sure they don't forget about your brand and model of router, if it is giving issues like the one described in this thread.

So far I have seen these mentioned in this thread as part of a troublesome setup:
DrayTek 2130Vn
Motorola SB6580
AVM Fritz!Box 7360
AVM Fritz!Box 7240
AVM Fritz!Box 6360 cable

If there are other routers with the same issue, I suggest you join this thread to let Netgear know.

I agree that a list of routers could be helpful for them.

I don't think this is likely to have much to do with the chipset. More likely it relates to the IP software stack in the router.

I too am having this issue!

Issue present with

BT HomeHub 4 & TP-LINK TD-8817 - both crash moments after my RN102 (6.21 Final).

UPnP switched off on both routers.

Connman version is 1.27

I can still access both the webui and SSH post the router crashes. All Ethernet traffic is routed through a SamKnows box before router.

I am happy to allow remote access to the network for fault testing - if the router can stay up long enough!

Just wondering - is there a way to disable IPv6 in the router? If so, did you try playing with that setting?

StephenB wrote:
I agree that a list of routers could be helpful for them. I don't think this is likely to have much to do with the chipset. More likely it relates to the IP software stack in the router.

Don't IP protocol stacks run inside chipsets?

StephenB wrote:
Just wondering - is there a way to disable IPv6 in the router? If so, did you try playing with that setting?

There is a way to switch off IPv6 in mine (Fritz!box 7360) and I would expect in most routers. Didn't think of that during testing though. And not going to try it any more now that I finally have a workaround in place and my website is online again. To be honest, I'm quite scared to do a reboot in fear of the issue reappearing.

dsnpevl wrote:
StephenB wrote: I agree that a list of routers could be helpful for them. I don't think this is likely to have much to do with the chipset. More likely it relates to the IP software stack in the router. Don't IP protocol stacks run inside chipsets?

Software can and is ported to more than one platform. Platforms can often run more than one software stack.

So a software bug can affect multiple routers using different hardware chipset, and there might be other routers using the same chipset that have no problem at all.