Can't Ping Google.com

[CrimsonShirnaui]

Good Day everyone,
So i have been having this issue a while now, never bothered to fix it but it's starting to cause an issue now.
So as the title says I cant ping google this is what happens when I try.

root@section5p:~# ping google.com
ping: socket: Address family not supported by protocol
PING google.com (172.217.2.206) 56(84) bytes of data.
^C
--- google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2038ms

Reason why I never bothered was simple I have a single ubuntu server which works fine and can ping google.com
the proxmox Server itself can ping static ip's.. This also means I have never updated it, however this is a relatively new set up, Im on 7.2-3

This is my hosts file, also my ISP does use some NAT as by default I have an IPV6 address (Im not very good at networking, I think what I said just now makes sense)

root@section5p://etc# cat hosts
127.0.0.1 localhost.localdomain localhost
192.168.100.5 proxmox.local section5p

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

This is my interfaces file

root@section5p://etc/network# cat interfaces
auto lo
iface lo inet loopback

auto enp5s0
iface enp5s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.5/24
        gateway 192.168.100.1
        bridge-ports enp5s0
        bridge-stp off
        bridge-fd 0
           dns-nameservers 1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4

Any help would be greatly appreciated.

 

[Moayad]

Hi,

Have you checked the /etc/resolv.conf file in your Proxmox VE if correct?

 

[UdoB]

root@section5p:~# ping google.com
ping: socket: Address family not supported by protocol

This is my hosts file, also my ISP does use some NAT as by default I have an IPV6 address

Use ipv6 then, there is a separate binary for this:

~$ ping6 google.com
PING google.com(sof04s07-in-x0e.1e100.net (2a00:1450:4017:816::200e)) 56 data bytes
64 bytes from sof04s07-in-x0e.1e100.net (2a00:1450:4017:816::200e): icmp_seq=1 ttl=118 time=28.9 ms

 

[CrimsonShirnaui]

So per this,

Have you checked the /etc/resolv.conf file in your Proxmox VE if correct?

root@section5p:~# cat /etc/resolv.conf
search proxmox.local
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 1.1.1.1

I get that, and I think its correct... Not sure.

When I use ping6 like you suggested

Use ipv6 then, there is a separate binary for this:

I get no dice,

root@section5p:~# ping6 google.com
ping6: socket: Address family not supported by protocol
root@section5p:~#

 

[CrimsonShirnaui]

Hey figured I would give a small update, issue not yet resolved.
This is what I get when I try to update

root@section5p:~# apt update
Err:1 http://download.proxmox.com/debian/pve bullseye InRelease                                                                                                           
  Could not connect to download.proxmox.com:80 (144.217.225.162), connection timed out
Err:2 http://ftp.debian.org/debian bullseye InRelease                                                                                                                     
  Could not connect to debian.map.fastlydns.net:80 (146.75.30.132), connection timed out Unable to connect to ftp.debian.org:http:
Err:3 http://ftp.debian.org/debian bullseye-updates InRelease       
  Unable to connect to ftp.debian.org:http:
Err:4 http://security.debian.org/debian-security bullseye-security InRelease
  Could not connect to debian.map.fastlydns.net:80 (146.75.38.132), connection timed out Could not connect to security.debian.org:80 (151.101.194.132), connection timed out Could not connect to security.debian.org:80 (151.101.130.132), connection timed out Could not connect to security.debian.org:80 (151.101.66.132), connection timed out Could not connect to security.debian.org:80 (151.101.2.132), connection timed out
Reading package lists... Done                         
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://ftp.debian.org/debian/dists/bullseye/InRelease  Could not connect to debian.map.fastlydns.net:80 (146.75.30.132), connection timed out Unable to connect to ftp.debian.org:http:
W: Failed to fetch http://ftp.debian.org/debian/dists/bullseye-updates/InRelease  Unable to connect to ftp.debian.org:http:
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease  Could not connect to download.proxmox.com:80 (144.217.225.162), connection timed out
W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease  Could not connect to debian.map.fastlydns.net:80 (146.75.38.132), connection timed out Could not connect to security.debian.org:80 (151.101.194.132), connection timed out Could not connect to security.debian.org:80 (151.101.130.132), connection timed out Could not connect to security.debian.org:80 (151.101.66.132), connection timed out Could not connect to security.debian.org:80 (151.101.2.132), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.
W: Target Packages (pve-no-subscription/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list.d/pve-no-subscription.list:1
W: Target Packages (pve-no-subscription/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list.d/pve-no-subscription.list:1
W: Target Translations (pve-no-subscription/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list.d/pve-no-subscription.list:1
W: Target Translations (pve-no-subscription/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list.d/pve-no-subscription.list:1
root@section5p:~#

 

[vesalius]

maybe your isp is blocking things when you try and use a default bridged config (the isp is seeing more than 1 MAC address at a single port) have you ever tried to use routed or masquerading network config for internet access?

Also curious what DNS your isp provides through DHCP?

 

[CrimsonShirnaui]

huh interesting, I never thought about that will def have to look into that. I had another proxmox install a year or so ago, it worked fine but due to some hardware issues ended up installing a new copy. That last proxmox worked fine no issues at all.

So I'm fairly certain something is off... just don't know what.

 

[CrimsonShirnaui]

I have changed my DNS on proxmox to the three DNS servers that my ISP uses. Two are their own like inhouse DNS servers and the last is the cloudflare 1.1.1.1 .
I am still at a loss here, nothing changed. Can ping direct ip's, nothing named resolves.

 

[CrimsonShirnaui]

Update, I changed my dns settings on the proxmox to the one from the isp. The machine lost complete internet connection couldnt even ping gateway.
So i think my dns settings are correct sorta.

 

[otymm]

I have exactly the same problem. My VMs can all ping domains, just not proxmox host, which works only with ip addresses. Real pain..

 

[CrimsonShirnaui]

So update and I resolved it.
It's not a proxmox issue it was related to the ISP's modem.. It's weird I am on a huawei Router and assigning Static IP addresses on it's Primary net a 192.168.100.0/24 , well it doesn't seem to like that, so to resolve it. I used a secondary address pool,( which I always thought was weird it had that by default anyway) 192.168.2.0/24.... Anyway it worked when the Proxmox was set to that can update and everything.. Hope this helps you and I only discovered this after reinstalling.

 

[joputi]

Hi,

Have you checked the /etc/resolv.conf file in your Proxmox VE if correct?

Oh man! So simple, and so accurate answer.
I was blocked and searching for days, and you gave me the solution to my problem in a single line.
Your answer helped me a lot.

Thank you so much.