ed_dantes

Well, I ended up solving it. Just in case anyone else runs into this issue, it turns out I had a rogue pass rule for the VLAN interface. Even though my first rule should have passed to the VPN, the existence of another pass all rule was providing it a workaround.

Hoping someone may be able to help me with some troubleshooting. I've looked through a bunch of guides and got pieces of this to work, but can't get it all working together. I currently am running an unraid server, with a pfsense box as my router/firewall. I'd like to have one unraid VM routed out over a VPN using VLANs. I can get the following pieces to work: 1) Route all traffic out of Unraid over VPN with appropriate rules in pfsense. 2) Enable VLANs on br0.10 with a VLAN interface on pfsense, so the VM pulls the appropriate IP for the VLAN and maintains all connectivity to internet and local network. However, as soon as I enable the VLANs, it "breaks" the VPN tunnel. I still have connectivity on all devices (unraid server and VM), but the traffic is now being routed over the WAN with my ISP IP, not the VPN. I'm guessing that somehow I'm not isolating the VLAN appropriately, and there's a route over br0 out through the WAN. Problem is that I'm not sure how to pinpoint the issue.

Hi, Just had a question that I've been messing around with for the past few days and can't get it to work. I've searched the forum, and while I've found related questions, nothing specific. I'm running Unraid 6.5.3, and I'm trying to route docker traffic (xteve) through the the binhex-delugevpn client. I can get this to work by setting the network to "none" in the xteve docker and adding "--net=container:binhex-delugevpn" to the extra parameters. This works without issue, as when I query the IP from within the xteve console, it returns the VPN IP. My problem however is retaining access to the WebUI/ports of the xteve docker. I have found reference elsewhere (https://github.com/dperson/openvpn-client/blob/master/README.md) to using this methodology, but then setting up a nginx proxy to retain access ports. For the life of me, however, I can't figure out how to get this to work. I have installed the nginx docker, but it won't start as there are port conflicts. Even if I could get it to start, I'm still fairly unclear as to what I actually need to do. I'm at kind of a loss, and any help would be greatly appreciated. Thanks!

Ok, thanks.Tried to save some hardware and money by integrating the tuner into the unraid box but seems like it may just be easier to go with something like the HDHomeRun Connect.

Hey, just about 6 months in to my first unraid build and couldn't be happier. However, just decided to add a TV tuner, and ended up with the Hauppauge (1595) WinTV-dualHD. At first, I this this would not be a problem with the libelec drivers, but as it turns out, I can't get tvheadend to recognize the tuner after I've installed the DVB plugin (Unraid 6.3.2). The status page on the DVB plugin shows that the DVB kernel is installed with libreelec 1.21 drivers. However, the adapter driver is not found. Following Hauppage's instructions for Ubuntu, I have been able to get things working in an Ubuntu VM on the unraid server. As it turns out, this version of the Hauppauge tuner is only natively supported in kernel 4.11 per the LinuxTV wiki. However, it does appear that there areways to patch these drivers into previous kernels. Unfortunately, that goes beyond my skillset. Would it be possible to have these drivers integrated? Or any chance someone might be able to provide some direction on how to do it myself? Thanks!