Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About tbrasser

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Dear unRAID community, I've been running unRAID for a few years now, and most of the time, everything works as expected. However, I keep having weird DNS issues when I'm trying to route all my internet traffic through a VPN using my (opnsense) router. My reverse proxy setup works fine (always), but seemingly at random I fail to resolve domainnames from containers / the unraid host / sometimes other devices on the network. I've been reading up on the Docker custom networks and how it works internally, however, I've been unable to get it to work. Current situation: public-ip-->[ISP Modem/Router][OPNSense Router] of my network (unRAID server, WIFI-AP's, Switches etc) The OPNSense router is in the DMZ of my ISP-provided box (that I unfortunately can't put into bridge mode) I have allowed private IP ranges on WAN on my OPNSense router I have set and as the only DNS in the OPNSense router, this is what all clients get via the DHCP server that is running on the LAN interface. I have disabled any type of DNS resolver/forwarder for now. This DHCP server gives out adresses from till I have 2 interfaces in my unRAID box, eth0 and eth1, I have configured unRAID as follows: eth0 has the ip via DHCP (static lease), bridging is disabled eth1 has no ip, bridging is enabled (br1) Docker custom network on br1 is, default gateway, no DHCP. I spin up every docker container with a specific IP on br1 (between and and I provide the --dns= flag. The problem I keep facing, and the reason I went and configured everything as above, is that whenever I make changes on how devices on my network access the internet (over VPN or not etc) I get weird DNS issues, either my unRAID host can't ping google.com, or my docker containers are unable to resolve domainnames. What I'd want ideally: I can't begin this list without stating that I'm trying to get rid of this DMZ / double-NAT situation, it sucks. I want a simple network (for a start, can do vlans later for iot/guest things) All devices on my network should be able to resolve internal and external domains. I like my current setup of using my /24 subnet as follows: .1 for the default gateway, .2-.63 for static leases, .64-.127 for dynamic leases, .128 and above for docker containers running on the unRAID host. Here are some screenshots and outputs of various commands: - unraid gui settings related to networking and docker - opnsense gui settings related to dns/dhcp and overview - ping and dns results from my laptop ( - ping and dns results from the unraid host ( - ping and dns results from a container started with --dns= on br1 with ip Can someone help me debug this? I haven't been able to get a stable network for ages now, and I have no clue what I'm doing wrong. server-diagnostics-20181027-1759.zip
  2. 1. Pinging my router works fine: root@Server:~# ping PING ( 56(84) bytes of data. 64 bytes from icmp_seq=1 ttl=64 time=0.255 ms 64 bytes from icmp_seq=2 ttl=64 time=0.294 ms 64 bytes from icmp_seq=3 ttl=64 time=0.143 ms 64 bytes from icmp_seq=4 ttl=64 time=0.202 ms ^C --- ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3095ms rtt min/avg/max/mdev = 0.143/0.223/0.294/0.058 ms 2. Oh yeah, it's still on a /24 subnet, the /25 is the DHCP pool for the br0 docker network: Subnet: Gateway: DHCP pool: (128 hosts) Can't ping google's DNS servers either. However while typing this comment I took a look at my pfsense config again, and found that the only thing different between the unraid server and the laptop I'm typing this comment on now is that I've had my laptop configured to go through an openVPN interface, I just tried to add the unraid server to that alias list and now it's connecting again. weird. So it's safe to say that the problem is not at the server, it's in my router config. Thanks for the reactions anyway, I'll be reconfiguring my router/firewall now to tackle the problem.
  3. My unRAID server can't access the internet. I've searched the forums & checked my network but I can't find anything wrong. Pinging google / github / etc from console doesn't work. I run a physical pfSense router, which runs a DNS (I use dnsmasq blocking, but have that disabled to rule out that that was the problem, backend DNS is ) Pfsense box: LAN: DHCP pool: unRAID server: docker network: This started happening after I updated my pfsense firmware, but no other devices on my network seem to have any issues. Diagnostics are attached if anyone wants to take a look, hopefully it's something simple I've overlooked. server-diagnostics-20180805-1511.zip
  4. Issue 43 is a windows nvidia driver issue as far as I know, I'm beginning to agree with methanoid, this is no slowchat, this is a (support) forum. The issues that you observe can all reasonably be due to the error 43, so first resolve that before posting general 'nothing is working' posts. Have you isolated cpu's from the host? Have you pinned cpu's to the guest? etc etc etc
  5. https://www.youtube.com/channel/UCZDfnUn74N0WeAPvMqTOrtA I don't know if it also works when you boot unraid in GUI mode, I'd advice the non-gui boot. And then just access the webinterface from another computer / laptop / whatever.
  6. you can dump the bios from the unraid command line as per the video's instructions. Works for me, I passthrough my gtx 970 to windows VM and its the only graphics adapter that is installed.
  7. Also, with looking glass, you'd still need to pass through an entire gpu to a VM (for example windows), what you'd then could do (not with unRAID as jonathanm correctly pointed out) with a linux host is have the framebuffer of the windows gpu copied to the frame buffer of your linux host so you get a kind of picture-in-picture, and you only need 1 cable.
  8. You can now also input the location to the rom file via the unraid web gui (since latest 6.5.0 version), this way you dont need to edit your xml file with the address manually.
  9. I narrowed it down to my /var filling up with syslogs. Turned out my VM setup with primary nvidia passtrhough is giving me BARs warnings continuesly. Not starting any VM's on boot made everything work again. So it didn't have anything to do with this plugin in the end, got LibreElec 6.5.0 running now! Thanks for the help anyway, and if someone knows how to stop uninteresting log entries from filling up the partition (or is familiar with the type of error I got, posted in the 6.5.0 release thread) feel free to post it (A)
  10. Thanks, I just found it as well. Not sure what is causing it, any ideas on where to look for? So after some googling I didn't get much wiser other than that those log entries don't indicate anything serious. However they do fill up my /var .... It seems to be a result of my NVIDIA GTX 970 + Some linux kernel changes that have happened in the past. To pass through my gpu (it's the only one I have) I use an extracted bios that since 6.5 I can point to without modifyin the xml. I have 1 VM on autostart which probably resulted in above spamming in the logs. I can confirm that if I don't start any VM I don't get these log entries, and everything is functioning like it normally would. However I would like to start VM's with my GPU without getting this behaviour. Is there any way I can reduce the logging or any other fix?
  11. I'm not sure whether I'm posting in the correct thread. But I've started noticing these issues when trying to upgrade from 6.5.0-rc to 6.5.0 (DVB edition, but now I'm on 6.5.0 stock). I can't seem to install (some) plugins, I get tar errors. I think I've narrowed it down to the fact that my /var is full? Can someone take a look at my diagnostics to see if that's whats the problem. (and if it is, how can I correct it)? I've also posted in the unraidDVB thread, but I don't think my problem is specific to that plugin. (I've also had CA failed to install after I noticed my APPS tab was missing, however it showed back up on 6.5.0 stock) server-diagnostics-20180315-1617.zip
  12. I was on 6.5.0-rc6 and when I wanted to upgrade to 6.5.0 weird things started happening. Initially I got an error on the DVB plugin page. So I tried to uninstall the plugin which said it wasn't installed in the first place. Then I tried installing it (again), but I got errors when it tried to extract the tar file (errorcode 2). What I did is upgrade to 6.5.0 stock using the normal upgrade path. And after that I tried installing the plugin again. Same error: plugin: installing: https://raw.githubusercontent.com/linuxserver/Unraid-DVB-Plugin/master/plugins/UnraidDVB.plg plugin: downloading https://raw.githubusercontent.com/linuxserver/Unraid-DVB-Plugin/master/plugins/UnraidDVB.plg plugin: downloading: https://raw.githubusercontent.com/linuxserver/Unraid-DVB-Plugin/master/plugins/UnraidDVB.plg ... done plugin: downloading: https://raw.github.com/linuxserver/Unraid-DVB-Plugin/master/archive/UnraidDVB-2018.03.14.txz ... done +============================================================================== | Installing new package /boot/config/plugins/UnraidDVB/UnraidDVB-2018.03.14.txz +============================================================================== Verifying package UnraidDVB-2018.03.14.txz. Unable to install /boot/config/plugins/UnraidDVB/UnraidDVB-2018.03.14.txz: tar archive is corrupt (tar returned error code 2) ---------------------------------------------------- UnraidDVB has been installed. CHBMB/Squid Version: 2018.03.14 ---------------------------------------------------- plugin: installed Is there anything I can do to fix this. Before the upgrade I had the same issues with CA, the apps tab was not showing anymore (6.5.0-rc6) but it now is back on 6.5.0.. Here's a screenshot of me uninstalling the plugin after it failed to correctly install:
  13. I'm eager to try it. Got a used dell T7500 and got some 8TB HDD's and 2 SSD's show up. But I'm wondering at wat speed they're connected.
  14. I'm in the same boat as everyone here (old thread). However the USB Key is not just an installer / license drive. It's what actually boots when you start unRAID so that all your physical drives (SSD's for cache , HDD's for storage) are available for usage. unRAID runs mostly from ram so your drive doesn't see many writes. Having said that, writeable diskimage on the lime-tech website would be friendlier than zip files, so that we can use etcher or other tools to simply prepare our USB boot device from any platform.