New Proxmox install with intermittent internet

[koopa79]

I've been trying various things, as i have mixed results with deploying containers using the helper scripts.

but i've since noticed that if i try pinging 8.8.8.8 that i often get some pings, and some fail

as an example,

64 bytes from 8.8.8.8: icmp_seq=312 ttl=119 time=14.8 ms
64 bytes from 8.8.8.8: icmp_seq=313 ttl=119 time=14.0 ms
64 bytes from 8.8.8.8: icmp_seq=322 ttl=119 time=14.8 ms
64 bytes from 8.8.8.8: icmp_seq=323 ttl=119 time=14.3 ms
64 bytes from 8.8.8.8: icmp_seq=332 ttl=119 time=15.1 ms
64 bytes from 8.8.8.8: icmp_seq=333 ttl=119 time=14.2 ms
64 bytes from 8.8.8.8: icmp_seq=334 ttl=119 time=14.2 ms
64 bytes from 8.8.8.8: icmp_seq=337 ttl=119 time=13.9 ms
64 bytes from 8.8.8.8: icmp_seq=338 ttl=119 time=14.4 ms
64 bytes from 8.8.8.8: icmp_seq=339 ttl=119 time=14.3 ms
64 bytes from 8.8.8.8: icmp_seq=340 ttl=119 time=14.3 ms
64 bytes from 8.8.8.8: icmp_seq=341 ttl=119 time=13.8 ms
64 bytes from 8.8.8.8: icmp_seq=342 ttl=119 time=14.3 ms
64 bytes from 8.8.8.8: icmp_seq=343 ttl=119 time=14.2 ms
64 bytes from 8.8.8.8: icmp_seq=344 ttl=119 time=14.4 ms
64 bytes from 8.8.8.8: icmp_seq=352 ttl=119 time=14.6 ms
64 bytes from 8.8.8.8: icmp_seq=353 ttl=119 time=14.1 ms
64 bytes from 8.8.8.8: icmp_seq=354 ttl=119 time=13.8 ms
64 bytes from 8.8.8.8: icmp_seq=363 ttl=119 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=364 ttl=119 time=14.0 ms
64 bytes from 8.8.8.8: icmp_seq=373 ttl=119 time=14.6 ms
64 bytes from 8.8.8.8: icmp_seq=374 ttl=119 time=14.2 ms
64 bytes from 8.8.8.8: icmp_seq=375 ttl=119 time=14.4 ms
64 bytes from 8.8.8.8: icmp_seq=384 ttl=119 time=14.6 ms
64 bytes from 8.8.8.8: icmp_seq=385 ttl=119 time=14.2 ms
64 bytes from 8.8.8.8: icmp_seq=390 ttl=119 time=15.0 ms
--- 8.8.8.8 ping statistics ---
390 packets transmitted, 147 received, 62.3077% packet loss, time 395060ms
rtt min/avg/max/mdev = 12.558/14.355/15.658/0.396 ms

any idea what i can do make my connection more stable? I don't know if it helps, but i'm installing this on an old HP N54L Microserver, i'm assuming this is teh reason that sometimes thinsg deploy and others it fails?

 

[fireon]

• Does this also happen from other machines in the network?
• Even if you ping other targets on the Internet?
• What happens if you ping another internal machine?

 

[koopa79]

to confirm, this is only my home setup, and everything else works fine, its only this server.

i might see if i have a spare nic card which i could install in the server and see if that helps, i've also noticed i get the same when pinging my gateway which is the router on 192.168.1.1

 

[fireon]

Thank you for clarify. Have you ever replaced the network cable for test?

 

[koopa79]

Thank you for clarify. Have you ever replaced the network cable for test?

Yes so i did replace it yesterday and i thought it fixed it, i rebooted it, and it all went pants again

 

[fireon]

Yes so i did replace it yesterday and i thought it fixed it, i rebooted it, and it all went pants again

Tell me... could it be that there is a duplicate IP in your network? That would also have such effects.
Which networks do you use? Are they all in the correct RFC? Because if, for example, public subnets are used internally, this can also have very strange effects.

 

[koopa79]

Tell me... could it be that there is a duplicate IP in your network? That would also have such effects.
Which networks do you use? Are they all in the correct RFC? Because if, for example, public subnets are used internally, this can also have very strange effects.

I made sure my router dhcp doesn't start on low numbers, so it "shouldn't" be that, as the server ip is 192.168.1.6, but my dhcp scope starts at .20 to be safe. But I will double check the router settings when i get home

 

[BobhWasatch]

Maybe shutting down your PVE and pinging its IP would be a better way to detect a duplicate IP.

 

[koopa79]

You were spot on, on my router i had accidently pinned something down to the same IP which wasn't my server. I've now released that and its working much better. Thanks Fireon

 

[fireon]

You were spot on, on my router i had accidently pinned something down to the same IP which wasn't my server. I've now released that and its working much better. Thanks Fireon

Perfect. If your issue is resolved, please mark your thread as "solved". You can do this by editing your first post and setting the flag.