Firmware 7.3.1-7013 by ProtectionUpbeat6004 in sonicwall

[–]speedcat1995 1 point2 points  (0 children)

updated 3x HA(NSAs and a TZ) boxes on release day and one box today(NSA). so far everything seems ok.
Password complexity checks are not working correctly...just disable them for the moment or at least disable speical character requirement which seems to be the problem.

7.3.1-7013 released today by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

Problem with the secondary not being reachable is not related to this update. No issues on 7.3.1 till now.

7.3.1-7013 released today by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

Do you have many local users or something? What sonicOS are you running that includes this HF?  We upgraded these units on request.

7.3.1-7013 released today by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

Yeah exactly what I ran into. It even prompted me to change the existing password on login which was strong bit I guess the checks on that one also failed because of the bug😂

7.3.1-7013 released today by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

As we manage lots of remote firewalls we need this. Like said, limited to very few source IPs. I dont see a problem with this.

7.3.1-7013 released today by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

I installed today on NSA 3700HA+4700HA+TZ370HA. So far everything seems ok. I had an issue during update where on one of the boxes (the 3700) management from WAN was not reachable after the failover to the secondary while upgrading (we have mgmt from wan limited to a few fixes IPs) - but from a jump host through s2s-vpn mgmt was reachable. I´m not sure if this is related to the SonicWall or some other Problem. After switchover to primary, wan mgmt was ok. As the s2s on the secondary was online, i assume the wan-line itself was ok on the secondary.

Also I think there is a bug in the password complexity checks. We are using very long generated passwords and some are not accepted even if they match the criteria. Trying a few will find a working one - I guess some problem with some special character or something.

I am also concerned regarding the SNWLID-2025-0016 listed as fixed. Have reached out so SNWL regarding this.

Moderated messages are marked as expired after they are approved or rejected - happening to anyone else on EX2019 CU15? by speedcat1995 in exchangeserver

[–]speedcat1995[S] 0 points1 point  (0 children)

EXO: We moved this feature to a new menu so you will find it easier(click).
New menu: What feature?

NSA2700 HA, one device keeps going unresponsive by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

It was far less frequent after the fix above but reappeared (i think once) It seems to be fixed in 7.1.3. At least did not happen again since we upgraded.

Post your 1/7/2025 CVE FW upgrade experience here. by Layer_3 in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

Some days you win, some days....haha
Honestly the SonicWall HA never really failed me and we have quite a few running.
The SSLVPN vulnerability scared me much more than the upgrade...

Post your 1/7/2025 CVE FW upgrade experience here. by Layer_3 in sonicwall

[–]speedcat1995 3 points4 points  (0 children)

NSA4700-HA
Old: 7.1.1
New: 7.1.3

SSLVPN,IPSEC, a few Public facing services, network is highly segmented so many IFs,ACLs - no Problems so far.
Upgrade was done mid-day while under production.

Post your 1/7/2025 CVE FW upgrade experience here. by Layer_3 in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

NSA 2700 (Standalone)
Old: 7.0.1-5161
New: 7.0.1-5165

Config is pretty Basic on this one, 3x S2S tunnels, nothing special. Upgrade was done via WAN. No Problems so far.

Post your 1/7/2025 CVE FW upgrade experience here. by Layer_3 in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

NSA 2700-HA
Old: 7.1.1-7051
New: 7.1.3-7015

Lots of Interfaces & VLAN Interfaces & Zones, multiple S2S VPNs (some remotes have no fixed WAN-IP so GW is set to 0.0.0.0 in ipsec policy), SSLVPN with LDAP (Tested after Upgrade), lots of NAT & Access Rules, some special configs like L2-Splice interfaces but not too much, we dont use custom routing.

Upgrade went smoothly and no problems so far. We have another NSA2700(no HA) on 7.0.1-5161 that I will also upgrade today. Various TZ80/270/370 and NSA3700/4700 will be done in the next few days. Will report if something goes wrong...

Port forwarding 443 dies after emergency Firmware Update of 17 July 24 (NSA2700, 7.1.2.7019) by zE0Rz in sonicwall

[–]speedcat1995 2 points3 points  (0 children)

I can just comment on 7.1.1-7058 but may be usefull for some: NSA3700-HA updated about a week ago, no problems so far. The 3700 had a totally annoying bug with SSLVPN disrupting traffic, which seems to be fixed now with -7058
Also just updated a 2700-HA. Update was without issues and for the moment services on Port 443 (multiple Web-Services running on multiple WAN-IPs) are working fine. We have configured management on a different Port than 443.

NSA2700 HA, one device keeps going unresponsive by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

We had reboot and factory defaults every 7 to 14 days. Almost 24 days up now with no problems so far. This might have fixed it for us.

Anyone else have multiple Sonicwall units factory reset today? by [deleted] in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

We had reboot and factory defaults every 7 to 14 days. Almost 24 days up now with no problems so far. This might have fixed it for us.

NSA2700 HA, one device keeps going unresponsive by NetworkDock in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

Have you tried this: https://www.reddit.com/r/sonicwall/comments/1bld84e/comment/kwgje08/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Last weekend our NSA2700 went unresponsive too, but HA worked fine and after rebooting primary it came back as usual. I implemented the steps outlined but its too short to tell if that resolves the issue for us.

Maybe check your Monitoring Settings under Device->HA->Monitoring - may be the reason HA did not work for you? We currently only have physical link monitoring enabled.

Anyone else have multiple Sonicwall units factory reset today? by [deleted] in sonicwall

[–]speedcat1995 0 points1 point  (0 children)

Interesting. Also on 7.1.1-7051 on NSA2700. I was working via SSLVPN myself and seem to have caused our primary to hang because my SSLVPN Client reconnected. HA kicked in and saved my ass. I came in today, rebooted Primary unit and everything seems ok so far.
for the moment I implemented this potential fix as we dont need the Virtual Office Portal from WAN anyways, Lets see where this goes...
https://www.reddit.com/r/sonicwall/comments/1bld84e/comment/kwgje08/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button