Arkwright Community Legend ✭✭✭✭✭
Reactions
Comments
-
Did you hear back @EnaBev ?
-
We trialled a few at a customer site and we had random reboots and then some bizarre issue with the switch continually uploading to chicken-sonicwall.sonicwall.com [I'm not making this up, there were other animals as well, eg raccoon]. Sonicwall switches don't properly support SNMP at this time. I was told in late 2020…
-
Any ideas on this @EnaBev?
-
You might need to forward ports to your Mitel [note that "Mitel" is a company that makes about 94 different phone systems, so you should probably be more specific] but you ONLY want to allow SIP from your SIP provider. Do not leave SIP open from the entire internet to your phone system. I suggest you don't attempt to…
-
Yes, by "unnumbered" I mean a tunnel-mode VPN policy with no VTI bound to it. My worry is that in 6 months when I have some obscure problem, support are going to say "Y U NO ADD VIRTUAL TUNNEL INTERFACE, TICKET CLOSED. HUR HUR HUR"
-
Put an AP on the LAN side of the Sonicwall, then the Sonicwall is in between the wireless users and the internet, and wireless user traffic will pass through the Sonicwall.
-
Found in my notes that i used (config-license)# register-code XXXXXX to do this from the CLI, not safemode. Sorry for the noise!
-
I could have sworn I did this with a TZ370 that I couldn't get registered. But if they've removed this ability with later versions, then that explains that.
-
You can update firmware in safe mode if it isn't registered.
-
Observe notes on there about how firewall harvests DNS responses. If you make sure clients are using same DNS servers as the Sonicwall itself then it is much more likely that both firewall and client will agree what IP a hostname resolves to, and that the rule will then work as expected. This is really more relevant with…
-
Truvision DVR Don't allow access from anywhere on internet to an NVR. Enable HTTPS on web interface of NVR and forward that port instead. If you can't enable HTTPS on this device then only allow access for VPN client users instead.
-
It depends what you want to achieve. If you plug your Sonicwall WAN into the LAN port of your router, the LAN side of the Sonicwall will be a completely separate network to the wireless side of your router. By default you will be able to reach your wireless devices from your Sonicwall LAN side, but the wireless devices…
-
There needs to be an access rule that allows port 22 [or whatever port you're using] and have "Management" ticked. This is usually created automatically by enabling the management service on the interface.
-
Configure a static route on 120.0.0.200 to reach 119.0.0.0 via Sonicwall X2 That way a) it doesn't have to go out to the internet and back in again to reach that network b) no spoof problem any more.
-
What's the purpose of the 10.5.1 network here? Surely it would be easier just to give the firewall the IP 75.51.206.55 and be done with it.