Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About aim60

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For experimentation, I'm running two Plex dockers (one LinuxServer and one Binhex), using different appdata folders. Since you can't change the port that Plex listens on (38400), I needed to assign a different IP address to one of the dockers. So the Binhex docker is running on Custom:br0, and a fixed IP address. br0 is a Linux bridge, not a Docker bridge, so port mappings are not required. Its like Host mode. I'm still on 6.6.7, but that shouldn't matter.
  2. I believe that within unraid you can only use vlans for dockers and vms. See if you can configure your switchport to send vlan 10 traffic as untagged, while sending the other vlans as tagged.
  3. Make sure all shares are set to COW. Any problem converting the system share containing the docker and libvirt images to COW?
  4. I'm planning on adding a new SSD to my cache pool, and was wondering if and how Unraid users test new SSDs. I give spinners a SMART long test, and 3 Preclear passes.
  5. While testing the "Virtual Machine Wake On Lan" plugin, I discovered that I had two VMs using the same MAC address (sloppy editing of the XML's). It would be useful if Fix Common Problems could scan the docker configs and VM configs for duplicate MACs, and the docker configs for duplicate IP's.
  6. If the interface is connected to a cable modem (not router) or some such device, your upstream provider's first hop is on the same link-local subnet that you are. It seems that the most secure way to run a vm firewall is with a pass-through wan nic.
  7. Testing done with 6.4 RC6, with unRAID and a test client in VM's. Even though an interface is configured for "Network Protocol = IPv4 only", an IPv6 link local address is being assigned to the interface or bridge. This happens if an IPv4 address is assigned, or the interface is configured for "IP Address Assignment=None". The enclosed screenshots show the server Network Settings, an ipconfig, and a Windows client connected to eth1 with no IP addresses assigned. The client can ping the server, access the management GUI, and access server shares, all through the IPv6 Link Local address. This can be a security concern if the interface is Internet facing, with the intent that the bridge will be used for the wan port of a vm firewall . unRAID 6.4 RC6 IPv6.zip
  8. Sure. Watch Gridrunner’s excellent video for background information.
  9. 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 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.
  10. Could be that whatever function call unRAID is using to query the NICS doesn't work in a vm.
  11. 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
  12. 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
  13. 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.
  14. I dont see the Interface Rules option. When I saw that the option was missing
  15. UEFI support makes running unRAID in a vm easier. Prepare the usb key as you normally would, and set the vm bios to ovmf. No need for a disk image of the usb key. I was even able to upgrade from RC4 to RC5 via the plugin. On every boot, I'm dropped into the UEFI shell, and have to kick things off with "fs0:/EFI/boot/bootx64.efi". I added a boot entry using bcfg, but it gets wiped out on boot. Was this by design to keep people out of trouble?