Coder68 - What's your recent experience with Country Blocking Exceptions? We were having heck with malicious botnets scanning our network for RDP connections. We eventually had to purchase RDP guard software (Windows protection is useless) for those few machines we had to have listening all the time, and turn the rest of the listening machine's NAT translations off, and only turn them back on when needed.
So, I thought we'd just block all the countries in the list, and create specific country blocking exceptions to accept SMTP incoming traffic, which is the only thing we'd be interested in accepting from most foreign countries. However, later one of our suppliers whose email routes through Israel complained that their emails were getting rejected, and sure enough they were right. I had to turn off the country block for Israel to restore functionality for them, even though they were in the country blocking exception rules. I can open a support case, but I know it's going to be difficult for Sophos Techs to test this, and I don't want to make my supplier a guinea pig.
Thanks,
Steve P
Hi,
I'm running 9.311-3 on an SG 230 and having this same problem. The workarounds didn't work in my case. Conde68's idea with the transparent skip list got closer though. Rather than a "country blocked" message from the page, the page timed out after a couple minutes.
I also tried doing both a country exception AND a transparent proxy skip list.
Now wondering if there'd be any point in submitting a support ticket since Soohos MUST know this is still an issue.
Thanks,
Jeff
Jeff - Sophos fixed this for me, after submitting an SR. They need to look at your particular setup. After looking at mine, they figured out where the blocking was taking place, and we were able to come up with an exception rule that worked.
Thanks,
Steve P
Well, I've been battling an inbound country blocking exception for days and I just found this topic.
Synology support from Thailand needed to access my NAS over SSH, and HTTPS over port 5001. So, I built a DNAT with an auto FW rule to handle the SSH, and let my existing HTTPS/5001 web publishing rule handle the rest. I also built a country block exception for Taiwan from Synology's support IP addresses on destination ports 22 and 5001.
I can connect just fine from a US address, which is allowed by country blocking along with Canada - in other words, these countries are switched "off." All other countries are set to block traffic "from" them, including Taiwan.
But unfortunately, Synology support can't connect and the FW log stubbornly shows GEOIP blocks for the inbound traffic on both ports.
Upon reinspection, the DNAT and auto FW rule looked to be correctly constructed, and the country block exception, also.
I ran the source IPs through the MaxMind database and confirmed they were in the excepted country.
I've now disabled Country Blocking and I'm waiting for Synology support to try again. It occurs to me that I could also switch Taiwan to "off" in Country Blocking, and achieve the same result.
/sigh ....sure would like this to work as designed.
edited to add: In fact, Synology was able to access my appliance five times overnight, after I disabled Country Blocking altogether. I've since re-enabled Country Blocking, but switched Taiwan to "off," and I'm waiting to see a connection attempt.
Timothy, please have a ticket submitted to Sophos Support. They won't fix it unless we complain when it doesn't work!
Cheers - Bob