hdlineage

Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

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

hdlineage's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Need a way to disable the notification. Thanks.
  2. I am impressed by the work you put in to find the problem and provide a working solution. Thank you for the effort, and yes I agree this should be included in future releases. I believe this is an important feature as some services need to be run on multiple different networks (Apple home kit for example).
  3. Hello, I'm currently using Home Assistant docker connected to two networks: one is custom created (using docker network create), the other one is br0 (my Lan network). I found that if a second network is connected to the docker (using docker network connect), on unraid reboot or even just turning off and on the unraid docker daemon the container will not auto-start. When trying to start the container manually I get the error message "No such container." The only way to fix it is by a force image update or by editing/updating the container config (so that a new container is created).
  4. BUG found, I have two wg interfaces wg0 and wg1 wg0 is set to no server NAT, thus thus no associated firewall rules are set on pre-up and post-down wg1 is set to enable server NAT After unraid reboots wg1 will fail to start due to non existent WIREGUARD chain in iptables. I have to manually add WIREGUARD chain to start the wg1 interface.
  5. I think I know exactly what is happening here. If there is no port mapping that binds from the container to host, the web ui link doesn't show. I have a custom bridge network that doesn't require port mapping, and WEB UI link doesn't show no matter what I put in the WEBUI field. As soon as I map even one port to host the webui appears. It's kind of annoying, is there a way to force WEB UI link setting?
  6. Feature request: Allow users to configure custom PostUp and PostDown scripts. I have some iptables rules I want to use, but it gets overwritten everytime I change the config through GUI. Would be nice to have a field where we can use it in the GUI.
  7. Thanks for your help. We have very similar config except I have the unraid on the vlan as well. Turns out it was the two interfaces that's causing trouble. Somehow if unraid has an interface that is on the same subnet/vlan as docker, you can't access docker no matter what. For me it doesn't really matter where unraid is, but I do wonder if there is a way to for unraid to be on the same subnet as docker.
  8. Can you share your setup including how you configured the unraid VLAN? My unraid has two interfaces: br0 with subnet 192.168.1.0/24 (unraid host ip: 192.168.1.10) gateway(router) 192.168.1.1 br0.100 (vlan) with subnet 192.168.100.0/24 (unraid host ip: 192.168.100.10) gateway(router) 192.168.100.1 My VM and docker uses br0.100 with subnet 192.168.100.0/24 I configured wireguard to use the subnet 192.168.150.0/24 My router is configured with static route to all the subnets listed above. Whenever I'm connected via unraid wireguard I can access everything except docker (I can connect to VM on the same subnet) When routing Wireguard traffic back to unraid I could only use 192.168.100.10 but not 192.168.1.10 (this is weird since I could access unraid GUI through both IP which means the two interfaces were working normally, maybe wireguard pick one interface to listen on?) With this setup I could not access docker on the 192.168.100.0/24, but was able to access VM on the same subnet. However, when i connect to wireguard installed on the VM, there is no problem at all.
  9. After two days of trying the unraid implementation of wireguard, here is my summary of what works and what doesn't work: 1. Simple connection (if you dont have any vlan or vlan interfaces on unraid) between unraid sever and windows client works in "Lan mode" and "Tunnel mode" 2. Even when routed properly on router, if your docker is on a separate subnet (ie vlan), you will still be blocked, however, VM on a different vlan can be reached 3. Windows client currently only supports one connection/interface at a time, there is a workaround to add more interface but is not elegant. Not being able to reach docker on a different subnet was the deal breaker for me, so I stopped using unraid for wireguard. When wireguard is installed on a VM it works perfectly, you can reach everything including docker on a vlan. Edit: turns out it was vlan/docker setting issue, see below
  10. Multiple interfaces/connections on Windows client. Hello I have a question regarding connecting to multiple servers on Windows. The wireguard client on Windows only allows one connection at a time. Is there a way to establish two connections with two separate interfaces? I have two servers on two different subnets and I can't seem to find a way to connect them simultaneously. There is also very little documentation on the windows client.
  11. Hello I have a question regarding connecting to multiple servers on Windows. The wireguard client on Windows only allows one connection at a time. Is there a way to establish two connections with two separate interfaces? I have two servers on two different subnets and I can't seem to find a way to connect them simultaneously. There is also very little documentation on the windows client.