Virtual Machine has no internet connection since a few days

UCS - Univention Corporate Server
#1

dear forumists,

yesterday I tried to access my VM via it’s internal IP (as I often do but not on a regularly/daily basis). But I can’t reach it anymore.
So I think it got broken during one of the latest updates (runnig 4.3-3 err481 now).
I still can access it using VNC. And so I see that it won’t connect to the interal ethernet using DHCP anymore. It would - at least kind of half connect - if I’d setup a manual connection it tells me that it has got setup this internal IP but still can’t ping to router/other internal devices).
After investigating a bit through the forum I found this thread and tried it

$ sudo brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.bc305be519e5       no              eno1
docker0         8000.02420922df6e       no              veth5d9cf21

but there simply is no vnet0 (as suggested in the mentioned thread) as well as br0 is already connected to somewhere (eno1).

Since I did nothing more than just updating my UCS I’m pretty sure that it wasn’t me breaking the connection.
So maybe someone else here has an idea on what to do?

Looking forward to your hits
Thanks in advance
Jimmy

#2

Hi,

well, how is your interface named? Please post
ip a show.

/CV

#3

gives me

$ ip a show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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 mq master br0 state UP group default qlen 1000
    link/ether bc:30:5b:e5:19:e5 brd ff:ff:ff:ff:ff:ff
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:09:22:df:6e brd ff:ff:ff:ff:ff:ff
    inet 172.17.42.1/16 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:cccc:dddd:df6e/64 scope link
       valid_lft forever preferred_lft forever
7: veth5d9cf21@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether a2:a2:12:52:98:d4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::aaaa:bbbbfe52:98d4/64 scope link
       valid_lft forever preferred_lft forever
11: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether bc:30:5b:e5:19:e5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.xxx.yyy/24 brd 192.168.xxx.zzz scope global br0
       valid_lft forever preferred_lft forever
    inet6 fe80::xxxx:yyyy:fee5:19e5/64 scope link
       valid_lft forever preferred_lft forever
#4

@JimmyKater Maybe this is the same issue as described here:

Do you have rebooted the host system?

1 Like
#5

am gonna do in a few… and will let you know if it helped. thanks for the hint so far!

#6

THIS hint helped me with my problem… or even better: it solved it so far. thanks @SirTux

Mastodon