Kurkoko

Got back from hollydays Finally just got back to single nic and all work great. Using vlan and not the second nic. Thanks for answering but I think will keep this config. Enviado desde mi iPhone utilizando Tapatalk

Hello, I've got a strange issue that seems to freeze unraid interfaces for minutes and then come back again. Already on ipvlan for docker. My motherboard have 2 nic: -eth0 on range 192.168.1.0/24 from where I manage and local services -eth1 on range 10.10.10.0/24 direct to my firewall for separated lan where I have all my internet services like nextcloud,..... so are separated from network. My unraid came from another mainboard with only 1 nic, managed to migrate all to new system and becouse have 2 nic then created 2 bridges, one for each nic so traffic is separated. Got lots of issues to make unraid understand I have 2 nic and want 2 bridges. Had to delete both network files and reconfigure all again,... I started to notice some nic drops becouse all stop working (home assistant VM, dockers acces,...) for minutes then comes back to work. My NICs are: [8086:15bc] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10) [8086:1539] 02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) Main error I managed to find are these on system logs Aug 22 00:15:47 Tower kernel: veth1732a34: renamed from eth0 Aug 22 00:15:47 Tower kernel: docker0: port 2(veth2756685) entered disabled state Aug 22 00:15:47 Tower kernel: docker0: port 2(veth2756685) entered disabled state Aug 22 00:15:47 Tower kernel: device veth2756685 left promiscuous mode Aug 22 00:15:47 Tower kernel: docker0: port 2(veth2756685) entered disabled state Aug 22 00:15:49 Tower kernel: docker0: port 2(veth87b1ca7) entered blocking state Aug 22 00:15:49 Tower kernel: docker0: port 2(veth87b1ca7) entered disabled state Aug 22 00:15:49 Tower kernel: device veth87b1ca7 entered promiscuous mode Aug 22 00:15:59 Tower kernel: eth0: renamed from veth88a1e09 Aug 22 00:15:59 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth87b1ca7: link becomes ready Aug 22 00:15:59 Tower kernel: docker0: port 2(veth87b1ca7) entered blocking state Aug 22 00:15:59 Tower kernel: docker0: port 2(veth87b1ca7) entered forwarding state Aug 22 00:18:27 Tower kernel: veth0176cf2: renamed from eth0 Aug 22 00:18:53 Tower kernel: eth0: renamed from veth305acd7 Aug 22 00:19:31 Tower emhttpd: read SMART /dev/sdd. I think is not related to the docker issue I see around, already on ipvlan from beggining just in case. Why unraid renames eth0 by itself??? Is a known issue?? I created the diagnostics file and exported system log in case need more info.