I spotted an issue today whilst on customer site with them accessing HTTPS sites over the SXT LTE i have recently implemented, the config looks a little like this:
What i spotted was that 90% at least of requests to HTTPS sites where just dying ... I could see the browser find the IP, then get estblishing secure connection .... then it just stayed at that point till it timed out.
I did some digging and could see one particular firewall drop rule with lots of traffic logged against it, the rule was disabled and the problem went away.
The rule in question is this one:
Code: Select all
add action=drop chain=forward comment="defconf: drop invalid" \
!connection-bytes !connection-limit !connection-mark \
!connection-nat-state !connection-rate connection-state=invalid \
!connection-type !content disabled=yes !dscp !dst-address \
!dst-address-list !dst-address-type !dst-limit !dst-port !fragment \
!hotspot !icmp-options !in-bridge-port !in-interface !ingress-priority \
!ipsec-policy !ipv4-options !layer7-protocol !limit log=no log-prefix="" \
!nth !out-bridge-port !out-interface !p2p !packet-mark !packet-size \
!per-connection-classifier !port !priority !protocol !psd !random \
!routing-mark !routing-table !src-address !src-address-list \
!src-address-type !src-mac-address !src-port !tcp-flags !tcp-mss !time \
!ttl
Many Thanks
Nik