realies
realies
@peacey, any idea how to not leak this DNS traffic on reboot when FORCED_LOCAL_INTERFACE is set to the WAN interface?
@peacey, do you think a firewall rule could filter out this traffic if it's not going on udp.port == 51820?
Somewhat related to #182, I'm trying to limit anything other than the VPN go out of the WANs, and going the FORCED_LOCAL_INTERFACE route, there is still some traffic that goes...
@Unlearned6688, I think the leaking issues can be solved with: https://community.ui.com/questions/Prevent-internal-network-traffic-leaking-when-using-a-WireGuard-VPN-client/b929a88a-6e86-497d-a438-93ec40d9a57a#answer/e777b6e5-0295-4575-971a-0f3211f9baea
@peacey, how can all traffic from everywhere be routed through the VPN, and the only thing coming out of the WAN ports is the VPN?
Is /tmp mounted in the container? What are the permissions of that folder?
Do you still see the issue with the latest update, @ThatzOkay?
@ThatzOkay is this still an issue?
you can check the docs for setting up a vnc password you know; i don't know why it would ask for one based on the network used by the container
could you test with a password that's at least 6 characters long?