Larry All-Knowing Sage ✭✭✭✭
Reactions
Comments
-
The March 2024 firmware releases (for Gen 6.5, Gen 7, and Gen 7.1) contain the fix for this problem.
-
The March 2024 firmware releases (for Gen 6.5, Gen 7, and Gen 7.1) contain the fix for this problem.
-
The March 2024 firmware releases (for Gen 6.5, Gen 7, and Gen 7.1) contain the fix for this problem.
-
-
You would want to take advantage of the NSM / SonicOS API. From the NSM Administrator Guide: A RESTful (Representational State Transfer) API (application programming interface) has been developed for Network Security Manager. This allows you to either script or build custom user interface elements to manage a unit or…
-
@CF_ADMIN The reps here have said the first MR for 7.1.1 will be in "second half of March," and that statement has been made with the caveat that QA testing could extend it. Could it be released in April? Yes, that is a possibility. So if you decide to wait, implement the workaround solution that was provided. (Note:…
-
@CF_ADMIN - You were already ON a Maintenance Release for your 7.0 device as you stated at the outset. What's upsetting - at least to me - is that you missed three known updates - over a one year span. By all accounts, you should have gone to the General Release of that SAME software (Version 7.0 - 5095 to 5145). So I'm…
-
@Bcon08 - As I stated in mid-January 2024, shortly after the initial release: I am not going to install 7.1 on my office (test) firewall until after the third update to 7.1 is released. It was nearly a year late in coming out of the gate and looks like insufficient attention was paid to all the parts and pieces. I have…
-
Two cents from someone who has no skin your game. You never stated why you upgraded your device to 7.1 (never mind there was a more recent 7.0 update you could have deployed). However, you were quickly given a workaround to your problem when you reported it. Kudos to SonicWall for acknowledging the problem. For reasons…
-
@Danny - unfortunately, you MUST use the serial number of any AP at that site to open a Support case. Sad, stupid, but true... Good luck!
-
@MichaelCrean that was an unexpected, but pretty thirsty response. In 2020 and 2021 I devoted incalculable hours to try to come to grips with SonicWall's NSM offering. The expenditure of those countless hours soured me on the product altogether. Finally, in 2024, NSM is approaching a more solid offering and maybe by 2026…
-
@MustafaA - Your Capture Labs site shows IPs 94.156.64.239 and 94.156.67.57 as Bulgaria (which matches the site's System Log). However, AbuseIPDB shows them as Limenet, which is based in The Netherlands. Also 5.181.170.244 SW identifies as as Russia versus other parties show France. What am I to make of these discrepancies?
-
Follow-up. It took 25 minutes total before a CSR picked up the call. I guess that's OK (except for the music). Further testing this morning using Chrome's Developer Tools showed that a CSS file common to the sites was taking an incredibly long time to load. They came from use.fontsawesome.com, which the IP address shows as…
-
@Arkwright - I haven't used NSM in more than two years. I can only glean "what it's like" from the technical documentation. And while it says there is the ability to send an email for alerts, I can't find how or where that email address should be entered. It could be my lack of direct reference to how NSM is currently…
-
Take a look at the NSM Adminitrator Guide, under the section System Events, then Alerts and Notifications SonicWall requires you to have a Twilio (third-party) account to send SMS messages (not emails). You can find my outrage at this approach when it first appear in WNM a few years ago:…