So, after finding two commands which allowed my containers to correctly discern my client's IP addresses:
This then breaks my LAN access to a couple of containers which use a VPN to access the network/internet - VPN compose snip:
I have a container on the docker "synology" network which has firefox inside and I can access jackett and qbittorrent from that, however I cannot access them from my desktop.
After rebooting the NAS I can no longer discern my client IP addresses but can once again access those two containers so I know it's something to do with the command.
Does anyone have any ideas what's going wrong?
Code:
https://www.pedrolamas.com/2020/11/04/exposing-the-client-ips-to-docker-containers-on-synology-nas/
sudo iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
sudo iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER
Code:
privoxy:
image: binhex/arch-privoxyvpn:latest
container_name: privoxy
cap_add:
- NET_ADMIN
ports:
- 8118:8118
- 9118:9118
- 9117:9117 #jackett
- 9080:9080 #qbittorrent
volumes:
- "${SSD}privoxy:/config"
- '/etc/localtime:/etc/localtime:ro'
environment:
- VPN_ENABLED=yes
- VPN_USER=${NEWVPNUSER}
- VPN_PASS=${NEWVPNPASS}
- VPN_PROV=custom
- VPN_CLIENT=openvpn
- LAN_NETWORK=192.168.0.0/24
- SOCKS_USER=${ITSME}
- SOCKS_PASS=${MYCOMPASS}
- ENABLE_SOCKS=yes
- ENABLE_PRIVOXY=yes
- TZ=${TZ}
networks:
- synology
restart: always
I have a container on the docker "synology" network which has firefox inside and I can access jackett and qbittorrent from that, however I cannot access them from my desktop.
After rebooting the NAS I can no longer discern my client IP addresses but can once again access those two containers so I know it's something to do with the command.
Does anyone have any ideas what's going wrong?