Final 6.2.1 update causing LAN instability/sluggishness

Thanks both for reply.
We may still need your help because so far all works ok here.
I run a RN316 at home myself and no issue son 6.2.1, I run plex , but not bond, I don't use IPv6 either.

For looking at 1.2.6 v 1.27 connmand, that would be a bit more involved than you might think and not guaranteed solution because the issue is not widespread but I will ask dev to have a look.

_Frantic_ & dsnpevl can you send in your full system logs using info here http://kb.netgear.com/app/answers/detail/a_id/21543 with as much detail about your network as possible, router / switch models in use.
Would you both be ok to allow Netgear remote access to your systems at some pint if needed.

OptimusPrime wrote:
_Frantic_ & dsnpevl can you send in your full system logs using info here http://kb.netgear.com/app/answers/detail/a_id/21543 with as much detail about your network as possible, router / switch models in use.

Info and logs are in the mail, as requested.

OptimusPrime wrote:
Would you both be ok to allow Netgear remote access to your systems at some pint if needed.

Don't drink beer myself :) I prefer wine.
OK with allowing remote access, but I'm not going to revert back to the faulty state, as I don't want any more down time on my website.

How's this for a shot in the dark? Correct me if my assumptions are wrong, because this UPnP is not my field of expertise.
- RN is using UPnP to connect to discovery server
- Router blocks UPnP
- connman 1.27-netgear1 package doesn't like this and ends up in an endless loop sending IP packages.

@_frantic_, do you have UPnP blocking on your router?

@OptimusPrime, were there changes made to UPnP handling between 1.26 and 1.27?

Not sure if this is related at all, but in regard to Wifi (direct):
[quote="Andrei Laperie @ tizen.org":2zlfzqwg]Please note that WiFi P2P is very sensitive to the wireless hardware/firmware. The combination that worked for us was Intel WP2/latest firmware/3.17 kernel. It is quite likely that other configurations might require extra work to enable P2P. [/quote:2zlfzqwg]
Could this be related to WLAN firmware / hardware in the router?

I think so far looks like fritzbox + ipv6 + new connman might be the root cause I will check with dev if we can reproduce somehow or get detailed info what was updated in 1.27
We have 1 similar internal user with same and again it is fritzbox + ipv6 and a RN312 on 6.1.2.

No UPnP is not used for connection to discovery server.
A packet trace would have been nice when it was flooding but we won't expect you to kill webserver again :-). We will see can we get more from an internal tester.

And my typo's are legendary at this point (or pint) :-)
For now I just need to get with dev team on this and see if we can solve asap.

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

OK. That seems to be the common denominator. But then my friend with RN312 also has same make and model Fritz!Box without upgrade issues. And _frantic_ has a different model and does have upgrade issues. Please note that even within one make/model you can have different versions (v1, v2), a bit like GS108 also has. The 7360 I borrowed had extension v2 versus mine having no extenstion, just 7360 on the information sticker on the bottom. Still they have the same article number 2000 2536, but when I saved the setting from my router and tried to put them on the v2 version, it was not accepted as a native settings file.

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

I have the same error on my failing RN314 on the front display: "Cannot connect discovery server" and I have no apps installed on either system. They are configured identical, but one upgrade fine and the other has issues...very strange.

scravatt wrote:
They are configured identical, but one upgrade fine and the other has issues...very strange.

The RNs are indentical you say, but what about the routers at the different premises?

Do you have AVM Fritz!box at one location and something else in the other location?

Location 1: FRITZ!Box 7240 with UPnP off (default setting), the box is connected to a cable modem, the modem is set to "bridge-mode", IPv4 (from ISP) + IPv6 (via tunnel provider SixXS)
Location 2: FRITZ!Box 6360 cable with UPnP off, IPv4 (ISP) + IPv6 (SixXS)

I took the RN312 away from location 1 (kind of weekend house) to location 2, my home.
I might assist, allow remote access etc. But I will be out for holidays for some days from tomorrow on.

Identical equipment at both places ... Motorola cable modem/gateway

@_frantic_ We are still guessing here, but the problem might only be triggered by certain models Fritz!box in combination with RN and IPv6. So moving the RN from the troublesome location to your home, means you will be using a different router and the issue might not occur any more.

The location 2 with 6360 is the site where there are problems?
Did you already test RN from location 2 at the location 1 with 7240?

Enjoy your holidays!

@dsnpevl: yes, same problem on both locations (http://www.readynas.com/forum/viewtopic.php?f=65&t=79118&start=15#p445035).

I also have a RN104 here at home. I might try the update on that one too... or shall I wait...
Of course its an ARM box, it might behave differently.