Open tbosnjak opened 1 year ago
I've just had a similar issue on Linux using wg-quick (I had no issue before with standard wireguard config with nmcli), I fixed it by not routing all my traffic through wireguard (just needed to specifiy in AllowedIPs the subnets I want to route, including the one where my sshuttle server is).
My setup is as fallows:
sshuttle has no special configuration and it is in version:
I'm using kuberntes pod as bastion and using kuttle
The bastion pod image is alpine based with python version:
The command used to start sshuttle is:
Sudoers is set to allow starting of sshutlle without password.
I can confirm that WireGuard works as expected and sshuttle when there is no WireGurad works as expected. When I connect first to WireGurad and then start sshuttle, dns resolution starts to fail.
I did a quick WireShark check and found out that dns request goes throught the WG interface and dns reply gets back, but the reply doens't get back to lo0 interface.
Just to be transparent, I have no clue about MacOS networking stack.
I checked the following issues, without any success: https://github.com/sshuttle/sshuttle/issues/706 https://github.com/sshuttle/sshuttle/issues/563
I tried to apply the patch proposed in: https://github.com/azolotko/sshuttle/pull/1/files, no luck neither.
Any help will be appreciated.