Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 1 subscriber
  • Views 7245 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

Update of Public Ip Address

pmoore
We have changed internet providers in a number of sites, but the ACC still reports the OLD public IP address.

Should this be updated automatically? 
Is there something I need to do to get this to update?


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to pmoore
    I've seen the same issue ... no idea on how to fix it either.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Sophos Platinum Partner

    --------------------------------------

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Just for "fun" I tried what Thorsten suggested again (ACC 2.100, several clients with "mismatched IPs" ASG 7.502, hardware appliances) ... the mismatch continues.  At this point I'm not so sure it's not the ACC Agent daemon on the Astaro that's not "letting go" of the old IP it's reporting... pressing the GEOIP button does not make a difference.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Sophos Platinum Partner

    --------------------------------------

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Hi,

    there are two issues.

    1) GeoIP resolution servers

    The previous/former server infrastructure for the GeoIP retrieval is currently unavailable and we have migrated the resolution facilities to the official V7 Up2Date servers. Alas, the ACC agent on the 7.502 Gateways is still using an outdated server list. This behavior should be fixed in 7.503 - apologies for that.

    2) Perceived external IP

    There might be a difference on what you might expect to get as a public IP and what the GeoIP lookup mechanism might yield. What you will get is the IP address which is perceived by the Astaro Up2Date server as the REMOTE_HOST for an HTTPS request originating from the Gateway. This address actually might be the external IP of the Gateway itself, but can also be the address of the last masquerading firewall or HTTP proxy in between your Gateway and the Up2Date server.

    Workaround/Fixes:

    Option 1) Wait for 7.503 and let the issue repair itself ...

    Option 2) Trigger the GeoIP manually on each Gateway using the correct Up2Date servers. This is suprisingly easy:

    # mv /etc/location /etc/location.backup
    # iplocator.plx
    # cat /etc/location (to see the lookup result)

    The ACC agent should pickup the change automatically and reflect it back in the ACC.

    Sorry for the inconvenience - this should be up and running within the next week(s).

    Thanks and regards,
    Henning
Unfiltered HTML