Why is Veeam trying to communicate to 5.255.255.5 (yandex.ru) ?

[juanmachado]

I have a Veeam agent running on a fresh physical Ubuntu box.
As soon as I try to run a baremetal backup that connects to a Veeam SOBR, it fails with:

Failed to connect to the endpoint [5.255.255.5:2502]. Connection timed out

[Mildur]

Hi Juan,

Our Veeam Agent does not connect to yandex.ru, and I can't find any similar cases matching the situation you are describing. Therefore, I suspect there may be an issue with your machine.

I strongly recommend opening a case with our customer support team for further investigation. Additionally, it would be wise to involve your security team to check the machine and backup environment.

Best,
Fabian

[juanmachado]

I am part of the security team.
Case opened. Thanks

[Mildur]

Can you please share with the case number?

Thank you very much,
Fabian

[juanmachado]

Case # 07613784

[Mildur]

Thank you. It looks like one of your backup infrastructure components has this IP address assigned to it. I assume your repository. Our Veeam Agent will try to connect to all IP Addresses retrieved by the backup server.

Thank you very much,
Fabian

[Gostev]

Wow. I know Direct to Cloud backups are pretty popular, but Direct to Putin... that would be the first

[juanmachado]

@Gostev,
Just hearing that name was not funny

Anyway, we found what the problem was. One of my staff added5.255.255.5 as a "private IP" to one of the hardrepos. I know... don't ask me why
But we did find a problem that we didn't know has existed for over 6 years, where veeam agent can't talk to VBR proxies, but instead talk directly to the hard repositories, which is the opposite of what you want.

post540471.html#p540471

So the mystery has been solved, but now I know I can't send baremetal backups to Inmutable hard repos