Second IP address not reachable...

Hello,

Does it take time when ordering a second IPV4 address before its active?

We configured it on the VM but does not work nor on debian, nor on almalinux installed via the rescue system.

Maybe netcup.de needs to do this by hand or?

Regards,

Arjan Westmaas

Yes, its assigned, the rescue system assigned it in the config and it works... But from outside the MTR trace stops at:

From another VM in the same datacenter i can ping the server, just not from outside...

Host Loss% Snt Last Avg Best Wrst StDev

1. x.x.x.x 0.0% 205 1.4 0.6 0.2 3.8 0.8

2. x.x.x.x 0.0% 205 2.5 2.7 1.0 12.8 1.9

3. x.x.x.x 0.0% 205 2.9 2.3 1.2 67.2 4.8

4. x.x.x.x 0.0% 205 4.0 2.5 1.7 19.9 1.6

5. 130.117.51.13 0.0% 205 75.6 5.1 2.3 134.0 13.4

6. 130.117.14.102 0.0% 205 4.5 2.9 2.1 16.5 1.6

7. 62.115.120.228 40.5% 205 3.9 2.8 2.3 7.0 0.7

8. 62.115.124.81 0.0% 205 4.4 3.7 2.8 77.7 5.2

9. 62.115.171.229

10 > no server not response

Looks like routing is not completely setup yet... Since i can ping from another VM within Amsterdam DC to the assigned ip address, so the server is setup correctly.

On almalinux 8 its just assigned as a seconde ip address...

Ok, created a support ticket, thanks for the headsup!

Update: Questions where asked to send some info but nothing has been resolved yet...

Update 04-11-2024 - 15:35: nothing has been resolved yet... No new communication.

Update 05-11-2024 - support asked to try rescue system, which is completely obsolete. No further update, no fix yet.

Update 09:33 netcup has found the right switch to turn, it started working (not confirmed from nc yet but ping works)