June 22, 20179 yr Looks like support for Interface Rules got dropped somewhere in 6.4. I found it useful. My motherboard has 4 NICS. eth0 and eth1 were physically harder to get to than eth2 and eth3, so I swapped them around. IMHO, if this was done to to reduce clutter in the GUI, its ok to that little-used features are only available by editing files. Edited June 27, 20179 yr by aim60
June 22, 20179 yr Author 1 hour ago, bonienl said: Nothing changed in that department, it is still there... I dont see the Interface Rules option. When I saw that the option was missing
June 22, 20179 yr Author I'm running the RC series in an unRAID vm, but I don't think that matters. I did a clean install of RC4, and Interface Rules was not an option in the GUI. No change after upgrading to RC5. There was no network-rules.cfg in /config, so I brought over a copy from a 6.3.3 system, and edited it to reflect the MAC addresses in the vm. That caused the GUI to show Interface Rules. However, after rebooting RC5, network-rules.cfg was gone. So I assumed that Limetech had removed the feature.
June 22, 20179 yr When there is no interface-rules file, it means unRAID doesn't see the interfaces at startup. Could be due to your VM setup. What is the output of ifconfig -s
June 22, 20179 yr Author Thought it might be related to the NICs being virtio, so I changed them to e1000, but no difference. root@Tower-VM:~# ifconfig -s Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg br0 1500 607 0 0 0 384 0 0 0 BMRU br1 1500 2 0 0 0 32 0 0 0 BMRU eth0 1500 607 242 0 0 499 0 0 0 BMPRU eth1 1500 2 1 0 0 61 0 0 0 BMPRU lo 65536 2 0 0 0 2 0 0 0 LRU
June 22, 20179 yr This shows two interfaces eth0 and eth1, both configured in bridge mode. Not 4 as you mentioned in the OP. Can you post your syslog file, need to see if there is a race condition (see Tools ->System Log). Edited June 22, 20179 yr by bonienl
June 22, 20179 yr Author My physical server has 4 NICs and runs 6.3.3. I'm testing 6.4 RC5 in a vm with 2 nics. The syslog is from the latest boot of the vm. tower-vm-syslog-20170622-1115.zip
June 22, 20179 yr Author 28 minutes ago, bonienl said: When there is no interface-rules file, it means unRAID doesn't see the interfaces at startup Could be that whatever function call unRAID is using to query the NICS doesn't work in a vm.
June 22, 20179 yr Are you saying you run the unRAID VM with 6.4 on top of unRAID 6.3? I suppose you have only one USB device in the system? In that case unRAID 6.4 will get confused because it sees the network-rules.cfg file with 4 interfaces defined, while it has only 2 itself. And likely the VM eth0 and eth1 interfaces are not the same as your bare-metal interfaces. In the syslog all looks okay.
June 22, 20179 yr 8 minutes ago, aim60 said: Could be that whatever function call unRAID is using to query the NICS doesn't work in a vm. It uses udev, don't know if there are any restrictions when running in a VM.
June 22, 20179 yr Author 1 hour ago, bonienl said: Are you saying you run the unRAID VM with 6.4 on top of unRAID 6.3? I'm currently running 6.4 RC5 on top of 6.3. There is a usb key with label UNRAID for the host, and a usb key with label UNRAID-VM for the vm. I am booting the vm in uefi mode. See Quote Since the vm is booted via uefi, there is no disk image of the usb key to confuse things. All unraid files are on the key. 6.4 RC5 syslinux\syslinux.cfg is modified with "append unraidlabel=UNRAID-VM initrd=/bzroot", so as not to have 2 keys with the same label. So the network config of the host and the network config of the vm should be completely separate, with no confusion. If this problem is purely a quirk of running unRAID in a vm, so be it.
Archived
This topic is now archived and is closed to further replies.