Is your feature request related to a problem? Please describe.
When trying to use the agent from the compromised machine and it's connected to the subnet that trying to access.
i.e ( If we're connecting to 192.168.0.5 and trying to forward 192.168.0.0/24), this generates the connection to die or not subnet accessible.
Describe the solution you'd like
add exclusion for host(s) or subnet(s) from forward
Describe alternatives you've considered
add manually a route to exclude compromised host to go through ligolo interface , it seems to work but if I tried to add a second forward can't reach ligolo proxy.
Is your feature request related to a problem? Please describe. When trying to use the agent from the compromised machine and it's connected to the subnet that trying to access. i.e ( If we're connecting to 192.168.0.5 and trying to forward 192.168.0.0/24), this generates the connection to die or not subnet accessible.
Describe the solution you'd like add exclusion for host(s) or subnet(s) from forward
Describe alternatives you've considered add manually a route to exclude compromised host to go through ligolo interface , it seems to work but if I tried to add a second forward can't reach ligolo proxy.
Additional context sshutle uses flag -x to exclude host/subnet more info https://sshuttle.readthedocs.io/en/stable/manpage.html#cmdoption-sshuttle-x keep in mind that also connected through a VPN ( can replicate it on the free Wreath room from THM https://tryhackme.com/r/room/wreath)
Cheers Nico for amazing tool ;)