[SOLVED, user error] Proxmox not conncected to internet, but is reachable on LAN
[SOLVED, user error] Proxmox not conncected to internet, but is reachable on LAN
[SOLVED] Turns out I'm just a bigger moron than I thought. The MAC address of my server had accidentally been flagged in my router for black listing.
As the title says, my proxmox host is apparently not able to reach the internet anymore, not sure for how long this has been an issue, I rarely work on the host itself. It can ping other devices on my network just fine, and other devices can ping it. I can also SSH in to it and access the web interface. My VMs are connected to the internet without any issues. I don't need to access the host remotely/outside my home network, this is just for updating it etc.
I can't see the host under active devices in my router though.
I have been trying to figure why, but so far without any luck.
Sounds like potentially a DNS issue
This is what I'm thinking too, but I don't know how to fix it.
Is the host configured with static IP or DHCP? Either way, verify it has the correct DNS config.
Personally I use static for any device that hosts a service.
What happens if you ping Yahoo.com from the console in Proxmox? It should show the DNS server IP it's using for resolution.
This really sounds like a problem with the default route. What’s the output of
ip route? That should give us some hints about what’s up.this is the output of ip route.
192.168.68.1 is my router, 192.168.68.120 is the proxmox host
Cool. That looks right. Have you checked that the bridge is set up properly and that the router doesn’t have anything silly going on for that subnet?
PVE’s network settings are in
/etc/network/interfacesand that’s where you can see how the bridge is set up.It might be beneficial to know more about your network. Is this the only subnet or do you have a bunch of VLANs? Can other devices on the subnet ping outbound? Have you looked at the firewall on PVE?
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters More Letters DHCP Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network DNS Domain Name Service/System IP Internet Protocol PCIe Peripheral Component Interconnect Express
[Thread #648 for this sub, first seen 1st Apr 2024, 16:45] [FAQ] [Full list] [Contact] [Source code]
Does it work after a reboot? I vaguely remember having this problem on my old motherboard. Adding a PCIe LAN adapter and switching everything over solved it for me. Now I have a new mobo and it doesn't have any network problems.
Nope, reboot doesn't change anything
Try a traceroute to something like 9.9.9.9 and google's IP. You're able to resolve things ok. So, not DNS. Need to find out where the traffic is going to die.
Also, try a
curl https://google.com -vvv. This should give some more info on what is happening to TCP traffic.this is the output when i run curl httpS://google.com -vvv
