Atera showing strange 4 digit public IP address on some agents.

dennphy
dennphy Member Posts: 10
edited December 2023 in Remote Monitoring

Hi,

I have a ticket raised already regarding this but has anyone else noticed this recently ? I believe the common factor maybe when Cloudflare WARP is being used on the endpoint.

Dennis

Comments

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭

    @dennphy I have not noticed anything within our endpoints.

  • dennphy
    dennphy Member Posts: 10

    Its not cloudflare warp as I suspected. Happening on new endpoints recently added. Its like its TRYING to show an IPv6 but only 4 digits…..

  • robin.van.noorwege
    robin.van.noorwege Member Posts: 1

    Hello,

    We seem to be having the same issue on some of our agents.
    Added a screenshot to confirm we are referring to the same thing.


    Haven't really found anything these agents would have in common to cause this issue.

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭

    @dennphy @robin.van.noorwege The first number is your external IP, so it may be that it is an IPV6 and its screwed up or that something on the network, like a firewall is blocking that from polling.

  • dennphy
    dennphy Member Posts: 10

    Yes its the external IP thats wrong. I may have confused Atera support by referring to it as the "public IP". But I have sent them screenshots as well. Now starting to spread and show up on LINUX agents e.g Amazon Lightsail instances I monitor via Atera. The one shown below DEFINITELY has a STATIC external IPv4 assigned to it…

  • dennphy
    dennphy Member Posts: 10

    Word from Atera support this morning - still "investigating". This has been going on for weeks now. Its killed a tracking system I developed using the API to know approximately where an endpoint such as a laptop is located based on its external IP. I could see if a laptop is currently at a customer based on that customers static external IP or another location….

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭

    @dennphy I have also started to have the same issue with my endpoints.

  • dennphy
    dennphy Member Posts: 10

    Seems to have been resolved, finally….

  • dennphy
    dennphy Member Posts: 10

    Now I am seeing SOME agents at the SAME LOCATION reporting the full IPv6 external address not the IPv4 one. I wish it would work like it used to up until a month or so ago before this all started happening. Also Linux agents are NOT reporting changed external addresses at all…..

  • sarah+success
    sarah+success Member Posts: 70 ✭✭

    Hey @dennphy , I am happy to hear that the issue was resolved. If things are still not working how you want them to, please reply to the ticket you had opened.

  • dennphy
    dennphy Member Posts: 10

    The ticket says "still investigating" have not had a reply I am not convinced its really fixed still seeing sporadic FULL IPv6 addressess when it used to show IPv4. Somehow the behaviour has been changed in the attempted fix.

  • sarah+success
    sarah+success Member Posts: 70 ✭✭

    Hey @dennphy , Sarah from Atera here.

    Support for IPv6 should be added in the next few weeks.

    If you still have issues after that, please answer back on the ticket so our support can be aware. That is the fastest way to get in touch!

  • nina
    nina Internal Posts: 428 ✭✭✭✭✭

    Hi @dennphy - Our Dev Team has investigated this, and as of a few weeks ago, IPv6 should now be available for the devices. Is everything working now?