You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to tunnel all my traffic through a specific ssh server using sshuttle
I installed the package via apt-get install sshuttle without issues.
But establishing the connection to the ssh host gives me the following error message: iptables v1.6.0: can't initialize iptables table 'nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
It seems that the Ubuntu inside the WSL does not fully support the iptables commands sshuttle is calling.
Using sshuttle to tunnel traffic through so called jump hosts to access a secured infrastructure network is a common practice in IT administration. Our Linux and Mac users are doing this since a long time. On Windows it was always a pain to use solutions like putty as a dynamic port socks proxy. This anyway only does the job for applications that are able to use a socks proxy but not for command line tools.
It is actually the only thing that is holding back some of my colleagues to change from a Mac to a windows workstation.
The text was updated successfully, but these errors were encountered:
I would like to tunnel all my traffic through a specific ssh server using sshuttle
I installed the package via
apt-get install sshuttle
without issues.But establishing the connection to the ssh host gives me the following error message:
iptables v1.6.0: can't initialize iptables table 'nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
It seems that the Ubuntu inside the WSL does not fully support the iptables commands sshuttle is calling.
Using sshuttle to tunnel traffic through so called jump hosts to access a secured infrastructure network is a common practice in IT administration. Our Linux and Mac users are doing this since a long time. On Windows it was always a pain to use solutions like putty as a dynamic port socks proxy. This anyway only does the job for applications that are able to use a socks proxy but not for command line tools.
It is actually the only thing that is holding back some of my colleagues to change from a Mac to a windows workstation.
The text was updated successfully, but these errors were encountered: