Just to note; I upgraded an MX75 from 17.6 to this release and it required a hard power cycle to bring up the WAN port. I will try some other devices next week.
So far no issues on the couple of MX67's I have upgraded.
Will try a couple of more models a little later. - Unfortunately I dont have a MX75 or MX85 in the lab ...
MX250 - seems fine (it was offline for a little while longer then I thought, but .. all good)
MX75 upgraded from 17.6 without issue here
Same here, upgraded fine.
Lets see if this fixes the wan port going down/up.
Mx75 port 12 does not indicate poe status(anyone can confirm this?)
@ww my MX75 also had the WAN port (port 2 in my case) go down and I had never had that issue with 17.6. The connection is direct into the ISP's ONT...
Is this the EEE 802.3az issue ? - If it is, didnt know it was also present on MX67 and 68 ... 😕 - But good thing if it is now fixed.
I'm guessing so, but the release notes are a bit vague on this one. Hopefully someone can confirm soon.
I see that a 16.16.2 has showed up , with the same vague formulation on this fix.
It seems that this "phrasing" is the fix for the EEE problem. I had it confirmed in a mail from support.
MX67C / MX84 / MX85 upgrade without any hickups.
Hello, could I ask if you had any issues with the WAN port on MX85 flapping before you upgraded the firmware. I have an issue with WAN port to ISP kit flapping and causing user interupptions. Hoping this upgrade fixes. Cheers!
Any insights on these two items? Stable release candidate with significantly reduced VPN throughput? After all the 16.16 issues we are going to need some more details!
MX75 updated without problems (and no power cycle needed), MX64s are fine. Only my own pair of MX68 didn't update because they state that the dashboard is not reachable on TCP/443 which is obviously not true as I run 16.16 and have MR28 running inside the network.
Connection to Google file stream slowed significantly after upgrading to 17.7, had to roll back.
MX 68 Advanced Security
Upgraded MX250 over the weekend. Extreme slowness when trying to negotiate an initial connection to any HTTP or HTTPs
Hi DavidTX, did you upgrade to 17.7 or 16.16.2 on your MX250? How is the performance? We have MX450 and having lots of performance issues with MX16.16. We are hesitant to upgrade till school testing is over.
My Infra manager mistakenly went to 17.7 on our production MX250's - big mistake. While things appear functional, outbound web traffic was quite a bit slower for me, sometimes receiving 'this page cannot be displayed'
why 17.7 fw upgrades page reports: Warning - August 31, 2022🙄
I wish there would be more detailed information for every warning/critical label.
The bizarre thing is that there isn't a single version that isn't on a warning or critical...
I am now seeing MX16.16.3 (latest patch, Released on June 8th) and MX17.8 (Looks like it was released on June 9th) under Stable Release Candidate instead of MX17.7 and Warning options only to update to MX16.16.3 or MX17.8. I hope the MX17.8 update has resolved the issues in MX16.16 and MX17.7.