[SOLVED] Can't Connect to Internet on Fresh Installation (but can access local network)

[t0fr]

Hi,

I'm new to Proxmox and I'm having some difficulty getting setup with internet connectivity.
I decided to reinstall Proxmox from scratch to see if I had made a mistake along the way but it hasn't solved my issues.
After a successful install, I changed the update repositories to the no subscription servers, and have successfully updated proxmox.

When I go into the shell of my pve1, I can successfully ping other devices on my local network, but I cannot ping internet addresses.
I have tried to ping 1.1.1.1, 8.8.8.8, and google.com and have 100% packet loss.
I can't even ping 24.201.245.77 which is the DNS server that was setup automatically during the installation.

This is my /etc/network/interfaces:

auto lo
iface lo inet loopback

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.69/24
        gateway 192.168.0.1
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0

Here are the results when I run ip a:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 60:a4:4c:b4:98:10 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 60:a4:4c:b4:98:10 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.69/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::62a4:4cff:feb4:9810/64 scope link
       valid_lft forever preferred_lft forever

 

[pos-sudo]

Hello,

I think that the problem might be within the DNS server on your Proxmox host. In our situation we have filled in 1 DNS server to 8.8.8.8. If you fill this in and the gateway of your local network is filled in correctly with the interface port (which seems to be correct). Then you should be able to ping outside the network

 

[t0fr]

Yes, I thought so too.
I edited /etc/resolv.conf which reset after I reboot
So I redid it this morning using the gui (which worked). I now have 8.8.8.8 as my DNS
But I still can't ping the internet

For my own sanity I tried pinging the same domains directly from my Windows machine (which has internet) and I have not been able to.
Requests to google.com, 1.1.1.1, and 8.8.8.8 all time out and there is 100% packet loss.

Well I'm at least comfortable elimintating proxmox and my installation.
I suppose the problem lies with my router or ISP somewhere

 

[t0fr]

I feel stupid
Problem wasn't Proxmox at all.
Marking post as solved

Found this in my router settings:

 

[pos-sudo]

I feel stupid
Problem wasn't Proxmox at all.
Marking post as solved

Found this in my router settings:
View attachment 54928

No problem! Glad that it is working now

 

[jmsilva]

Have the same problem, but in my case do believe it's proxmox, the same machine was running Ubuntu 22.04 LTS and there were no problems. The network has not been changed and I have an identical system sitting next to this one with Ubuntu and it all works.

I even turned the data center firewall and node firewall off, but it still refuses the browser access or email client, tested pinging outside of my local network and on
Ubuntu:
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=25.7 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=25.4 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=25.1 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=52 time=25.8 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=52 time=24.7 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=52 time=24.8 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=52 time=33.5 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=52 time=25.4 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=52 time=25.4 ms
^C
--- 1.1.1.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8017ms
rtt min/avg/max/mdev = 24.713/26.204/33.520/2.609 ms

Proxmox:
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
From 169.254.224.96 icmp_seq=1 Destination Host Unreachable
From 169.254.224.96 icmp_seq=2 Destination Host Unreachable
From 169.254.224.96 icmp_seq=3 Destination Host Unreachable
From 169.254.224.96 icmp_seq=4 Destination Host Unreachable
From 169.254.224.96 icmp_seq=5 Destination Host Unreachable
From 169.254.224.96 icmp_seq=6 Destination Host Unreachable
^C
--- 1.1.1.1 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8196ms
pipe 4

Question here is why did the ping under proxmox return a different IP address than given by the ping command?

Juan Silva
jmsilva@famg.xyz

 

[pos-sudo]

Have the same problem, but in my case do believe it's proxmox, the same machine was running Ubuntu 22.04 LTS and there were no problems. The network has not been changed and I have an identical system sitting next to this one with Ubuntu and it all works.

I even turned the data center firewall and node firewall off, but it still refuses the browser access or email client, tested pinging outside of my local network and on
Ubuntu:
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=25.7 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=25.4 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=25.1 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=52 time=25.8 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=52 time=24.7 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=52 time=24.8 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=52 time=33.5 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=52 time=25.4 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=52 time=25.4 ms
^C
--- 1.1.1.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8017ms
rtt min/avg/max/mdev = 24.713/26.204/33.520/2.609 ms

Proxmox:
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
From 169.254.224.96 icmp_seq=1 Destination Host Unreachable
From 169.254.224.96 icmp_seq=2 Destination Host Unreachable
From 169.254.224.96 icmp_seq=3 Destination Host Unreachable
From 169.254.224.96 icmp_seq=4 Destination Host Unreachable
From 169.254.224.96 icmp_seq=5 Destination Host Unreachable
From 169.254.224.96 icmp_seq=6 Destination Host Unreachable
^C
--- 1.1.1.1 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8196ms
pipe 4

Question here is why did the ping under proxmox return a different IP address than given by the ping command?

Juan Silva
jmsilva@famg.xyz

Could you provide more details of the network settings of the host and VM? The reason that you get an different IP as response is because most likley 169.254.224.96 Is your gateway address.

 

[jmsilva]

First like to thank you for responding, that aside to business.

That behavior is gone! Left behind a mystery of how it happened or why it's gone (suspect my ISP), but since you asked and I have another post where this info is necessary, I gather it here, for you and all who might be interested on getting involved.

System/Network info: Domain name famg.xyz;

1. EERO 6 pro+ router, wired and wifi, gateway 172.16.0.1 with IPv4 Primary DNS 75.76.160.3 and 2nd .4. IPv6 disabled, WAN/IP 24.96.11.20.
2. AMD 7, 64G ram, 1.5tb SSD - Ubuntu server 22.04/LXQt Desktop <amda> 172.16.75.150 (open port 443 <https://famg.xyz> Coming Soon page...
3. AMD 7, 32G ram, 1tb SSD - Proxmox 8.0 <amdb> 172.16.75.160 (not forwarded, only local access) Not gotten to install desktop yet. No VM created
4. AMD 5, 32G ram 1tb SSD - Ubuntu Server 22.04/headless <amdc> 172.16.75.170
5. QNAP 664 - 6 bay NAS running RAID 10 on 4 10tb 3.5" HDD, 2 2.5G Ethernet IP's 172.16.75.220 and .221
6. Raspberry PI4 SBC 8G ram, 512G SSD - Ubuntu Server 22.04/headless <pi4a> 172.16.75.100
7. Raspberry PI4 SBC 4G ram, 512G SSD - Ubuntu Server 22.04/headless <pi4b> 172.16.75.101
8. Raspberry PI4 SBC 4G ram, 512G SSD - Ubuntu Server 22.04/headless <pi4c> 172.16.75.102
9. Raspberry PI4 SBC 4G ram, 512G SSD - Ubuntu Server 22.04/headless <pi4d> 172.16.75.103

 

[jmsilva]

Objective is to cluster all those resources together...