IpDo Posted March 17, 2018 Share Posted March 17, 2018 Hello all, After upgrading from 6.4 to 6.5 I've had many issues (with the VM engine mostly) but I've managed to fix all of them. the only problem that I can't seem to fully fix is the network issue. my setup is - network #1 ISP A [192.168.1.1] - connected as eth0 and is the main connection. network #2 ISP B [192.168.0.1] - connected as eth1 and is the backup connection and used to serv the media stored in the server to a different part of the house. before the upgrade everything worked fine. after the upgrade I've lost eth1 completely (only br1 showed with link down). after reading the change log (many network related updates) I've guessed that cleaning the config might help. I've removed: network.cfg & network-rules.cfg and rebooted. that seem to make eth0 and eth1 work. after some basic config both network are seeing the server and have access to the web UI. the problem is with network #2 and Samba - it can't seem to access it. with network #1 everything works fine. I've attached the old and new config files for the network. Any ideas? network.cfg network.cfg.bu network-rules.cfg network-rules.cfg.bu Quote Link to comment
IpDo Posted March 18, 2018 Author Share Posted March 18, 2018 Hello again, I'm facing the original problem once again - eth1 is missing. the strange thing is that the network is connected, pinging network #2 from within the windows 10 VM works but from Unraid (the host) I get no ping. VM: C:\Users\Ido>ping 192.168.1.1 Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\Ido>ping 192.168.0.1 Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms UNRAID: root@Tower:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.337 ms ^C --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.337/0.337/0.337/0.000 ms root@Tower:~# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. ^C --- 192.168.0.1 ping statistics --- 28 packets transmitted, 0 received, 100% packet loss, time 27644ms here is some more info that might be helpful: root@Tower:~# lspci | egrep -i --color 'network|ethernet' 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) root@Tower:~# lshw -class network *-network description: Ethernet interface product: Ethernet Connection (2) I218-V vendor: Intel Corporation physical id: 19 bus info: pci@0000:00:19.0 logical name: eth0 version: 05 serial: 38:d5:47:23:80:64 size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.1-4 latency=0 link=yes multicast=yes port=twisted pair promiscuous=yes speed=1Gbit/s resources: irq:46 memory:fb300000-fb31ffff memory:fb336000-fb336fff ioport:f000(size=32) *-network description: Ethernet controller product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:06:00.0 version: 06 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list configuration: driver=vfio-pci latency=0 resources: irq:19 ioport:c000(size=256) memory:d0004000-d0004fff memory:d0000000-d0003fff *-network:0 description: Ethernet interface physical id: 2 logical name: br0 serial: 38:d5:47:23:80:64 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=192.168.1.222 link=yes multicast=yes *-network:1 DISABLED description: Ethernet interface physical id: 3 logical name: virbr0-nic serial: 52:54:00:07:a8:97 size: 10Mbit/s capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=no multicast=yes port=twisted pair speed=10Mbit/s *-network:2 description: Ethernet interface physical id: 4 logical name: vnet1 serial: fe:54:00:36:e8:25 size: 10Mbit/s capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=yes multicast=yes port=twisted pair speed=10Mbit/s *-network:3 DISABLED description: Ethernet interface physical id: 5 logical name: gretap0 capabilities: ethernet physical configuration: broadcast=yes multicast=yes *-network:4 description: Ethernet interface physical id: 6 logical name: virbr0 serial: 52:54:00:07:a8:97 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=192.168.122.1 link=no multicast=yes *-network:5 description: Ethernet interface physical id: 7 logical name: vnet0 serial: fe:54:00:e3:81:fa size: 10Mbit/s capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=yes multicast=yes port=twisted pair speed=10Mbit/s *-network:6 DISABLED description: Ethernet interface physical id: 8 logical name: erspan0 capabilities: ethernet physical configuration: broadcast=yes multicast=yes root@Tower:~# ifconfig -a br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.222 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fd4d:e7fb:46eb:0:3ad5:47ff:fe23:8064 prefixlen 64 scopeid 0x0<global> inet6 fe80::c06c:3cff:fefc:5156 prefixlen 64 scopeid 0x20<link> ether 38:d5:47:23:80:64 txqueuelen 1000 (Ethernet) RX packets 866448 bytes 187508409 (178.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 979578 bytes 1249128328 (1.1 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 erspan0: flags=4098<BROADCAST,MULTICAST> mtu 1450 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 inet6 fe80::3ad5:47ff:fe23:8064 prefixlen 64 scopeid 0x20<link> ether 38:d5:47:23:80:64 txqueuelen 1000 (Ethernet) RX packets 4893058 bytes 3662543084 (3.4 GiB) RX errors 0 dropped 83 overruns 0 frame 0 TX packets 3740252 bytes 1718171974 (1.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xfb300000-fb320000 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1000 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 443988 bytes 188297584 (179.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 443988 bytes 188297584 (179.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sit0: flags=128<NOARP> mtu 1480 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1000 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:07:a8:97 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 52:54:00:07:a8:97 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::fc54:ff:fee3:81fa prefixlen 64 scopeid 0x20<link> ether fe:54:00:e3:81:fa txqueuelen 1000 (Ethernet) RX packets 843319 bytes 199018000 (189.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 751535 bytes 839056856 (800.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::fc54:ff:fe36:e825 prefixlen 64 scopeid 0x20<link> ether fe:54:00:36:e8:25 txqueuelen 1000 (Ethernet) RX packets 4313029 bytes 1900159552 (1.7 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5814744 bytes 4268662816 (3.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@Tower:~# ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1364 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 11: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff 12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff 13: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff 14: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff 15: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:e3:81:fa brd ff:ff:ff:ff:ff:ff 16: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:36:e8:25 brd ff:ff:ff:ff:ff:ff root@Tower:~# 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: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1364 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 11: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff inet6 fe80::3ad5:47ff:fe23:8064/64 scope link valid_lft forever preferred_lft forever 12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff inet 192.168.1.222/24 scope global br0 valid_lft forever preferred_lft forever inet6 fd4d:e7fb:46eb:0:3ad5:47ff:fe23:8064/64 scope global dynamic mngtmpaddr valid_lft forever preferred_lft forever inet6 fe80::c06c:3cff:fefc:5156/64 scope link valid_lft forever preferred_lft forever 13: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 14: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff 15: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000 link/ether fe:54:00:e3:81:fa brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fee3:81fa/64 scope link valid_lft forever preferred_lft forever 16: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000 link/ether fe:54:00:36:e8:25 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe36:e825/64 scope link valid_lft forever preferred_lft forever Quote Link to comment
bonienl Posted March 18, 2018 Share Posted March 18, 2018 Is your eth1 interface using a different driver as eth0? Can you post diagnostics. Quote Link to comment
IpDo Posted March 18, 2018 Author Share Posted March 18, 2018 I guess so, one is Intel and the other is Realtek 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Diagnostics attached. tower-diagnostics-20180318-2203.zip Quote Link to comment
bonienl Posted March 18, 2018 Share Posted March 18, 2018 Something goes wrong with your Intel driver, which causes eth1 not to be present. e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock Perhaps try a different PCI slot. Quote Link to comment
IpDo Posted March 18, 2018 Author Share Posted March 18, 2018 the Intel NIC is the build in one (in the MOBO) and is ETH0. maybe something else? it's only happened from the 6.4 -> 6.5 upgrade. Quote Link to comment
bonienl Posted March 18, 2018 Share Posted March 18, 2018 (edited) No, eth0 is assigned to your realtek. Mar 17 23:06:46 Tower kernel: r8169 0000:06:00.0 eth0: RTL8168e/8111e at 0xffffc90003205000, 74:da:38:a1:35:97, XID 0c200000 IRQ 46 Mar 17 23:06:46 Tower kernel: r8169 0000:06:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] Mar 17 23:06:46 Tower kernel: e1000e 0000:00:19.0 eth1: (PCI Express:2.5GT/s:Width x1) 38:d5:47:23:80:64 Mar 17 23:06:46 Tower kernel: e1000e 0000:00:19.0 eth1: Intel(R) PRO/1000 Network Connection Mar 17 23:06:46 Tower kernel: e1000e 0000:00:19.0 eth1: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF You are correct, later on eth0 gets re-assigned. Edited March 18, 2018 by bonienl Quote Link to comment
bonienl Posted March 18, 2018 Share Posted March 18, 2018 At first eth1 is present. Mar 17 23:07:19 Tower avahi-daemon[17080]: New relevant interface eth1.IPv6 for mDNS. Mar 17 23:07:19 Tower avahi-daemon[17080]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.222. Mar 17 23:07:19 Tower avahi-daemon[17080]: New relevant interface eth1.IPv4 for mDNS. Mar 17 23:07:19 Tower avahi-daemon[17080]: Network interface enumeration completed. Mar 17 23:07:19 Tower avahi-daemon[17080]: Registering new address record for fe80::76da:38ff:fea1:3597 on eth1.*. Mar 17 23:07:19 Tower avahi-daemon[17080]: Registering new address record for 192.168.0.222 on eth1.IPv4. But then removed Mar 17 23:08:49 Tower avahi-daemon[17080]: Interface eth1.IPv6 no longer relevant for mDNS. Mar 17 23:08:49 Tower avahi-daemon[17080]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::76da:38ff:fea1:3597. Mar 17 23:08:49 Tower avahi-daemon[17080]: Interface eth1.IPv4 no longer relevant for mDNS. Mar 17 23:08:49 Tower avahi-daemon[17080]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.222. Mar 17 23:08:49 Tower avahi-daemon[17080]: Withdrawing address record for fe80::76da:38ff:fea1:3597 on eth1. Mar 17 23:08:49 Tower avahi-daemon[17080]: Withdrawing address record for 192.168.0.222 on eth1. No clue why Quote Link to comment
IpDo Posted March 19, 2018 Author Share Posted March 19, 2018 I'll try to exchange the "Interface Rules" in the Network Settings page so that eth0 will be realtek and eth1 is Intel. in a few hours and report back. Anyone have more ideas? Quote Link to comment
bonienl Posted March 19, 2018 Share Posted March 19, 2018 56 minutes ago, IpDo said: Anyone have more ideas? As a test start in safe mode and see if that makes a difference. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.