No network at host but vm have

P

PeterPan25

New Member
Mar 11, 2025
7
0
1
Not sure how to address that
My vm can connect to the internet or other services without problems
But the host itself have no network connectivity.
Mean, vm full internet access host timeout or host not reachable
First I thought it's the r8168/69 problem (have r8168) but after got r8168 running problem is still there
If restart network service broblem fixed for a minute but back after

It's an proxmox on an Debian setup running aktual proxmox from no-subscription

Google so far didn't help or I asked the wrong question

Any suggestion? Standard settings
 
Do you have any duplicate IPs in your network? That can often cause the network to temporarily work and then stop working.

Please post your full network configuration of the host and inside the VM:
Code: 
cat /etc/network/interfaces
ip r
ip a
 
OK here the requested files, cause there is no running VM, that could interfere, I only posted the stuff from the host.
As mentioned no problems in the VM if they are running, before or after systemctl restart networking.

And the host is not touched in that time from working to not working.

I can still (before or after) access the managment console from another LAN client. just no Internet on the host.


Code: 
cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto enp4s0
iface enp4s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.88.200/24
        gateway 192.168.88.1
        bridge-ports enp4s0
        bridge-stp off
        bridge-fd 0

Code: 
ip r      #before systemctl restart networking (no network on the host, no VM running
0.0.0.0 dev enp4s0 scope link 
default dev enp4s0 scope link 
default via 192.168.88.1 dev vmbr0 proto kernel onlink 
169.254.0.0/16 dev enp4s0 proto kernel scope link src 169.254.248.199 
169.254.0.0/16 dev vmbr0 scope link metric 1000 
192.168.88.0/24 dev vmbr0 proto kernel scope link src 192.168.88.200

Code: 
ip r      #after do systemctl restart networking (internet access on the host, no VM running
default via 192.168.88.1 dev vmbr0 proto kernel onlink 
169.254.0.0/16 dev vmbr0 scope link metric 1000 
192.168.88.0/24 dev vmbr0 proto kernel scope link src 192.168.88.200

Code: 
ip a    #before systemctl restart networking (no network on the host, no VM running

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 noprefixroute 
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    altname enxb025aa32a4b7
    inet 169.254.47.221/16 brd 169.254.255.255 scope global enp4s0
       valid_lft forever preferred_lft forever
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link 
       valid_lft forever preferred_lft forever
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.88.200/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link 
       valid_lft forever preferred_lft forever

Code: 
ip a      #after do systemctl restart networking (internet access on the host, no VM running
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 noprefixroute 
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    altname enxb025aa32a4b7
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link 
       valid_lft forever preferred_lft forever
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.88.200/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link 
       valid_lft forever preferred_lft forever
 
Seems like you have IP address autoconfiguration enabled which is messing with your network configuration. What is the ouput of

Code: 
systemctl status avahi-daemon
 
I did not make any changes to that. Maybe it was done by the previous debian. I followed the Proxmox to Debian wiki

Code: 
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-03-18 10:58:28 CET; 33min ago
 Invocation: 90cc75b9efb84ca5b32518af3bb5d5f3
TriggeredBy: ● avahi-daemon.socket
   Main PID: 1099 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 38109)
     Memory: 1.8M (peak: 2.2M)
        CPU: 102ms
     CGroup: /system.slice/avahi-daemon.service
             ├─1099 "avahi-daemon: running [mavitec.local]"
             └─1139 "avahi-daemon: chroot helper"
 
quite possibly. I'd disable and mask the service:

Code: 
systemctl disable --now avahi-daemon && systemctl mask avahi-daemon

You can check what pulled it in by running, if you're interested why this was pulled in.

Code: 
apt-cache rdepends avahi-daemon

E: you need to restart networking afterwards
 
Ok I did that and ended where I was, after restarting networing works for some seconds and off again.
if I run the Disable second time I get the following.

Code: 
Unit /etc/systemd/system/avahi-daemon.service is masked, ignoring.
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

if I run apt-cache rdepends avahi-daemon I get an longer list, not sure what debian installed all.
Should I delete thoses packages?
 
PeterPan25 said:
if I run the Disable second time I get the following.
Click to expand...
You only need to disable / mask it once.

Can you repost your network configuration after disabling avahi-daemon and reloading the network configuration?
 
Here the result
Funny enough so much different stuff in, checked the VM they still connect

