You are not logged in.
I'm using sshuttle as a poor man vpn to connect to my network that works under ipv4 and ipv6.
IPv4 still works (even after updates). Since the 1rst august, I can't make IPv6 work (but it did before on arch linux).
I can make work IPv6 today with the same command on an other distribution.
Here is the command I use (as explain in the documentation for tproxy method for making udp and ipv6 work) :
sudo ip route add local default dev lo table 100
sudo ip rule add fwmark 0x01 lookup 100
sudo ip -6 route add local default dev lo table 100
sudo ip -6 rule add fwmark 0x01 lookup 100
sudo sshuttle --listen 127.0.0.1:0,[::1]:0 --dns --auto-hosts --method=tproxy -t 0x01 -e ssh -4 -p 22 -J <first server>:22 -r <second server> 10.10.10.0/24 ::/0Have you got any idea on updates (kernel or other) that could impact iptable mangle or python version that sshuttle is using ?
Thanks in advance.
Thomas
Last edited by retzs64 (2023-08-10 16:08:15)
Offline
After some more tests, the host os has to have a default ipv6 route (any ips will make it work).
I don't know what changed in the network configuration after the updates but it might have remove the creation of the gateway.
The way sshuttle make it work is a little bit dirty, although I'm not sure if there is an other solution.
Maybe make sshuttle create the default ipv6 gateway if there is no ip.
Offline