http://bugzilla.suse.com/show_bug.cgi?id=916771 Thomas Wagner <wagner-thomas@gmx.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wagner-thomas@gmx | |.at) | --- Comment #3 from Thomas Wagner <wagner-thomas@gmx.at> --- (In reply to Marcus Meissner from comment #2)
what kind of network device does sshuttle create? Apparently, sshuttle does not create a network device. It just manipulates some NAT rules with iptables. Here is the log output of sshuttle's iptables (instead of X.X.X.X the IP of my ssh server appears):
iptables -t nat -N sshuttle-12300 iptables -t nat -F sshuttle-12300 iptables -t nat -I OUTPUT 1 -j sshuttle-12300 iptables -t nat -I PREROUTING 1 -j sshuttle-12300 iptables -t nat -A sshuttle-12300 -j RETURN --dest 127.0.0.0/8 -p tcp iptables -t nat -A sshuttle-12300 -j REDIRECT --dest 0.0.0.0/0 -p tcp --to-ports 12300 -m ttl ! --ttl 42 iptables -t nat -A sshuttle-12300 -j REDIRECT --dest X.X.X.X/32 -p udp --dport 53 --to-ports 12300 -m ttl ! --ttl 42
how does the network setup look afterwards? Sorry, I don't really understand that question. The network setup is simple. One client machine (tested with wlan and ethernet connection of my laptop and a KVM machine) and a ssh server (tested via NAT and on the local network).
-- You are receiving this mail because: You are on the CC list for the bug.