Thread Info
  • State Suggested Answer
  • +7 person also asked this people also asked this
  • Locked Locked
  • Replies 58 replies
  • Answers 4 answers
  • Subscribers 49 subscribers
  • Views 191201 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Country Blocking Not Working for a WAN > LAN Rule

Timothy Stewart

Hi.  It seems like country blocking is not working for WAN -> LAN (or any other protected network behind XG Firewall).

I have tested this with a proxy in the blocked countries.

I have this rule at the top of the list and network traffic still passes even though the rule shouldn't allow it, basically ignoring it.  The rule is never triggered thus always stating in 0 B, out 0 B.  I have tried every combination of Source/Destination/Zone/Network and still it doesn't work.



This thread was automatically locked due to age.
Parents
  • 0

    I have read through this thread and forgive me if I missed it, but it wasn't clear to me whether or not this is a confirmed bug in the XG or not?  I've seen some various workarounds offered (thanks for those) but has Sophos confirmed this is a bug?  If they say its not a bug (I have no idea how that could be true) is there a feature request somewhere we can upvote?

  • 0 in reply to Bill Roland

    No, this issue has not been recognized here by anyone from Sophos.  It is also still missing from the known issues list.

    In his post on page 2, Aditya Patel demonstrated that the IP to country mappings are working correctly (which had already been proven in this thread).  But there has been no other information about the actual issue that blocking by source country in a Network Rule is broken in XG.

  • 0 in reply to sachingurung

    Silence and sometime in the future are quite different period of time and they have different meaning. If there is SW code there are bugs and no one complains on that. What we are not happy and really angry here is the silence for a long time and then...pooof someone from Sophos reported the NC and gave even an expected release version.

    So be sure to properly report time and NC most efficently here and to all users. Another issue that is around the forum are bookmarks. There is an NC number but it does not cover all issues (I guess).

    Taking a year to have an answer is more than alot. Be sure to at least inform as that it is a bug, your are investigating, or whatever phases you are but the silence is the worse phase users accept.

    Silence means poor quality!

    Kind Regards

  • 0 in reply to lferrara

    We understand the concerns but the NC-# was not created until v16-MR1 and the JIRA was not directly referenced to the country blocking issue, which is one of the reason my team was not sure to reference it. We were already discussing this internally but we were not able to get a solid case reference on this issue. The cases were mostly resolved configuring a blackhole business rule and it is an accepted solution as we see. 

    We work as a tangant team between the Support and a Customer hence we can only report and expidite the NC-# if they are already created & reported but we cannot emphasize on creating one of the NC#. The reason we were not able to provide an update on this issue is because, the workaround was accepted and the cases were never reported in the escalations or went cold. 

    I will take the responsibilities of such unresolved thread, please PM me and I will make sure they are immediately looked upon by us and the support team. 

    Sincerely,

  • 0 in reply to sachingurung

    Sachin,

    I have sent a PM to you.

    Regards

  • 0 in reply to sachingurung

    Hi.  I created the original issue and I want to make sure it is not getting diluted with other issues and workarounds.  The issue still stands.  My steps to reproduce are in the first post.  A workaround of a blackhole is just that, a workaround and not a fix.  Will this issue be fixed?  Is it being address?  The feature clearly does not work.

  • 0 in reply to Timothy Stewart

    Thanks Timothy.

    Sophos has recognized the issue/design limitation. It should be fixed in v17 MR1 as reported by . NC-17413

    So they are going to change the behaviour and fix the Country Blocking at the same time.

    Finally!!!!

  • 0 in reply to GregH

    GregH said:

    I can confirm that this is something that has been logged and the intention is to change how this behaves in v17 MR1. The reference for this change is NC-17413 in case anyone needs an update on the release version from Support. 

     

    Thanks for confirming.

    What is the expected timeframe for v17 MR1 release?

  • 0 in reply to GregH

    I see the NC-17413 was supposedly in MR-2.  Unless I am doing something drastically wrong, it still does not work at all (I am on MR3 now).  I even see a KB article posted about it on December 21st (https://community.sophos.com/kb/en-us/123007)and I followed it exactly and still it does not work.  At all.  It does nothing.  

    Look I don't mean to give you a hard time but this is a really simple feature that any firewall should be able to do out of the box in its sleep.  There were ways to accomplish this as far back as at least Microsoft ISA Server 2004.  I like XG and don't subscribe to the general bashing it receives but this one is legit and quite frankly the excuses are just that.

  • 0 in reply to Bill Roland

    Just to add a vote to this - I am getting hammered on ports 23 / 2323 / 1900 from a bunch of countries that we have no dealings with and I would like to block all of them and using a simple WAN to LAN rule with the countries seems easy - but like others say it doesnt work.

    I am also on v17 MR3

    Really need this as it gives us a much larger attack surface.

    Have any of you managed a work around?

  • +2 in reply to M8ey

    This fix was released in MR3, and I just double-checked my firewall, to confirm it's working. Check your zones in the block rule, as there's probably a mistake there. Test with zones set to ANY/ANY. You're defining the network source in the rule by specifying the country, so defining the zones also, is a bit redundant anyway. 

  • 0 in reply to AlanT

    AlanT said:

    This fix was released in MR3, and I just double-checked my firewall, to confirm it's working. Check your zones in the block rule, as there's probably a mistake there. Test with zones set to ANY/ANY. You're defining the network source in the rule by specifying the country, so defining the zones also, is a bit redundant anyway. 

     

    It seems for me the trick is it has to be set to Any/Any for the zones, once doing that it started working.  Thanks Alan!

     

    You may want to update this KB article here https://community.sophos.com/kb/en-us/123007, the settings show selecting WAN and LAN zones. 

Reply
  • 0 in reply to AlanT

    AlanT said:

    This fix was released in MR3, and I just double-checked my firewall, to confirm it's working. Check your zones in the block rule, as there's probably a mistake there. Test with zones set to ANY/ANY. You're defining the network source in the rule by specifying the country, so defining the zones also, is a bit redundant anyway. 

     

    It seems for me the trick is it has to be set to Any/Any for the zones, once doing that it started working.  Thanks Alan!

     

    You may want to update this KB article here https://community.sophos.com/kb/en-us/123007, the settings show selecting WAN and LAN zones. 

Children
No Data