[SOLVED] No internet on host

sergentum

New Member
May 20, 2022
7
1
1
Hi again. I've read all posts I was able to find, but here we go again.
Problem: no pings, but dns works.
If I comment vmbr0 and uncomment vmbr1 then internet works.

I tried to restart networking, reboot host, put out cable - nothing helps. I guess it might be related to my installation of KDE on top of proxmox and network manager, but I removed it already and I can't find any traces of it.

Any help would be appreciated.
Bash:
root@vaio:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
^C
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2039ms

root@vaio:~# ping 1.1.1.1 -I vmbr0
PING 1.1.1.1 (1.1.1.1) from 192.168.1.212 vmbr0: 56(84) bytes of data.
^C
--- 1.1.1.1 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5121ms
pipe 3


root@vaio:~# nslookup google.com
Server:         192.168.1.1
Address:        192.168.1.1#53

Non-authoritative answer:
Name:   google.com
Address: 142.251.143.78
Name:   google.com
Address: 2a00:1450:4008:807::200e
root@vaio:~#

Bash:
root@vaio:~# 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 3c:07:71:65:60:1b brd ff:ff:ff:ff:ff:ff
4: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 9a:23:84:85:08:68 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9823:84ff:fe85:868/64 scope link
       valid_lft forever preferred_lft forever
5: tap103i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 6a:a9:97:fb:d8:6f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::68a9:97ff:fefb:d86f/64 scope link
       valid_lft forever preferred_lft forever
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3c:07:71:65:60:1b brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.212/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::3e07:71ff:fe65:601b/64 scope link
       valid_lft forever preferred_lft forever

Bash:
root@vaio:~# ip route
default via 19.168.1.1 dev vmbr0 proto kernel onlink
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.212

Bash:
root@vaio:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto enp3s0
iface enp3s0 inet manual

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


#auto vmbr1
#iface vmbr1 inet dhcp
#        bridge-ports enp3s0
#        bridge-stp off
#        bridge-fd 0

Bash:
root@vaio:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.212 vaio.lan vaio

# 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

Bash:
root@vaio:~# cat /etc/resolv.conf
domain lan
search lan
nameserver 192.168.1.1
 
Last edited:
your gateway is wrong, so you cannot talk to anything outside your configured subnet (and your DNS is in that subnet, so you can reach it ;))
 
  • Like
Reactions: sergentum
Paris_Tuileries_Garden_Facepalm_statue.jpg

Thank you. I knew that there is something I missed...