Comments
-
thank you
-
James, Reseller told me your access points are all cloud managed. I'm not into that. If that's not true what's the smallest ap I can get that works with the firebox? Just to be clear, when you say reset, does that mean the ap config will or wont survive a reboot like pulling the ac plug out and plugging it back in? Thanks
-
ping out from internal1 via external1 bound for ip on external 2. See in the firebox log the traffic went to external1. Doesnt seem the traffic is coming back. There's no log prompting me what to do next.
-
Tech support says it got fixed a couple of months ago, but forget to tell me. I tested this morning and it looks fixed.
-
Thanks for the suggestion. Moved from 1-1 nat to snat without issue, but still cant seperate into two isolated networks Logging is set to info. Best I can do is make rules to get the traffic out on the right external - or so the log says - but nothing after that. No ping, no log.
-
I moved back to 1.1 for a while, then the cloud. No problem with either. Switched back to 2.0 and got the same error. Switched back to 1.1 and got the same error. Changed the shared key on both sides and both ok.
-
latest status says this is still pending fix
-
Thanks for the idea.
-
Not the cli either Maybe somebody can make that a feature request?
-
So if I want to drop someone using shared hosting from getting in, what kind of rule works for that?
-
Looks like one can. Sorry to bother you. FWDeny, Denied, pri=4, disp=Deny, policy=EXCEPTION-Block-Inbound-00, protocol=http/tcp, src_ip=64.62.197.17, src_port=3956, dst_ip=x.x.x.x, dst_port=80, dst_ip_nat=10.10.10.251, src_intf=EXT-BUSINESS, dst_intf=INT-BUSINESS, rc=101, pckt_len=48, ttl=46, pr_info=offset 7 S 3574765286…
-
thanks.
-
I dont think there was a traffic trouble. Fixed by going back to an old config and rebuilt with the same settings from there up.
-
thank you