Code: 
#ip r the not working 
0.0.0.0 dev tap110i0 scope link
0.0.0.0 dev fwpr110p0 scope link
0.0.0.0 dev fwln110i0 scope link
0.0.0.0 dev enp4s0 scope link
default dev tap110i0 scope link
default dev enp4s0 scope link
default via 192.168.88.1 dev vmbr0 proto kernel onlink
169.254.0.0/16 dev enp4s0 proto kernel scope link src 169.254.205.139
169.254.0.0/16 dev fwln110i0 proto kernel scope link src 169.254.165.238
169.254.0.0/16 dev fwpr110p0 proto kernel scope link src 169.254.162.183
169.254.0.0/16 dev tap110i0 proto kernel scope link src 169.254.17.92
169.254.0.0/16 dev vmbr0 scope link metric 1000
192.168.88.0/24 dev vmbr0 proto kernel scope link src 192.168.88.200

Code: 
#ip r the working
0.0.0.0 dev tap110i0 scope link
default via 192.168.88.1 dev vmbr0 proto kernel onlink
169.254.0.0/16 dev tap110i0 proto kernel scope link src 169.254.17.92
192.168.88.0/24 dev vmbr0 proto kernel scope link src 192.168.88.200

Code: 
# not working
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 noprefixroute
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    altname enxb025aa32a4b7
    inet 169.254.86.163/16 brd 169.254.255.255 scope global enp4s0
       valid_lft forever preferred_lft forever
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link
       valid_lft forever preferred_lft forever
5: tap110i0: <BROADCAST,MULTICAST,PROMISC,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master fwbr110i0 state UNKNOWN group default qlen 1000
    link/ether ca:c8:2d:aa:42:94 brd ff:ff:ff:ff:ff:ff
    inet 169.254.17.92/16 brd 169.254.255.255 scope global tap110i0
       valid_lft forever preferred_lft forever
6: fwbr110i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 92:d8:ef:9e:3f:bd brd ff:ff:ff:ff:ff:ff
7: fwpr110p0@fwln110i0: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 1e:4c:e9:1b:cf:ad brd ff:ff:ff:ff:ff:ff
8: fwln110i0@fwpr110p0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP,M-DOWN> mtu 1500 qdisc noqueue master fwbr110i0 state LOWERLAYERDOWN group default qlen 1000
    link/ether 92:d8:ef:9e:3f:bd brd ff:ff:ff:ff:ff:ff
9: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.88.200/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link
       valid_lft forever preferred_lft forever

Code: 
# after restart
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 noprefixroute
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    altname enxb025aa32a4b7
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link
       valid_lft forever preferred_lft forever
5: tap110i0: <BROADCAST,MULTICAST,PROMISC,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master fwbr110i0 state UNKNOWN group default qlen 1000
    link/ether ca:c8:2d:aa:42:94 brd ff:ff:ff:ff:ff:ff
    inet 169.254.17.92/16 brd 169.254.255.255 scope global tap110i0
       valid_lft forever preferred_lft forever
6: fwbr110i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 92:d8:ef:9e:3f:bd brd ff:ff:ff:ff:ff:ff
7: fwpr110p0@fwln110i0: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 1e:4c:e9:1b:cf:ad brd ff:ff:ff:ff:ff:ff
8: fwln110i0@fwpr110p0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP,M-DOWN> mtu 1500 qdisc noqueue master fwbr110i0 state LOWERLAYERDOWN group default qlen 1000
    link/ether 92:d8:ef:9e:3f:bd brd ff:ff:ff:ff:ff:ff
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b0:25:aa:32:a4:b7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.88.200/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::b225:aaff:fe32:a4b7/64 scope link
       valid_lft forever preferred_lft forever
 
There is still something doing IP address autoconfiguration, there are several daemons for that - you'll need to check what is actually doing the autoconfiguration (maybe via journalctl) and disable that service. Might be worthwhile to find out why that was pulled in in the first place, since nothing gets pre-installed that does that.
 
not giving up, even other stuff fucked now
get the system still runing only see in journal command [1335] ... than it stop working so far had postfix and network manager removed

working on it, if more clues please
 
OK I found it.
You gave me the right direction, thank you

After I saw during the start:
Code: 
connman-waiting-online

I disabled the connman and connman-waiting-online service
Since that I have no issues from host or VM's

where ever that came from.

cheers
 
You must log in or register to reply here.
Top Bottom