Overall... 7.2-1 and 1.3.1-5 Things are quiet here

[Jan Janowski]

It's been pretty quiet here..... Everything is working as expected....

The issue with new iPhone only burped once on 5Ghz, not 2ghz...

Since 7.2-1 no further DS FINDER issues with Abnormal Drive Status, that computer access doesn't see...

I guess next will be SRM update... Awaiting.... whatever is next! !

 

[Rusty]

Everything is working as expected

Ok people are not updating :P

 

[Jan Janowski]

I can only report how things are going here.... As a report to others....

 

[zombiephysicist]

1.3.1u5 still not connecting clients correctly. My Mac Pro sits maybe 10ft from my 6600ax and always connects around 650mbs on 5ghz2 radio instead of at 1300mbs on 5ghz1 radio. On my 2600ac and 1.2.5 it always connected correctly. Work around is to force the back haul connection to 5ghz 1 and back to 5ghz2, and that forces the Mac Pro client to catch the 1300mbs connection on 5ghz1. It will stay connected until it reboots or sleeps.

so the connection logic on the 6600ax/1.3.1u5 is borked. It should start trying to connect clients ~to radio on 5`ghz1 at 1300bps first and only move to other radio if there is a failure. Or better yet, let users select what radio they want their clients to connect to. This has been an issue in all 1.3.x versions.

 

[Jan Janowski]

My 2600, on 1.3.1-5, is not seeing this, 15' away, any device on 5ghz Wifi, will see 866.0 (2600's limit).. -3 & -4 did have crazy connect speeds at times (wasn't consistantly good or bad)... -5 fixed that on 2600...

Sorry to hear 6600 is still acting up... This morning Looked and see others with Synology Mesh still reporting strange stuff too... I have not had any issues with my homemade mesh... Without an issue, I've not read the posts about mesh by others recently..

I have Never have had an issue with Linksys E2000 in garage, as Wired Access point on the 2600...... With ANY 2600 Firmware... No Issues with switching over from 2600 to E2000 or visa versa! (Using iPhone 6, then 2020SE for me, 8+ and now 14+ for Wife.)..

Now we are using Static IP's on iPhones..... but I doubt that should cause an issue...
Not Using: VPN, VLAN, GUEST WIFI, ANY Port Forwarding.
AM Using: QuickConnect, DoH, Changed default ports, DHCP, Firewall, Threat Prevention (Which has also been relatively quiet, since -5)

 

[zombiephysicist]

My 2600, on 1.3.1-5, is not seeing this, 15' away, any device on 5ghz Wifi, will see 866.0 (2600's limit).. -3 & -4 did have crazy connect speeds at times (wasn't consistantly good or bad)... -5 fixed that on 2600...

Sorry to hear 6600 is still acting up... This morning Looked and see others with Synology Mesh still reporting strange stuff too... I have not had any issues with my homemade mesh... Without an issue, I've not read the posts about mesh by others recently..

I have Never have had an issue with Linksys E2000 in garage, as Wired Access point on the 2600...... With ANY 2600 Firmware... No Issues with switching over from 2600 to E2000 or visa versa! (Using iPhone 6, then 2020SE for me, 8+ and now 14+ for Wife.)..

Now we are using Static IP's on iPhones..... but I doubt that should cause an issue...
Not Using: VPN, VLAN, ANY Port Forwarding.
AM Using: QuickConnect, DoH, Changed default ports, DHCP, Firewall, Threat Prevention (Which has also been relatively quiet, since -5)

I am using another 6600ax as part of a 2 node mesh. It’s on another floor. Not sure, perhaps there is some interplay. But for that Mac Pro, the synology always assigns it to the wrong/slower channel. At the very least synology should let you choose a “preferred” radio/node connection per device. So that it tries to connect to your preferred connection first by default. But I think their own internal logic should also be fixed so it tries the faster connection radio first, befor dropping to slower radio channels. That alone would fix it as demonstrated by my work around of force switching the back channel that temporarily kicks the Mac Pro off channel 2 and sticks it to faster 5ghz1.

 

[Jan Janowski]

I’d say 9 times of 10 5Ghz WIFI is selected here, under multiple versions.
I have 2x 2600’s. Both at same version, and have had both online at one time or another. Both acted same way.

Now a neighbor has a 2600 at 1.2.5-6 I think. I set it up. They report no issues.
On next version they asked me to update theirs to latest 1.3.

Once next version works on one of my 2600, I’ll consider theirs too: no mesh, no VPN, TP running on a SSD: Ext USBV3 sata enclosure.

At present no issues on my 2x 2600 at 1.3.x or neighbors at 1.2.5-6
I’m on 200/20 Zito service
Neighbor is on Spectrum 350/25 I think.

 

[zombiephysicist]

I’d say 9 times of 10 5Ghz WIFI is selected here, under multiple versions.
I have 2x 2600’s. Both at same version, and have had both online at one time or another. Both acted same way.

Now a neighbor has a 2600 at 1.2.5-6 I think. I set it up. They report no issues.
On next version they asked me to update theirs to latest 1.3.

Once next version works on one of my 2600, I’ll consider theirs too: no mesh, no VPN, TP running on a SSD: Ext USBV3 sata enclosure.

At present no issues on my 2x 2600 at 1.3.x or neighbors at 1.2.5-6
I’m on 200/20 Zito service
Neighbor is on Spectrum 350/25 I think.

That is so interesting. I guess maybe part go the issue is I am using the 2 node mesh and youre not really using a mesh but your own extender setup. Because 10 out of 10 times mine will connect to 5GHz2 and wont go to 5GHz1 unless I force the switch by toggling the backhaul radio selection.

 

[Jan Janowski]

I guess then there is 6600 specific code and/or mesh code that needs to occur.