rayun56

Hey all, gonna start out by saying I really appreciate the work you all have done with the binhex apps. I'm trying to use a wireguard VPN to work while I have a seperate UNRAID wireguard tunnel. Essentially, I have a wireguard tunnel set up called wg1 that allows 12 or so peers to connect to the unraid server, and can connect to each other. That wireguard config has the following iptables commands in it: [Interface] #wg1 PrivateKey=[key] Address=172.17.0.1 ListenPort=51821 PostUp=logger -t wireguard 'Tunnel WireGuard-wg1 started';/usr/local/emhttp/webGui/scripts/update_services PostDown=logger -t wireguard 'Tunnel WireGuard-wg1 stopped';/usr/local/emhttp/webGui/scripts/update_services PostUp=ip -4 route flush table 201 PostUp=ip -4 route add default via 172.17.0.1 dev wg1 table 201 PostUp=ip -4 route add 192.168.1.0/24 via 192.168.1.1 dev br0 table 201 PostDown=ip -4 route flush table 201 PostDown=ip -4 route add unreachable default table 201 PostDown=ip -4 route add 192.168.1.0/24 via 192.168.1.1 dev br0 table 201 [Peer] [Peers omitted] Now when using the binhex-qbittorrentvpn container, I can set the network to "Bridge", however it is not able to access the internet from that mode. I suspect that it is attempting to use this wireguard tunnel to access the internet. I can set the network to "Custom : br0", from that point it can access the internet and seems to start up properly, however I am unable to access the webui. If I disable the wireguard interface and set the network to "bridge", qbittorrent and the webui work flawlessley. I have been scratching my head trying to figure this out for a while. Essentially I just want UNRAID's wireguard tunnel to only allow peers to connect to the server and each other, but the server does not need to access the peers in any way, and I certainly don't want any docker containers using this network. I appreciate any help, and I can post more information if it is needed.