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

GeoIP

Is anybody having success in using the GeoIP functionality? I am not and i find it quite frustrating.

What have i done:
1. created a country group within that group f.i. Romania:

2. created a Drop rule based on the country group:

3. Have been checking logs for a couple of weeks, today i saw that there wher entries in the log showing me that traffic was allowed originating from a Romanian IP:

And this is only one example, my log is filled with more similar ones.
Any thoughts on this? Is my thinking wrong, was my execution poor or are my expectations not right?

Grtz, Peter-Paul



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

    Hi Peter-Paul Gras,

    I was able to replicate this issue in my LAB, traffic from the country that supposed to be blocked by the country blocking rule, it did not trigger that block rule. I have reported this issue to internal team. I will update this thread as soon as I get feedback on this issue.

    Thanks,

     

Reply
  • FormerMember
    0 FormerMember

    Hi Peter-Paul Gras,

    I was able to replicate this issue in my LAB, traffic from the country that supposed to be blocked by the country blocking rule, it did not trigger that block rule. I have reported this issue to internal team. I will update this thread as soon as I get feedback on this issue.

    Thanks,

     

Children
  • Thank you for letting us know and confirming the findings.

    Grtz, Peter-Paul

     
    SFVH (SFOS 20.0.0 GA-Build222) - Last (re)boot on November 6th  2023
    Asus H410i-plus - Pentium 6605 Gold - 250GB M.2 PCIe NVMe SSD - 8GB - 3 ports
    [If any of my posts are helpful to you please use the 'Verify Answer' link]
  • Hi,

    Is this issue also related to NC-51857 ?

    GeoIP works fine on v17.5.x, but not on v18. I've had this issue in v18 EAP 1.

     

    Thanks!


    If a post solves your question use the 'Verify Answer' button.

    Ryzen 5600U + I226-V (KVM) v20 GA @ Home

    XG 115w Rev.3 8GB RAM v19.5 MR3 @ Travel Firewall

  • Do you maybe know if this is fixed in latest release?

  • No, they didn't fixed it.

    The issue people are having on this thread is pretty much the same I reported on v18 EAP 1.

    I also through it would have been fixed by now, since it has reported on EAP 1. but, well...

     

    I hope It's fixed soon.


    If a post solves your question use the 'Verify Answer' button.

    Ryzen 5600U + I226-V (KVM) v20 GA @ Home

    XG 115w Rev.3 8GB RAM v19.5 MR3 @ Travel Firewall

  • It is a long standing issue, not just in V18.

    Ian

    XG115W - v20 GA - Home

    XG on VM 8 - v20 GA

    If a post solves your question please use the 'Verify Answer' button.

  • I can be wrong, but this issue has never present on >v17.5.6

    I've always used geoip blocking on inbound/outbound and on WAF on v17.5.x, and never had any of those issues.

    The issue is currently only present in v18, It's present since v18 EAP 1 came out.


    If a post solves your question use the 'Verify Answer' button.

    Ryzen 5600U + I226-V (KVM) v20 GA @ Home

    XG 115w Rev.3 8GB RAM v19.5 MR3 @ Travel Firewall

  • Outbound has always worked in IP4, but inbound was an issue and neither work in IPv6.

    Ian

    XG115W - v20 GA - Home

    XG on VM 8 - v20 GA

    If a post solves your question please use the 'Verify Answer' button.

  • The key difference and this thread discussion is about inbound GeoIP on IPv4, It always worked on v17.5, but doesn't work anymore on v18.

    GeoIP on IPv6 is a whole different history in XG.


    If a post solves your question use the 'Verify Answer' button.

    Ryzen 5600U + I226-V (KVM) v20 GA @ Home

    XG 115w Rev.3 8GB RAM v19.5 MR3 @ Travel Firewall