[SOLVED] Proxmox host unable to access Internet only LXCs

ibbs

New Member
May 8, 2023
4
1
3
Hi, I am suddenly unable to access the internet from my proxmox host, I noticed this while trying to use some Proxmox Helper Scripts. When i try to ping google from the host shell I get temporary failure in name resolution, however it works in any of the lxcs shells. I did today change the IP address of the web gui, however this is because after a restart i suddenly was not able to access, web gui anymore and noticed the ip on the router assigned had changed. So i am unsure if this is related to this. I have tried reading through some other posts however I have no clue were to start. Below are some outputs.

ip addr
Code:
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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 18:60:24:a8:49:0f brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 18:60:24:a8:49:0f brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.56/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::1a60:24ff:fea8:490f/64 scope link
       valid_lft forever preferred_lft forever
4: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:d4:b9:f0:44:b4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
5: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:ae:74:70:25:62 brd ff:ff:ff:ff:ff:ff link-netnsid 1
6: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:fa:e4:29:f1:01 brd ff:ff:ff:ff:ff:ff link-netnsid 2
7: veth200i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:41:bf:29:20:1e brd ff:ff:ff:ff:ff:ff link-netnsid 3
8: tap300i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr300i0 state UNKNOWN group default qlen 1000
    link/ether 82:a6:e5:46:ac:9c brd ff:ff:ff:ff:ff:ff
9: fwbr300i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e6:c8:82:98:e0:b2 brd ff:ff:ff:ff:ff:ff
10: fwpr300p0@fwln300i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 52:69:2c:ea:ed:4d brd ff:ff:ff:ff:ff:ff
11: fwln300i0@fwpr300p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr300i0 state UP group default qlen 1000
    link/ether fa:14:4c:18:4a:f9 brd ff:ff:ff:ff:ff:ff
12: veth410i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:c6:a8:93:89:cf brd ff:ff:ff:ff:ff:ff link-netnsid 4

/etc/network/interfaces
Code:
auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.50.56/24
        gateway 192.168.50.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

I added the auto eno1 line because I saw that was there in one of the posts.

ip route
Code:
default via 192.168.50.1 dev vmbr0 proto kernel onlink 
192.168.50.0/24 dev vmbr0 proto kernel scope link src 192.168.50.56[ICODE]

Also I dont not have a resolv.conf file
 
Hi,

When i try to ping google from the host shell I get temporary failure in name resolution
Also I dont not have a resolv.conf file
this basically says why. The /etc/resolv.conf configures name resolution by e.g. setting up DNS servers which should be contacted.
Thus, if this file is missing, programs won't know how to resolve any domain names.

Either set it up using the GUI (System -> DNS on a node) or create the file with contents like e.g.
Code:
search localdomain
nameserver 9.9.9.9

After that, name resolution should work again.
 
  • Like
Reactions: ibbs
Hi,



this basically says why. The /etc/resolv.conf configures name resolution by e.g. setting up DNS servers which should be contacted.
Thus, if this file is missing, programs won't know how to resolve any domain names.

Either set it up using the GUI (System -> DNS on a node) or create the file with contents like e.g.
Code:
search localdomain
nameserver 9.9.9.9

After that, name resolution should work again.
Excellent this works. Un sure how this happened tho. Thank you.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!