Arkwright Community Legend ✭✭✭✭✭
Reactions
Comments
-
DurableDNS is another one.
-
Everything on the internet will have a source MAC address of your WAN router. So no, this is not a viable approach.
-
This will be in the associated MySonicwall account. Did you get the details for that?
-
It looks like failover isn't a common thing? Not sure what you mean, I've suggested a commercial off-the-shelf solution, little to no development required on your part. I assume there will be other DNS services with similar probe systems available.
-
Amazon AWS Route 53 DNS with a probe ["Health Check"] on some TCP service. You can either do active/standby failover like this or load balance by weighting the DNS entries.
-
It's annoying, GVC is much better performing than SSLVPN, but Sonicwall have lost interest in developing GVC, so we struggle along with SSLVPN.
-
The UUID will be that of the access rule in question. The UUID should not change once the rule has been created; if all your automation does is add/remove IPs to a group which is used by a rule, then all you need to do is learn the UUIDs of the rules you're interested in. If you are lucky, there might be an API method to…
-
X1 is only using one IP so I suppose I would have to add another interface for another WAN IP; which is fine, if that makes things easier No need. Create a specific NAT policy which translates the source IP for network you want to distinguish. See BWC's first post.
-
My CATP reports are still working with today's catches.
-
So just to clarify the rest of this - there's no point in getting a 3 year SSL certificate and reissuing the public key annually, should just be creating a new cert every year? So long as you are rotating the private key regularly, it doesn't matter if you do it by creating a CSR on the firewall and importing the resulting…
-
I am not talking about the DN/CN/SAN, I am talking about the "name" of the certificate on the Sonicwall [the "Certificate" field here]:
-
If you still have the private key then you can assemble them all in to a PKCS#12 file which you can import in to the firewall BUT it's not good practise to keep reusing the same private key! You need to use a slightly different name for your new CSR, I usually put the year in I'm requesting it.
-
That's interesting, I have never seen in a packet capture, a packet being both allowed and dropped. It really does look like the same packet, same 4-tuple. What is uuid="00000000-0000-0003-0700-2cb8ed8fb59c" ? I assume that's an access rule? Export a TSR and search for that UUID, that should show what this is. As to your…
-
So long as you have some way of distinguishing the VOIP traffic so that you can apply a BWM rule to it then you're good. Voice VLAN is good practice anyway.
-
This is working today!