MarkD Cybersecurity Overlord ✭✭✭
Reactions
Comments
-
I saw that "X1 IP" is defined as 192.168.1.30 looks like your ISP router is also doing NAT instead of having the X1 with a non RFC1918 address, you will also have to create the apporpriate NAT rules on the ISP router.
-
If these services use different WAN interfaces, create route and NAT policies to define the egress interface and NAT address
-
Has the DMS company added routing back you your subnets?
-
You dont say what your X1 Wan interface is connected to. This is my setup usign 2 internal subnets with routes on the NSv to each subnet via the Azure gateway 10.181.1,209 X1 default gateway is the Azure gateway with a Pubic IP attatched. This natted by the gateway at 10.181.1.225 and presented as the public IP routelan…
-
The Migration tool :- Use the latest release v7.0.1-5 when migrating from Gen6 Gen5 migration is not supported so unfortunately not. If possible take out the ipsec config, unmask the PSK and setup the same as the 205. On a version 7.0.1-5051-R2624 we have the following wireless firmware…
-
I believe this function is available from with NSM management,
-
If its a case of these devices communicaing with each other and its the event logged to the FW you dont want to see (its a m'cast to all devices on the subnet so seen by the firewall) You should be able to click the X in the event log and the FW will no longer log this message.
-
Performance is dependant on many factors, Threat Prevention/GatewayAV/Anti-Spyware/IPS Full DPI inspection will affect overall throughput. Sorry but there is no fixed answer.
-
I would ask why the Ubuntu is generating AH packets to a multicatst address, not why the firewall is dropping them....
-
NSv uses SonicOSX and has more granular Action Profiles Creating a specific Security Action rule, you can add both TCP and UDP timeout as well as specific SIP values values to the Miscellaneous tab. Hope this helps
-
Ubuntu Nginx one for the Ubuntu Community
-
Using external Antenna's can increase the output signal level, however that isnt always best for an environment. Ebook-Wireless-Best-Practices.pdf (sonicwallsecurity.co.uk)
-
If this is the only option, hesitantly - I would suggest adding the ports TCP 5000, 5001, 6690 as service-objects and then running throught the public server wizard and selecting Web Server and then adding the new service objects for 5000,5001 and 6690. After this, you should add an inbound access rule allowing ONLY the…
-
I would suggest explore using VPN to secure communication and not externally exposing your NAS, it will get hacked..
-
And the ( infected host address object) device is NOT directly accessible via Layer 2











